Why Damages Allocation results differ in Mississippi

The top 5 reasons results differ

Run this scenario in DocketMath using the Damages Allocation calculator.

When you run DocketMath’s Damages Allocation calculator for Mississippi (US-MS), the results can differ from another run—or from another system—because the allocation logic depends on time-window and bucketing rules that can behave differently based on your inputs and configuration.

For Mississippi, the general/default statute of limitations (SOL) period is 3 years under Miss. Code Ann. § 15-1-49, and no claim-type-specific sub-rule was found for purposes of this diagnostic. That means the calculator is using the general 3-year SOL framework rather than a different SOL period based on a specific claim category.

Here are the top five reasons results differ:

1. Different SOL “start dates”

   • One run may treat your provided date as the triggering event (for example, when the claim accrued).
   • A change to the start date changes the eligible damages window, which can materially alter the allocation split.

2. Different SOL window ends

   • With a 3-year SOL (Miss. Code Ann. § 15-1-49), shifting the start date typically shifts the calculated end date as well.
   • That can change which portion of damages falls “inside” vs. “outside” the actionable timeframe.

3. Unequal handling of overlapping periods

   • Damages allocation often relies on whether events fall into the same time buckets.
   • A small date shift can push amounts across a boundary, which can move damages from “included” to “excluded” (or vice versa).

4. Input mismatches in itemized damages

   • If one run uses more line items, or different category/component breakdowns, DocketMath may redistribute damages differently.
   • Even when the total damages are the same, the allocation by bucket/category can change based on how the items are entered.

5. Tool rule-set version or configuration differences

   • DocketMath applies jurisdiction-aware defaults (here, the general 3-year rule).
   • If another method uses different assumptions for bucketing, inclusion/exclusion logic, or date interpretations, you’ll likely see different allocations even with the same underlying facts.

How to isolate the variable

To find the exact reason two outputs differ, use a controlled approach: change one input at a time and rerun DocketMath.

• 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-by-step checklist (repeat for both runs)

Practical diagnostic method (fastest path)

1. Run A: Use your full, current input set.
2. Run B: Keep everything identical to Run A, but change only one variable (start with the SOL start date).

   • Try a small shift (e.g., 30–90 days) to test whether date boundaries are driving the difference.
3. Interpret the change:

   • If allocation changes but totals don’t: bucketing/boundary logic is likely the driver.
   • If totals change: the eligible window logic (based on the 3-year SOL) is likely the driver.
   • If both change: re-check for itemization differences and any date boundary crossings.

If you want the quickest way to run these comparisons, start from /tools/damages-allocation.

Gentle reminder: This is a diagnostic workflow, not legal advice. SOL accrual/date interpretations can be fact-specific, and small input differences can change the calculated allocation.

Next steps

Once you identify what changed between Run A and Run B, you can make results more consistent:

• Standardize your “SOL start date” input approach

  • Because Mississippi’s diagnostic uses the general/default 3-year SOL under Miss. Code Ann. § 15-1-49 (and no claim-type-specific sub-rule was found here), using one consistent interpretation for what date you enter is often the biggest lever for stability.

• Test around likely boundary points

  • If the difference appears near a cutoff, rerun with dates incrementally closer to the boundary to see exactly when the inclusion/exclusion flips.

• Document your input assumptions per run

  • Keep a short note with each run:

    • the date basis used for the SOL start date
    • what you entered for damages (single total vs. multiple components)
    • whether any itemization mapping differed

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