How to calculate Settlement Allocator in Nevada

Quick takeaways

• Nevada settlement allocation for class settlements is grounded in Nev. R. Civ. P. 23—you’re applying the general class-action framework for fairness and allocation rather than relying on a special “claim-type” allocator rule.
• In DocketMath’s Settlement Allocator (US-NV), you typically:

  1. calculate a relative weight per class member, then
  2. convert those weights into dollar allocations that sum to the allocable pool.
• Your results depend mainly on two inputs:

  • the allocation basis you choose (equal shares, exposure, transactions, composite, etc.)
  • the eligibility/population counts and how excluded members are handled
• No claim-type-specific sub-rule was found for Nevada beyond the general/default class-action framework described by Nev. R. Civ. P. 23. Treat the workflow as general unless your settlement agreement or court guidance specifies a different allocation approach.
• Use DocketMath to produce an allocation that is reproducible, internally consistent, and easy to document for transparency.

Inputs you need

Before you run DocketMath’s /tools/settlement-allocator, collect these inputs. For Nevada, this workflow is framed within Nev. R. Civ. P. 23 (general class-action fairness/allocation concepts), rather than a claim-type-specific rule.

A. Settlement and allocation setup

• Total settlement amount (numeric)
• Fee and cost amounts you intend to treat separately (numeric), if applicable

  • If you net them out, be consistent: either

    • allocate gross first and then subtract fees/costs, or
    • allocate net directly.
• What’s in scope for class-member payments

  • If your settlement includes approved set-asides (e.g., certain administrative amounts), note how they are handled so your tool’s “allocable pool” matches the intended distribution.

B. Eligibility and population counts

• Total number of eligible class members (count)
• A list of class members (or claimant groups) with:

  • a unique identifier
  • eligibility status (eligible / not eligible / excluded)
  • the numeric components you’ll use for weighting (or fields you’ll derive from)

C. Allocation basis (the “weighting” inputs)

In DocketMath, the Settlement Allocator converts your weighting inputs into allocation weights. Choose a basis that matches the settlement’s distribution logic.

Common approaches:

• Equal-share weighting

  • Weightᵢ = 1 for each eligible member
• Transaction-based weighting

  • Weightᵢ = number of eligible transactions
• Exposure-based weighting

  • Weightᵢ = exposure proxy (e.g., total purchases, estimated loss proxy)
• Time/probability weighting

  • Weightᵢ = duration of exposure or another participation probability measure
• Composite weighting

  • Combine components (e.g., Weightᵢ = exposure × time multiplier, or exposure + transaction component)

D. Nevada jurisdiction framing (documentation-focused)

Your methodology should be documented as consistent with Nev. R. Civ. P. 23 class settlement principles (fairness and reasonableness). Practically, that means:

• you explain why the chosen weighting basis reasonably reflects participation/exposure as defined by the settlement
• you show how eligibility/exclusion rules were applied consistently across records

Also remember: no claim-type-specific sub-rule was found for Nevada in addition to the general/default class-action framework—so treat the approach as general unless specified otherwise.

How the calculation works

DocketMath’s Settlement Allocator for US-NV follows a standard, explainable workflow. You can use this structure to check your inputs and confirm outputs.

Step 1: Establish the allocable pool

Compute the amount available for class-member allocations.

A common structure is:

• Allocable Pool = Total Settlement − Fees/Costs (if treated separately) − Any approved set-asides

DocketMath’s tool settings should mirror your settlement’s distribution math. The key is consistency: the pool you input should be the pool you intend to distribute.

Step 2: Compute each class member’s allocation weight

For each eligible class member i:

• Weightᵢ = f(eligibility + weighting inputs)

Examples:

• Equal-share: Weightᵢ = 1
• Transactions: Weightᵢ = eligible transaction count
• Exposure: Weightᵢ = exposure amount (purchases, estimated loss proxy, etc.)
• Composite: Weightᵢ = (exposure component) × (time multiplier) or exposure + transactions

Step 3: Sum all weights

• Total Weight = Σ Weightᵢ (sum across eligible members)

If Total Weight = 0, DocketMath can’t produce meaningful allocations. That usually signals:

• a mapping/eligibility issue
• missing weighting inputs
• an unexpected filter that excluded everyone

Step 4: Convert weights into dollar allocations

For each eligible class member i:

• Allocationᵢ = (Weightᵢ / Total Weight) × Allocable Pool

This produces dollar amounts that (within rounding) reconcile to the allocable pool.

Step 5: Handle ineligible or excluded members

For members marked excluded/ineligible:

• Allocationᵢ = 0
• and they should not be included in Total Weight, so they don’t dilute the pool.

Step 6: Document the Nevada “why” using Nev. R. Civ. P. 23

Because Nevada’s framework is treated as general/default here, your documentation should connect:

• the mechanical weighting choice (the “how”)
• to the settlement’s described fairness rationale (the “why”)
• using Nev. R. Civ. P. 23 as the anchoring authority for class settlement handling

Practical tip: Even if the formula is mechanical, explain what your weighting proxy represents (participation, exposure, or another settlement-defined concept).

Common pitfalls

These issues commonly cause allocation results to drift away from the intended settlement logic in Nevada (US-NV) using DocketMath.

• Including excluded members in Total Weight

  • If excluded/ineligible records accidentally remain in the denominator, eligible members receive smaller allocations.
• Mixing weight units without normalization

  • Example: Some weights are transaction counts while others are dollars, and you add them as if comparable.
• Rounding drift

  • If you round per-member amounts too aggressively outside the tool, totals may not reconcile to the allocable pool. Always reconcile sums after export.
• Assuming Nevada has claim-type-specific allocation sub-rules

  • Here, no claim-type-specific sub-rule was found beyond the general/default framework rooted in Nev. R. Civ. P. 23. Treat your method as general unless settlement/court guidance provides specifics.
• Ignoring the settlement agreement’s defined allocation basis

  • The best math can still be wrong for the settlement if your weighting inputs don’t match the settlement’s participation criteria, time window, or netting rules.

Pitfall example: Switching from equal shares to exposure-based weights after importing data—without re-validating eligibility mapping and time windows—can lead to allocations that don’t match the settlement’s narrative.

Sources and references

• Nev. R. Civ. P. 23 — Nevada Rules of Civil Procedure (class actions; settlement framework)
  https://www.leg.state.nv.us/CourtRules/NRCP.html

Next steps

1. Open DocketMath’s Settlement Allocator: /tools/settlement-allocator
2. Select (or configure) the allocation basis that matches your settlement’s distribution logic:

   • equal shares vs. transactions vs. exposure vs. composite
3. Validate eligibility mapping:

   • confirm excluded members are not included in Total Weight
   • confirm the eligible count matches your class definition
4. Run the calculation and reconcile totals:

   • verify that exported member allocations sum to the intended allocable pool (accounting for rounding)
5. Export results and create an audit trail:

   • keep a mapping table: Weightᵢ inputs → computed Allocationᵢ
   • reference Nev. R. Civ. P. 23 to explain the Nevada class-action context, noting this is a general/default approach unless the settlement or court guidance states otherwise

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