Workers compensation settlement guide for Missouri

Direct answer

In Missouri, comparative-fault allocation mechanics are governed by Mo. Rev. Stat. § 537.067. For settlement allocation math, the practical result is that you’ll typically allocate a specified damages pool across parties using fault percentages, and then run those inputs through DocketMath’s jurisdiction-aware workflow for US-MO.

If your scenario uses DocketMath’s “joint and several” allocation mechanics, the Missouri configuration includes a 51% threshold: once a party’s fault percentage reaches or exceeds the configured threshold, it can change how the allocation responsibilities are modeled in the tool.

What you need to know

DocketMath’s damages-allocation tool is designed to help you consistently apply jurisdiction-aware allocation logic. For Missouri (US-MO), the model is anchored to the comparative-fault concept in Mo. Rev. Stat. § 537.067.

Before you calculate, you should understand three things:

1. Your starting point is a damages pool to allocate

   • The calculator does not “figure out” damages. You provide the total figure you want allocated.

2. You provide fault percentages by party

   • The comparative-fault premise means the allocation shares move based on how the factfinder-related fault percentages are assigned.

3. The Missouri “joint and several” mechanic uses a 51% threshold

   • For certain “joint and several” allocation mechanics inside the tool, Missouri uses a 51% threshold (verified configuration).
   • A shift from just below the threshold to at/above the threshold can materially change outcomes—so you’ll want to model both the base case and any threshold-sensitive scenario.

How this shows up in settlement discussions

Settlement packages often require answers like:

• “What portion of the damages pool is attributable to each party’s fault?”
• “How sensitive is the allocation to disputed fault percentages?”
• “If fault is close to the 51% line, what changes once it crosses that point?”

DocketMath helps you turn those questions into repeatable, math-consistent allocation outputs.

Step-by-step

Use this workflow to run Missouri damages allocation in DocketMath and produce settlement-ready numbers.

1) Confirm your Missouri comparative-fault basis

Start with the legal and conceptual foundation that informs the allocation method:

• Mo. Rev. Stat. § 537.067 (primary comparative-fault allocation provision for this guide)
• Gustafson v. Benda, 661 S.W.2d 11 (Mo. banc 1983) (adopting pure comparative fault)

This matters because allocation results depend on the “fault-based sharing” premise rather than an all-or-nothing model.

2) Gather the allocation inputs

At minimum, DocketMath needs:

• Total damages pool (the number you will allocate)
• Fault percentages for each party you want included in the allocation

If your settlement modeling uses the “joint and several” mechanic within the tool, you should also ensure you’re using the correct DocketMath options for Missouri, since the tool’s Missouri configuration includes a 51% threshold.

3) Enter inputs in DocketMath

Open the calculator at: /tools/damages-allocation

Then:

1. Select Missouri (US-MO) (jurisdiction-aware mode).
2. Enter the damages pool.
3. Enter each party’s fault percentage.
4. If applicable, configure the scenario so the tool applies the Missouri “joint and several” mechanics correctly (including the 51% threshold behavior).

4) Review the allocation output

When you run the numbers, double-check:

• The parties listed match your intended scenario.
• The fault percentages are what you meant to model.
• The output reflects the correct allocation mechanic for the scenario (especially if any party is near the 51% threshold).

Because this is settlement math, small input changes can create big output changes—so verify both the numbers and the assumptions.

5) Stress-test assumptions (threshold and sensitivity runs)

To make your settlement allocation package easier to defend and easier to explain, run at least two versions:

• Base case run: your best estimate of fault percentages
• Threshold-impact run: adjust inputs to test whether any party crosses the 51% line

Example approach (conceptual):

• Keep the damages pool constant.
• Re-run allocation after shifting one party’s fault up or down enough to test whether the 51% threshold changes the tool’s allocation behavior.

This creates a clear record of how contested facts affect allocation.

Key statutes and citations

This guide’s Missouri damages-allocation workflow is anchored to:

• Mo. Rev. Stat. § 537.067 — comparative-fault allocation mechanics (primary source for this guide)
• Gustafson v. Benda, 661 S.W.2d 11 (Mo. banc 1983) — adopting pure comparative fault

Common pitfalls

Avoid these common errors when preparing Missouri settlement allocation math:

• Assuming the wrong fault framework

  • If your spreadsheet or assumptions treat fault as all-or-nothing, the math may conflict with the pure comparative fault premise reflected in Mo. Rev. Stat. § 537.067 and the approach in Gustafson v. Benda.

• Ignoring the “51% threshold” behavior

  • Missouri’s DocketMath configuration includes a 51% threshold for the relevant “joint and several” mechanics.
  • Inputs around the 50% → 51% change can lead to sharply different allocation outcomes.

• Changing party lists between runs

  • If you add or remove parties between the base-case run and the sensitivity run, your comparison won’t isolate the effect of disputed fault percentages.
  • Keep the parties consistent when testing sensitivity.

• Mixing separate damages concepts into one allocation pool

  • DocketMath allocates based on the damages pool you enter.
  • If you’re using different assumptions for different damages categories, run separate allocation pools so the math stays internally consistent.

• Over-trusting a single iteration

  • Settlement discussions often turn on disputed numbers.
  • At minimum, run your base case and a threshold-impact scenario so you can explain how outcomes move.

Run the numbers

Use DocketMath’s damages-allocation calculator to generate allocation outputs for Missouri.

Quick checklist before you click calculate

• You selected Missouri (US-MO)
• You entered the total damages pool you want allocated
• You entered fault percentages for each party
• If “joint and several” mechanics are relevant in your model, you accounted for the Missouri 51% threshold behavior
• You reviewed the output for internal consistency (party list + fault inputs)

What to look for in the output

Because the allocation is comparative-fault-driven under Mo. Rev. Stat. § 537.067, outputs typically change as fault percentages shift. In particular:

• If any party’s fault crosses the 51% threshold, allocation results may change materially compared to a scenario just below that line.
• If fault is redistributed while keeping the damages pool constant, each party’s share of the allocated damages will move accordingly.

Practical workflow for settlement-ready numbers

To keep your settlement math clear:

1. Run Base Case (your current fault assignments)
2. Run Threshold Impact (test whether any party crosses 51%)
3. Document the input deltas (what changed in fault percentages) and the corresponding output deltas

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