Choosing the right Damages Allocation tool for Utah

Choose the right tool

Run this scenario in DocketMath using the Damages Allocation calculator.

Choosing the right Damages Allocation approach for Utah (US-UT) is less about doing the math perfectly and more about making sure your tool’s assumptions match the rules that govern what portions of damages are potentially recoverable. In practice, DocketMath’s damages-allocation calculator is your starting point—but in Utah, you should first narrow the time scope using the applicable limitations period, then allocate within that narrowed window.

Gentle note: This guidance is informational and tool-focused, not legal advice. SOL rules can vary by claim type and specific facts, so confirm the limitations period that applies to your situation before relying on results.

1) Start with the Utah time window (and keep it default unless you find a specific rule)

For Utah, the general baseline to anchor many civil claims is a 4-year statute of limitations (SOL). The Utah Courts’ legal-help page describes the baseline as 4 years, referencing Utah Code § 76-1-302.

Importantly, no claim-type-specific sub-rule was found in the material provided for this brief. That means you should treat the 4-year period as the general/default SOL unless you later confirm a different, claim-specific limitations rule applies.

Use this anchor:

• General SOL period: 4 years
• Statutory anchor: Utah Code § 76-1-302
• Source: https://www.utcourts.gov/en/legal-help/legal-help/procedures/statute-limitation.html

2) Use DocketMath to translate timelines into allocable damages

Once you’ve selected the proper limitations window, DocketMath helps translate your timeline into allocable amounts. The damages-allocation calculator is designed to allocate a total into time periods and/or categories based on inputs you provide (for example: dates, total damages, and how the damages should be distributed across segments).

A practical workflow is:

• Define the event dates that matter for damages (commonly the beginning of the damages period, and the end date you want to analyze).
• Apply the 4-year default SOL (Utah Code § 76-1-302) to decide what portion is potentially within reach.
• Allocate damages only within the allowed window, then interpret totals and breakdowns as “SOL-compliant” outputs.

If your damages span a long range, the limitations window is what prevents your allocation from “counting” amounts outside the recoverable period.

3) Know what DocketMath expects (inputs) and what it changes (outputs)

Even when Utah’s SOL baseline is the same, your allocation outcome changes depending on what you feed the calculator. That’s why you should treat your inputs as “jurisdiction-aware” data construction steps, not merely form fields.

Input checklist for DocketMath (damages-allocation)

Output checklist (what to verify after running the tool)

4) Pick the “right tool” behavior: SOL-filter first, allocation second

In Utah, the most common selection error is doing allocation first without narrowing the timeline—then using the allocation outputs as if they already exclude time periods outside the SOL. To avoid that, use a two-stage approach:

1. SOL filtering stage (time scope): Use the 4-year default under Utah Code § 76-1-302 unless you confirm a different period applies.
2. Allocation stage (distribution): Run DocketMath’s damages-allocation calculator using only the date range that falls within the chosen limitations window.

This order matters because allocating across the full span and then “mentally trimming” later can lead to inconsistent totals and breakdowns.

Quick example of how the SOL filter changes results

If your damages timeline runs 2018–2024, but only the last 4 years are within reach, your SOL-compliant window might effectively start in 2020 (depending on when the clock starts in your scenario). In that case, you should enter:

• Start date: 2020 (not 2018)
• End date: 2024 (or the last date you want included)

When you do this, DocketMath will change both:

• the recoverable total (the total attributable to the entered window), and
• the distribution across the calculator’s periods/categories.

5) Utah rule anchor (what you’re mapping into your tool)

Keep your Utah anchor explicit so your dates match your legal assumptions:

• General SOL period: 4 years
• Statutory anchor: Utah Code § 76-1-302
• Courts’ legal-help reference: https://www.utcourts.gov/en/legal-help/legal-help/procedures/statute-limitation.html

That’s the rule you’re operationalizing by constraining your damages date window before you allocate.

Next steps

Now that you understand the Utah “tool selection logic” (SOL window first, allocation second), use a repeatable process to generate allocations you can defend and re-check.

After you run the Damages Allocation calculation, capture the inputs and output in the matter record. You can start directly in DocketMath: Open the calculator.

Step 1: Confirm your SOL baseline before you run allocation

Start with the 4-year default under Utah Code § 76-1-302, then verify whether your claim type has an exception. Because this brief did not identify a claim-specific sub-rule, default to 4 years only if you can’t confirm a different limitations rule.

If you later discover a shorter or longer period applies, update your start/end dates accordingly before trusting the allocation output.

Step 2: Build SOL-compliant date ranges for DocketMath

Use the limitations window to construct your calculator inputs.

Practical range-building checklist

Then enter those SOL-filtered dates into /tools/damages-allocation.

Step 3: Run DocketMath and sanity-check the allocation

After you run /tools/damages-allocation, do quick checks to confirm the output matches your expectations about the timeline.

Sanity checks

If you are also working on a broader case timeline, you may want to align this with other date-driven tools available in DocketMath (for example, reviewing timeline math first) by using the tool index at /tools.

Step 4: Document inputs for reproducibility

A good allocation is not just a number—it’s a set of dated assumptions. Save:

• Utah baseline used: 4-year default SOL under Utah Code § 76-1-302
• DocketMath inputs:

  • start date (SOL-compliant)
  • end date (SOL-compliant)
• Total damages and how you broke out any components

This makes it much easier to rerun the calculator if you later confirm a claim-specific limitations rule.

Step 5: Use the outputs in a decision-ready way

Present DocketMath output as:

• Recoverable total (within the entered SOL window)
• Breakdown by period and/or category (as the calculator produces)
• A brief note on the date window used and that it reflects the Utah 4-year default unless you’ve confirmed otherwise

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