Spreadsheet checks before running Damages Allocation in New Mexico

What the checker catches

Run this scenario in DocketMath using the Damages Allocation calculator.

DocketMath’s Damages Allocation workflow in New Mexico (US-NM) works best when the underlying claim appears to be within the statute of limitations (SOL) before you allocate amounts across damages categories. A spreadsheet check helps catch input issues that can otherwise “spread” through the allocation totals—especially when the SOL inputs are wrong, mismatched, or incomplete.

For New Mexico, this checker uses the general/default 2-year SOL period under N.M. Stat. Ann. § 31-1-8. No claim-type-specific sub-rule was found for this checker setup, so it does not attempt to identify a different SOL period for particular claim types. In other words: treat the results as a baseline screen using the general 2-year rule, not a claim-by-claim legal determination.

Here are the most common spreadsheet problems the checker flags before you run allocation:

• Missing or inconsistent “trigger date” fields

  • Example: a settlement demand date is entered in one column but later treated like a “filing” date in the SOL logic.
  • Likely impact: the checker’s computed SOL end date can shift by months (or more), which can change whether the scenario looks “in time.”

• Date formatting errors

  • Example: a cell contains 1/5/24 as text (typed manually) rather than as a real spreadsheet date value.
  • Likely impact: the calculator may treat the input as blank or fail date math silently, which can produce an unreliable “status” signal.

• Off-by-one column mapping

  • Example: damages allocation uses a filing date, while the SOL check compares against a service date (or vice versa).
  • Likely impact: your totals can add up correctly while the SOL evaluation input is taken from the wrong column—meaning the output may not reflect the timeline you intended to test.

• Timezone/day-boundary mismatches

  • Example: one field is timestamp-based (includes time-of-day), while another is date-only.
  • Likely impact: dates can appear to shift near month-end/day boundaries, which can move the SOL cutoff by a day.

• SOL status ambiguity due to missing fields

  • Example: the sheet leaves blank a “last possible relevant date” (or equivalent field) the checker expects to validate the 2-year window.
  • Likely impact: the tool may be unable to confidently determine whether the timeline fits the 2-year window under N.M. Stat. Ann. § 31-1-8, so it’s better to correct the input than rely on any placeholder behavior.

• Confusing “2 years” with “two calendar years”

  • The checker applies the rolling 2-year span using date math, rather than treating the SOL as “Year X and Year Y only.”
  • Likely impact: a March-to-March window can differ substantially from a March-to-December window, even if they share the same two calendar years.

When to run it

Run the spreadsheet checker before you trigger the Damages Allocation calculator, and rerun it whenever you change dates, date columns, or the scope of what you’re allocating.

A practical sequence:

• Step 1: Confirm your date columns

  • The trigger/operative date your workflow uses for SOL math
  • The comparison/endpoint date you’re comparing against
  • Any pivot dates you’ve included (e.g., amendment dates, if your process uses them)

• Step 2: Run the checker

  • Use DocketMath’s Damages Allocation spreadsheet checks to validate date integrity and whether the timeline fits the general 2-year SOL baseline used by this setup.

• Step 3: Only then run Damages Allocation

  • If the checker indicates the SOL inputs “look consistent,” proceed to allocation categories and amounts.

• Step 4: Rerun after edits

  • Common edit types:

    • correcting a date format,
    • swapping the trigger field to the intended column,
    • updating the filing/operative date after review.

Quick pre-flight checklist for the spreadsheet (especially for a 2-year SOL under N.M. Stat. Ann. § 31-1-8):

Try the checker

You can run the Damages Allocation tool (and its spreadsheet checks) here: /tools/damages-allocation

If you want to access DocketMath tools more broadly while building your spreadsheet, you can start from: /tools/

When you open the tool, focus on:

1. **Inputs (dates)

   • Ensure the checker can interpret your date cells as real dates (not text).
   • Confirm your chosen “trigger date” and “comparison date” match the timeline you intend to test under N.M. Stat. Ann. § 31-1-8’s general 2-year SOL baseline.

2. **Outputs (status + computed window)

   • The checker should reflect whether the computed timeline falls within the 2-year window.
   • If the output signals missing fields or unclear status, fix the spreadsheet inputs first—don’t rely on defaults.

To make your spreadsheet more robust before rerunning:

• Use consistent date formats across relevant columns.
• Avoid manual text entry; paste dates from your source system when possible.
• Keep “trigger date” and “comparison date” in dedicated columns (don’t overload a single field with multiple meanings).

Note (gentle reminder): This checker applies New Mexico’s general/default 2-year SOL under N.M. Stat. Ann. § 31-1-8 and does not identify claim-type-specific SOL sub-rules for this setup. Use it as a baseline input validation screen.

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