Why Damages Allocation results differ in Missouri

4 min read

Published April 15, 2026 • By DocketMath Team

The top 5 reasons results differ

If you run DocketMath’s damages-allocation calculator for Missouri (US-MO) and get different results across cases—or across reruns with slightly different inputs—those differences usually trace back to how Missouri measures timing, applies a general limitations rule, and interprets categories of “what counts” in allocation.

In Missouri, the default statute of limitations (SOL) period referenced for claims is a 5-year general period under Mo. Rev. Stat. § 556.037. Importantly, no claim-type-specific sub-rule was found in the provided material—so treat 5 years as the default unless your scenario independently supports a different governing rule.

Here are the top 5 reasons damages allocation results differ in Missouri:

  1. Different “lookback” windows driven by the 5-year default SOL

    • DocketMath allocation outputs can change when the assumed event date (or an accrual-related date) moves, because the SOL window determines which time periods are considered eligible for allocation.
  2. **Accrual date assumptions (event date vs. filing date vs. notice date)

    • Even a relatively small shift (for example, 30–90 days) in the assumed accrual can move damages in or out of the 5-year eligibility window, changing the eligible total and the allocation distribution.
  3. Input category selection affects what portion is “allocated”

    • If you enter amounts under different damage buckets (e.g., different damage components), DocketMath allocates totals according to the selected categories. Changing the bucket mapping can alter the distribution even if the overall sum stays similar.
  4. Rounding and aggregation across payment periods

    • Allocation often depends on how values are periodized (e.g., by month/quarter/other segments). Small rounding differences across many periods can accumulate and shift totals.
  5. Inconsistent treatment of out-of-window amounts

    • When parts of the damages fall before the limitations window, DocketMath may either exclude them entirely from the eligible allocation or present them as an “excluded” subtotal (depending on the calculator’s design). That choice can affect what you see as the “headline” output.

Note: Missouri’s 5-year default SOL baseline comes from Mo. Rev. Stat. § 556.037. Without a claim-type-specific sub-rule, interpret DocketMath results using that general/default period rather than assuming a shorter or longer one.

How to isolate the variable

Use a quick diagnostic workflow in DocketMath to pinpoint what’s driving the mismatch.

  1. Lock the dates first

    • Keep the same event/accrual date across runs.
    • Keep the filing-related date (or whatever filing/notice inputs you’re using) constant too.
    • Then change only one other input at a time.
  2. Run controlled comparisons

    • Compare two runs that differ by exactly one factor:
      • Date change: shift the accrual by (e.g.) 30 days and observe how the eligible-window changes.
      • Category change: move a single dollar amount from one damage bucket to another.
      • Periodization change: adjust how the calculator groups time segments (if your workflow supports this).
  3. Check the breakdown, not just the total

    • Look for outputs such as:
      • Eligible vs. excluded amounts
      • Allocation by damage component
      • Any timing eligibility indicators (if shown)
  4. Confirm the limitations rule being applied

Checklist (use during triage):

Quick reference: what DocketMath is likely doing

DocketMath’s damages-allocation workflow typically ties the timing window (SOL-based eligibility) to which periods are counted toward eligible allocation. With Missouri’s 5-year default rule, date inputs are often the biggest lever affecting outputs.

Next steps

Start with the fastest path to stable, explainable outputs:

  • Re-run using the primary tool CTA to keep your workflow consistent: damages allocation tool
    Keep inputs consistent, then change one variable at a time.
  • Record each run’s inputs (dates + totals + bucket selections). This helps you identify whether drift comes from:
    • date eligibility shifts, or
    • bucket/category allocation, or
    • periodization/rounding.
  • Use the Mo. Rev. Stat. § 556.037 baseline when you’re evaluating what should fall inside the eligible window (default 5-year approach):

Gentle reminder: If your scenario involves a special statutory scheme or a different limitations rule than the default 5-year period, the results you see in DocketMath may not match what ultimately applies in that specific situation. The calculator is best used as a modeling tool while you verify the governing rule for your facts.

Related reading