How Offer Of Judgment Analyzer rules vary in Utah

What varies by jurisdiction

Run this scenario in DocketMath using the Offer Of Judgment Analyzer calculator.

Offer of judgment rules can change in two big ways: (1) timing rules for making the offer and (2) the legal consequences if the offer is accepted or rejected. In Utah, DocketMath’s Offer Of Judgment Analyzer uses jurisdiction-aware logic keyed to Utah Code Ann. § 78B-6-320.

Utah’s statute authorizes offers of judgment in civil actions generally:

“A party may make an offer of judgment in a civil action…”
Source: Utah Code Ann. § 78B-6-320, https://le.utah.gov/xcode/Title78B/Chapter6/78B-6-S320.html

Utah timing rule: default/general period (no claim-type-specific sub-rule found)

In Utah, the guidance you’ll see implemented in DocketMath should treat the rule as general/default. No claim-type-specific sub-rule was found for § 78B-6-320 based on the information provided for this brief.

What that means in practice: the analyzer should apply the statute’s general offer period rather than a special shortened/extended deadline tied to a specific category of claim. So, if you’re expecting a different deadline because of the type of civil case, the tool should not apply that kind of claim-type variation unless your workflow separately encodes it.

How “outputs” change when you change jurisdiction inputs

When you run the Offer Of Judgment Analyzer for US-UT, the computed results (for example, flags showing whether the offer timing is within the allowable window, and the offer-vs-judgment outcome comparison) are driven by the inputs you provide, commonly including:

• Case stage / offer date (and whether it falls within the allowed period)
• Offer amount
• Ultimate judgment value you want the tool to compare against the offer
• Acceptance / rejection handling (if your workflow captures those timing or outcome details)
• Costs/fees posture (if your workflow includes those values in the comparison)

If you switch jurisdictions (or even switch between different court settings or docket configurations), the analyzer can adjust the allowable offer window and related outcome comparison logic—even if your entered offer amount stays the same.

Pitfall (timing first): If DocketMath flags an “out of time” offer in Utah, don’t assume the math is wrong. The first place to check is whether the offer date you entered fits Utah’s general/default period under § 78B-6-320. Timing is often the most jurisdiction-sensitive variable.

Key Utah citation used by the analyzer

• Utah Code Ann. § 78B-6-320 (Offer of judgment in civil actions)
  https://le.utah.gov/xcode/Title78B/Chapter6/78B-6-S320.html

Because the statute text is general (and no claim-type-specific sub-rule was identified here), DocketMath should treat Utah’s offer-of-judgment timing as the default rule under § 78B-6-320.

To start the tool, use: /tools/offer-of-judgment-analyzer

What to verify

Before relying on any computed “best outcome” signal from DocketMath, verify the details that most often cause Utah offer-of-judgment calculations to diverge from what the actual docket supports. (This is not legal advice—just practical input-checking guidance.)

1) Confirm the statute applies to your civil action

Utah’s framework in § 78B-6-320 authorizes offers of judgment in civil actions. If your matter doesn’t fit the civil offer-of-judgment mechanism contemplated by the statute, the analyzer’s assumptions won’t match reality.

Quick checklist:

Reference: Utah Code Ann. § 78B-6-320
https://le.utah.gov/xcode/Title78B/Chapter6/78B-6-S320.html

2) Validate the offer window using your specific timeline

Because Utah’s rule here is treated as general/default (no claim-type-specific sub-rule found), your biggest data-quality risk is usually a timeline mismatch.

Verify in the docket:

3) Match the “judgment value” concept to what the comparison should mean

Offer-of-judgment frameworks typically compare the offer amount to the ultimate result to determine statutory consequences. In practice, “ultimate judgment” can vary in what it includes (e.g., damages only vs. damages plus certain categories).

To reduce mismatches:

4) Keep your tool inputs consistent with Utah’s statute workflow assumptions

DocketMath’s Offer Of Judgment Analyzer can only score what you input. For Utah, keep your inputs anchored to the assumptions implied by § 78B-6-320:

• general civil offer-of-judgment timing (default rule)
• offer-vs-judgment comparison using your entered “judgment value”

If you use DocketMath, start from the calculator entry point so you can match the calculator’s expected fields:

• Primary CTA: /tools/offer-of-judgment-analyzer

Related reading

• Offer of Judgment Analyzer Guide for Alabama
• Offer of Judgment Analyzer Guide for Arizona
• Offer of Judgment Analyzer Guide for Colorado