How to run Wrongful Death Damages in DocketMath for Utah

Step-by-step

This guide walks you through running Wrongful Death Damages in DocketMath for Utah (US-UT) using jurisdiction-aware rules—so your timeline inputs align with Utah’s general/default statute of limitations. It’s written to be practical and workflow-focused, not legal advice.

1) Start at the Wrongful Death Damages calculator

Open DocketMath’s calculator here:

• Primary CTA: /tools/wrongful-death-damages

2) Confirm the Utah statute-of-limitations basis (default rule)

For Utah, this workflow uses the general/default statute of limitations unless you have a claim-type-specific rule that changes the period.

• General SOL (Utah): 4 years
• Utah Code § 76-1-302 (general SOL reference used in this workflow)
• Source (general SOL guidance): https://www.utcourts.gov/en/legal-help/legal-help/procedures/statute-limitation.html

Important note: The jurisdiction data provided did not identify a claim-type-specific sub-rule. So there’s no separate “wrongful death only” timing override in this workflow—use the general 4-year period.

3) Enter the “date of death” (and related) inputs that drive your SOL timeline

In the calculator, find the fields used to test timeliness. The UI labels can vary, but they typically include:

• Date of death (the date death occurred)
• Assessment date / filing date / today (the date you want to compare against the SOL window)

Use the dates that match your scenario and your goal (e.g., “was it timely when filed?” vs. “what is the deadline as of today?”).

How this affects outputs:

• DocketMath will apply a 4-year SOL window derived from your inputs (commonly keyed to the date of death in wrongful death workflows).
• The tool can then indicate whether your assessment/filing date falls inside vs. outside the SOL window.

4) Set jurisdiction to Utah (US-UT)

Make sure the calculator is set to Utah, US-UT so it applies the Utah SOL logic.

• Jurisdiction code: US-UT

How this affects outputs:

• With US-UT selected, DocketMath should use the Utah general 4-year SOL assumptions provided in this workflow.

5) Provide damages-related inputs (amounts and/or durations)

Next, enter the damages inputs the calculator requests under Wrongful Death Damages. Field names vary by UI, but they often include combinations of:

• Economic losses (e.g., lost earnings/support)
• Non-economic components (only if the calculator supports them)
• Other specified amounts that the model uses in its calculation

Practical guidance:

• Enter values in the format the tool expects (currency/number).
• If the tool uses durations (e.g., “years of loss” or an end-of-loss date), make sure those duration inputs reflect the scenario you’re modeling.

How inputs change outputs (in practical terms):

• Larger economic (and any other supported) inputs typically increase the estimated totals.
• Changing duration-related inputs (like years of lost support) will usually increase or decrease the resulting damages because it changes how long losses are modeled.
• If the tool includes any internal assumptions (like weighting, discounting, or stepwise periods), your entered amounts will propagate through those steps.

6) Review the SOL/timeliness summary separately from damages

After entering dates and damages, review both parts of the results:

1. SOL deadline / timeliness indicator

   • Derived from the 4-year SOL window and your date inputs.
2. Damages estimate

   • The model’s estimate based on your damages inputs.

Why this matters: a damages estimate can exist even when a SOL/timeliness output indicates a timing issue.

7) Capture results for reporting or next steps

Once the scenario matches what you need, capture:

• Total wrongful death damages estimate (and any breakdown, if shown)
• SOL deadline and whether your selected assessment/filing date is inside vs. outside the 4-year window
• Any ranges the tool provides (if it supports them)

A best practice is to save the exact inputs you used (especially the dates). Small date changes can move the computed SOL deadline by months and flip timeliness indicators.

8) Iterate with “what-if” scenarios (keep US-UT fixed)

DocketMath is strongest when you run multiple scenarios. For apples-to-apples comparisons:

• Keep jurisdiction fixed at US-UT
• Change only one scenario variable at a time (commonly the filing/assessment date or one damages component)

Examples:

• Scenario A: assessment/filing date equals the actual filing date
• Scenario B: assessment/filing date equals the earliest plausible filing date you want to test
• Scenario C: adjust loss-duration inputs to see how the damages totals respond

Common pitfalls

Use this checklist to avoid the most frequent workflow errors when running wrongful death damages in DocketMath for Utah (US-UT).

The jurisdiction data provided did not identify a claim-type-specific sub-rule. This workflow therefore uses Utah’s general/default 4-year SOL referenced via Utah Code § 76-1-302.

For this workflow, SOL timing is tied to the triggering event you enter—typically the date of death. Don’t substitute investigative/discovery dates unless the calculator explicitly asks for them.

Even small date entry errors (day/month mix-ups) can shift the SOL deadline and change the timeliness indicator.

If US-UT isn’t selected, results may reflect a different jurisdiction’s assumptions.

Damages estimation and SOL/timeliness are different outputs. Always check the timeline panel.

If the tool defaults to “today,” but you want to know “timely when filed,” update the date to the filing date (or the tool’s equivalent field).

If you switch states during a what-if run, you can’t tell whether changes come from Utah rules or from a different jurisdiction’s assumptions.

Try it

Follow this quick “hands-on” sequence to validate your setup in DocketMath.

1. Open the calculator: /tools/wrongful-death-damages
2. Set jurisdiction to **Utah (US-UT)
3. Enter:

   • Date of death
   • Filing date / assessment date (whichever the UI uses for timeliness testing)
4. Verify the SOL behavior:

   • Confirm you see a 4-year SOL window consistent with the general/default approach tied to Utah Code § 76-1-302 and Utah’s general SOL guidance.
5. Enter the damages amounts requested by the tool.
6. Review outputs in this order:

   • SOL deadline / timeliness indicator
   • Damages total (and any breakdown, if available)
7. Run one simple what-if:

   • Change only the filing/assessment date by a small increment (for example, a few weeks or a couple of months) and re-check whether timeliness changes.
8. Save the scenario outputs you want to reference later.

If you tell me the exact date field labels you see in the DocketMath UI (and what dates you’re working with—month/year is fine), I can help you map each input to the right step for this Utah workflow, without providing legal advice.

Related reading

• Wrongful Death Damages Estimator Guide for Alabama
• Wrongful Death Damages Estimator Guide for Arizona
• Wrongful Death Damages Estimator Guide for Colorado