Why Damages Allocation results differ in New Mexico

4 min read

Published April 15, 2026 • By DocketMath Team

The top 5 reasons results differ

If you’re running a damages-allocation calculation in New Mexico (US-NM) with DocketMath, you may notice that two otherwise similar-looking runs produce different results. The most common cause isn’t “math”—it’s inputs and jurisdiction-aware rules that shift outcomes.

Below are the top 5 reasons DocketMath allocation results diverge in New Mexico, using N.M. Stat. Ann. § 31-1-8 as the relevant general limitations anchor.

Note: DocketMath helps diagnose inconsistencies, but this isn’t legal advice. Use the output to identify what changed—then confirm any legal assumptions in the context of your case.

1) Different start dates for claim eligibility (limitations)

New Mexico’s general statute of limitations is 2 years under N.M. Stat. Ann. § 31-1-8. If your dataset (or opposing party’s position) uses different “event” dates (e.g., accrual date, notice date, or last qualifying act), the allocation can move because some damage components may be treated as time-barred versus included.

  • Rule used: General SOL: 2 years
  • Statute: N.M. Stat. Ann. § 31-1-8
  • No claim-type-specific sub-rule was found in the jurisdiction data you provided—so DocketMath applies the general/default period.

2) Damage components are bucketed differently (labor, materials, rent, etc.)

Damages allocation results often change when you:

  • allocate amounts into different categories, or
  • switch whether a category is treated as within the limitations window.

Even a small re-binning—like moving $8,500 from “ongoing” to “discrete”—can push portions of damages beyond the 2-year boundary, changing the included amount.

3) Aggregation timing differs (per invoice vs. total project)

Two runs can use the same total dollars while still producing different allocations if DocketMath receives:

  • invoice-level dates vs.
  • one project-level date.

Invoice-level dating typically creates more precise inclusion/exclusion relative to the 2-year window from § 31-1-8.

4) Partial-period coverage (mid-month and cutoffs)

Allocation is sensitive to boundaries. If one run assumes damages “hit” on the first day of a period and another assumes the last day, you can see different included amounts—even without changing totals.

5) Input normalization (rounding, currency, or duplicate records)

Common data issues that change outcomes:

  • duplicated line items,
  • rounding differences (e.g., $1,999.99 vs $2,000),
  • inconsistent currency formatting,
  • missing end dates for recurring damages.

These issues can shift “effective totals” and how DocketMath applies time slicing, resulting in different allocations.

How to isolate the variable

Use DocketMath’s jurisdiction-aware setup and change one factor at a time. Start with limitations because New Mexico’s general SOL is 2 years under N.M. Stat. Ann. § 31-1-8, and no claim-type-specific sub-rule was identified—so the general/default period is the baseline.

A quick diagnostic checklist

Run-comparison approach

  1. Run A: your current dataset
  2. Run B: same dataset, but shift only the start/trigger date by a small amount (e.g., ±15 days)
  3. Run C: revert, then change one category mapping (e.g., move “rent” from discrete to recurring)
  4. Review which run causes the biggest delta

If the largest swing follows changing the trigger date, the discrepancy is usually a limitations window boundary issue tied to N.M. Stat. Ann. § 31-1-8.

For a focused workflow, open the calculator here: /tools/damages-allocation.

Next steps

Once you identify which variable is driving the discrepancy, lock in a repeatable process:

  • Document the chosen trigger date rule (the “why” behind the date selection matters when results hinge on the 2-year window in § 31-1-8).
  • Standardize the damage data model:
    • Use consistent category names
    • Include start/end dates where applicable
    • Prevent duplicates
  • Re-run with controlled edits (only one change per run) until deltas stabilize.
  • If a disagreement persists, export the intermediate allocation breakdown (by time bucket and category) and compare it line-by-line.

Warning: The same dollar total can still yield different allocations if date attribution and category bucketing differ. Treat dates and categories as first-class inputs, not metadata.

Related reading