Whiplash settlement value guide for Missouri

Direct answer

In Missouri, the ultimate value of a whiplash injury settlement is often driven by how comparative fault is allocated. Under Mo. Rev. Stat. § 537.067, the claimant’s share of fault reduces the portion of damages that translates into expected recovery.

DocketMath helps you turn that rule into settlement-value math by letting you compare settlement demand to allocated recovery under a Missouri (US-MO) workflow.

What you need to know

Missouri’s allocation structure matters more than the label “whiplash.” Even when the case is described as a rear-end collision with neck/soft-tissue complaints, the net settlement value depends on:

• Whether fault is shared between the claimant and others
• How fault is apportioned (the percentages assigned to each party)
• Whether any threshold behavior applies to how joint-and-several style allocation is handled in the model

DocketMath’s “jurisdiction-aware” approach for US-MO is designed to apply the comparative-fault framework associated with Mo. Rev. Stat. § 537.067 when you run a damages-allocation analysis.

What inputs drive the output in DocketMath (US-MO)

In the damages-allocation workflow, you typically supply:

• Total claimed damages (your modeled “total damages pool,” including the economic and non-economic components you want to test)
• Fault allocation percentages you expect to be assigned (often including claimant fault, plus any other parties’ fault)

DocketMath then computes what fraction of the modeled damages remains after applying the Missouri allocation logic, so you can estimate allocated recoveries for settlement planning.

Step-by-step

Use this workflow to estimate how a Missouri whiplash settlement value can change after comparative-fault allocation, using DocketMath.

1) Gather your damages “before allocation” number

Start with one figure representing the total damages pool you want to model.

Common categories teams include (as part of the pool) are:

• Medical expense totals (treatments and follow-ups)
• Wage-loss totals (if included in your model)
• Non-economic damages modeling (e.g., pain and suffering)

Keep it as a single total pool for the allocation run so you’re not accidentally introducing inconsistencies.

2) Choose a fault allocation scenario (at least two)

Because allocation outcomes can swing, test multiple plausible fault scenarios rather than relying on a single assumption.

For example:

• Scenario A (lower claimant fault): claimant fault at a realistic lower percentage
• Scenario B (higher claimant fault): claimant fault at a realistic higher percentage
• If more than one defendant exists: split the remaining fault among them according to your theory

DocketMath uses your percentages as inputs to estimate allocated recoveries.

3) Apply Missouri’s comparative-fault rule using the US-MO workflow

In DocketMath, use the jurisdiction-aware damages allocation tool:

• Open: /tools/damages-allocation
• Select Missouri (US-MO) so the tool applies the allocation logic tied to Mo. Rev. Stat. § 537.067

4) Pay attention to any allocation threshold logic

Missouri allocation math in the DocketMath Missouri setup includes threshold behavior for joint-and-several style logic, including:

• 51% joint-and-several sub-rule threshold

That means if your modeled fault reaches the threshold behavior logic, the output can change materially compared to scenarios below it.

5) Compare settlement demand to “allocated” expected recovery

Once DocketMath outputs an allocated recovery percentage, compute an expected recovery amount by multiplying your damages pool by the allocated recovery fraction:

• Expected recovery ($) = Total damages pool × Allocated recovery %

Then compare your settlement demand to that expected recovery to evaluate leverage and negotiation posture.

Key statutes and citations

Missouri’s comparative-fault allocation is anchored in:

• Mo. Rev. Stat. § 537.067
  Provides Missouri’s comparative fault approach and directs how fault reduction operates when negligence contributed to the harm.
• Mo. Rev. Stat. § 537.067.1
  Additional details within the same comparative-fault allocation framework that can affect how comparative fault is implemented.

The Missouri Supreme Court’s decision:

• Gustafson v. Benda, 661 S.W.2d 11 (Mo. banc 1983)
  Adopted pure comparative fault, meaning recovery may be reduced based on claimant fault rather than being automatically barred in all situations.

Related provisions also listed in the packet for comparative-fault context:

• Mo. Rev. Stat. § 537.765 and Mo. Rev. Stat. § 537.765.2
  These can be relevant depending on the legal theory and whether the scenario involves the packet’s permitted products-liability comparative-fault framing.

Common pitfalls

Many whiplash settlement mis-estimates come from avoidable modeling errors when translating fault allocation into damages outcomes. Use these checks while running US-MO in DocketMath:

• Mixing fault percentages with damage amounts
  Fault percentages belong to allocation; damage amounts belong to the damages pool. Enter them in the correct fields.

• Forgetting the comparative-fault reduction effect
  Even with credible injury and treatment documentation, claimant fault under Mo. Rev. Stat. § 537.067 can reduce expected recovery.

• Running only one scenario
  Fault allocation is uncertain. If you test only a “best case,” your settlement evaluation can be overly optimistic.

• Ignoring threshold behavior
  DocketMath’s Missouri settings include the 51% joint-and-several sub-rule logic. If a scenario hits or crosses that threshold behavior, the output may jump compared to nearby fault percentages.

• Double-counting damages
  Don’t count the same category twice. For example, if medical expenses are included inside your single total pool, don’t also add them again as a separate line item before running allocation.

Run the numbers

Here’s a compact, actionable way to sanity-check your DocketMath output for Missouri whiplash allocation.

Allocation checklist (before you finalize a settlement range)

• I entered a single total damages pool (economic + non-economic as I intend to model it)
• I entered fault percentages that sum to 100% across all relevant parties in the model
• I ran at least two scenarios (e.g., lower vs. higher claimant fault)
• I checked whether my modeled claimant fault crosses the 51% joint-and-several threshold logic (if applicable in the scenario)

Scenario comparison template (use your DocketMath outputs)

Interpreting the swing

If increasing claimant fault from one scenario to another materially reduces the allocated recovery, that’s not automatically a calculation mistake—it reflects the comparative-fault reduction approach under Mo. Rev. Stat. § 537.067 and the pure comparative fault framework recognized in Gustafson v. Benda.

If the change is most pronounced at 51%+, that aligns with the 51% threshold behavior used in the DocketMath Missouri settings for joint-and-several style logic.

Related reading

• How to calculate Damages Allocation in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Damages Allocation in Philippines — Worked example with real statute citations
• Inputs you need for Damages Allocation in Philippines — Input checklist with sourcing guidance