Worked example: Damages Allocation in Nevada

Example inputs

Run this scenario in DocketMath using the Damages Allocation calculator.

Below is a worked example showing how DocketMath can allocate damages in a Nevada case using jurisdiction-aware rules—specifically Nevada’s general statute of limitations (SOL) framework.

Scenario (for the calculator)

Assume a Nevada plaintiff files a civil action after a payment dispute that includes:

• Time of last breach / accrual date (alleged): 2024-06-15
• Filing date: 2026-07-10
• Total claimed damages: $120,000

  • Component A (e.g., contract damages): $85,000
  • Component B (e.g., related damages): $35,000

Why SOL matters for allocation

When some portions of damages are tied to conduct occurring outside the applicable limitations period, those portions may be vulnerable to dismissal or reduction as time-barred. DocketMath can help you model that issue by applying Nevada’s SOL cutoff date and allocating amounts accordingly.

Nevada SOL rule used (general/default)

From your Nevada jurisdiction data:

• General SOL period: 2 years
• General statute citation: NRS § 11.190(3)(d)
• Source: https://law.justia.com/codes/nevada/chapter-11/statute-11-190/

Also important: No claim-type-specific sub-rule was found in the provided jurisdiction data. That means this example uses the general/default 2-year period for the entire modeled damages allocation, rather than switching to a different SOL based on the label of Component A vs. Component B.

Inputs you would enter into DocketMath (damages-allocation)

Open the calculator at /tools/damages-allocation and enter:

• Jurisdiction: US-NV
• Limitations basis: **General SOL (2 years) under NRS § 11.190(3)(d)
• Accrual / last-breach date: 2024-06-15
• Filing date: 2026-07-10
• Total claimed damages: $120,000

  • Component A: $85,000
  • Component B: $35,000

If the calculator accepts separate timing inputs per component (for example, “component occurred between date ranges”), you can refine the allocation by date instead of doing a case-level proportion. In this example, we assume the tool models the SOL impact using the overall relationship between accrual and filing dates.

Step 1: Compute the SOL cutoff date (illustrative)

Using the 2-year period:

• Accrual date: 2024-06-15
• End of limitations window: 2026-06-15

Because the filing date is 2026-07-10, the filing occurs 25 days after the 2-year period ends. That timing drives the allocation output discussed next.

Example run

Now let’s run the example with the inputs above in DocketMath (damages-allocation) (see /tools/damages-allocation).

Run the Damages Allocation calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

Interpreting the allocation logic (tool outcome)

Because the filing date is after 2026-06-15, the model treats amounts attributable to events outside the limitations window as less likely to be recoverable.

In this example, we allocate using an illustrative proportional method: estimate what share of the claimed damages is treated as “inside SOL” versus “outside SOL,” based on how far the filing date falls beyond the end of the limitations period. Since no component-specific date ranges are provided, the model uses a case-level timing approximation.

Time gap breakdown

• Limitations end: 2026-06-15
• Filing: 2026-07-10
• Overrun beyond end date: 25 days

For illustration, take the 2-year window as roughly 730 days (the tool’s exact day-count conventions may differ, but the practical allocation effect is similar here):

• Fraction outside window ≈ 25 / 730 = 3.42%
• Fraction within window ≈ 96.58%

Example allocation result (illustrative)

Using the within-window fraction (96.58%) and outside-window fraction (3.42%):

What the calculator is doing with NRS § 11.190(3)(d)

DocketMath applies the general/default SOL of 2 years from NRS § 11.190(3)(d), consistent with the jurisdiction data provided.

Because the inputs indicate no claim-type-specific sub-rule was found, DocketMath does not switch to a different SOL simply because the damages are described as “Component A” versus “Component B.” This keeps the example as a baseline using only the general rule; if your specific claim type has a different Nevada limitations rule not covered by the provided data, you would need a re-run using the correct rule set.

Sensitivity check

Next, test how sensitive the modeled allocation is to the filing date. The goal is to see how quickly the “outside SOL window” amount grows as you move the filing date relative to the cutoff (2026-06-15).

To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.

Sensitivity inputs (keep everything else constant)

Hold constant:

• accrual date: 2024-06-15
• total damages: $120,000
• component split: $85,000 / $35,000
• general SOL: 2 years under **NRS § 11.190(3)(d)

Change only the filing date and re-allocate.

Sensitivity table (illustrative proportional method)

Assuming the same within/outside proportional approach:

Checklist: what to review before relying on allocation output

Practical takeaway: When a filing is close to the cutoff, small changes in filing timing can materially change the modeled “outside SOL window” amount. In this example, shifting from 2026-06-30 to 2026-07-10 changes the modeled outside amount by roughly $1,700.

Turning sensitivity into practical takeaways

• If you’re days from the cutoff, allocations may swing noticeably with minor date differences.
• If you’re weeks or months past the cutoff, the modeled time-barred share can become a much larger portion of total claimed damages.
• Because this example uses only the general/default SOL (per the “no claim-type-specific sub-rule found” instruction), treat results as a baseline unless you apply the correct claim-specific limitations rule.

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