How Settlement Allocator rules vary in Utah

Settlement Allocator calculations in Utah depend less on “claim type” branching and more on how the settlement and class procedure define who is included and which timing window you use. In practice, DocketMath’s jurisdiction-aware rules can change which inputs matter most—especially for timing, opt-outs, and the boundaries of class membership—when a case proceeds under Utah R. Civ. P. 23.

To get started, use the calculator at /tools/settlement-allocator and make sure you select the correct jurisdiction (US-UT) before you enter any dates or assumptions about who falls within the settlement’s coverage.

What varies by jurisdiction

Even though settlement allocation approaches often look similar across states, Utah can differ in practical ways—particularly in (1) what rule is the procedural anchor, (2) what “period” you should treat as the default for allocator eligibility, and (3) whether you should apply a class-action procedural schedule rather than a claim-type-specific schedule.

1) Utah uses the class action rule in Utah R. Civ. P. 23

Utah’s key procedural source for class actions is:

• Utah R. Civ. P. 23 (general class action rule)
  Source: https://legacy.utcourts.gov/resources/rules/urcp/urcp023.html

When DocketMath is set to US-UT, it effectively treats URCP 23 as the starting point for how the class is handled procedurally—certification, notice, objections, and the framework for who ends up bound by the class process.

2) Utah’s default allocator period is not claim-type-specific (per available sub-rule evidence)

For this Utah guidance, no claim-type-specific sub-rule was found for the period logic discussed. That means you should treat URCP 23’s relevant general/default period as the controlling approach when you set the allocator’s timing window in DocketMath.

Practical takeaway:
When you see a “period” input in DocketMath for Utah, map it to the general/default class-action timing structure under URCP 23, rather than trying to select a different period based on claim category.

3) Inputs that change outputs in Utah allocator runs

In DocketMath, changing certain inputs can materially alter allocator outcomes in a Utah case—especially under a class-action procedural framework:

• Class definition / eligibility date boundaries (what counts as “in class”)
• Notice/objection timeline assumptions (which can shift practical inclusion/exclusion behavior)
• Opt-out mechanics (who is treated as excluded from allocation vs. included)
• Settlement fund categories (if the settlement agreement divides money into buckets)
• Number of participating class members (which affects the per-person allocation math, depending on the method)

In short: for Utah, the allocator configuration tends to be more sensitive to class-process dates and inclusion criteria than to claim-type branching—at least under the general/default period approach described above.

What to verify

Before you rely on a Utah (US-UT) DocketMath output, verify these items against your case file and settlement documents.

Checklist for a Utah (US-UT) DocketMath run

• Confirmed jurisdiction selection: US-UT selected in /tools/settlement-allocator
• URCP 23 procedural posture: the case is actually proceeding as a Rule 23 class action (not a different procedural vehicle)
• Default period mapping: the DocketMath “period” logic matches the URCP 23 general/default period approach (no claim-type-specific override)
• Class membership definition: the settlement defines class members by one or more of:

  • specific conduct dates,
  • claim submission dates, or
  • membership status at a defined cutoff
• Notice mechanics: the dates you input match the notice schedule described in the settlement record
• Opt-out treatment: confirm whether opt-outs are excluded from allocation (and how they’re handled in the denominator)
• Approval order instructions: the settlement allocation must track what the court authorizes in the approval/implementation order

Inputs to sanity-check against the settlement record

If DocketMath requests date ranges, these should be traceable to documents you can point to in the case:

• Settlement approval timeline (or the effective date used for class eligibility)
• Cutoff date(s) for inclusion/exclusion
• Any opt-out deadline referenced in the notice/order
• Any participation/claim form deadline (if the settlement uses one)

Even when the tool provides a computational approach, URCP 23 compliance still depends on whether your assumptions match the procedural reality and the settlement’s actual terms.

A quick “rule confidence” check

Because the available evidence does not establish a claim-type-specific allocator period for Utah, your confidence is highest when your allocator configuration uses one consistent timing window based on URCP 23’s general/default period.

If a settlement agreement includes claim-category-specific timelines, treat that as a contractual/court-order instruction and ensure DocketMath reflects those explicit instructions—rather than inventing a “URCP 23 claim-type” rule override.

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