How to calculate Settlement Allocator in Utah

Quick takeaways

• Utah uses a Rule 23 settlement-allocation framework for class actions, so your “Settlement Allocator” is typically built to match the class notice / claims process under Utah R. Civ. P. 23 (US-UT).
• DocketMath’s Settlement Allocator calculator is designed to translate case-specific inputs (class definition, claims, and damages/participation measures) into an allocation aligned with how payments are distributed.
• No claim-type-specific sub-rule was found in the Utah rule text you’re working from—so treat Utah’s guidance as general/default, not a claim-type-specific ladder.
• If your allocation method could treat class members inconsistently, you should expect more scrutiny in a Rule 23 settlement context—so plan to document the “why” behind each input and weighting decision.

Inputs you need

Before you run DocketMath’s Settlement Allocator (start at /tools/settlement-allocator), gather inputs that match how the settlement will be administered in your case. In DocketMath, the allocator is only as accurate as the variables you feed it.

A. Class and settlement context (Utah R. Civ. P. 23)

Use inputs tied to the class action’s settlement administration:

• Class definition used for settlement purposes

  • Example inputs:

    • Number of class members (or estimated count)
    • Who is eligible (e.g., opt-in/opt-out status if applicable to your settlement design)
• Settlement fund amount

  • Total settlement to allocate (confirm whether it’s entered as net or gross per your administration plan, including fees/costs)
• Allocator denominator basis

  • The measure used to produce proportional shares (for example: claim value, economic loss proxy, participation units)

B. Allocation mechanics

You’ll typically need:

• Eligibility counts by participant bucket

  • Even if you don’t need “buckets” for the final math, grouping helps keep the calculation auditable.
• Claims or proof amounts per participant (or per bucket)

  • If your settlement uses a claims-based allocator, include:

    • Amount claimed (or capped amount)
    • Adjustments for verified documentation
• Caps, floors, or normalization rules

  • Common in practice:

    • Maximum allocation per claimant
    • Minimum threshold for filing a claim
    • Total-claim normalization so the fund fully distributes

C. Timing and periods (general/default, not claim-type-specific)

Utah Rule 23 is the starting point for settlement procedures, but the rule text you referenced does not identify claim-type-specific allocation sub-rules. That means:

• Use a general/default Rule 23 settlement administration approach rather than special periods by claim type.
• Any “period” inputs you include in DocketMath (if your settlement notice/administrator uses them) should reflect what the settlement notice and claims process actually sets—because this Utah material doesn’t break out distinct claim-type periods.

How the calculation works

DocketMath’s Settlement Allocator (US-UT) follows a proportional allocation model. Conceptually, the allocator converts your inputs into a share for each eligible participant (or bucket), so the total of shares equals (or approximates, after rounding) the settlement fund.

1) Choose the allocation basis (the “denominator”)

You start with a single allocation basis consistently applied:

• Denominator = sum of “allocation units” across all eligible participants

  • Allocation units might be:

    • Verified claim amounts
    • Claim amounts after reductions/caps
    • Another economic-loss proxy you can justify in the settlement administration

In DocketMath terms: provide the unit values for participants/buckets and the settlement fund to allocate.

2) Compute proportional shares

For each participant (or bucket), the raw share is:

• Raw share = (Participant units ÷ Total eligible units) × Settlement fund

If your settlement uses normalization (so total distributions exactly match the intended net fund), the tool can reflect that via the way you set the denominator and then scale/reconcile the outputs.

3) Apply caps, floors, or adjustments (if used by the settlement)

If you input caps or reductions, apply them in a way that matches your administration logic:

• Verification adjustments → determine final units
• Caps → reduce unit values if they exceed the cap
• Ensure the denominator reflects those final unit values (so proportionality stays consistent)

Then recalculate shares and distribute the net fund.

4) Rounding and reconciliation

Money math requires rounding. DocketMath typically includes a reconciliation step:

• Round each share to the chosen currency precision
• Adjust the remainder (commonly to the largest residuals or a designated bucket) so totals match the intended settlement distribution

5) Where Utah R. Civ. P. 23 fits (and what not to over-assume)

Utah’s governing authority here is Utah R. Civ. P. 23—the rule framework for class actions. In a settlement allocation context, that usually drives:

• the settlement process reflected in notice and administration mechanics
• the need for a coherent, documented method aligned with Rule 23 procedures

Also, per your requirement: no claim-type-specific sub-rule was found in the referenced Utah material. So:

• don’t build a claim-type-specific timing/period system into the allocator unless your settlement agreement/notice and administration plan explicitly require it
• treat the Utah rule guidance here as general/default rather than a claim-type ladder

6) Document your allocator inputs for defensibility

To keep a Rule 23 settlement allocation defensible, document:

• what “units” represent (economic loss proxy, claim amount, etc.)
• which verification and cap rules were applied (and when)
• how eligibility was determined
• how rounding reconciliation was handled

DocketMath supports this by tying outputs to your specific, auditable inputs.

Common pitfalls

Settlement allocation errors often come from math assumptions—not from the rule text alone. Watch these issues when using DocketMath for US-UT.

Pitfalls to avoid

• Using the wrong denominator

  • Example: mixing eligible units with ineligible claim amounts inflates the denominator and can distort shares.
• Double-counting reductions

  • If you apply verification reductions twice (once to “units” and again to “claimed amounts”), you can underpay or skew proportions.
• Not aligning caps with denominator timing

  • If caps are applied after the denominator is finalized, shares may exceed the intended distributable fund.
• Assuming claim-type-specific timing or math rules exist in Utah Rule 23

  • Your note is explicit: no claim-type-specific sub-rule was found in the cited material. Use a general/default approach unless the settlement documents provide a specific method.
• Rounding without reconciliation

  • Even small rounding drift can cause the sum of allocations to miss the intended settlement amount.
• Inconsistent eligibility criteria

  • If eligibility differs between the settlement notice and the allocator inputs, allocations may conflict with the settlement administration rules.

Sources and references

• Utah R. Civ. P. 23 (Class Actions) — Utah Rules of Civil Procedure
  https://legacy.utcourts.gov/resources/rules/urcp/urcp023.html

Next steps

1. Open DocketMath’s Settlement Allocator tool: /tools/settlement-allocator
2. Enter the settlement fund amount you intend to allocate (confirm whether the amount is net of fees/costs per your settlement administration plan).
3. Define eligibility and allocation units:

   • Provide claimant/bucket unit amounts
   • Apply caps/verification rules exactly once in the workflow (so you don’t double-reduce)
4. Run the calculation and review reconciliation output:

   • Ensure total allocated matches the intended fund
   • Check whether any bucket gets zero due to unit eligibility logic
5. Export your inputs/output for auditability:

   • Save the input dataset and summary so you can explain the allocator method in the Rule 23 settlement record.

If you want the fastest path, start with a small subset (e.g., top 10 buckets), verify denominators and reconciliation, then scale to the full dataset.

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