Abstract background illustration for How to calculate Wrongful Death Damages in South Dakota

How to calculate Wrongful Death Damages in South Dakota

8 min read

Published June 4, 2026 • By DocketMath Team

Under review

missing_or_unverified_packet

Quick takeaways

  • In South Dakota, wrongful death claims are governed by SDCL § 21-5-1, which allows damages when a death is caused by a wrongful act, neglect, or default that would have entitled the injured person to recover if death had not ensued.
  • DocketMath’s Wrongful Death Damages calculator is a component-based estimator: you enter modeled inputs (such as economic loss and non-economic damages), and it aggregates them into a total damages figure.
  • SDCL § 21-5-1 is the core “gateway” rule for wrongful death: it links wrongful conduct to recoverable damages as if the underlying injury claim had survived.
  • The jurisdiction data provided did not identify any claim-type-specific “period” sub-rule. So, this guide treats the time framing as default/general under SDCL § 21-5-1, with timing typically driven by your chosen modeling horizon (e.g., years of expected work remaining).
  • If your inputs are uncertain—especially lost earnings and future-care/non-economic assumptions—your output will change a lot. Use consistent units and document how you chose each number.

Note: This guide focuses on how to calculate wrongful death damages using DocketMath under South Dakota’s wrongful-death statute framework. It does not provide legal advice or guarantee results in any specific case.

Inputs you need

Before you run DocketMath’s Wrongful Death Damages calculator, gather the inputs that drive the modeled damages total. If you’re unsure about certain values, use a conservative range and then rerun to see how sensitive the outcome is.

Core factual inputs (damage drivers)

  • Decedent’s pre-death earnings
    • Annual salary or hourly wage × work pattern
  • Work-life assumptions (if used in your model)
    • Expected work horizon (e.g., years remaining)
  • Future economic loss inputs
    • Any expected wage growth rate you want to model (if applicable)
    • Discount rate / present-value setting (if your DocketMath workflow uses discounting)
  • Non-economic damages (if you choose to include them)
    • Pain and suffering (modeled amount)
    • Loss of companionship / loss of society (modeled amount)
    • Other non-economic categories your workflow includes

Evidence/assumption inputs (how you justify numbers)

  • Source of earnings data
    • Pay stubs, W-2s, tax returns, or employment records
  • Support and household context
    • Whether your model includes economic support to survivors (if applicable to your approach)
  • Medical and related costs (optional components)
    • Funeral/burial expenses
    • Medical expenses between injury and death
      (Only include these if your DocketMath setup includes them.)

Jurisdiction-aware framing input

  • South Dakota wrongful act trigger
    • You’re using SDCL § 21-5-1 as the statutory foundation: wrongful act/neglect/default causing death where the decedent could have recovered if death had not occurred.

Quick input checklist (use this in practice)

  • Decedent earnings (annualized)
  • Expected work horizon (years, and consistent with the calculator’s time units)
  • Economic loss modeling method (plain total vs. present value, if your DocketMath workflow supports it)
  • Non-economic damage amounts (if included)
  • Any add-ons (funeral/medical/other costs, if your model supports them)

How the calculation works

DocketMath’s wrongful death estimate is most useful when you treat it as a structured, explainable model: you choose components, enter your inputs, and the calculator aggregates them into a total damages figure.

1) Confirm the statutory foundation (South Dakota: SDCL § 21-5-1)

South Dakota’s wrongful death statute begins with a conditions-based rule:

  • When the death or injury of a person is caused by a wrongful act, neglect, or default, and that act would—if death had not ensued—have entitled the injured party to maintain an action and recover damages, then a wrongful death action exists under the statute’s framework.

In other words, SDCL § 21-5-1 is the “gateway”: it connects wrongful conduct to compensable damages that would have been recoverable for the underlying injury claim if the person had not died.

Source: SDCL § 21-5-1 (statutory text excerpt referenced in the jurisdiction data)
https://sdlegislature.gov/Statutes/Codified_Laws/2060401

2) Choose what damages categories you model in DocketMath

In many DocketMath wrongful-death workflows, you can conceptualize the modeled damages total as a sum of:

  • Economic damages
    • Lost earnings / future earnings support (depending on your modeling approach)
    • Potential medical expenses between injury and death (if included in your component list)
    • Funeral costs (if included in your component list)
  • Non-economic damages
    • Pain and suffering (often modeled)
    • Loss of companionship / society (often modeled)

A practical approach is to run economic-only first, then add non-economic categories and compare the change.

3) Apply the time-based component logic (default/general approach)

You asked for jurisdiction-aware rules, and the jurisdiction data provided included:

  • A general/default period rule under SDCL § 21-5-1
  • A clear note that no claim-type-specific sub-rule was found in the jurisdiction data supplied.

So, for this calculator approach, treat timing as default/general under SDCL § 21-5-1, not as a special separate “period” framework tied to a particular claim type.

Practically, that means your time framing generally comes from your modeling inputs—for example, the number of years you assume the decedent would have continued working—rather than from an additional South Dakota sub-rule you haven’t identified.

4) Aggregate components into a total

After you enter the component amounts and time-based inputs:

  • DocketMath calculates each modeled component (for example, earnings over the chosen horizon, and any present-value adjustments if enabled).
  • It then adds economic and non-economic components into a single damages total.

Sanity-checking your output is easier if you watch which inputs are driving the change:

ScenarioEconomic inputs change?Non-economic inputs change?Expected effect on total
BaselineNoNoBaseline total
Conservative earningsYes (down)NoLower total economic damages
Longer work horizonYes (up)NoHigher total economic damages
Add non-economicNoYes (add)Total increases by the modeled non-economic amount

5) Keep outputs explainable

DocketMath output is strongest when you can tie the number back to inputs:

  • If total damages rise, is it because of earnings, duration, growth/discount assumptions, or added categories?
  • This helps you review whether the model is reflecting what you intend to quantify.

Common data issue to watch: entering earnings as a monthly figure when the calculator expects annual can inflate results by 12×. Confirm the units required by each DocketMath field before running.

Common pitfalls

1) Mixing units and time horizons

  • Monthly vs. annual earnings
  • Years vs. months when entering work horizon inputs
  • Present-value setting enabled with a mismatched discount rate

2) Double-counting the same category

Avoid counting the same loss twice, such as:

  • Including medical expenses both in an “economic loss” block and again as a separate add-on
  • Treating funeral costs as both an economic component and a separate “other costs” component (if your DocketMath setup would do both)

3) Using assumptions without a clear basis

DocketMath will compute based on what you enter. Credibility depends on whether your inputs are supported by:

  • Pay stubs/W-2s/tax returns for earnings
  • Employment history or credible work-life estimates for work horizon
  • Consistent documentation for non-economic category amounts

4) Assuming a special claim-type timeline exists (without evidence)

Based on the jurisdiction data provided, treat the period handling as default/general under SDCL § 21-5-1, because no claim-type-specific sub-rule was identified.

5) Treating the statute as the complete numeric formula

SDCL § 21-5-1 establishes the cause-of-action trigger, but it does not automatically generate each damages component amount. Your numeric total depends on the categories you model and the assumptions you input into DocketMath.

Sources and references

  • SDCL § 21-5-1 (South Dakota wrongful death statute)
    https://sdlegislature.gov/Statutes/Codified_Laws/2060401
    Statutory concept referenced in provided jurisdiction data: wrongful act/neglect/default causing death where the injured party would have had a claim and recoverable damages if death had not ensued.

Next steps

  1. Open DocketMath’s wrongful death calculator: /tools/wrongful-death-damages
  2. Enter earnings and horizon inputs first and run a baseline economic damages only estimate.
  3. Add non-economic components (if your workflow includes them) and observe the delta:
    • If non-economic figures dominate the total, verify they align with your evidence and consistent modeling approach.
  4. Run quick sensitivity checks:
    • Reduce earnings by a conservative percentage and rerun
    • Shorten work horizon by a few years (e.g., 2–5) and rerun
  5. Save your input set and document each number’s basis (pay stubs/tax returns/medical records, or clearly stated assumptions).

Related reading