How to run Wrongful Death Damages in DocketMath for Minnesota

Step-by-step

Run this scenario in DocketMath using the Wrongful Death Damages calculator.

Here’s a practical way to run Wrongful Death Damages in DocketMath for Minnesota (US-MN) using jurisdiction-aware rules and the calculator settings that correspond to Minnesota’s default wrongful-death time limits.

For Minnesota, the relevant default rule is the 3-year statute of limitations under Minnesota Statutes § 628.26. Your jurisdiction notes also indicate that no claim-type-specific sub-rule was found, so DocketMath should treat this as the general/default period (and not apply a different wrongful-death-only timing rule unless the tool supports it and you provide qualifying facts).

1) Open the Wrongful Death Damages tool

Start from the primary CTA so you land in the correct calculator:

• /tools/wrongful-death-damages

If your interface supports jurisdiction selection, set it to Minnesota (US-MN).

2) Confirm the jurisdiction time-limit logic (SOL)

In many calculators, wrongful-death timing is handled as a gating/timeliness component—for example, whether the filing date is within the allowed window based on the anchor date.

For Minnesota, DocketMath should use:

• General SOL period: 3 years
• Minnesota Statutes § 628.26 (general rule)

Important: Because your jurisdiction data says no claim-type-specific sub-rule was found, DocketMath should rely on the default/general 3-year period from Minn. Stat. § 628.26. In other words, the 3-year window is the baseline unless you have additional, case-specific facts that trigger a different rule (and unless the tool supports overriding that logic).

3) Enter the key date(s) needed for the timeline

To run the SOL/timeliness logic for Minnesota’s 3-year default, you’ll typically provide:

• Date of death (often the anchor date in wrongful-death models)
• Filing date (or the date you want to evaluate against for timeliness)
• Any additional timeline inputs the tool requests (for example, an incident date, if the calculator separates “incident” from “death”)

If DocketMath asks for multiple dates, make sure they are consistent. If it only asks for one required anchor date plus an evaluation date, enter what the tool labels as required.

4) Provide the damages inputs

The Wrongful Death Damages calculator generally depends on inputs such as:

• Economic losses (if included in the model)
• Non-economic components (if included in the wrongful-death template)
• Any other model inputs the tool lists (for example, factors related to timing/periods, or assumptions like income/loss schedules)

Use the tool’s labels exactly as written. Also double-check:

• Units (annual vs. monthly; days vs. years)
• Consistency (gross vs. net, if applicable)
• Whether any inputs you enter are already adjusted/discounted by a different step (to avoid double-adjusting)

5) Run the calculation and review both outputs

After you click Calculate / Run / Compute (wording depends on the UI), DocketMath should return at least two kinds of results:

• A damages estimate (the main numeric output)
• A timeliness/SOL component (based on Minnesota’s 3-year default under Minn. Stat. § 628.26)

A practical workflow is:

1. First review whether the damages numbers look internally consistent (inputs make sense).
2. Then review the SOL/timeliness outcome, because timing can affect how the estimate is interpreted or used in a workflow.

6) Adjust inputs to see how results change

DocketMath is most useful when you iterate. Change one input at a time to understand sensitivity.

Common iteration targets include:

• Filing date (watch for the timeliness result or threshold behavior to change)
• Economic-loss inputs (wages, expenses, time periods—whatever the tool requests)
• Any tool-specific timing assumptions (for example, if it breaks losses into periods)

When you re-run, compare the new results to the previous run. If DocketMath provides a summary of changes, use it to track why the number moved.

7) Save or export (if your workflow supports it)

If the tool offers:

• a shareable link
• a PDF export
• a scenario history

save the run that matches your current “best available facts.” If you later update dates (like the filing date), re-run and compare side-by-side.

Common pitfalls

Wrongful-death calculator runs commonly break due to date handling, mismatched units, or assuming a specialized rule when only a general/default rule is available.

• missing a required input
• using a stale rate or rule
• ignoring calendar or holiday adjustments
• skipping documentation of assumptions

Checklist: pre-run checks

Before you rely on outputs, confirm:

Typical failure modes

• Wrong anchor date: If the tool expects date of death but you provide an incident date (or vice versa), the SOL window may shift and produce a misleading timeliness component.
• Assuming claim-type-specific SOL rules: Your jurisdiction note states no claim-type-specific sub-rule was found, so the tool should use the general default 3-year period from Minn. Stat. § 628.26. Don’t override timing logic in the UI unless the tool supports it and you have a documented basis.
• Assuming outputs equal adjudicated results: DocketMath produces structured estimates based on entered inputs and its model assumptions. These are not guaranteed settlement values or court awards.

Try it

Use this quick test to validate your workflow end-to-end:

1. Go to the calculator: /tools/wrongful-death-damages
2. Confirm jurisdiction: US-MN
3. Enter:

   • Date of death
   • Filing date (or the date you want DocketMath to evaluate against)
   • Your damages inputs per the tool’s labels
4. Run the calculation.
5. In the results panel, check:

   • Damages estimate
   • SOL/timeliness outcome using the 3-year default under Minn. Stat. § 628.26

Then do a one-variable sanity check:

• Change filing date by +30 days and re-run.
• If the timeliness output doesn’t change when you clearly moved across a threshold (or seems insensitive), pause and re-check date entry and units.

If you want a broader walkthrough of how DocketMath calculators typically structure outputs, browse the blog first:

• /blog

Related reading

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