Why Damages Allocation results differ in Nevada

The top 5 reasons results differ

Run this scenario in DocketMath using the Damages Allocation calculator.

If you run DocketMath’s “damages-allocation” calculator for Nevada (US-NV) and see different results across attempts, the causes are usually not mysterious—they’re diagnostic. Nevada applies a general/default statute of limitations (SOL) period of 2 years, and the calculator’s jurisdiction-aware rules can change which time windows count toward damages allocation.

In this Nevada setup, the baseline is the general SOL period of 2 years under NRS § 11.190(3)(d). No claim-type-specific sub-rule was found in the available jurisdiction inputs, so the 2-year default is the baseline.

Here are the top 5 reasons allocation outputs differ in Nevada:

1. Wrong “case date” vs. “event date” pairing

   • DocketMath needs a consistent timeline: when the alleged damages began (or were first measurable) and when the claim is treated as filed.
   • Shifting those dates by weeks (or months) changes which portion of the damages falls inside/outside the Nevada SOL window.

2. SOL window cutoff is applied to damages, not just the claim

   • Under the 2-year default in NRS § 11.190(3)(d), damages that fall outside the allowable window may be allocated differently (often effectively reduced or reallocated).

3. Input precision changes how much falls inside the 2-year span

   • Even with the same rough story, entering “around March 1” versus an exact date can materially change the portion treated as within the 2-year window.
   • Small date changes can swing the included/excluded amounts when the damages timeline sits near the cutoff.

4. Multiple damage components are bucketed differently

   • DocketMath typically allocates across the components you enter (e.g., categories or time-based chunks).
   • If one component’s date range is entered differently from another—even unintentionally—its allocation can move more than the others under Nevada’s SOL cutoff rules.

5. Users mix Nevada-specific assumptions with generic ones

   • Nevada’s baseline is the 2-year period from NRS § 11.190(3)(d).
   • A prior run using a different jurisdiction (or a non-Nevada assumption) can create a “persistent mismatch” that looks like a math error, even when the only issue is the SOL period being applied differently.

Note (non-legal advice): If one Nevada run shows “full damages” while another shows “trimmed damages,” the most common driver is SOL window application caused by date differences—not a change in underlying allocation logic.

How to isolate the variable

Use this repeatable checklist to identify what’s driving the difference in DocketMath outputs for US-NV.

• 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 isolation method

• the SOL cutoff date / window boundary (or equivalent indicator shown),

  • the allocated totals per component (if displayed).
  • Change only the event start date by a known amount (e.g., +30 days).
  • Re-run and compare:

    • which damage components changed,
    • how allocation totals moved.
  • Keep event dates fixed; adjust only the claim date by the same amount.
  • Confirm the calculator is set to US-NV.
  • Confirm it uses the general 2-year SOL under NRS § 11.190(3)(d).
  • Again, because no claim-type-specific override was found in the available jurisdiction inputs, the 2-year default should govern the damages window in these runs.

Where to start (hands-on)

Begin by running the tool directly: /tools/damages-allocation

Next steps

To move from diagnosis to a stable, repeatable result set:

1. Standardize your timeline inputs

   • Use exact dates when possible.
   • If you only have estimates, keep them consistent and document your assumption style across runs.

2. Align all components to the same “time logic”

   • If one component uses monthly increments and another uses a broad date range, outputs may shift differently under the same 2-year Nevada cutoff.

3. Keep the Nevada SOL basis explicit

   • Nevada baseline here is 2 years under NRS § 11.190(3)(d).
   • Since no claim-type-specific sub-rule was identified in the provided jurisdiction inputs, use the 2-year default as the controlling assumption.

4. Re-run with controlled changes only

   • Change one variable at a time (start date, then claim date, then component ranges). Otherwise, you can’t tell what caused the output to change.

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