Common Damages Allocation mistakes in Nevada

The top mistakes

In Nevada, DocketMath can help you model damages allocation, but the output is only as reliable as the inputs you feed it—especially when Nevada’s statute of limitations (SOL) acts like a time gate on what damages are recoverable. A key point: for this Nevada setup, the jurisdiction data provides only the general/default SOL, not a claim-type-specific override. So, treat the 2-year default SOL as the working rule unless you confirm another Nevada SOL statute applies to your specific claim.

1) Using the wrong Nevada SOL window when deciding what damages can be claimed

A common error is allocating damages based on the full harm timeline—without checking whether part of that harm falls outside Nevada’s SOL.

• Nevada general/default SOL period: 2 years
• Statute: NRS § 11.190(3)(d)
• No claim-type-specific sub-rule was found in the provided jurisdiction data, so the 2-year default is the baseline working rule.

What goes wrong in DocketMath: You may enter a longer “damages start date,” and DocketMath will allocate across that span—even though Nevada’s 2-year limit under NRS § 11.190(3)(d) may bar part of the claim period.

Practical warning: If any portion of the alleged damages is outside the applicable 2-year window, you risk allocating amounts that may be unrecoverable. DocketMath can model allocation, but it can’t replace the legal time gating you need to apply from your filing timing and claim characterization.

2) Allocating “all damages” without separating recoverable vs. non-recoverable components

Another frequent error is collapsing different components (or “inside SOL” vs. “outside SOL”) into one total and then allocating percentages or shares across everything.

If you don’t separate the bucket that should be treated as recoverable, you can end up with an allocation that looks mathematically tidy but fails the recoverability logic. In a Nevada SOL context, that often means:

• DocketMath may allocate amounts that should be excluded because they occur outside the recoverable window.

Fix: Create component-level inputs. Even a simple split—recoverable vs. barred by SOL—helps keep the model aligned with what you’re actually claiming.

3) Misstating the allocation basis (dates vs. percentages vs. categories)

People often assume allocation depends only on “when the harm happened.” But DocketMath outputs change materially depending on the allocation basis you choose and how you map it to your timeline.

Common missteps include:

• Using percent allocations when your model should be date-window based
• Applying one uniform “rate per period” assumption even though the inputs reflect different time segments (e.g., different billing rates or different calculation bases)
• Reusing the same starting point for categories that actually begin on different dates

Result to watch for: If your allocation basis doesn’t match the structure of your damages, your output can shift even when the total number you typed seems reasonable.

4) Confusing the harm timeline with the recoverable timeline

Even careful users sometimes model the harm period instead of the recoverable period.

Here, the working default is Nevada’s 2-year SOL under NRS § 11.190(3)(d). That means:

• Damages occurring more than 2 years before the relevant filing timing should be treated as barred under the default SOL analysis (unless another Nevada statute applies, which your jurisdiction data did not identify).

Important: DocketMath can help you allocate through a timeline, but it doesn’t decide which SOL clock applies. The practical goal is to ensure your DocketMath inputs reflect the recoverable window, not just the underlying event timeline.

5) Skipping date normalization and creating off-by-one errors

Small date inconsistencies can move the SOL boundary. If your model uses different date conventions across inputs, you can unintentionally expand or shrink the recoverable window.

Typical issues:

• Mixing filing date vs. demand date vs. incident date without noticing
• Calculating days using one convention in your narrative and another in DocketMath inputs
• Entering an “end date” that unintentionally extends the period you intended to exclude

Quick takeaway: If your recoverable total barely changes when you expect it to, or changes dramatically with a seemingly minor date tweak, investigate date normalization first.

How to avoid them

Use this Nevada-focused, tool-forward checklist to reduce damages-allocation mistakes in DocketMath. (This is modeling guidance—not legal advice.)

Use a written checklist for inputs, document each source, and run a quick sensitivity check before finalizing the result. When two runs differ, compare inputs line by line and re-run with one variable changed at a time.

Step 1: Lock in the Nevada SOL rule you’re modeling

Because your jurisdiction data provides only the general/default SOL, use that default as your baseline:

• 2-year general/default SOL: **NRS § 11.190(3)(d)
• Working assumption: The 2-year period applies unless you confirm a different Nevada SOL statute is applicable to your claim type (your provided data did not include a claim-type-specific sub-rule).

If you’re uncertain whether an override applies, a practical hygiene step is to run scenarios and keep your assumptions transparent.

Step 2: Align every damages component to a recoverable window

Model recoverable damages using the 2-year window under the default SOL approach.

A simple workflow:

• Split damages into components (for example: inside SOL vs. outside SOL)
• Allocate only the inside SOL portion into recoverable buckets
• Track the outside SOL portion separately so it can’t contaminate your recoverable totals

Step 3: Match the allocation method to the numbers you enter

Before running DocketMath, confirm your input structure:

• Time-based allocation: ensure your damages-per-day/per-period assumptions align with the windows you entered.
• Percentage-based allocation: confirm the percentages apply to recoverable totals, not non-recoverable totals.
• Category-based allocation: verify each category’s start/end dates are correct and consistent.

Sanity checks:

• Do the dates you entered match your narrative timeline?
• Do allocation percentages behave as expected for the recoverable components?
• Does the recoverable total actually shrink after the SOL gate?

Step 4: Use scenario comparisons instead of overwriting everything

A strong way to catch SOL-related input errors is to compare outputs:

• Scenario A: model using the harm timeline as fully recoverable (for baseline comparison)
• Scenario B: apply the 2-year default SOL under **NRS § 11.190(3)(d)

If Scenario B doesn’t reduce the recoverable total (when you believe some damages should fall outside the 2-year window), you likely entered dates incorrectly or didn’t apply the SOL gate in the model inputs.

Step 5: Tie outputs to inputs you can explain

DocketMath is easier to validate when you can point to what changed.

Examples:

• A shift of ~365 days (about 1 year) can materially alter a recoverable window under a 2-year SOL model.
• Even 30–60 days can change whether some amounts land inside vs. outside the SOL boundary.

If you can’t identify which input drove the difference, treat the output as less audit-ready until you can.

Quick checklist (before finalizing your allocation)

To start modeling, use DocketMath here: /tools/damages-allocation

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