How to calculate Damages Allocation in Utah

Quick takeaways

• In Utah, damages allocation in most cases follows comparative fault with a “50% bar”: if the plaintiff’s fault equals or exceeds the combined fault of all defendants, the plaintiff is barred from recovery under Utah Code Ann. § 78B-5-818.
• Utah also uses several liability principles (each defendant is generally responsible for their individual share) under Utah Code Ann. § 78B-5-820, which informs how totals get split across defendants.
• No claim-type-specific sub-rule was identified in the source review. That means the steps below reflect Utah’s general/default comparative-fault allocation approach rather than a specialized rule for a particular cause of action.
• DocketMath’s damages-allocation tool helps you compute:

  • whether the plaintiff clears the 50% bar, and
  • each defendant’s proportional responsibility when recovery is allowed.

Inputs you need

Before you run DocketMath → /tools/damages-allocation, collect the inputs needed to apply Utah’s comparative-fault rules correctly—especially the fault totals.

A. Parties and fault percentages

For each relevant actor, gather a fault figure (often a percentage) for:

• Plaintiff fault %
• Each defendant fault %

Also note the source and format:

• Did the numbers come from a jury/verdict allocation, bench findings, or a settlement allocation?
• Are the fault numbers already normalized to 100%, or do they sum to a different total due to rounding or data export?

B. Fault total framework (what the tool uses)

You’ll need to compare:

• Combined defendant fault % = Σ (all defendants’ fault %)
• Plaintiff fault % compared to the combined defendant amount for the 50% bar analysis (Utah’s test is plaintiff vs. combined defendants, not plaintiff vs. a standalone “50%” label)

C. Damages to allocate (your monetary base)

Provide the damages amount(s) that you want allocated:

• A single total damages figure, or
• Multiple damage buckets (e.g., economic vs. noneconomic) if your workflow requires separating categories

Common practical workflow: allocate a single total damages figure using the fault-derived proportions. If you have multiple buckets and you enter them separately in the tool, confirm the reduction logic is applied consistently with how you intend to present the results.

D. Optional validation checks (highly recommended)

• Do plaintiff + Σ defendants match what your record indicates?
• Are very small percentages included (they can affect cents-level rounding)?
• If you’re using court findings, confirm the fault breakdown includes the plaintiff as required for the comparative-fault test.

How the calculation works

DocketMath applies Utah’s comparative-fault framework and then uses Utah’s several-liability concept to split the reduced recovery across defendants. The key legal anchors are:

• Utah Code Ann. § 78B-5-818 (comparative fault / “50% bar”)
• Utah Code Ann. § 78B-5-820 (several liability principle used to guide proportional allocation across defendants)

Step 1: Apply Utah’s “50% bar” test (comparative fault)

Under Utah Code Ann. § 78B-5-818, a plaintiff whose fault equals or exceeds the combined fault of all defendants is barred from recovery.

Operationally:

1. Compute

   • Defendant_total = Σ (Defendant fault %)
   • Plaintiff_total = Plaintiff fault %

2. Apply:

   • If Plaintiff_total ≥ Defendant_total → Recovery = 0
   • If Plaintiff_total < Defendant_total → proceed to proportional allocation

Because the statute uses “equals or exceeds”, exact 50/50 (and any equality) is a bar.

Step 2: Compute the plaintiff’s recovery share (when not barred)

When the plaintiff is not barred, Utah’s comparative fault reduces recovery in proportion to the fault mix.

A practical computation structure is:

• Plaintiff recovery % = (Defendant_total − Plaintiff_total) / Defendant_total

Equivalent intuition:

• The plaintiff’s fault reduces the recoverable portion, and the reduced amount is what gets allocated among defendants.

DocketMath uses this comparative-fault logic as part of the allocation workflow. Knowing the structure helps you sanity-check outputs.

Step 3: Allocate damages across defendants (several-liability concept)

If recovery is allowed, Utah’s several-liability approach means defendants generally pay based on their individual shares, not as one “group payer.”

Math approach consistent with proportional splitting:

1. Compute each defendant’s share of total defendant fault:

   • Defendant_i share % = Defendant_i_fault / Defendant_total

2. Allocate damages:

   • Allocated damages_i = Total damages × Plaintiff recovery % × (Defendant_i share %)

So:

• If the plaintiff is barred → all allocations should effectively be zero.
• If not barred → defendant allocations should sum to the plaintiff-reduced total you provided (subject to rounding).

Step 4: Normalization, rounding, and data consistency

Fault percentages might be:

• already normalized to 100%,
• slightly off due to rounding,
• or provided as fractions that need conversion.

DocketMath’s proportional approach generally works as long as the relative ratios among fault figures are consistent. Still, rounding can affect final dollar cents on large damage amounts.

A practical QA checklist:

• Confirm your inputs define a consistent fault set.
• If your record provides percentages, prefer entering the most precise numbers available before rounding.
• Ensure your defendant list matches the record’s comparative-fault set.

Default vs. special sub-rules

This Utah guide uses the general/default comparative-fault allocation steps. No claim-type-specific sub-rule was identified for overriding the core method. If your case involves a specialized legal framework not covered here, you may need to adjust how inputs are interpreted or how the comparative-fault set is determined.

Common pitfalls

Use this section as a quick quality-assurance checklist before relying on DocketMath’s output.

• Triggering the bar incorrectly

  • Don’t compare plaintiff fault to a standalone 50% threshold.
  • Under § 78B-5-818, compare plaintiff fault vs. combined defendant fault.

• Missing the equality rule

  • If Plaintiff fault = Combined defendant fault, the plaintiff is barred because the statute uses “equals or exceeds.”

• Using an incomplete defendant fault pool

  • If a defendant included in the fault findings is omitted, Defendant_total becomes wrong, which cascades into:

    • the bar determination, and
    • every defendant’s allocated share.

• Double-rounding

  • Avoid converting and rounding multiple times (e.g., raw verdict → rounded percent → rounded again). Use one consistent rounding step when needed.

• Mixing fault sources

  • Don’t combine fault numbers from different stages or standards (e.g., some parties from verdict allocation and others from a later estimate). Keep the fault figures from the same allocation record when possible.

• Assuming joint-payment

  • Several liability affects allocation across defendants; don’t assume one defendant effectively “covers” the whole reduced amount.

• Splitting damages buckets inconsistently

  • If you enter multiple damage categories, ensure your workflow applies the same fault-based reduction logic to each bucket in the way you intend.

Sources and references

• Utah Code Ann. § 78B-5-818 (Liability Reform Act of 1986; comparative fault / 50% bar)
  https://le.utah.gov/xcode/Title78B/Chapter5/78B-5-S818.html
• Utah Code Ann. § 78B-5-820 (several liability concept referenced for proportional splitting across defendants)

Next steps

1. Gather plaintiff fault % and each defendant fault % from the same comparative-fault record.
2. Compute/confirm:

   • Defendant_total = Σ defendants
   • the comparative comparison needed for the § 78B-5-818 bar test
3. Choose your damages base:

   • one total figure, or
   • separate buckets (if your workflow requires it)
4. Run DocketMath → /tools/damages-allocation with those inputs.
5. Validate the results with a quick self-check:

   • If the bar condition is met, allocations should be zero.
   • If not barred, defendant allocations should sum to the plaintiff-reduced total (within expected rounding).
6. Save/export the output for your internal workflow.

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