Spreadsheet checks before running Damages Allocation in Missouri

What the checker catches

Before you run a Damages Allocation calculation in DocketMath for Missouri (US-MO), you can reduce downstream errors by validating the inputs that drive the allocation logic. A good spreadsheet checker focuses on “time and math” failure modes—especially issues that can interact with Missouri’s statute of limitations (SOL).

For Missouri, the general/default SOL period is 5 years, governed by Mo. Rev. Stat. § 556.037. In this workflow, no claim-type-specific sub-rule was found, so the checker should be clear that it uses the general 5-year period as the default.

Here’s what the spreadsheet checker should catch before you hit Damages Allocation:

• Wrong SOL window applied

  • Confirm the calculation uses 5 years (not 3, not 10).
  • Ensure the sheet is not configured to apply a claim-specific override that you haven’t actually selected or populated.

• Date fields in the wrong format

  • Watch for dates stored as text (e.g., 01/15/2024 treated as a string) instead of true date values.
  • Identify swapped components (MM/DD vs. DD/MM) that can silently move matters outside the 5-year window.

• Off-by-one mistakes in “elapsed time”

  • If your spreadsheet computes elapsed time by subtracting dates, verify it measures elapsed time the way your allocation model expects.
  • A small day-count mismatch can flip an “in-window” value into an “out-of-window” result.

• Silent unit or scale errors

  • Catch cases where damages are entered in the wrong scale, such as:

    • thousands vs. dollars (e.g., 50 meaning $50,000),
    • monthly amounts vs. totals.
  • These errors can distort allocation proportions even when the dates look correct.

• Inconsistent allocation inputs

  • If DocketMath’s damages allocation uses category weights (or similar factors), verify:

    • weights sum to 1.00 (or 100%, depending on your spreadsheet convention),
    • category counts/rows align with your dataset (no missing rows or categories).
  • The checker should flag mismatches early, so they don’t cascade into incorrect redistribution.

• Negative or impossible values

  • Preempt rows where:

    • damages are negative,
    • quantities are negative,
    • adjustment factors are zero or negative (unless your model explicitly supports them).

A quick “inputs → outputs” map

When to run it

Use the checker right before running the DocketMath damages-allocation calculator, and again whenever you modify date-related or allocation-related cells.

A practical workflow:

1. Build the base dataset

   • Enter event/incident date(s), filing date(s), and category damages.
   • Keep date columns as true dates (not text).

2. Run the spreadsheet checker

   • Validate date formats, missing values, and elapsed-time logic.
   • Confirm the SOL rule being applied is the Missouri general 5-year default from Mo. Rev. Stat. § 556.037 (not a claim-specific rule).

3. Only then run Damages Allocation in DocketMath

   • The checker reduces “garbage in, garbage out” before calculations distribute losses across categories.

4. Re-run after edits

   • Trigger another pass if you update:

     • an incident date,
     • a filing/claim date,
     • damages scale (e.g., thousands → dollars),
     • category weights/factors.

5. Document what you changed

   • Keep a short change log in your workbook or notes, such as:

     • “Adjusted filing date format to YYYY-MM-DD”
     • “Converted amounts from thousands to dollars”
   • This makes it easier to explain unexpected allocation shifts.

Try the checker

You can run a jurisdiction-aware setup for Missouri (US-MO) in DocketMath using the primary CTA:

• Damages allocation tool: /tools/damages-allocation

If you start with a spreadsheet first, use the checker logic to validate the specific fields your model depends on—especially:

• the event/incident date
• the filing/claim date
• damages category amounts (and units)
• any allocation weights or factors

What to look for in results

After your spreadsheet passes validation, the Damages Allocation output should respond predictably to input changes:

• Adjusting dates

  • Moving a filing date across the 5-year threshold should be the kind of change that affects eligibility (if your model includes SOL gating).
  • If nothing changes after a large date shift, verify that your eligibility/date logic is actually connected to your allocation model.

• Adjusting amounts

  • If you scale all damages by 2× (and weights stay constant), allocated totals should scale by ~2×.
  • If totals don’t scale proportionally, check for inconsistent units or categories missing from the dataset.

• Adjusting weights

  • If you change one category weight while keeping the total constant, redistribution across categories should follow that change.

To sanity-check your pipeline faster, compare:

• pre-check totals (sum of inputs),
• post-allocation totals (sum of allocated outputs),
• expected relationships (equal scaling for unit changes; weight-based redistribution for factor changes).

Missouri SOL default the checker assumes

This workflow assumes the general/default SOL period of 5 years under Mo. Rev. Stat. § 556.037. No claim-type-specific sub-rule was found, so the checker uses the 5-year general period as the default.

Link for the calculator entry point (before you run allocation):

• Damages allocation tool

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