Pre/Post-Offer Damages Split Guide for Utah

What this calculator does

Run this scenario in DocketMath using the Pre Post Offer Damages calculator.

DocketMath’s Pre/Post-Offer Damages Split guide and tool help you sort damages into two time-based buckets for Utah matters involving an offer (for example, an offer of judgment or similar settlement offer, depending on your context). The core concept is a time split:

• Pre-offer damages: the portion of damages that accrued before the offer date.
• Post-offer damages: the portion of damages that accrued on or after the offer date (or a court-defined “effective” date tied to the offer).

Then, the calculator produces a split and can be used to support downstream calculations like interest and totals based on which phase the damages belong to.

Utah timing framework used here (civil limitations backdrop)

Utah generally uses a 4-year statute of limitations for many civil actions:

• Utah Code § 76-1-302 — 4 years (with exceptions, including a specific “P4” exception noted in Utah’s legal-help materials)

Source reference:

• Utah Courts legal help: https://www.utcourts.gov/en/legal-help/legal-help/procedures/statute-limitation.html

When to use it

Use this calculator when your damages need to be categorized according to whether they accrued before or after a particular offer date, which is common in disputes where a procedural event changes the financial consequences of settlement.

Typical triggers include:

• You have daily/monthly accruing damages (e.g., rent, use and occupancy, certain interest components, or other time-based measures) and you want to allocate them cleanly around the offer date.
• Your model requires separate treatment of damages before versus after the offer.
• You have a damages start date (when accrual began) and an offer date (when the time split starts).

Quick “fit check” (Utah)

If all of the following are true, the split approach usually fits well:

• You can identify:

  • A damages accrual start date (e.g., date of injury, breach, default, or first measurable loss)
  • An offer date
  • A damages end date (or a date used for the calculation period)
• The damages you’re splitting are time-based (or at least can be reduced to time-based components).
• You need a clear pre/post allocation to match how the court or agreement treats damages around offers.

Step-by-step example

Below is a practical example you can mirror using DocketMath.

Example facts (Utah)

Assume you’re calculating damages for a claim period based on time accrual:

• Accrual start date: 2022-01-15
• Offer date: 2023-06-01
• Calculation end date: 2024-12-31
• Daily damages amount: $125.00 per day
• Cap/limits: None for this example (but you’ll want to apply any contract or court limitations in your workflow)

DocketMath then splits the time between:

1. Pre-offer period = accrual start → day before offer date
2. Post-offer period = offer date → calculation end date

Step 1: Confirm your date boundaries

For a split driven by an offer date:

• Pre-offer includes accrual through 2023-05-31
• Post-offer starts on 2023-06-01

That means your days are separated cleanly at midnight boundaries (in practice, your system should treat dates consistently—DocketMath’s calculations assume date-based day counts).

Step 2: Compute number of days in each bucket

Compute “days” as the number of calendar days that fall within each range:

• Pre-offer days: 2022-01-15 through 2023-05-31
• Post-offer days: 2023-06-01 through 2024-12-31

To keep this concrete, here’s the idea (DocketMath will do the math based on its day-count convention):

• Pre-offer days = (days from 2022-01-15 up to but not including 2023-06-01)
• Post-offer days = (days from 2023-06-01 through 2024-12-31 inclusive)

Step 3: Multiply by the daily damages rate

Once days are known:

• Pre-offer damages = Pre-offer days × $125.00/day
• Post-offer damages = Post-offer days × $125.00/day

Step 4: Add any non-daily components (if applicable)

If you have:

• a lump-sum item (e.g., replacement cost), and
• a time-based item (e.g., continuing loss),

you’d typically:

• allocate the lump-sum entirely to whichever period it belongs to, and
• apply the daily split to the time-based component.

DocketMath’s output will be driven primarily by the inputs you give it—so make sure the daily rate reflects only the portion that truly accrues per day.

Step 5: Check against the Utah limitations backdrop (quick sanity test)

Utah’s general limitations framework often includes Utah Code § 76-1-302 (4 years), referenced in Utah Courts’ legal-help materials. That matters because your calculated period might include days outside what’s recoverable.

For example:

• If your accrual start date is 2019-01-01 and your calculation is being used in 2024, a 4-year lookback could cut off a portion even if the offer split is correct.

Common scenarios

Use these scenarios to decide what inputs you should provide to DocketMath (and how the output will change).

1) Daily accruing damages with a single offer date

When you’ll use it: Most common.

• Inputs you’ll need:

  • accrual start date
  • offer date
  • calculation end date
  • daily amount

• Output behavior:

  • The total damages are split by day count.
  • Post-offer damages increase as the offer date moves earlier.

Checklist:

2) Offer date before accrual start date

What happens: Pre-offer period becomes empty.

• Pre-offer days = 0
• Post-offer days = whole accrual period

Practical effect:

• The tool will show 0 pre-offer damages and all damages post-offer, because nothing accrued “before” the offer relative to your defined start date.

3) Offer date after calculation end date

What happens: Post-offer period becomes empty.

• Post-offer days = 0
• Pre-offer days = whole accrual period

Practical effect:

• The tool will show 0 post-offer damages and all damages pre-offer.

4) Multiple damages streams (mixed units)

Example: You have:

• $125/day continuing damages, plus
• a $2,000 lump-sum repair at a specific date

Approach:

• Use DocketMath for the time-based portion.
• Add lump-sum outside (or pre-allocate it to the correct period) so you don’t mistakenly “double count.”

5) Limitations pressure (Utah Code § 76-1-302)

This guide references Utah’s 4-year statute of limitations framework under Utah Code § 76-1-302 (with exceptions noted in Utah Courts legal help).

How it changes your workflow:

• You may need to adjust your accrual start date used in the calculator to the earliest date that remains within the recoverable period for your claim.
• Your pre/post split could still be correct relative to the adjusted start date, even if the original accrual began earlier.

Tips for accuracy

To get reliable outputs from DocketMath (and reduce surprises), follow these practical rules.

Date discipline

Unit consistency

Validate boundary math

Even when the calculator handles the day counts, you can do quick checks:

Limitations awareness (Utah)

Utah’s 4-year statute of limitations referenced in Utah Courts legal help and tied to Utah Code § 76-1-302 can affect whether the “outer edges” of your modeled period are recoverable.

• If your accrual start is more than 4 years

Related reading

• Pre/Post-Offer Damages Split Guide for Alabama
• Pre/Post-Offer Damages Split Guide for Arizona
• Pre/Post-Offer Damages Split Guide for California