How to calculate Wrongful Death Damages in Minnesota

Quick takeaways

• Minnesota wrongful-death damages are calculated under Minn. Stat. § 573.02, which authorizes a wrongful-death action when death is caused by a wrongful act or omission.
• The claim is tied to the idea that it exists only to the extent the decedent “might have maintained an action, had the decedent lived.” That “had the decedent lived” hook shapes which damages categories you should include in your estimate.
• Use DocketMath to organize your assumptions into a structured worksheet (typically economic loss, non-economic loss if modeled, and any adjustments), then total the selected line items.
• Minnesota’s wrongful-death structure does not include a claim-type-specific period sub-rule in the provided jurisdiction data—so apply the general/default period in your worksheet rather than a special carve-out.
• For a useful Minnesota estimate, capture (1) the identity of the claimant(s)/beneficiaries you’re modeling for allocation, (2) the underlying actionable injury categories the decedent could have pursued if alive, and (3) the economic figures you’re projecting.

Inputs you need

To run DocketMath for wrongful-death-damages (US-MN), collect inputs in three buckets: (1) decedent/claim context, (2) economic-loss math inputs, and (3) optional adjustments that affect the final total.

A. Decedent and claim basics (needed to route the calculation)

• Jurisdiction: Minnesota (US-MN)
• Date of death: anchors your timelines and helps you apply the worksheet’s general/default period consistently.
• Cause-of-death link you’re modeling: label the wrongful act/omission scenario you’re estimating (you are not proving liability here—just describing the fact pattern for the model).
• “What the decedent could have sued for” categories: choose the damages categories you intend to estimate, aligned to the actionable injury the decedent could have pursued if alive.

B. Economic damages inputs (typically the core of the worksheet)

In DocketMath, decide which components you want to model:

• Lost earnings / earning capacity (based on your chosen timeline convention)
• Lost household services (if modeled)
• Medical expenses connected to the wrongful act (pre-death costs)
• Funeral and burial expenses (often modeled as a separate line item in wrongful-death frameworks)
• Other out-of-pocket costs (transportation, caregiving costs, etc.)

For each economic component, you’ll generally need:

• Amount (or base figure): e.g., monthly/annual earnings, or documented medical totals
• Time horizon / duration: how long you project the loss

  • This is where your general/default period is applied
• Growth or discount assumptions (if you use them): many worksheets treat these as user inputs rather than automatically derived from statute

C. Non-economic damages inputs (if you choose to estimate them)

• Non-economic damages estimate: if you model categories such as pain and suffering, loss of enjoyment, or related concepts, enter a single figure or a computed value.
• Fit to the “had the decedent lived” framing: keep the non-economic line item tied to the decedent’s underlying actionable harm conceptually (even though the decedent cannot actually recover it post-death).

D. Parties / payout allocation (keeps you from totaling the wrong number)

Minnesota wrongful-death claims are brought by a representative, and distributions occur under the statutory scheme. For modeling purposes, you may want either:

• Total damages for the claim (the sum of your chosen line items), or
• An estimated split among beneficiaries for planning.

If splitting totals, capture:

• Beneficiary categories and count (e.g., spouse, children, parents, etc.—as applicable to your scenario)
• Allocation assumptions you’re using for estimation

How the calculation works

DocketMath’s wrong​ful-death-damages workflow for Minnesota (US-MN) is structured to reflect Minn. Stat. § 573.02. The key statutory concept you’re modeling is:

• Wrongful death is actionable when death is caused by a wrongful act/omission, if “the decedent might have maintained an action, had the decedent lived.”
• Practically, that means you translate the decedent’s underlying injury into estimation inputs that resemble what the decedent could have claimed if alive, then total those selected categories.

Step 1: Build the “could have sued if alive” damage categories

Translate the decedent’s actionable injury profile into the line items you will model in DocketMath, such as:

• Medical expenses incurred before death
• Lost earnings / earning capacity
• Loss of household services (if applicable)
• Non-economic damages (if you elect to estimate them)
• Funeral and burial expenses (if you elect to estimate them)

This is the key translation from § 573.02’s “had the decedent lived” concept into a worksheet.

Step 2: Compute economic loss using your selected time horizon

For categories like lost earnings and earning capacity, you’ll typically use:

• Lost earnings = earnings rate × time horizon

For medical and other costs, you’ll typically:

• Medical expenses = sum of documented amounts (or projected amounts if you choose that approach)
• Household services = hourly/annual value × duration (if modeled)

Minnesota period routing note: Based on the provided jurisdiction data, no claim-type-specific sub-rule was found. That means your worksheet should apply the general/default period you select (for example, the same projection window from death date to your chosen endpoint), rather than applying a special carved-out time rule.

Step 3: Add non-economic estimates (only if you’re modeling them)

If included in your worksheet:

• Enter your non-economic value as a separate DocketMath line item.
• If you compute it using a method elsewhere (duration × intensity, for example), input the resulting figure rather than trying to “double model” it inside DocketMath.

Step 4: Apply adjustments (if your workflow includes them)

Adjustments vary based on how you set up DocketMath, but common estimation adjustments include:

• Excluding items you decided not to model
• Reconciling overlapping time windows (to avoid double counting)
• Ensuring each line item is consistently treated as pre-death costs versus projected loss

DocketMath is most reliable when every line item clearly represents the loss period and category you intended.

Step 5: Total the damages estimate

• Total damages = sum of all line items entered into DocketMath.

If you enable beneficiary allocation mode:

• Keep in mind that allocation changes who receives what, while your claim total should remain the sum of the damages line items (unless you intentionally re-run the model with different included categories).

Common pitfalls

1. Totaling categories that don’t align with the “had the decedent lived” anchor

   • Minn. Stat. § 573.02 keys off what the decedent could have pursued if alive.
   • Pitfall: adding damages categories that don’t map to the underlying actionable harm conceptually.

2. Mixing time horizons across line items

   • Example: projecting lost earnings over one period while projecting medical expenses using a different window, then accidentally projecting overlap.
   • Fix: use a single timeline framework (or clearly document intentional differences) across your economic line items.

3. Using the wrong period rule

   • Your jurisdiction data note states: no claim-type-specific sub-rule was found, so the worksheet should use the general/default period.
   • Pitfall: applying a shortened/extended special period without a basis tied to statute or documented assumptions.

4. Double-counting earnings loss

   • Pitfall: including both an earnings loss “through death” component and another survival-based earnings segment that covers the same interval.
   • Fix: label each earnings-related line item as pre-death or post-death projection, and ensure the intervals don’t overlap.

5. Confusing the total damages figure with beneficiary allocation

   • Pitfall: interpreting allocation changes as changes to the claim total.
   • Fix: treat DocketMath totals and distribution splits as related but distinct outputs.

Sources and references

• Minn. Stat. § 573.02 (Wrongful death)
  https://www.revisor.mn.gov/statutes/cite/573.02

Next steps

1. Open DocketMath for the Minnesota calculator: /tools/wrongful-death-damages
2. Enter:

   • Date of death
   • The damages categories you’re modeling (medical, earnings, non-economic if included, funeral/burial, etc.)
   • A single consistent general/default period framework for economic projections
3. Run the calculation, then do a quick sensitivity check:

   • Adjust the time horizon (shorter vs. longer endpoint)
   • Update the earnings rate (monthly vs. annual)
   • Add/remove non-economic to see how much it changes the estimate
4. If you want scenario comparisons, save each worksheet version and note what assumptions changed (timeline, earnings baseline, included categories).

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