How Damages Allocation rules vary in Missouri

What varies by jurisdiction

Damages allocation rules can change dramatically depending on the jurisdiction’s comparative-fault framework and how it treats multiple responsible parties. For Missouri, the key rule used for comparative-fault allocation mechanics in many civil negligence-related settings is Mo. Rev. Stat. § 537.067, which addresses comparative fault among “claimants and defendants.” (Primary source: https://revisor.mo.gov/main/OneSection.aspx?section=537.067)

Using DocketMath (with the jurisdiction set to US-MO), the practical effect is that the same accident facts—such as who was driving, who failed to yield, and who contributed to the harm—can produce different allocation outcomes if Missouri’s statutory allocation mechanics apply differently than they do in other states/countries.

Missouri-specific drivers of variation in outputs

Even when fault percentages come from the same evidence, the “rules for turning percentages into recoverable damages” are jurisdiction-specific. For Missouri, two verified concepts matter for DocketMath’s jurisdiction-aware calculations:

• Pure comparative fault (baseline concept): Missouri uses comparative fault rather than an all-or-nothing approach. The Missouri Supreme Court recognized this approach in Gustafson v. Benda, 661 S.W.2d 11 (Mo. banc 1983) (adopting pure comparative fault under the Uniform Comparative Fault Act).
  Practical takeaway: the presence of fault should not automatically end recovery; instead, fault percentages are used to determine recoverable damages according to the statutory mechanics.

• A statutory percentage threshold affecting allocation mechanics: Mo. Rev. Stat. § 537.067 includes a percentage threshold that can change how allocation impacts recovery. The verified threshold for DocketMath’s Missouri rule logic is 51 (i.e., the calculator’s Missouri logic uses a 51% threshold).

Data-thinking tip (not legal advice): “Comparative fault” refers to how fault percentages are assigned. “Allocation rules” refer to how those percentages translate into recoverable amounts—and Missouri’s § 537.067 includes threshold-driven mechanics that can change results.

How DocketMath maps inputs to outputs (what changes)

To model Missouri in DocketMath, you’ll typically supply (or source) inputs like:

• Which parties are being compared (claimant vs. one or more defendants)
• Each party’s fault percentage
• Whether the case posture triggers the statutory threshold effect tied to Mo. Rev. Stat. § 537.067

When the threshold logic is triggered, small changes around the 51% benchmark can lead to noticeably different output allocations.

If you’re looking for the calculator directly, start here: /tools/damages-allocation.

What to verify

Before relying on DocketMath’s Missouri damages allocation output, verify that your run is aligned with the verified Missouri authorities and the calculator’s inputs.

1) Confirm the governing authority is mapped correctly in US-MO

In DocketMath’s US-MO workflow, ensure the calculator is using Mo. Rev. Stat. § 537.067 as the primary comparative-fault allocation authority for the scenario you’re modeling (per the verified packet).

Also consider related contexts where Missouri may apply different comparative-fault provisions. For example, Mo. Rev. Stat. § 537.765.2 is a products liability comparative-fault provision. If your fact pattern is products liability–focused, you should ensure DocketMath is using the product-specific logic rather than assuming the general comparative-fault allocation mechanics under § 537.067 apply.

2) Use the correct threshold logic (51%)

DocketMath’s verified Missouri rule logic includes a 51% threshold used with Mo. Rev. Stat. § 537.067.

Verification checklist:

• The threshold logic is enabled for the correct Missouri allocation scenario/case type within the calculator.
• The relevant party’s fault percentage is entered using the same baseline used to compute “percent fault” in your underlying case facts.
• You are not rounding fault percentages in a way that moves a party across 51 (e.g., treat 50.6% vs. 51% carefully).
  Pitfall to avoid: rounding before entering numbers into DocketMath can flip whether the statutory threshold effect is triggered.

3) Verify the “receipts” limitation period setting used by DocketMath

Your Missouri run should use the receipts-related limitation setting reflected in the verified packet: “see statute.”

Verification checklist:

• In DocketMath, select the Missouri receipts limitation configuration that corresponds to the statute-linked setting.
• If the calculator asks you to confirm a receipts limitation period, pull the relevant language directly from Mo. Rev. Stat. § 537.067 using the revisor link provided in the verified packet (https://revisor.mo.gov/main/OneSection.aspx?section=537.067).

4) Confirm the calculator treats comparative fault as non-absolute

Missouri’s comparative-fault approach is consistent with pure comparative fault as recognized in Gustafson v. Benda. In practical terms, this supports an expectation that fault presence alone should not automatically bar recovery; instead, the allocation mechanics (including the 51% threshold logic in § 537.067) drive the recovery impact.

5) If the matter is products liability, check whether § 537.765.2 changes inputs/logic

If your scenario involves products liability, verify whether DocketMath is applying Mo. Rev. Stat. § 537.765.2.

Verification checklist:

• Is your claim specifically framed as products liability?
• If yes, ensure the calculator uses the § 537.765.2 comparative-fault provision rather than defaulting to § 537.067.

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