How to run Wrongful Death Damages in DocketMath for Utah

Step-by-step

This guide shows how to run Wrongful Death Damages in DocketMath for Utah (US-UT) using jurisdiction-aware setup and the Utah wrongful-death cause of action. DocketMath is designed to help model damages using calculator inputs; this post is practical and procedural, not legal advice.

1) Open the calculator

Start at the primary CTA:

• /tools/wrongful-death-damages

You’ll be able to enter case facts and assumptions, then generate a damages output.

2) Confirm the Utah wrongful-death basis (what the calculator is modeling)

Utah authorizes a wrongful-death action when a death is caused by another’s wrongful act or neglect. The Utah Code provides:

Utah Code § 78B-3-106 states that when the death of a person is caused by the wrongful act or neglect of another, “his heirs, or his personal representatives for the benefit of his heirs, may maintain an action for damages against the person causing the death.”

Source: https://le.utah.gov/xcode/Title78B/Chapter3/78B-3-106.html

What this means for your run in DocketMath: The statute is framed as an action “for the benefit of…heirs,” which aligns with a damages model focused on losses (economic and possibly non-economic), rather than a purely punitive concept.

3) Enter the wrongful-death damages inputs

In DocketMath’s Wrongful Death Damages tool, work through the inputs in the order the UI presents them. Common categories include:

• Decedent information

  • Age at death (often used to project remaining years in the calculator logic)
  • Any employment/income assumptions (if prompted)

• Economic loss assumptions

  • Earnings and/or wage replacement assumptions
  • Work-life participation assumptions (if requested)
  • Discounting factors (if the tool includes a time-value or rate input)

• Non-economic losses

  • Any non-economic component (if enabled in the tool)

• Cap/limitation switches (if present)

  • If DocketMath includes Utah-specific switches or toggles, use the Utah (US-UT) option for consistency.

If the interface offers a “jurisdiction” selector, choose US-UT. That helps ensure the tool uses the correct Utah-specific setup where applicable.

4) Set the default period logic clearly (Utah has a general default)

Your workflow should assume a general/default period unless DocketMath provides a claim-type-specific sub-rule.

Important for Utah runs: Based on the jurisdiction note provided, no claim-type-specific sub-rule was found for the period logic. Therefore, you should rely on the general/default period in the tool’s configuration for Utah.

5) Run the calculation and review the outputs

After you click the calculate/run action, DocketMath should produce:

• A total damages figure (often with separate economic/non-economic components)
• A breakdown showing how each entered input affected the result
• Any time-projection details (for example, year-by-year loss streams), if displayed

Use the breakdown to sanity-check the model:

• Did increasing income assumptions increase the economic component?
• Did changing a discount-related input (if available) meaningfully affect later-year contributions?
• Do the displayed categories match the inputs you provided?

6) Adjust inputs to see how outputs change

Utah wrongful-death modeling outputs (like most damages calculators) can be sensitive to life, income, and timing assumptions. Use small, controlled adjustments and compare outcomes.

Try these “what-if” levers:

• Age at death: often changes the modeled remaining years
• Annual income / wage replacement: scales economic losses
• Growth/stability assumptions: can increase or flatten projected streams
• Timing assumptions: if the tool asks when losses begin or how long they continue, it changes the modeled loss period

Quick checklist:

• Increase annual income slightly (e.g., +10%) → confirm economic totals increase
• Increase/decrease life expectancy inputs (via age) → confirm the modeled projection horizon changes as expected
• Adjust discount rate inputs (if present) → confirm the weighting of later years changes as expected

7) Document the run for reproducibility

Even with a calculator, your results depend on your entered assumptions. For future review, use a simple documentation method:

• Save screenshots of the input panels and the output summary
• Copy key assumptions into your case notes—especially:

  • age at death
  • income/wage replacement
  • any non-economic amounts/toggles
  • any discounting/rate inputs
  • any period selection showing “default” behavior

Reminder (not legal advice): DocketMath outputs are only as good as the assumptions you choose. Consider consulting a qualified professional for legal or evidentiary decisions.

Common pitfalls

These issues commonly distort wrongful-death damages outputs in DocketMath for Utah (US-UT).

1) Using the wrong jurisdiction setting

If your run uses a default jurisdiction other than US-UT, your output may reflect non-Utah assumptions or configuration.

• Confirm US-UT is selected before running

2) Overriding period logic despite “no claim-type-specific sub-rule found”

You were provided an explicit jurisdiction note: no claim-type-specific sub-rule was found for the period logic. That means you should use the general/default period.

• Keep period logic on the calculator’s general/default behavior for Utah

3) Feeding unrealistic income numbers without checking units

Economic-loss models often scale directly with the income or wage replacement variable. A small data-entry mistake can swing totals.

• Double-check commas and zeros
• Confirm whether the tool expects annual vs monthly amounts
• Confirm the income field you edited is the one actually used by the output

4) Ignoring how the tool groups economic vs non-economic components

Many results screens show multiple components. If you only look at the total, you may miss why it changed.

• Verify whether a non-economic toggle/slider is on or off intentionally
• Compare component breakdowns across runs, not just the final total

5) Not sanity-checking directionality

A reliable calculator should move in the expected direction:

• Increasing income should not reduce economic damages (absent special constraints)

• Extending a modeled loss horizon should typically increase totals (unless an unusual cap/limitation is applied)

• If behavior is counterintuitive, revisit:

  • jurisdiction selection (US-UT)
  • unit expectations (annual vs monthly)
  • which exact field you changed

Try it

Use DocketMath with a clean, controlled workflow:

1. Go to /tools/wrongful-death-damages
2. Select Utah (US-UT) if the tool offers a jurisdiction control
3. Enter inputs in the order DocketMath presents
4. Keep period logic on the general/default period for Utah (no claim-type-specific sub-rule was found)
5. Run the calculation
6. Adjust only one variable at a time (e.g., annual income) to confirm sensitivity and directionality

Quick-test sequence:

• Baseline: use your best-estimate age at death and income
• Increase annual income by ~10% → confirm economic total increases
• Modify age input slightly (shorter projection) → confirm totals decrease
• Review component breakdown to ensure the results match the categories you entered

If you see counterintuitive changes (for example, income increases but the economic component falls), pause and verify:

• jurisdiction selection (US-UT)
• unit expectations (annual vs monthly)
• field selection (did you update the correct input box?)

Related reading

• How to calculate Wrongful Death Damages in Texas — Full how-to guide with jurisdiction-specific rules
• How to calculate Wrongful Death Damages in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Wrongful Death Damages in Philippines — Worked example with real statute citations