How to run Settlement Allocator in DocketMath for Nevada

Step-by-step

This guide explains how to run Settlement Allocator in DocketMath for Nevada (US-NV) using jurisdiction-aware rules aligned to Nev. R. Civ. P. 23 (Nevada’s civil procedure class action rule set). You’ll see how to set inputs so the outputs reflect Nevada’s default allocation timing logic.

1) Start with the DocketMath tool

1. Open the Settlement Allocator tool: /tools/settlement-allocator
2. Set Jurisdiction to Nevada (US-NV).
3. Confirm the tool indicates it is using Nevada’s Nev. R. Civ. P. 23-based rules (and that Nevada is selected, not a neighboring or default jurisdiction).

2) Gather the inputs the allocator needs

Before you run the calculator, collect the allocation drivers your settlement and damages model rely on. In practice, you’ll typically need:

• Total settlement amount (the fund to distribute)
• Allocation base (e.g., eligible class shares, claim weights, or another distribution metric you’ve already determined)
• Eligible claimant list (or grouped representation, depending on how your model structures claimants)
• Any caps/limits your settlement agreement applies (if your model supports them in the tool)
• Timing reference inputs if DocketMath’s Nevada logic asks for timing-related fields

If your settlement agreement uses a specific allocation methodology (for example, a formula keyed to damages, injury severity, or participation terms), make sure those inputs map cleanly into DocketMath’s required fields.

3) Use Nevada’s default timing period from Rule 23

DocketMath uses jurisdiction-aware rule logic. For Nevada, that logic is anchored to Nev. R. Civ. P. 23. The key constraint for this guide is:

• No claim-type-specific sub-rule was found.
• Therefore, DocketMath applies the general/default period associated with the Rule 23 framework for allocation-related timing.

Operational takeaway: use a single default timing period in your inputs and model structure unless your dataset is explicitly designed for claim-type splits and your DocketMath rule logic supports that. In this Nevada setup, the allocator is expected to use one general/default timing period, not multiple claim-type-specific periods.

4) Enter data and run the calculation

In DocketMath:

1. Paste or enter claimant/group data into the allocator input section.
2. Set the total settlement amount and the allocation base.
3. Re-check that your selections show Jurisdiction = US-NV and that the tool indicates Nevada/Rule 23-based behavior.
4. Click Calculate.

After calculation, review at least the following outputs:

• Total allocated amount vs. the settlement amount
• Per-claimant (or per-group) allocated shares
• Rounding/residual handling, if the tool reports it

5) Validate output behavior against your settlement terms

DocketMath will produce an allocation distribution, but you’re responsible for consistency checks. Use a quick validation checklist:

• Sum check: Allocations sum to the settlement total (or follow the tool’s residual handling—then confirm that residual behavior matches what your settlement agreement expects).
• Eligibility check: Each claimant included in the dataset is eligible under the settlement’s participation criteria.
• Cap/limit check: Any exclusions or caps should be reflected correctly through your inputs (not applied twice).
• Timing check: The timing period used in the allocator matches the Rule 23 general/default period assumption (since no claim-type-specific sub-rule was identified for this workflow).

6) Export results and document the run

When your numbers match the expected structure:

1. Export the allocation output from DocketMath.
2. Save the run settings, especially:

   • Jurisdiction: US-NV
   • Any timing reference fields used
   • How the allocation base and claimant weights were defined
3. Keep the claimant list and allocation base definitions together with the export so the scenario is reproducible.

This documentation step is what allows internal review (or an audit trail) to confirm how the allocation shares were computed under the same Nevada Rule 23 settings.

Common pitfalls

Settlement allocation projects fail less often due to arithmetic and more often due to input mismatch or rule-logic mismatch. Watch for these common issues when running DocketMath for Nevada (US-NV) under Nev. R. Civ. P. 23:

Pitfall checklist

• Wrong jurisdiction code: Running with settings intended for another jurisdiction can silently skew timing and allocation behavior.
• Inconsistent allocation base: If your claimant weights (or shares) are based on one definition (e.g., “eligible class members”) but your claimant list includes ineligible persons, outputs won’t align with the settlement’s intended population.
• Double-counting caps/limits: If you apply caps/limits in preprocessing and again via DocketMath inputs, allocations may be overstated or artificially compressed.
• Residual differences ignored: If rounding leaves a small leftover amount, confirm the tool’s residual handling matches how your settlement agreement intends to treat residuals.
• Eligibility criteria not reflected: Settlement documents often exclude categories (e.g., certain opt-outs, inactive accounts, or disqualified claim submissions). Make sure those exclusions are removed (or flagged appropriately) before running.
• Missing timing context: If the tool expects timing-related fields, leaving them blank or inconsistent can shift output assumptions away from your intended model.

A quick “sanity check” table

Use this during review:

Try it

You can run a quick first pass in DocketMath to see how the Nevada setup affects results.

Suggested “first run” workflow

1. Open /tools/settlement-allocator
2. Set Jurisdiction = Nevada (US-NV)
3. Enter:

   • a small test dataset (e.g., 5–20 claimants or groups),
   • a known total settlement amount, and
   • an allocation base you already trust
4. Click Calculate
5. Compare the output with:

   • the allocation method described in your settlement agreement, and
   • the expectation that Nev. R. Civ. P. 23 uses a general/default period (not claim-type-specific timing)

What to look for after you calculate

• Per-claimant allocations respond predictably when you adjust claimant weights.
• Changing the total settlement amount scales allocations proportionally (unless caps/limits are triggered).
• Timing-related settings remain consistent with the Rule 23 default-period logic.

If results look “off”:

• reduce complexity (fewer inputs),
• confirm US-NV is selected,
• then reintroduce eligibility filters and caps/limits one at a time.

Related reading

• How to calculate Settlement Allocator in Ohio — Full how-to guide with jurisdiction-specific rules
• How to calculate Settlement Allocator in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Settlement Allocator in Philippines — Worked example with real statute citations