How to calculate Damages Allocation in Missouri

Quick takeaways

• In Missouri, damages allocation is driven by comparative fault concepts—so start with (1) the total damages and (2) each actor’s fault percentage. See Mo. Rev. Stat. § 537.067.
• This Missouri tool includes a joint-allocation threshold effect tied to the claimant: when the claimant is found more than 51% at fault, the allocation outcome can change. The key threshold used here is 51%.
• Use DocketMath’s damages-allocation calculator to turn your entered percentages and damages into an allocation-by-party result and a claimant impact output, using a consistent workflow.
• Keep runs versioned: if you amend allegations, update witnesses, or revise fault opinions, rerun DocketMath because even modest percentage changes can shift the allocation—especially around the 51% point.

Inputs you need

Before you open DocketMath’s damages-allocation tool, collect the numbers that will map directly to the calculator’s fault-and-damages inputs.

A. Core case numbers

• Total damages to allocate (the “pool” to be split)
• Fault percentages for each relevant actor

  • Defendant A: ___%
  • Defendant B: ___%
  • Any other liable party: ___%
• Claimant’s fault percentage (when you’re evaluating allocation effects that depend on claimant fault)

B. Jurisdiction-aware allocation settings

• Select the Missouri (US-MO) jurisdiction profile in DocketMath so the calculator applies Mo. Rev. Stat. § 537.067 rules.
• Confirm whether your scenario requires checking the joint-allocation threshold logic for claimant fault:

  • If claimant fault is greater than 51%, the statute-backed allocation effect is triggered (threshold value used: 51).

C. Sanity-check inputs (recommended)

These checks reduce avoidable mistakes before you rely on the output:

• Make sure the fault percentages align with the allocation universe you intend to model (i.e., the same parties you want reflected in the allocation result).
• Ensure your total damages figure is the same “basis” you intend to allocate (for example, the same compensatory-damages pool you’re discussing in pleadings or settlement).
• Confirm rounding: the logic described here turns on “greater than 51%”, so 51.00% vs. 51.01% can matter for the mode the calculator uses.

How the calculation works

Use this workflow to understand what the DocketMath output is doing in Missouri (US-MO) under Mo. Rev. Stat. § 537.067. (This is a practical translation of the statute-backed structure into calculation steps—always interpret results in context.)

Step 1: Enter the total damages (the base “pie”)

• In DocketMath, input your total damages to allocate.
• The calculator treats this as the starting point for assigning shares based on the fault inputs you provide.

Step 2: Apply the fault percentages to compute shares

Missouri’s comparative-fault approach affects allocation through percentage-driven mechanics referenced in Mo. Rev. Stat. § 537.067.

Practically:

• Each party’s entered fault percentage corresponds to that party’s computed share of the allocation pool.
• If you change a fault percentage, that party’s allocation share should change correspondingly.

(Illustrative only—use your numbers in the tool.)

• Total damages: 100,000
• Defendant A fault: 30%
• Defendant B fault: 70%
• The output allocation shares reflect those percentages on the stated total damages base.

Because Missouri recognizes comparative fault principles (as discussed in Gustafson v. Benda, 661 S.W.2d 11 (Mo. banc 1983), adopting pure comparative fault), the calculator’s day-to-day behavior is built around your fault-percentage inputs tied to the Missouri statutory structure.

Step 3: Apply the claimant fault threshold logic (51%)

This is the main “mode switch” to watch.

• If the claimant’s fault percentage is greater than 51%, the calculator reflects the statute-backed allocation effect associated with that threshold.
• If the claimant’s fault is at or below 51%, the calculator follows the alternative allocation path consistent with the standard comparative-fault allocation mechanics under Mo. Rev. Stat. § 537.067.

Why this matters:

• A small adjustment near the threshold can produce a structural change in the claimant-related output, not just a proportional shift.

Quick check:

• If your inputs put the claimant at 51.0%, confirm the tool is receiving that exact figure as intended.
• If your litigation record supports the claimant being slightly above 51%, rerun DocketMath after updating that number.

Step 4: Use the output table to interpret results

After you run the calculator, review outputs in two layers:

• Share-by-party allocation: confirm each defendant’s computed share tracks the fault percentages you entered.
• Claimant impact: confirm the claimant-related outcome aligns with whether the claimant fault is greater than 51%.

A good workflow:

• Make one change at a time (e.g., adjust Defendant A from 30% to 35%) and rerun.
• Watch which output rows change and how (proportional shifts vs. threshold-driven changes).

Step 5: Confirm products-related comparative-fault inputs (only if applicable)

If the matter is products liability, Missouri also includes a comparative-fault provision in Mo. Rev. Stat. § 537.765 and Mo. Rev. Stat. § 537.765.2.

Practical instruction:

• Use the Missouri profile and make sure you’re selecting the scenario settings in DocketMath that correspond to the type of claim you’re modeling.
• Then rerun allocation using the fault percentages that correspond to that products-related framework.

Gentle reminder: DocketMath calculations are only as good as your input assumptions and scenario selection. If a claim type is misclassified, outputs can diverge.

Common pitfalls

1. Entering claimant fault incorrectly

   • The greater than 51% threshold is sensitive to how you input the claimant’s fault.
   • Common error: treating the claimant’s fault as if it were just another defendant’s fault when the tool’s mode depends on claimant fault.

2. Percentages that don’t match the allocation universe

   • If you omit an actor that you intend the allocation to reflect, the resulting shares can be misleading relative to your intended model.
   • Keep your parties consistent from run to run.

3. Assuming changes will only be proportional

   • Near the 51% line, allocation can shift due to threshold logic (not just linear percentage effects). Always rerun after changing claimant fault inputs.

4. Mixing claim type rules unintentionally

   • If it’s a products liability matter, make sure DocketMath is using the appropriate Missouri products-related comparative-fault provision framework (referencing Mo. Rev. Stat. § 537.765 and Mo. Rev. Stat. § 537.765.2).

Sources and references

• Mo. Rev. Stat. § 537.067 (primary authority; Missouri allocation framework)
  https://revisor.mo.gov/main/OneSection.aspx?section=537.067
• Gustafson v. Benda, 661 S.W.2d 11 (Mo. banc 1983) (comparative fault adoption discussion)
• Mo. Rev. Stat. § 537.765 (products liability comparative-fault provision)
  https://revisor.mo.gov/main/OneSection.aspx?section=537.765
• Mo. Rev. Stat. § 537.765.2
  https://revisor.mo.gov/main/OneSection.aspx?section=537.765

Next steps

1. Open DocketMath’s damages-allocation calculator:
   /tools/damages-allocation
2. Select the Missouri (US-MO) jurisdiction profile.
3. Enter:

   • Total damages to allocate
   • Fault percentages for each party (and claimant fault if the scenario depends on it)
4. Review the output:

   • Confirm party shares align with your entered fault percentages
   • Check claimant-related results for the greater than 51% threshold behavior
5. Save your run:

   • If you update fault opinions, liability theories, or evidence, rerun the calculator and compare versions.

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