Abstract background illustration for How to run Damages Allocation in DocketMath for Utah

How to run Damages Allocation in DocketMath for Utah

7 min read

Published June 4, 2026 • By DocketMath Team

Partially verified

older_than_packet

Step-by-step

Below is a practical walkthrough for running Damages Allocation in DocketMath for Utah (US-UT), using jurisdiction-aware rules tied to Utah’s comparative fault and several liability framework. This guide focuses on how to use the tool and how Utah law affects the allocation logic—not on legal strategy.

1) Start the correct calculator

  • Open DocketMath → Damages Allocation
  • Go directly to the tool here: /tools/damages-allocation
  • Confirm the jurisdiction selector is set to Utah (US-UT)

Note: Utah’s comparative fault “bar” is governed by Utah Code Ann. § 78B-5-818, and Utah’s several liability concept is governed by Utah Code Ann. § 78B-5-820. Those two rules drive whether the plaintiff can recover and how the damages are split.

2) Enter the allocation inputs DocketMath needs

You’ll typically provide inputs for each party (usually including the plaintiff and every defendant you want counted). The most common inputs are:

  • Fault percentages (or fault weights that DocketMath converts)
  • Damages pool (or separate components, depending on your case setup)
  • Which party is “recovering” (the tool uses this to apply the fault-bar logic)

Use this checklist to keep inputs consistent:

Checklist

  • Enter every fault-bearing defendant you want included in the comparative-fault denominator.
  • Enter plaintiff fault (if the plaintiff is the recovering party in your scenario).
  • Ensure your fault entries match the way DocketMath expects them (e.g., percent format vs. weights), so the tool’s normalization matches your intent.
  • Enter the total damages amount you want allocated (or confirm each component totals correctly to your intended pool).

3) Understand Utah’s key allocation rules used by the tool

Utah’s framework has two features that can strongly affect results:

A) The comparative-fault recovery bar (50% bar) under Utah Code § 78B-5-818

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

Operationally in an allocation tool, that means:

  • If plaintiff fault ≥ combined defendants fault, DocketMath should output $0 recovery for the plaintiff’s share.
  • If plaintiff fault < combined defendants fault, recovery is allowed and allocation proceeds using fault proportions.

B) Several liability under Utah Code § 78B-5-820

Utah follows a several liability concept, meaning defendants are generally responsible only for their allocated share, not the full amount as joint-and-several would allow.

In practice, your output will typically show:

  • Each defendant receiving an allocated amount based on their fault share, subject to the plaintiff’s eligibility under § 78B-5-818.
  • The plaintiff’s recovery (if not barred) reflecting allocation after accounting for the plaintiff’s fault.

Pitfall: It’s easy to unintentionally change the outcome when your fault inputs don’t reflect the parties you intended to include. If you omit a defendant or mis-enter fault, the § 78B-5-818 comparison can flip, and the plaintiff can move from “not barred” to “barred” (or vice versa).

4) Run the calculation

  • Click Calculate / Run allocation
  • DocketMath computes:
    • Whether the plaintiff is eligible to recover under § 78B-5-818
    • The translation from percent to dollars for each party
    • The final allocated damages by party (consistent with several liability concepts under § 78B-5-820)

5) Review the outputs in a Utah-aware way

When results appear, check these items first:

Output categories to look for

  • Plaintiff barred? (driven by § 78B-5-818)
  • Plaintiff allocated $ amount / share (if the plaintiff is not barred)
  • Each defendant’s allocated $ amount / share (several liability—defendants typically receive only their allocated portion under § 78B-5-820)

Quick interpretation table

Output checkWhat it means under Utah rulesWhat to do if it seems wrong
Plaintiff recovery = $0Plaintiff fault ≥ combined defendants fault under § 78B-5-818Re-check fault inputs and confirm all defendants are included in the denominator
Defendant amounts look “reduced”Several liability: each defendant is responsible for their share under § 78B-5-820Confirm you entered the intended total damages and didn’t double-count components
Percentages don’t add up as expectedTool may normalize or require a specific input formatAdjust inputs to match DocketMath’s expected fault entry method (percent vs. weights)

6) Export or save your work (for repeatability)

If you plan to test multiple scenarios:

  • Save the run
  • Compare results across alternative assumptions, such as:
    • different fault allocations
    • different damages pools / components

Note: This guide assumes the general/default period for allocation logic because no claim-type-specific sub-rule was found. In other words, DocketMath’s Utah allocation behavior here is based on the default comparative fault and several liability framework rather than any claim-type carve-out.

Common pitfalls

Watch for these issues, which commonly cause confusing or inconsistent allocation results in Utah:

  1. Forgetting to include all fault-bearing parties

    • If you omit a defendant, the “combined fault of all defendants” comparison in Utah Code Ann. § 78B-5-818 can change.
    • Result: the plaintiff may become barred/not barred unexpectedly.
  2. Mixing raw fault scores with percentages

    • If your inputs aren’t in the exact format DocketMath expects, the tool may normalize differently than you intended.
    • Result: output fault percentages (and therefore dollar allocations) may not match your scenario.
  3. Misunderstanding what “50% bar” means

    • Utah’s test is not “plaintiff fault alone is 50%.”
    • The key is whether plaintiff fault equals or exceeds the combined defendants fault under § 78B-5-818.
  4. Expecting joint-and-several outcomes

    • Utah uses several liability principles under Utah Code Ann. § 78B-5-820, so each defendant typically receives only their allocated share.
    • Result: you may expect one defendant to cover more than their share; DocketMath will usually not reflect that in a several-liability allocation.
  5. Changing the damages number without keeping components consistent

    • If you enter separate damages components, ensure they sum to the total damages pool you intend to allocate.
    • Result: the allocation percentages may be correct, but the dollar totals won’t match your intended pool.

Warning: Small changes in fault inputs near the § 78B-5-818 threshold can produce large changes in outputs—especially whether the plaintiff is barred from recovery.

Try it

If you want a quick Utah-focused trial run in DocketMath:

  1. Open Damages Allocation: /tools/damages-allocation
  2. Set Jurisdiction: Utah (US-UT)
  3. Enter fault inputs for:
    • the plaintiff (if applicable)
    • each defendant you want included
  4. Enter:
    • a single total damages amount (or components, if your workflow uses components)
  5. Run the calculation
  6. Do one quick sensitivity test:
    • Adjust plaintiff fault up or down slightly (for example, 1–5 percentage points)
    • Recalculate
    • Check whether the plaintiff crosses the § 78B-5-818 bar and whether defendant allocations shift primarily based on their fault shares (consistent with several liability under § 78B-5-820)

For reference, the Utah legal anchors used in this workflow are:

  • Utah Code Ann. § 78B-5-818: comparative fault recovery bar (plaintiff fault ≥ combined defendants fault → barred)
  • Utah Code Ann. § 78B-5-820: several liability (defendants liable only for their share)

Disclaimers: This is tool guidance and general educational information, not legal advice.

Source (for § 78B-5-818 text): https://le.utah.gov/xcode/Title78B/Chapter5/78B-5-S818.html

Related reading