Abstract background illustration for How to run Wrongful Death Damages in DocketMath for Michigan

How to run Wrongful Death Damages in DocketMath for Michigan

7 min read

Published June 4, 2026 • By DocketMath Team

Partially verified

older_than_packet

Step-by-step

This guide explains how to run Wrongful Death Damages in DocketMath for Michigan (US-MI) using jurisdiction-aware rules. You’ll enter the case facts, choose the correct calculation setup, and then interpret the outputs in the context of Michigan’s wrongful-death framework under MCL § 600.2922. (This is for calculation guidance, not legal advice.)

1) Open the Michigan wrongful-death calculator

Start at the primary CTA: /tools/wrongful-death-damages

Once the calculator loads, confirm you’re in the US-MI jurisdiction context. DocketMath uses jurisdiction-aware logic so the calculation structure and rule assumptions match the selected state.

2) Confirm the calculation basis (Michigan’s statute)

Michigan’s wrongful-death claim is created by statute. Michigan law provides that when death (or injuries resulting in death, or the death of an unborn quick child) is caused by another’s wrongful act, neglect, or fault, the person (or corporation) who would have been liable if death had not ensued is liable for an action for damages. See MCL § 600.2922:

Key practical takeaway for running the calculator: the Michigan wrongful-death framework is statutory, and the DocketMath run should reflect a death caused by another’s wrongful act, neglect, or fault.

Note: DocketMath applies jurisdiction-aware logic for US-MI, but this post focuses on how to use the tool and interpret outputs—not on legal strategy or advice.

3) Enter the core case inputs

The DocketMath UI may label fields slightly differently, but wrongful-death damages calculators typically collect the same core inputs. Enter Michigan case facts using the fields provided:

  • Fatality / death caused by wrongful act
    • A selection or yes/no input indicating death resulted from a qualifying wrongful act/neglect/fault scenario
  • Economic losses
    • Examples might include lost support, lost household services, and other quantifiable financial impacts (whatever categories the tool provides)
  • Non-economic losses
    • If DocketMath includes a category for non-economic impacts, enter those values according to your assumptions
  • Time horizon assumptions
    • Often tied to age (at death) or a related window used by the tool to model the period of damages
  • Discounting / discount rate
    • If a discount rate field exists, choose the rate you want the model to apply
  • Any deductions or offsets
    • If the tool includes reductions, offsets, or other adjustment fields, fill them only if you understand what the field is intended to represent in the calculation

As you change inputs, watch how the outputs update in real time. If you adjust a major driver—like the time horizon or earning assumption—the damages totals should respond accordingly.

4) Use Michigan’s general/default period rule (no claim-type-specific sub-rule found)

Your provided jurisdiction notes indicate:

  • No claim-type-specific sub-rule was found.
  • The above is the general/default period.

So, in DocketMath for US-MI, you should:

  • Use the calculator’s default wrongful-death period logic for Michigan.
  • If the UI offers a “period model” or “time window” selector, keep it set to the default/general Michigan approach unless DocketMath explicitly labels a specific alternative for US-MI.

Warning: Don’t “over-model” the time period by selecting an alternate option “because it sounds more specific,” when your jurisdiction notes confirm no claim-type-specific sub-rule was found for US-MI. That helps keep the output aligned with the intended default structure.

5) Review outputs by category

DocketMath commonly shows both totals and category breakdowns (the labels may vary). Use the category view to sanity-check the numbers:

  • Economic damages totals
  • Non-economic damages totals (if included)
  • Combined wrongful-death total

Practical check:

  • If the economic portion dominates, verify your earning/support inputs and the time horizon.
  • If the non-economic portion dominates, verify that you entered values consistent with your assumptions and that the calculator is actually including non-economic items.
  • If totals seem unusually low or high, revisit the largest drivers first—often time horizon and discounting.

6) Document assumptions for repeatability

To treat your run as a calculation exercise (and to enable later comparisons), record the inputs that most affect the result:

  • Age at death (or whatever time-horizon trigger the tool uses)
  • Income/earning assumptions or proxies you entered
  • Household service values (if included as a category)
  • Discount rate (if used)
  • Any deductions/offsets the tool applied
  • Whether the calculator used the default/general period model (important for US-MI)

A practical workflow:

  • Save/export your calculation output if DocketMath supports it.
  • Keep a short assumption checklist so you can rerun consistently.

Example checklist:

  • Jurisdiction set to US-MI
  • Inputs reflect a wrongful-death basis consistent with MCL § 600.2922
  • Default/general period model used (no claim-type-specific sub-rule found)
  • Economic inputs entered in a way consistent with the chosen time horizon
  • Discounting fields match your selected assumptions
  • Output reviewed by category (economic vs non-economic)

7) Run scenarios (sensitivity checks)

Wrongful-death damages can swing based on assumptions. Use DocketMath scenario testing (or rerun the tool) to understand sensitivity:

Try at least 2–3 runs:

  1. Base run: your best-estimate inputs
  2. Conservative run: lower economic input and/or a shorter time horizon (based on what the UI allows)
  3. Adjusted run: higher economic input and/or different discounting (only if you can vary those fields)

Then compare:

  • Which inputs change the total the most?
  • Does the output shift in a way that matches your expectations (e.g., economic changes mainly drive economic totals)?
  • Are category breakdowns stable, or do they re-balance significantly?

This is a validation step for your modeling choices, not legal advice.

Common pitfalls

These are common mistakes when running wrongful-death damages in DocketMath for Michigan:

  • Using the wrong period logic

    • Your jurisdiction note says no claim-type-specific sub-rule was found.
    • If the tool offers multiple period models, stick with the general/default wrongful-death approach for US-MI.
  • Misaligning inputs with Michigan’s statutory wrongful-death basis

    • Michigan’s action arises when death is caused by another’s wrongful act, neglect, or fault under MCL § 600.2922.
    • If your inputs reflect a scenario outside that concept (e.g., not tied to wrongful act causing death), the calculation output may not reflect the model you intend to study.
  • Updating a major assumption without re-checking category outputs

    • If you change time horizon or life expectancy drivers, re-check both economic and non-economic buckets.
    • Some tools update categories differently; always review breakdowns, not only grand totals.
  • Ignoring discounting inputs

    • If DocketMath includes a discount rate/discounting field, leaving it at an unintended default can materially affect totals.
  • Over-interpreting the “total”

    • Tool outputs are only as reliable as the assumptions you enter. Treat results as modeled estimates, not definitive valuations.

Pitfall to avoid: selecting an alternate time-period model simply because it seems more specific—when there’s no US-MI claim-type-specific rule basis in the provided jurisdiction notes—can yield a results structure that doesn’t match the intended default model.

Try it

Use this quick routine to produce a working Michigan run:

  1. Open /tools/wrongful-death-damages
  2. Confirm the jurisdiction is US-MI
  3. Enter:
    • your death-related selection (fatality caused by wrongful act scenario, per the tool’s field)
    • economic losses inputs
    • non-economic losses inputs (if available)
    • time horizon and discounting (if the tool provides fields)
  4. Ensure the calculator is using the general/default wrongful-death period
    • (since no claim-type-specific sub-rule was found in your jurisdiction data)
  5. Review the output by category and confirm totals align with your assumptions
  6. Run a second scenario where you change a meaningful input (e.g., earning capacity or time horizon) and compare the change in the total

After your base run:

  • export/save the output (if supported)
  • record your assumption checklist so you can rerun consistently

Related reading