Settlement Allocator Guide for Utah

What this calculator does

Run this scenario in DocketMath using the Settlement Allocator calculator.

DocketMath’s Settlement Allocator (Utah) helps you break a settlement amount into category buckets you might need for downstream tasks like drafting settlement language, structuring records, or preparing forms that depend on how money is characterized.

In Utah, one frequent driver for allocation is statute of limitations timing—especially when the parties debate whether a claim is time-barred. Utah generally uses a 4-year limitations period for certain civil actions under Utah Code § 76-1-302, with a referenced exception described as “P4” in Utah’s own plain-language court resources (see “Related reading” for the Utah Courts link).

This guide is designed to help you understand how to feed numbers into the /tools/settlement-allocator tool and interpret the output in a way that’s useful for case-management and documentation. It does not provide legal advice.

Typical outputs you’ll generate

Most allocator workflows boil down to:

• Total settlement (the gross amount)
• A set of allocated amounts by category (e.g., damages vs. other components)
• Residual / reconciliation (to make sure totals match)

Your inputs change your outputs by:

• Shifting the division of the settlement among categories
• Adjusting the remaining balance to keep the numbers consistent with the total

When to use it

Use DocketMath’s Settlement Allocator when you have a settlement figure but need a defensible, consistent breakdown for paperwork, negotiation drafts, internal accounting, or recordkeeping.

You may want allocation in these Utah-facing situations:

1) You’re tracking timing against Utah’s 4-year limitations framework

If your settlement discussion touches the viability of claims, the limitations clock often becomes part of the negotiation context. Utah provides a general 4-year statute of limitations period referenced by Utah’s court resources under Utah Code § 76-1-302.

• SOL Period: 4 years
• Utah Code: Utah Code § 76-1-302
• Utah Courts reference: https://www.utcourts.gov/en/legal-help/legal-help/procedures/statute-limitation.html
  (Utah’s page also notes an exception described as P4.)

Even if the settlement is reached, many parties still allocate because they want their documentation to reflect what was being addressed during the case.

2) You need totals to reconcile for later documentation

Settlements often come with:

• Payment components that differ in label or purpose
• Attorney fees or costs tracked separately
• Releases tied to certain “heads” of damages

Allocator tools reduce errors like:

• Category amounts that don’t sum to the total settlement
• Missing balances that later create accounting mismatches

3) You’re dealing with multiple claims or “mixed” settlement terms

When a settlement resolves:

• Multiple alleged damages categories, or
• Disputes about both liability and amounts

…allocation helps you keep the settlement narrative consistent across drafts.

Step-by-step example

Below is a practical example using the Utah setup in DocketMath’s /tools/settlement-allocator.

Scenario

Assume a settlement is agreed at $120,000. You want to allocate it among three categories for documentation:

• Economic damages: $70,000
• Non-economic damages: $40,000
• Other / allocation residual (e.g., administration or miscellaneous components): $10,000

Checklist before entering numbers

• Confirm the gross settlement total (here: $120,000)
• Decide category labels you’ll use consistently in your paperwork
• Ensure category amounts add up to the total

Step 1: Enter the settlement total

• Total settlement: 120,000

Step 2: Enter category allocations

• Economic damages: 70,000
• Non-economic damages: 40,000
• Other / residual: 10,000

Step 3: Run the calculator

When you submit, the tool typically:

• Computes category totals
• Verifies whether the categories reconcile with the total settlement
• Produces an output breakdown you can copy into your settlement documentation workflow

Example output (conceptual)

Step 4: Validate against timing context (Utah)

If your settlement discussion includes statute-of-limitations timing considerations, anchor your internal timeline to Utah’s referenced framework:

• 4-year period referenced for Utah Code § 76-1-302
• Utah Courts plain-language resource: https://www.utcourts.gov/en/legal-help/legal-help/procedures/statute-limitation.html

Common scenarios

Settlement allocation gets used in recurring patterns. Here are common scenarios and how you’d typically think about inputs and outputs in Utah.

Scenario A: You know the total, but category numbers are estimates

What you enter

• Total settlement (exact or agreed)
• Category estimates (based on your records or negotiation terms)
• A residual category (so the math reconciles)

What you get

• A breakdown that sums to the total
• Residual amount that absorbs estimation differences

When to choose this approach

• Negotiations are still “papering” the deal
• Parties haven’t agreed on exact valuation but want a consistent structure

Scenario B: Categories are known, but the settlement total includes fees or costs

What you enter

• If your settlement total includes items you’ll label separately, decide up front:

  • Include them in a category bucket, or
  • Treat them as part of “Other / residual” (consistent labeling matters)

What you get

• Output totals that reconcile cleanly
• Less chance of later disputes over whether your allocation omitted an amount

Scenario C: Mixed claims—some likely time-barred, others not

Even though this guide is about allocation (not legal conclusions), Utah’s 4-year limitations reference under Utah Code § 76-1-302 often shows up in settlement talks.

What you enter

• Allocate based on the settlement terms the parties agreed to (not on a conclusion about “validity”)

What you get

• A settlement breakdown that matches the negotiated outcome
• A clearer record of what the settlement documents purport to cover

Scenario D: You’re drafting settlement language and need consistent categories

What you enter

• Category totals that align with the headings in your draft
• Ensure the sum equals the settlement total

What you get

• Output that can be pasted into:

  • A settlement spreadsheet
  • A term sheet reconciliation
  • Internal approval memos

Tips for accuracy

These steps help you get output you can trust enough for paperwork and reconciliation.

1) Make sure the categories reconcile to the total

Before you finalize the tool run, verify:

If your categories don’t reconcile, the allocator output will either:

• Flag the discrepancy, or
• Push the difference into the residual bucket (depending on the tool’s logic)

2) Use Utah-specific timing references for internal timelines

If the allocation discussion is tied to limitations context, ground your timeline using Utah’s referenced guidance:

• Utah Code § 76-1-302: 4 years
• Utah Courts plain-language page: https://www.utcourts.gov/en/legal-help/legal-help/procedures/statute-limitation.html
  (includes the P4 exception reference)

This doesn’t change your settlement math, but it keeps your documentation consistent with Utah’s stated framework.

3) Keep labels consistent across drafts

If your draft uses “non-economic damages,” don’t later swap to “pain and suffering” in an Excel sheet that’s used to reconcile to the final settlement agreement. Consistency reduces confusion if the deal is revised.

4) Document what “Other” means

If you use a residual or catch-all bucket:

• Assign a plain meaning (e.g., “miscellaneous administrative amounts”)
• Keep the label stable across documents

5) Use the allocator output as a reconciliation tool

A practical workflow:

1. Draft category numbers
2. Run the allocator
3. Review the reconciliation
4. Only then update settlement documentation headings

This prevents “late” changes that accidentally break the total.

Related reading

• Settlement Allocator Guide for Alabama
• Settlement Allocator Guide for Arizona
• Settlement Allocator Guide for California