How to estimate car accident settlements in Utah

Direct answer

You can estimate Utah car accident settlements by running a comparative-fault damages allocation under Utah Code Ann. § 78B-5-818 and then applying Utah’s default 50% bar rule: a plaintiff whose fault equals or exceeds the combined fault of all defendants is barred from recovery (often called a “50% bar”).

In practice, your settlement estimate usually starts with projected total damages (e.g., medical bills, lost wages, property damage, and pain and suffering), then is reduced based on the fault percentages assigned—except that once the § 78B-5-818 threshold is met, the plaintiff’s recoverable amount can drop to $0.

What you need to know

For Utah, settlement estimation through DocketMath typically depends on two linked concepts:

1. Comparative fault affects whether any recovery is allowed (the § 78B-5-818 bar)

   • Utah applies comparative fault and sets a recovery threshold tied to the plaintiff’s fault relative to the combined fault of all defendants.
   • The “equals or exceeds” language matters: at the cutoff, recovery is barred.

2. Several liability affects “who pays what” (Utah Code § 78B-5-820)

   • Utah generally treats each defendant as liable only for their share of responsibility.
   • With multiple defendants, this can affect settlement posture and allocation negotiations.

Default rule scope (clear callout)

No claim-type-specific sub-rule for damages allocation was found in the provided statute excerpt. This article therefore uses the general/default comparative-fault framework under Utah Code Ann. § 78B-5-818 (and the several-liability concept under § 78B-5-820) as the governing approach.

Step-by-step

Use this workflow to estimate fault-based settlement value in Utah using DocketMath’s damages-allocation calculator.

1) Gather the inputs that drive the number

Break your estimated total damages into components you can reasonably estimate:

• Medical expenses (past)
• Future medical (if you have a basis)
• Lost wages (past)
• Lost earning capacity (future, if supported)
• Property damage
• Non-economic damages (pain and suffering, etc.—often modeled with a negotiable lump estimate)

Record your best estimate of total estimated damages (before fault reduction).

2) Identify each at-fault party you expect to be compared

DocketMath typically requires assigning fault percentages to the people/entities in the crash scenario.

• Include the plaintiff fault and each defendant fault you expect the factfinder could assign.
• Ensure your scenario is coherent—fault percentages should be set up so they can total to ~100% for the allocation inputs.

Even in a “simple” crash, you’ll usually still allocate between the injured party and at least one other driver/entity.

3) Run the Utah § 78B-5-818 “50% bar” check

Utah Code Ann. § 78B-5-818 provides the comparative-fault rule that bars recovery when the plaintiff’s fault is at least as large as the combined fault of all defendants.

Use this estimation logic:

• combined defendant fault = 100% − plaintiff fault
• If plaintiff fault ≥ combined defendant fault, then recovery is barred (for allocation purposes, your plaintiff recovery estimate can become $0).

Practical takeaway: the “bar zone” is where plaintiff fault approaches 50% (and in multi-defendant scenarios, what matters is still whether the plaintiff is at or above the combined defendant share).

4) Allocate damages with DocketMath when not barred

When the plaintiff is not barred, DocketMath uses the fault allocation inputs to produce an allocation-based recoverable damages estimate.

In an estimation workflow, your main tasks are:

• Provide realistic fault percentages based on available evidence.
• Provide damages components you want the allocation to apply to.
• Review the calculator output, then adjust inputs for sensitivity (next step).

5) Do sensitivity testing around fault (negotiation realism)

Because fault is often disputed, run quick “what if” tests:

• Increase plaintiff fault (e.g., 40% → 45% → 50%) to see when the § 78B-5-818 bar triggers.
• Decrease defendant fault if your evidence supports a shift.

This helps you understand the “risk zone” near the statutory threshold and gives you a defensible way to present a range rather than a single-point number.

6) Convert the allocation estimate into a settlement range

Once you have a recoverable damages estimate from DocketMath:

• Compare it to practical settlement factors (policy limits/coverage structure, evidentiary strength, and negotiation dynamics).
• If you’re modeling a range, consider:

  • a low-fault / high-recovery scenario
  • a high-fault / lower-recovery scenario

Use the calculator

• Primary CTA: /tools/damages-allocation

Key statutes and citations

Comparative-fault bar: Utah Code Ann. § 78B-5-818

Utah’s Liability Reform Act governs comparative fault and sets the recovery threshold under § 78B-5-818.

• Statute reference: https://le.utah.gov/xcode/Title78B/Chapter5/78B-5-S818.html
• Core rule for estimation: a plaintiff is barred from recovery when the plaintiff’s fault equals or exceeds the combined fault of all defendants.

For estimation, the recoverability condition is commonly expressed as:

• plaintiff fault ≥ (100% − plaintiff fault)

This creates the well-known “50% bar” concept in two-party comparisons, and the same cutoff logic still applies in multi-defendant settings because the comparison is against combined defendant fault.

Several liability: Utah Code Ann. § 78B-5-820

Utah generally applies several liability under § 78B-5-820, meaning each defendant is liable only for their share of responsibility rather than being jointly responsible for the full allocated amount.

Why it matters for estimation:

• In multi-defendant crashes, fault allocation can change which defendants appear most valuable to settle with (based on their percentage share and real-world collectability/limits).

Common pitfalls

• Forgetting the § 78B-5-818 bar condition

  • If the plaintiff’s fault hits or exceeds the combined defendant fault, an estimate that still assumes recovery is usually inconsistent with the statute’s threshold.

• Fault percentages that don’t reconcile to a coherent allocation

  • Inputs should be consistent. Incoherent totals can produce misleading outputs.

• Treating “fault” like “injury severity”

  • Fault percentages are about liability attribution, not how serious the injuries are.

• Misapplying “combined fault” logic

  • The bar is based on the plaintiff vs. combined defendant comparison—so look beyond a simple “under/over 50%” assumption, especially with multiple defendants.

• Overrelying on a single damages estimate

  • Pain and suffering, future care, and earning-capacity components often involve assumptions. Run at least two scenarios.

Run the numbers

Quick input checklist (for your DocketMath run)

• Total estimated damages (pre-fault): $_________
• Plaintiff fault %: _________
• Defendant(s) fault % (should be set up to reconcile with plaintiff fault): _________
• Number of defendants: _________
• Optional: alternate fault sets for sensitivity testing: _________

Bar-check you can do before the calculator

1. Compute combined defendant fault = 100% − plaintiff fault
2. If plaintiff fault ≥ combined defendant fault, plaintiff recovery is barred under § 78B-5-818

Example scenario structure (estimation only)

• Pre-fault damages estimate: $60,000
• Fault inputs:

  • Plaintiff: 45%
  • Defendant(s): 55% combined
• Result direction:

  • Not barred → an allocation-based recoverable amount should be available for estimation.

Then test the boundary:

• Plaintiff 50% vs. Defendant(s) 50% combined
• Result direction:

  • Bar threshold reached → plaintiff recovery estimate can become $0.

Related reading

• How to calculate Damages Allocation in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Damages Allocation in Philippines — Worked example with real statute citations
• Inputs you need for Damages Allocation in Philippines — Input checklist with sourcing guidance