Common Damages Allocation mistakes in Missouri

The top mistakes

Run this scenario in DocketMath using the Damages Allocation calculator.

Damages allocation errors are common in Missouri personal injury and property-related dockets—especially when teams try to “map” damages to recovery without checking how Missouri treats the timing of claims. With DocketMath and its damages-allocation calculator, these mistakes often show up as incorrect inputs, missing time-limit assumptions, or allocating damages in a way that can’t survive a statute-of-limitations (SOL) check.

Below are the most frequent allocation mistakes we see in US-MO (Missouri) case work.

1) Ignoring the 5-year general statute of limitations window

A major driver of allocation rework is treating damages allocation as independent from timing. In Missouri, the DocketMath workflow should assume a general/default 5-year period unless a specific rule applies elsewhere.

Missouri’s general statute of limitations for certain actions is set out in Mo. Rev. Stat. § 556.037, which provides a 5-year period. DocketMath’s Missouri mode should therefore treat 5 years as the default SOL when no claim-type-specific sub-rule is identified.

What goes wrong in allocation: teams allocate damages (e.g., past medical, lost earnings, property repair) without first verifying that the underlying claim window is open. The result is a spreadsheet that looks “right” economically but fails procedurally.

2) Feeding the calculator dates that don’t match “damage accrual”

DocketMath’s damages-allocation tool depends heavily on date inputs. A common error is using the wrong “anchor” dates, such as:

• the filing date instead of the date of loss/accrual,
• the date treatment ended instead of the first date expenses began,
• or a settlement negotiation date as the timeline starting point.

Practical consequence: when the tool is given incorrect start/end dates, its output can shift which portions of damages are treated as “within” the relevant period versus “outside” it.

Checklist (quick):

3) Mixing “past damages” and “future damages” without a consistent cutover

Another frequent allocation error is blending categories within the same bucket. Common patterns include:

• Past medical is partially included as future medical in one run, then corrected in a second run.
• Lost income is allocated through a certain month, then remaining months are still counted as “past.”

Why DocketMath flags this indirectly: if your date segmentation is inconsistent, the “within SOL vs. outside SOL” calculation can produce misleading totals—even if each category’s dollar figure looks reasonable on its own.

4) Over-allocating to categories that don’t match the docket narrative

Allocation errors also arise from using damages categories the case record doesn’t support, such as:

• adding speculative wage-loss months without documentation,
• including property damage amounts not tied to the claimed incident,
• double-counting repair costs that were later reimbursed.

DocketMath-specific operational issue: if you treat a revised claim as a new scenario, you may forget to remove the original numbers. That creates duplicates that inflate the “allocated total.”

5) Not reconciling totals between iterations (version drift)

Teams often run multiple DocketMath scenarios—changing just one date or one assumed monthly loss number. The top error here is failing to reconcile:

• the prior iteration’s totals,
• the updated iteration’s totals,
• and the deltas.

Practical result: the final docket figures can reflect a blend of two assumptions instead of a single coherent allocation.

How to avoid them

A clean allocation process in Missouri using DocketMath (damages-allocation) is mostly about building a consistent timeline and applying the correct default SOL assumption—5 years under the general rule.

Use a written checklist for inputs, document each source, and run a quick sensitivity check before finalizing the result. When two runs differ, compare inputs line by line and re-run with one variable changed at a time.

Step 1: Lock the default SOL assumption (and document it)

Because the jurisdiction data points to a general/default 5-year period and no claim-type-specific override was identified here, structure your workflow like this:

• Default SOL used: 5 years
• Authority: Mo. Rev. Stat. § 556.037
• Assumption: applies unless a separate, claim-specific rule is demonstrated by the case type and applicable Missouri law.

This prevents teams from accidentally “switching” SOL frameworks midstream.

Step 2: Standardize your date inputs across every run

Before you run DocketMath, decide a single set of rules for date selection and stick to them.

Use a simple internal mapping:

Step 3: Apply one cutover point for past vs. future

Pick a cutover and keep it stable:

• “last paid/recorded expense date,”
• “medical prognosis date,” or
• “first projected month.”

What matters is consistency and the ability to explain it later.

Practical rule: configure DocketMath so each dollar amount is assigned to exactly one time bucket (no partial overlap between “past” and “future” buckets).

Step 4: Validate outputs with a reconciliation pass

After running DocketMath, do a quick sanity check:

A lightweight reconciliation table can work, especially when you iterate:

• Scenario A total: $____
• Scenario B total: $____
• Change: $____ (aim for “date delta” changes, not unexplained category drift)

Step 5: Keep scenarios explainable (avoid version drift)

If you use multiple scenarios (e.g., conservative vs. aggressive anchor dates), label them with the date rationale:

• “Scenario 2: earliest documented bill date used for past medical”
• “Scenario 3: work-loss start aligned to HR/pay stub records”

This makes review faster and reduces errors caused by “just swapping a number” between versions.

Warning (timing vs. overlap): if your damages allocation changes but your anchor dates do not, you likely have a category overlap/duplication problem—not a timing problem.

If you’re ready to run a Missouri-focused allocation, start with the calculator here: /tools/damages-allocation.

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for Alaska — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules