How to run Settlement Allocator in DocketMath for Nevada

Step-by-step

Run this scenario in DocketMath using the Settlement Allocator calculator.

This walkthrough shows how to run Settlement Allocator in DocketMath for Nevada (US-NV) using jurisdiction-aware rules. You’ll see which inputs matter, how the tool applies Nevada’s general statute of limitations (SOL), and what to do with the outputs—without relying on legal advice.

1) Open the tool from the Primary CTA

• Go to: /tools/settlement-allocator
• After you open the calculator, you’ll typically see a workflow where you can select:

  • the jurisdiction (US-NV)
  • the allocation inputs
  • optional date-related inputs that affect timing logic

2) Set jurisdiction to Nevada (US-NV)

In the jurisdiction selector:

• Choose Nevada — US-NV

What to expect:

• DocketMath will apply Nevada’s general SOL period of 2 years based on the jurisdiction data.
• The rule is grounded in NRS § 11.190(3)(d) (General SOL Period: 2 years).

Citation/source:

• Nevada’s general statute: NRS § 11.190(3)(d) (2-year period)
  https://law.justia.com/codes/nevada/chapter-11/statute-11-190/

3) Enter the allocation inputs

Settlement Allocator works best when you provide inputs that let it compute amounts and timing-sensitive outputs. Because the exact labels on-screen can vary, use this checklist while you fill the form:

• Settlement amounts / totals you want allocated
• Recipient buckets (e.g., parties, categories, or claim components—whatever DocketMath exposes on the calculator)
• Any dates the tool asks for that affect SOL/timing logic, such as:

  • incident/trigger date
  • filing date (if included)
  • settlement date
• Any weighting factors or distribution preferences (if the calculator uses them)

As you type, watch for:

• whether DocketMath normalizes values (for example, converting entries into totals or percentages)
• whether the tool requires dates in a specific format (common patterns: MM/DD/YYYY or YYYY-MM-DD)

4) Confirm the tool is using the Nevada SOL rule

Before generating results, check any summary panel, rules banner, or jurisdiction confirmation in the output area. You should see language indicating it’s using Nevada’s general SOL approach.

For this Nevada setup, the expected SOL inputs are:

• General SOL Period: 2 years
• **General Statute: NRS § 11.190(3)(d)
• Default behavior: no claim-type-specific sub-rule identified in the provided data, so no claim-type override is applied

Warning (practical): If your situation involves a claim type that has a different SOL than Nevada’s general 2-year period, DocketMath may not automatically switch rules unless the interface supports claim-type-specific selection or you provide enough claim-type detail. Use the Nevada general/default SOL here unless you can accurately specify otherwise within the tool.

5) Generate the allocation

Click Calculate / Run / Allocate (the exact button label depends on the UI). After the tool processes your inputs, you should see outputs that commonly include:

• Allocated amounts per recipient/category
• Timing / eligibility indicators influenced by SOL logic (if your date inputs are used)
• A reconciliation view showing that allocations add up to the settlement total (or explaining any adjustments/proration the tool performs)

6) Review how changing inputs changes outputs

To validate your run, test at least one controlled change. For Nevada’s workflow, the easiest knob is usually a date input that determines whether you cross the SOL threshold.

Suggested micro-tests:

• Change the trigger/incident date by 30–90 days, then rerun.
• Adjust the filing date (or settlement date, if the tool ties it to timing logic), then rerun.

What to look for:

1. Amount changes: Do allocated amounts shift (for example, if the tool weights in-SOL vs. out-of-SOL items)?
2. Eligibility/indicator changes: Does DocketMath flag components differently once you cross the 2-year boundary?

Record what changes so you can interpret your final output confidently.

7) Export or save your results (if available)

If DocketMath offers a download/export:

• Save a copy of the allocation output.
• Capture the jurisdiction setting (US-NV) and the date inputs you used so the run is repeatable.

This is especially helpful when comparing:

• “early settlement” vs. “late settlement” scenarios
• “inside SOL” vs. “outside SOL” timing outcomes

Common pitfalls

Use this checklist to avoid mistakes that can distort allocator outputs when running US-NV.

• The Nevada default in this setup is 2 years under NRS § 11.190(3)(d).

• The provided data does not include claim-type-specific sub-rules, so the tool should treat this as the general/default period.

• If your scenario requires a different SOL than the general 2-year rule, you need a way in the tool to select the applicable rule—or enough detail to trigger claim-type-specific logic.

• If you can’t specify claim type in the UI, the safest expectation is that the tool stays on the general/default SOL.

• Example issue: 03/04/2024 could be read as March 4 or April 3 depending on settings.

• Fix by entering dates using the format DocketMath indicates (or switching to a unambiguous format if the UI allows).

• If the tool allows you to input both a settlement total and component amounts, ensure they match (or understand how the tool reconciles differences).

• If there’s a mismatch, the allocator may prorate or normalize inputs—changing the outputs.

• SOL-driven indicators can flip near the cutoff.

• When date uncertainty exists, run “before and after” scenarios to confirm how the tool behaves.

Pitfall note: Treating “2 years” as a fixed “always 730 days” approximation can mislead interpretation around borderline cases. DocketMath will apply its own internal date-calculation method—so a small date adjustment is a good way to confirm output sensitivity.

Try it

Use this quick practice sequence to validate the Nevada run in DocketMath.

1. Open /tools/settlement-allocator
2. Set jurisdiction to **Nevada (US-NV)
3. Enter a settlement total and allocate across at least two categories/recipients
4. Provide date inputs designed to test the SOL threshold:

   • one scenario where the key date difference is under 2 years
   • one scenario where it’s just over 2 years
5. Run the calculator twice and compare:

   • whether timing/eligibility indicators change
   • whether allocated amounts change or stay proportionate

Keep your statutory baseline in mind:

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

If you want to iterate quickly while working, you can revisit the same workflow at /tools/settlement-allocator after each adjustment.

Related reading

• Settlement Allocator Guide for Alabama
• Settlement Allocator Guide for Arizona
• Settlement Allocator Guide for Colorado