Spreadsheet checks before running Damages Allocation in Mississippi

What the checker catches

Before you run DocketMath’s Damages Allocation calculator for Mississippi (US-MS), use a spreadsheet “sanity check” to prevent avoidable allocation distortions caused by timing errors and inconsistent claim fields. This is especially helpful because Mississippi’s general statute of limitations (SOL) is 3 years, under Miss. Code Ann. § 15-1-49—and your jurisdiction data does not indicate any claim-type-specific sub-rule. That means the checker applies the 3-year general/default period for timing validation unless your spreadsheet already has a documented, applicable exception built in.

Run the Damages Allocation workflow with these checks in mind:

• **SOL window alignment (timing basics)

  • Verifies that the incident/event date and the filing date (or the relevant demand/service date your sheet uses) create an elapsed timeline consistent with Miss. Code Ann. § 15-1-49’s 3-year general SOL.
  • Flags rows where elapsed time is:

    • Less than 3 years (potentially within the general SOL)
    • More than 3 years (potentially outside the general SOL)
    • Missing or non-date (can’t verify; treated as incomplete)

• Date coherence

  • Checks whether date columns follow a realistic ordering:

    • The incident/event date should not be after the filing date.
    • Payment/application dates (if your spreadsheet tracks them) shouldn’t be earlier than the incident/event date unless your model explicitly supports that logic.

• Unit and currency consistency

  • Detects spreadsheet formatting problems that skew allocation results:

    • Mixed formats like $25,000 in one row and 25000 in another (or text versions of numbers)
    • Percentage inputs entered as 15 instead of 0.15
    • “Thousands separators” or currency symbols that break numeric parsing

• Allocation input completeness

  • Ensures the inputs needed for allocation aren’t blank or mismatched:

    • Damage category labels are present and consistent
    • Share/percentage fields exist for the rows you plan to allocate
    • Share/percentage totals match the logic your spreadsheet expects (often 100%, but follow your internal model rules)
    • Liability/damages basis flags or category drivers are populated so the calculator isn’t allocating blank categories

• Orphan rows and mismatched keys

  • Catches structural issues that don’t always trigger obvious arithmetic errors:

    • Totals rows exist, but their category line items are missing
    • Category names don’t match across the “inputs” and “allocation” sheets/tabs
    • Row identifiers/keys don’t match between related worksheets (so values may not be allocated to the intended categories)

When to run it

Run timing and structure checks right before you execute /tools/damages-allocation. Don’t wait until after allocation, because allocation math depends on upstream fields (dates, category mappings, and numeric formats). If those inputs are off, you may get results that “look” numerically consistent while being structurally unreliable.

A practical workflow:

• **Step 1: Pre-calc validation (before running /tools/damages-allocation)

  • Validate dates and data types.
  • Use the SOL timing validation based on Miss. Code Ann. § 15-1-49’s 3-year general SOL (with no claim-type-specific sub-rule applied based on the jurisdiction data you provided).
  • Address missing fields—blank dates are a common source of silent allocation errors.

• Step 2: Run the Damages Allocation calculation

  • After the checker reports no critical issues, run the Damages Allocation calculator on the verified dataset.

• **Step 3: Post-calc consistency scan (quick)

  • Confirm allocation totals and category sums align with your spreadsheet’s expected structure.
  • Look for sudden total changes that correlate with rows previously flagged by the checker.

Re-run the checker whenever you:

• Import a new batch of claims or line items
• Modify any date fields
• Change allocation category mappings or percentage inputs
• Update formatting (for example, reformatting/copy-pasting from another system)

Because the default SOL is 3 years under Miss. Code Ann. § 15-1-49, the checker’s biggest value is catching timing problems early—especially when multiple date columns exist and one date field is accidentally overwritten.

Try the checker

You can validate your spreadsheet inputs using DocketMath’s guided flow at /tools/damages-allocation.

Before you click through to the allocation tool, confirm the spreadsheet fields are set up so the checker can evaluate:

• Incident/Event date (the date your damages narrative ties to)
• Filing date (the court filing date, if your model uses it)
• Allocation categories and amounts (or the equivalent structure your sheet uses)
• Any percentage/share fields that drive allocation logic

Quick checklist while preparing your spreadsheet:

How to read outputs: focus on problem categories rather than any single flagged row.

Gentle note: This tool helps with input QA and spreadsheet logic checks. It’s not legal advice, and you should confirm any SOL or exception assumptions with qualified guidance.

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