How to interpret Damages Allocation results in Utah

What each output means

Run this scenario in DocketMath using the Damages Allocation calculator.

When you run DocketMath → Damages Allocation for Utah (US-UT), the tool applies Utah’s general limitations period to estimate which portions of your alleged damages are likely time-barred versus potentially recoverable under a 4-year framework.

In Utah, the default/general rule is the 4-year statute of limitations under Utah Code § 76-1-302 (see Utah Courts’ overview: https://www.utcourts.gov/en/legal-help/legal-help/procedures/statute-limitation.html).

Important scope note: No claim-type-specific sub-rule was found for this calculator setup, so DocketMath keeps a consistent general/default 4-year period rather than switching limitation logic based on a particular claim label.

You’ll typically see outputs that map to these ideas:

1) “Time-barred” vs. “Potentially recoverable” amounts

• Time-barred amount: Portions of alleged damages that fall outside the 4-year lookback window from the calculator’s trigger date logic (i.e., the date the tool treats as starting the limitations clock).
• Potentially recoverable amount: Portions that fall within the 4-year window.

In other words, the calculator is doing a timeline allocation: “How much of the total losses occurred inside the last 4 years (per the tool’s date rules) versus before?”

2) Allocation into date buckets (if your run shows them)

Some runs display totals in date buckets, commonly something like:

• “within the last 4 years,” and
• “older than 4 years.”

If you see buckets, interpret them as:

• Bucket totals contribute to your overall “within limitations” and “outside limitations” numbers.
• Any minor differences usually come from boundary handling (for example, how the tool treats exact cutoff dates) and the date inputs you provided.

3) Percentages and the “net effect”

If DocketMath shows a percentage (e.g., “X% likely within limitations”):

• treat it as a ratio of allocated amounts in the calculator’s model, not a guarantee you can recover that entire “potentially recoverable” portion.
• small input changes can move dollars across the 4-year boundary, which can shift the percentage.

Gentle disclaimer: This output is for interpretation and planning based on a general limitations framework. Utah courts can apply fact-specific accrual rules and other procedural doctrines not captured by a default timeline allocation. Use this as a guide for where to look and what to verify, not as legal advice.

What changes the result most

If you want to understand why your “within limitations” and “outside limitations” totals move, focus on these Utah-relevant levers.

These inputs have the biggest impact on the final number. Adjust them one at a time if you need a sensitivity check.

• date range
• rate changes
• assumption changes

Highest-impact drivers in Utah

What Utah Code § 76-1-302 means for your output

Because Utah’s general rule is 4 years, DocketMath’s Utah-aware allocation uses a four-year cutoff anchored to:

1. the tool’s trigger date logic, and
2. the dates you enter for when damages occurred.

And because this is the general/default framework (no claim-type-specific sub-rule applied here), you should expect the calculator to keep the same 4-year structure across runs, rather than changing limitation logic due to how a claim is labeled.

Boundary-date sensitivity (the “why did it flip?” effect)

Even with a straightforward 4-year rule, results can change sharply when:

• a damage date falls exactly on/near the cutoff,
• multiple date ranges overlap, or
• your inputs are off by a month (or sometimes even fewer days).

If the output looks unusually sensitive, rerun with a corrected date (even by a small amount) and compare bucket totals—DocketMath will usually make it clear which dollars moved across the boundary.

Practical tip: If you only input a single “event date” for all damages, you may blur how much loss occurred recently versus earlier. When possible, allocate using the most defensible loss/damage dates so the 4-year allocation is more meaningful.

Next steps

Use DocketMath’s results as a verification checklist—not a final determination.

1. Confirm the trigger date logic

• Identify the date the tool treated as the clock starter.
• If you have multiple plausible trigger candidates, run a couple of scenarios and compare changes in the “potentially recoverable” total.

1. Audit the damage timeline

• Separate damages into the most defensible date ranges.
• Pay special attention to entries close to the 4-year boundary.

1. Sanity-check totals

• If buckets are shown, confirm bucket sums match the overall totals.
• Check for gaps or overlaps in your entered ranges that could distort the allocation.

1. Document what drove the numbers Create a short internal note including:

• the trigger date used,
• the date ranges tied to each damage amount,
• the resulting within limitations and outside limitations totals.

This helps you explain differences between iterations when you update inputs.

1. Know what the general rule captures—and what it might miss Utah Code § 76-1-302 supports the general 4-year limitations framework referenced above, but real cases can involve additional issues (including accrual and procedural doctrines) that aren’t reflected in a default allocation model. Treat the tool’s output as structured interpretation of the general framework.

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for Alaska — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules