Worked example: Damages Allocation in Utah

Example inputs

This worked example shows how DocketMath (US-UT) can allocate damages when you’re modeling a multi-part claim in Utah using jurisdiction-aware time limits. This is a practical walkthrough of how the calculator behaves—not legal advice.

Here is a simple illustration for Utah. These values are for demonstration only and should be replaced with your actual inputs.

• Principal or amount: $100,000
• Rate or cap: 10%
• Start date: 2025-01-15
• End/as-of date: 2025-09-30

Assumptions for the example

You have two damage components that accrue over time:

• Component A: Property loss (e.g., damage to an item)
• Component B: Lost use / rental value (e.g., value lost because the property couldn’t be used)

Both components accrue over time on different date ranges, and you want to allocate which portions are likely recoverable based on Utah’s general statute of limitations.

Utah limitations rule used in this example

DocketMath uses a general/default limitations window because no claim-type-specific sub-rule was found in the provided jurisdiction data.

For this example, the general period is:

• 4 years under Utah Code § 76-1-302
• Reference (Utah Courts): https://www.utcourts.gov/en/legal-help/legal-help/procedures/statute-limitation.html

The dates and numbers you enter

Check the inputs below as they appear conceptually in the /tools/damages-allocation workflow:

How DocketMath interprets the time window

DocketMath allocates a portion of each component that falls inside the 4-year window.

Conceptually:

• SOL window = 4 years before the filing date
• Filing date = 2024-09-01
• Window start = 2020-09-01

So, any accrual before 2020-09-01 is treated as potentially time-barred for allocation purposes in this example (because the only rule available here is the general/default 4-year period).

Example run

Run the calculator from: **DocketMath → /tools/damages-allocation

Run the Damages Allocation calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

Step 1: Determine the SOL window

• Filing date: 2024-09-01
• General SOL: 4 years (Utah Code § 76-1-302)
• Window start: 2020-09-01

Step 2: Allocate Component A (property loss)

• Component A accrual: 2022-06-01 → 2023-08-15
• This entire accrual range falls within the 2020-09-01 to 2024-09-01 window.

Result: DocketMath allocates:

• Allocated A = 100% of $120,000 = $120,000

Step 3: Allocate Component B (lost use / rental value)

• Component B accrual: 2021-12-01 → 2023-08-15
• This also falls entirely within the same SOL window.

Result: DocketMath allocates:

• Allocated B = 100% of $60,000 = $60,000

Step 4: Total allocated damages

Output summary (what you’d expect DocketMath to show)

• Time-bar allocation adjustment: $0 reduced
• Total allocated damages: $180,000

Sensitivity check

To see how sensitive the allocation is to timing, tweak only one input: Component B accrual start.

To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.

Scenario: Component B starts earlier

Change just the Component B accrual start date:

• Keep everything else the same:

  • Component B accrual end: 2023-08-15
  • Total Component B damages: $60,000
  • Filing date: 2024-09-01
  • SOL window start: 2020-09-01

Now Component B spans two parts:

• Pre-window: 2020-06-01 → 2020-09-01
• Within-window: 2020-09-01 → 2023-08-15

Component A stays unchanged:

• Allocated A = $120,000

Illustration of the allocation approach

DocketMath conceptually uses the overlap between the component’s accrual period and the SOL window to allocate a proportional share of that component’s total damages.

A rough timeline view (for intuition):

• Total Component B span: 2020-06-01 → 2023-08-15 ≈ ~1,184 days
• Within-window span: 2020-09-01 → 2023-08-15 ≈ ~1,091 days

Inside-window ratio:

• 1,091 / 1,184 ≈ 0.921

Estimated allocated Component B:

• $60,000 × 0.921 ≈ $55,260

Updated total

What changed—and why

• The filing date did not change.
• The SOL window start remains 2020-09-01 under the general rule (Utah Code § 76-1-302).
• Moving Component B’s start earlier causes part of its accrual period to fall outside the SOL window.
• Result: DocketMath reduces the portion of Component B allocated to the actionable period, while Component A remains fully inside the window.

Checklist for using this sensitivity method

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