Why Damages Allocation results differ in Montana

5 min read

Published April 15, 2026 • By DocketMath Team

The top 5 reasons results differ

When you run DocketMath → Damages Allocation for a Montana matter (jurisdiction code US-MT), “why did the numbers come out differently?” usually comes down to a small set of inputs and jurisdiction-aware rules. Montana has a general/default statute of limitations (SOL) of 3 yearsMontana Code Annotated § 27-2-102(3)—and no claim-type-specific sub-rule was found for this SOL default in the available jurisdiction data. That clarity helps, but it doesn’t eliminate differences caused by how damages are allocated in practice.

Here are the top five causes of different results in Montana with DocketMath:

  1. Different assumptions about the time window

    • Even when the SOL is generally 3 years under § 27-2-102(3), your damages inputs may reflect different start dates, incident dates, or “economic-loss through” endpoints. Shift that window and the included damages change.
  2. Mismatch in which components are treated as “allocatable”

    • DocketMath’s calculator will allocate according to the damages categories you provide (e.g., medical vs. lost wages vs. non-economic). If one run includes an additional category (or excludes one), totals can diverge sharply.
  3. Conflicting discounting or rate assumptions

    • If you apply different inflation, wage growth, or discount assumptions (even slightly), allocation shares can change because the model is comparing component magnitudes after adjustments.
  4. Different injury or impairment inputs

    • Allocation often depends on functional impact numbers (days affected, impairment level, or similar quantification). Two data sets that both “describe the same injury” can still produce different allocation outputs if the quantification differs.
  5. Coverage or payment-credit timing differences

    • Where your scenario includes reimbursements, payments, or credits that occur at different times, DocketMath may allocate differently depending on how you structure those entries across the timeline.

Warning (non-legal advice): The 3-year general SOL under MCA § 27-2-102(3) is a baseline. Variations in your damages timeline can still cause your allocation outputs to differ even if you used the same SOL rule.

How to isolate the variable

To pinpoint what changed between two DocketMath runs, treat the calculator like a controlled experiment. Use this checklist:

  • Freeze the jurisdiction and tool settings so both runs use the same rule set.
  • Compare one input at a time (dates, rates, amounts) and re-run after each change.
  • Review the breakdown to see which segment or assumption drives the difference.

Step 1: Lock the SOL baseline

  • Confirm both runs are using the general/default 3-year period: MCA § 27-2-102(3).
  • Because no claim-type-specific sub-rule was found in the provided jurisdiction data, both runs should apply the same default SOL unless you explicitly change your rule set or inputs elsewhere in your workflow.

Step 2: Compare the timeline inputs first

Create a quick “diff table”:

Input groupRun ARun BEffect to watch
SOL start date / incident dateChanges what falls inside the window
Damages “through” dateChanges which expenses/losses are counted
Any cut-off datesAlters totals and relative weights

✅ If the dates differ, stop there—your allocation difference is likely explained by inclusion/exclusion of damages.

Step 3: Verify category selection and amounts

Check that both runs include the same damages components:

Then compare category totals before allocation. If category totals differ, the shares can differ even with identical weights.

Step 4: Normalize “rates” and adjustment assumptions

Look for settings like:

  • wage growth / inflation
  • discount rate (if used)
  • timing of costs (lumped vs. spread)

Even a small rate change can alter the relative magnitude of categories, which changes allocation results.

Step 5: Review “mechanics” inputs tied to injury impact

For example:

  • days impacted
  • impairment or severity quantification
  • treatment duration inputs (if mapped to timing)

Those typically drive lost-time and medical-time derived components.

If you want a fast way to reproduce the process, start from the calculator: /tools/damages-allocation.

Next steps

Use a repeatable workflow to prevent “silent” differences:

  • Create one canonical DocketMath input sheet for Montana (US-MT).
  • Run two scenarios only after you change one variable:
    • Change only the “through” date, rerun, record the change.
    • Then revert and change only the medical expense total, rerun, record the change.
  • Keep a short log of deltas:
    • “Date window changed: included 6 additional months of medical → allocation shifted toward medical.”

Finally, when sharing results, label the assumption set clearly:

  • SOL basis: MCA § 27-2-102(3), general/default 3 years
  • No claim-type-specific SOL sub-rule applied (per available jurisdiction data)

Pitfall: Comparing outputs without matching the timeline and category list is the fastest way to get an unexplained discrepancy—especially when the only “law” input (the 3-year SOL) is the same.

Related reading