Workers compensation settlement guide for Utah

Direct answer

In Utah, workers compensation settlement discussions often require parties to talk about fault and damages allocation. A key liability rule that often drives whether a plaintiff can recover (or how recovery is reduced) is Utah’s comparative fault “50% bar” in Utah Code Ann. § 78B-5-818.

Because you asked for a jurisdiction-aware Utah guide and specifically mentioned DocketMath, this page explains how to model settlement allocation numbers using fault-based inputs, and how to stress-test the results around the 50% threshold.

What you need to know

Even when a workers compensation settlement is a compromise between specific parties, allocation modeling is frequently used to organize settlement value around:

• total claimed damages (the “pool”),
• fault percentages (who is responsible for what share), and
• the comparative fault rule that can restrict recovery when fault is too high.

The two core statute-driven concepts (as reflected in your jurisdiction data)

• Comparative fault bar (“50% bar”) — Utah Code Ann. § 78B-5-818
  Under § 78B-5-818, a plaintiff is barred from recovery if the plaintiff’s fault equals or exceeds the combined fault of all defendants.

  • Practical effect in a typical 100% fault setup: if the plaintiff is at 50% or more, recovery can be barred under this comparative-fault gate.

• Several liability / share-based allocation — Utah Code § 78B-5-820 (referenced in your excerpt)
  Several liability principles generally support the idea that each defendant’s exposure corresponds to that defendant’s share, rather than automatic joint responsibility for the whole loss.

No claim-type-specific sub-rule (scope note)

Your jurisdiction data states: no claim-type-specific sub-rule was found. That means the comparative-fault framework discussed here should be treated as the general/default rule set for the concept being modeled—not as a special rule limited to a particular workers compensation subtype.

Step-by-step

Use this workflow to prepare settlement allocation numbers using DocketMath with Utah’s fault gate in mind.

1) Gather the settlement math inputs (before using DocketMath)

For allocation/settlement modeling, you’ll typically need:

• Total claimed damages (or the total loss you plan to allocate)
• Fault percentages

  • Plaintiff fault %
  • Each defendant fault % (so you can compute combined defendant fault)
• Which damages buckets you’re allocating (as applicable)
• Any agreed-upon offsets/caps that the settlement terms impose (if your modeling is meant to match the settlement agreement)

Quick checklist

• Total damages amount is identified
• Plaintiff fault % is identified
• Defendants’ fault % are identified (and sum consistently in your model)
• Damages categories/buckets are identified (if you’re allocating beyond a single total)
• Offsets/caps are identified (if applicable)

2) Apply the Utah comparative-fault gate (the “50% bar” logic)

Under Utah Code Ann. § 78B-5-818, the modeling logic is:

1. Take plaintiff fault %
2. Compute combined defendants’ fault %
3. If plaintiff fault % ≥ combined defendants’ fault %, the comparative-fault bar may be triggered (i.e., recovery can be barred in the model logic)

How to translate that into common “percentage-of-100” terms
If your inputs are expressed as a complete fault picture totaling 100%, then:

• combined defendants’ fault % = 100% − plaintiff fault %
• the condition “plaintiff fault ≥ combined defendants fault” becomes:
  plaintiff fault ≥ 50%

3) Use DocketMath to run damages-allocation scenarios

Open DocketMath’s damages-allocation tool and enter your inputs. Your goal isn’t just “one answer”—it’s to see how changing fault assumptions changes the allocation outputs.

What to watch for in your outputs:

• whether the fault gate produces materially different modeled recovery/allocation,
• how shifts in plaintiff fault change the modeled shares,
• how sensitive the result is near the 50% boundary.

4) Model multiple settlement positions (not just one)

Because the comparative-fault rule is threshold-based, you should run at least three scenarios to understand risk and negotiation leverage:

• Scenario A (plaintiff-favorable): plaintiff fault below 50%
• Scenario B (boundary): plaintiff fault at/near 50%
• Scenario C (defendant-favorable): plaintiff fault at/above 50%

This helps you create a negotiation range and identify which inputs matter most under § 78B-5-818.

Practical warning: Around the 50% bar, small changes—like moving from 49% to 50%—can create major differences in modeled outcomes. Scenario testing is key.

5) Reconcile the tool outputs with settlement drafting and structure

Settlement documents often include terms that affect how the settlement is implemented even if your allocation math is consistent. Make sure the settlement agreement aligns with what you modeled, for example:

• the settlement amount and how it is broken into components (if itemized),
• payment timing,
• releases and compromises,
• treatment of medical costs or future care (if addressed),
• any allocation-language inside the settlement terms (if the agreement itemizes amounts).

Key statutes and citations

Statute link (as provided):

• https://le.utah.gov/xcode/Title78B/Chapter5/78B-5-S818.html

How to use § 78B-5-818 in a Utah allocation model (rule-of-thumb):

1. Start with fault percentages.
2. Check the threshold: plaintiff fault ≥ combined defendants’ fault.
3. If yes, apply the comparative-fault gate in your model logic.
4. If no, allocation proceeds based on the fault shares you input (and then you match any settlement-specific terms like offsets/caps).

Common pitfalls

Avoid these common modeling errors when using DocketMath for Utah fault-and-damages allocation:

• Fault percentages that don’t match your model convention
  If your inputs don’t sum cleanly (or don’t represent a consistent “100%” picture), the “equals or exceeds combined defendants’ fault” test under § 78B-5-818 becomes harder to apply.

• Not stress-testing around the 50% threshold
  The rule is threshold-based; near the line, outcomes can flip quickly. Always run boundary scenarios.

• Treating the fault logic as “automatic” without checking assumptions
  Settlement modeling is fact-dependent. Re-run scenarios when fault assumptions or damages buckets change.

• Confusing liability allocation with settlement payment mechanics
  The model helps organize the underlying allocation logic, but the settlement agreement governs how money is actually paid and released.

• Assuming a claim-type-specific comparative-fault variant exists
  Your scope note says no claim-type-specific sub-rule was found. Don’t invent a special workers compensation comparative-fault rule for a particular category without specific authority.

Run the numbers

Use DocketMath’s damages-allocation tool to translate your fault and damages inputs into allocation outputs that you can use for settlement math and scenario comparison.

1. Open the calculator: /tools/damages-allocation

2. Enter:

   • Total damages
   • Plaintiff fault %
   • Each defendant fault %
   • Any damages categories/buckets you’re modeling
   • Any offsets/caps required to reflect your settlement structure

3. Run at least three models:

   • Below the 50% bar
   • At/near the 50% bar
   • Above the 50% bar

Illustrative scenario templates (replace with your actual numbers):

• Scenario A: Plaintiff 40%, Defendants 60%
• Scenario B: Plaintiff 50%, Defendants 50%
• Scenario C: Plaintiff 55%, Defendants 45%

Then compare outputs to see how Utah Code Ann. § 78B-5-818 affects the allocation gate.

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