How to run Damages Allocation in DocketMath for Missouri

Step-by-step

This guide walks you through running Damages Allocation in DocketMath for Missouri (US-MO) using jurisdiction-aware rules tied to Mo. Rev. Stat. § 537.067.

1) Start the Missouri damages allocation calculator

1. Open DocketMath’s tool: /tools/damages-allocation
2. Select Missouri (US-MO) as the jurisdiction (if prompted in the UI).
3. Confirm you’re using the damages allocation calculator (template: damages-allocation).

2) Enter the allocation inputs DocketMath needs

DocketMath will request inputs related to how fault is allocated among multiple parties. For Missouri, the tool’s rule set is grounded in Mo. Rev. Stat. § 537.067 and the statute’s mechanics for allocating responsibility when multiple parties are involved.

Use a checklist approach:

• Identify each potentially responsible party you want included in the allocation
• Assign a fault/percentage value for each party (as your case file reflects)
• Ensure the total of all parties’ percentages matches the convention your workflow uses (for example, whether you’re entering percentages that sum to 100%)
• Flag whether parties are treated as joint/several or whether the threshold rule applies in your scenario

3) Apply the Missouri rule that controls when joint/several allocation kicks in

Missouri’s allocation framework in this tool includes a threshold for when the joint/several logic applies.

DocketMath’s verified configuration includes:

• Joint/several sub-rule threshold: 51

That means the tool will treat allocation differently depending on whether relevant fault crosses the 51% boundary tied to the Missouri allocation mechanics reflected in Mo. Rev. Stat. § 537.067.

Practical implication for your run:

• If the key party (or the party grouping relevant to the tool’s logic) is at 51% or above, expect the output to reflect the statute’s joint/several-trigger behavior.
• If the highest party is below 51%, expect the result to follow the non-joint/several allocation path the tool is configured to use.

4) Use the receipts / limitation-period setting exactly as the statute directs

Missouri’s damages allocation setup in DocketMath also includes a receipts limitation period input behavior that’s governed by the statute.

In the verified facts packet, that setting is represented as:

• receipts.0.limitation_period: see statute

What to do in practice:

• Use the calculator’s guided input field for the receipts-related limitation period and set it in accordance with Mo. Rev. Stat. § 537.067 and Mo. Rev. Stat. § 537.067.1 (the tool is designed to map this jurisdiction rule consistently).
• If DocketMath shows the option as “guided” or “statute-derived,” rely on the tool’s Missouri-specific rule flow rather than trying to invent your own interpretation.

5) Run the calculation and review allocation outputs

After entering all required fields:

1. Click Calculate (or the tool’s equivalent action).
2. Review results screens for:

   • party-by-party allocation impacts
   • any joint/several-trigger indicators tied to the 51% threshold
   • final allocated amounts or allocation-adjusted damages outputs

Because Missouri allocates responsibility using the comparative-fault framework associated with Gustafson v. Benda, 661 S.W.2d 11 (Mo. banc 1983), the tool’s outputs are designed to reflect comparative fault concepts rather than an all-or-nothing approach.

6) Validate the run with a quick “sensitivity” check

Before finalizing your output, do a small consistency review:

• Identify the party closest to 51%
• If that party is near the threshold, change the percentage by a small amount (if you’re testing scenarios) and re-run
• Confirm whether the tool flips from one allocation treatment to another at 51%

This helps you catch input mistakes like:

• accidentally entering 49 instead of 51
• swapping percentages between two parties
• omitting a party entirely (which can inflate another party’s percentage)

Common pitfalls

Even when the inputs are mostly correct, a few issues repeatedly cause Missouri damages allocation runs to misstate outcomes in DocketMath.

1) Misunderstanding the 51% joint/several threshold behavior

The calculator uses a verified configuration:

• threshold_percentage: 51

If a scenario’s highest fault estimate is 50%, but you expected the joint/several logic anyway, the output will differ. Conversely, a party entered at 51% can shift the allocation treatment.

Checklist:

• Verify the party (or grouping) you believe is dominant is entered at the correct percentage
• Re-check rounding (e.g., 50.6 vs. 51)

2) Skipping the receipts/limitation-period field that is “see statute”

Missouri’s allocation mechanics in Mo. Rev. Stat. § 537.067 include receivers/receipts related rules (captured in the tool as a limitation-period input controlled by statute).

Pitfall pattern:

• leaving this field blank
• setting it to a value that’s not aligned with what the tool’s statute-guided Missouri option expects

Fix:

• Use the calculator’s Missouri-specific receipts/limitation period guidance tied to § 537.067 and § 537.067.1

3) Forgetting comparative-fault context for how the tool will allocate responsibility

Missouri follows comparative-fault concepts rooted in Gustafson v. Benda, 661 S.W.2d 11 (Mo. banc 1983), and product-related comparative-fault mechanics are referenced in Mo. Rev. Stat. § 537.765.2.

If your case involves product or related theories, your expectations should align with how the statute frames comparative fault rather than a “barred/total” model.

4) Entering parties that shouldn’t be included in the allocation run

DocketMath outputs are only as accurate as your included parties.

Quick check:

• Are all parties you list actually meant to be compared in the same allocation framework?
• Did you inadvertently include an entity whose fault isn’t part of your allocation basis?

Try it

Run a Missouri scenario in DocketMath and sanity-check the outputs using this mini-worksheet.

Quick scenario exercise (no new legal inputs required)

1. Open the calculator at: /tools/damages-allocation
2. Choose Missouri (US-MO)
3. Enter two main parties and optional others, then:

   • Scenario A: set the top party at 51%
   • Scenario B: set the top party at 50%
4. Re-run both scenarios and compare:

   • whether the output signals the 51% threshold-driven path
   • whether party-by-party allocation impacts move the way you expect

Use this as a fast internal QA:

• Does the tool’s behavior change at the 51% boundary?
• Are receipts/limitation-period values populated in a way that matches the statute-guided field?
• Do the allocations reflect comparative responsibility (consistent with Gustafson v. Benda)?

What to look for in your results

When reviewing outputs, focus on:

• The party entries whose percentages drive the outcome most
• Any explicit threshold-triggered behavior
• Allocation differences between Scenario A and Scenario B

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