How to run Damages Allocation in DocketMath for Utah

6 min read

Published April 15, 2026 • By DocketMath Team

Step-by-step

Below is a practical walkthrough for running Damages Allocation in DocketMath for Utah (US-UT). This focuses on jurisdiction-aware settings—especially the Utah statute of limitations (SOL) baseline that DocketMath uses when your workflow includes time-based damage logic.

Note: This guide explains how to configure and run DocketMath. It’s not legal advice and doesn’t determine the outcome of any particular claim.

1) Open the calculator

  1. Go to DocketMath’s Damages Allocation tool: **/tools/damages-allocation
  2. Confirm the jurisdiction is set to Utah (US-UT).

If you don’t see a jurisdiction selector, look for a settings panel or a jurisdiction field within the tool. The key is ensuring Utah rules are applied for the run.

2) Enter the core timeline inputs

Damages allocation commonly depends on when damages accrued and/or what time window is potentially recoverable under the applicable SOL logic.

Use the fields shown in the tool UI, such as:

  • Accrual date (sometimes labeled “date of injury” or “event date,” depending on how the calculator is worded)
  • Filing date (sometimes labeled “date suit filed”)
  • Optional damage start/end dates or a damages period breakdown, if the tool supports partial-period allocation

Because Utah’s general SOL baseline is:

…you’ll typically align the “clock” like this: accrual/event date → filing date, and (if you provide damages periods) ensure the damages period boundaries match the timeline your scenario intends to measure.

Warning: Don’t mix date meanings. If the calculator asks for an accrual date, don’t enter something else (like a payment date) unless the tool explicitly labels it that way.

3) Understand the Utah SOL assumption DocketMath will use

For this DocketMath setup, there is no claim-type-specific sub-rule identified. That means DocketMath will use the general/default SOL period.

So the baseline rule used for time-window calculations is:

Practically, that means:

  • If your filing date is more than 4 years after the accrual date, the tool may allocate a reduced or zero recoverable portion, depending on how it models the damages window.
  • If your filing date is within 4 years, the tool will likely allocate across the broader damage period you provided—again depending on whether your inputs include damage start/end dates or other period information.

4) Add damages inputs to be allocated

Next, enter the damages figures the calculator can apportion. Exact field names vary, but common inputs include:

  • Total damages amount (or multiple components, such as economic vs. non-economic, if supported)
  • Damage periods (e.g., damages accrue or worsen over time)
  • An allocation basis (for example, by date range, by event timeline, or by a provided schedule)

If the tool includes a periods table:

  • Add line items that cover the relevant timeframe.
  • Make sure each period’s start/end dates fit within (or intentionally extend beyond) the accrual-to-filing timeframe you entered in Step 2.

A helpful approach:

  • Define your full damages window (for example, from an event date through a later measurement date).
  • Let DocketMath apply the Utah 4-year general SOL window to determine what portion is included in allocation.

5) Run the allocation

Click the button such as Calculate / Run / Allocate (the label can differ).

While it runs, watch for:

  • Validation messages (missing dates, dates out of order, impossible ranges)
  • Any auto-applied SOL window output (e.g., “recoverable period” or similar wording)
  • Allocation outputs such as per-period amounts and a total allocated figure

6) Review outputs and iterate

After the run completes, check the output sections (if present), such as:

  • Recoverable period window (based on Utah’s 4-year general SOL logic)
  • Allocated damages by period (if the tool splits the claim into time slices)
  • Total allocated damages
  • Any differences vs. total claimed (sometimes shown as reduced/disallowed portions)

Then iterate carefully:

  • If you change the filing date, the recoverable window can shift.
  • If you change the accrual date, the SOL cutoff date shifts.
  • If you change the damage period boundaries, the allocation distribution can change even if the SOL window stays the same.

Pitfall to avoid: Updating only the damages amounts (but not the dates) won’t change what portion is included/excluded by the SOL-based window. To change inclusion/exclusion, update the relevant timeline inputs.

Common pitfalls

Use this checklist to avoid mistakes that most often distort damages allocation results in Utah runs:

DocketMath is using 4 years under Utah Code § 76-1-302 as the general/default period (no claim-type-specific sub-rule was found for this setup). Even a small shift can move the filing date across the “within 4 years vs. more than 4 years” threshold. If the tool allocates by periods, period start/end dates should overlap the intended accrual-to-measurement timeframe. If DocketMath prorates by time slice, damages that fall outside the recoverable window may be reduced or excluded. If the calculator is left on a different jurisdiction, the SOL window—and therefore the allocation—can change dramatically.

Note: If your results look “too low,” don’t assume a bug first—verify the date inputs. In most workflows like this, the SOL window is usually the dominant driver.

Try it

Use these quick test scenarios to validate your workflow end-to-end (numbers are illustrative):

Open the Damages Allocation calculator and follow the steps above: Run the calculator.

If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.

Test 1: Within 4 years

  1. Set jurisdiction to Utah (US-UT).
  2. Enter:
    • Accrual date (choose an event/injury date in the recent past)
    • Filing date within 4 years of the accrual date
  3. Enter a damages window that extends beyond the accrual-to-filing range (so the tool has something to allocate).
  4. Run Damages Allocation.
  5. Review:
    • Whether the displayed recoverable period corresponds to a 4-year window based on the tool’s date model
    • Whether allocated totals reflect partial-period inclusion

Test 2: More than 4 years

Keep the damages inputs the same, but change filing date to be more than 4 years after the accrual date.

You should observe the allocatable “recoverable period” shrink significantly or disappear under the 4-year default rule tied to Utah Code § 76-1-302.

If the output doesn’t change when you adjust dates:

  • Double-check that you’re editing the correct date fields
  • Confirm the tool is applying the Utah (US-UT) jurisdiction logic you expect

Ready to run? Start here: **/tools/damages-allocation

Related reading