How to calculate pre/post-offer damages split in Utah

Quick takeaways

• Utah uses a pre/post-offer split based on offer timing: once the defendant makes an offer and it’s not accepted, costs can shift depending on whether the plaintiff’s final judgment is not more favorable than the offer.
• The core rule is Utah Code § 78B-3-203, which addresses cost responsibility after the offer was made.
• In DocketMath (tool name: pre-post-offer-damages), you define the offer date, enter your damages to be split, and the tool calculates pre-offer vs. post-offer components for your reporting.
• Utah’s rule here is default/general: if you don’t have authority suggesting a claim-type-specific modification, don’t assume one.

Inputs you need

To calculate the split in DocketMath for Utah (US-UT), gather these inputs first. Having them ready prevents mismatches between your settlement offer timeline and your damages timeline.

1) Offer and judgment timing

• Offer date (the date the defendant’s settlement offer was made)
• Decision date or judgment date (usually when the court entered final judgment)
• Optional but helpful:

  • Acceptance date (if accepted; otherwise you’ll be in the “not accepted” analysis path)
  • Any amended judgment date (if damages changed post-trial)

2) Damages numbers

You need enough detail to split damages by time:

• Total claimed/awarded damages (the figure you plan to split)
• Pre-offer damages amount (damages attributable to the period before the offer date)
• Post-offer damages amount (damages attributable to the period after the offer date)

If you don’t already have pre/post allocations, you can still use DocketMath—but you’ll need a defensible way to allocate damages by time (for example, a damages ledger keyed to dates or a timeline-based accrual method).

3) Costs-sensitive threshold info (from § 78B-3-203)

Section 78B-3-203 triggers based on relative favorability and whether the offer was not accepted. To complete that trigger analysis, you’ll need:

• Settlement offer amount (and any meaningful terms affecting “favorability,” such as whether it’s effectively capped or structured)
• Final judgment amount (and how that number compares to the offer)

Because § 78B-3-203 depends on whether the plaintiff’s final judgment is “not more favorable than the offer,” you can’t finalize the cost-shift narrative without this comparison.

How the calculation works

DocketMath’s pre-post-offer-damages workflow is designed to split damages into period components depending on whether they accrue before or after the offer date. Then, separately, Utah’s statute determines whether costs after the offer shift based on the offer/judgment comparison.

Step 1: Use the correct Utah rule set (general/default)

Utah Code § 78B-3-203 sets a general framework. In plain terms, the statute looks for the following conditions:

• the defendant makes an offer of settlement that is not accepted, and
• the plaintiff’s final judgment obtained is not more favorable than the offer

If both are met, the plaintiff is responsible for costs incurred after the offer was made.

Source (Utah Code § 78B-3-203): https://le.utah.gov/xcode/Title78B/Chapter3/78B-3-S203.html
Statute text (summary): “If the defendant makes an offer of settlement that is not accepted, and the final judgment obtained by the plaintiff is not more favorable than the offer, the plaintiff is responsible for the costs incurred after the offer was made...”

Your brief review notes that no claim-type-specific sub-rule was found. That means you should treat this as the default/general period for the pre/post logic unless your case file points to a different governing authority.

Step 2: Split damages in DocketMath using the offer date

In DocketMath, the operative split is:

• Pre-offer damages = the portion of damages attributable to dates before the offer date
• Post-offer damages = the portion of damages attributable to dates on or after the offer date

A practical sanity check:

• Total damages = Pre-offer damages + Post-offer damages
• Your split inputs should reconcile with the court’s award figures as closely as your allocation method allows

If your totals don’t reconcile, the arithmetic may still run—but your model may not match the underlying award structure used for reporting.

Step 3: Tie the damages split to Utah’s “costs after the offer” trigger

Even though the statute is about costs (not damages), the timeline concept matters for consistent reporting. Under § 78B-3-203, costs incurred after the offer are shifted to the plaintiff when:

• the offer was not accepted, and
• the final judgment is not more favorable than the offer

To use this correctly with your DocketMath output, keep the two parts aligned:

1. Use DocketMath to generate your pre-offer vs. post-offer damages breakdown.
2. Separately apply § 78B-3-203 using your offer vs. final judgment comparison to determine whether the “costs after the offer” condition applies.
3. Document the comparison plainly: offer amount, final judgment amount, and a one-sentence conclusion about whether the judgment is “more favorable” or “not more favorable.”

Step 4: Produce a consistent settlement-impact summary

Once the tool calculates the split, you can report period impacts like:

• Pre-offer component: $[pre-offer]
• Post-offer component: $[post-offer]
• Statutory cost trigger (per § 78B-3-203): applies / does not apply based on the offer/judgment comparison

This keeps your reporting auditable because the period split is grounded in the offer date, while the cost-shift logic is grounded in the statutory favorability threshold.

Common pitfalls

These are the issues that most often cause incorrect splits or inconsistent Utah pre/post-offer reporting.

1. Using the wrong “offer date”

   • The split should be keyed to when the offer was made, not when it was received, discussed, or entered on a docket.
   • If your offer date doesn’t match your document timeline, your pre/post allocations can drift.

2. Assuming claim-type-specific logic without support

   • Your brief research indicates no claim-type-specific sub-rule for this Utah framework.
   • Don’t create special sub-period logic unless you have additional authority that requires it.

3. Ignoring the “not accepted” condition

   • § 78B-3-203 requires the offer to be not accepted.
   • If an offer was accepted (fully or in a way that changes the procedural posture), the cost narrative may differ.

4. Misstating “more favorable than the offer”

   • The statutory test uses a relative comparison.
   • If your model compares inconsistent numbers (e.g., judgment figures that exclude amounts included in the offer, or vice versa), you can accidentally flip the trigger.

5. Failing to reconcile totals

   • Pre + post should reconcile to the damages total you entered.
   • DocketMath can compute the split once your inputs are set—but it can’t correct inconsistent underlying allocations.

Sources and references

• Utah Code § 78B-3-203 (general rule regarding settlement offers and responsibility for costs incurred after an unaccepted offer when the final judgment is not more favorable):
  https://le.utah.gov/xcode/Title78B/Chapter3/78B-3-S203.html
• TODO (if your case needs it): Confirm whether any additional Utah procedural rules or case-specific authorities modify how “favorability” is assessed in your context.

Next steps

1. Open DocketMath’s calculator: /tools/pre-post-offer-damages
   (Primary CTA: /tools/pre-post-offer-damages)
2. Enter the offer date and verify it matches the settlement offer document.
3. Reconcile damages totals:

   • confirm Total = Pre + Post
   • spot-check entries that fall exactly on the offer date and apply your chosen “inclusion” rule consistently
4. Apply the § 78B-3-203 trigger using offer vs. final judgment:

   • document the comparison and whether the judgment is “more favorable” or “not more favorable”
   • confirm the offer was not accepted
5. Export or record a clean period summary for reporting:

   • pre-offer vs. post-offer damages
   • the cost trigger conclusion tied to § 78B-3-203

Related reading

• How to calculate pre/post-offer damages split in California — Full how-to guide with jurisdiction-specific rules
• How to calculate pre/post-offer damages split in Florida — Full how-to guide with jurisdiction-specific rules
• How to calculate pre/post-offer damages split in New York — Full how-to guide with jurisdiction-specific rules