How to calculate Wrongful Death Damages in Ohio

Quick takeaways

• Ohio’s wrongful-death claim is governed by Ohio Rev. Code § 2125.01, which creates a right of action when death is caused by a wrongful act, neglect, or default that would have allowed the injured person to sue and recover damages if death had not occurred.
• In a DocketMath wrongful-death-damages calculation, you typically assemble damages from economic losses (often the most structured inputs) and non-economic losses (which usually require careful, scenario-based valuation choices).
• Ohio’s framework ties the claim to what the injured person “would have been entitled to” recover, but the actual components and proof you use still matter a lot—especially for future support and non-economic harms.
• Your main modeling task is choosing and documenting inputs that map cleanly to your damages categories inside DocketMath.

Inputs you need

Before you enter numbers into DocketMath’s wrongful-death-damages calculator, gather the facts and assumptions you’ll need to defend your modeling choices later.

Core case inputs (jurisdiction-aware setup)

• Date of death
• Ohio venue/jurisdiction context (confirm Ohio is the proper jurisdiction for the damages model you’re running)
• Injury period facts (how long the decedent lived after the injury, if applicable)
• Liability theory framing (the statute requires a “wrongful act, neglect, or default” causing death—DocketMath helps compute inputs; it doesn’t replace the legal theory)

Damages model inputs (what DocketMath will use)

Choose categories you plan to include in your calculation.

Economic damages (often easiest to support)

• Decedent’s earnings

  • Current income and/or earnings history
• Work-life / earning horizon assumptions

  • How long earnings are projected to continue
• Fringe benefits (if you include them as part of compensation)
• Personal consumption rate

  • Common modeling choice: estimate what portion of earnings would have been consumed by the decedent versus available for others
• Future support assumptions

  • If your model captures reliance by survivors
• Household services value

  • If you’re valuing non-wage contributions
• Medical and related costs

  • If you’re including pre-death expenses in your chosen approach
• Funeral and burial expenses

  • If included in your damages approach

Non-economic damages (more valuation-dependent)

• Pain and suffering (if your model includes this component)
• Loss of companionship / consortium-type harms
• Duration/impact estimate

  • How long non-economic effects are modeled to persist

Timing and discounting (if your calculator prompts you)

• Discount rate / inflation assumptions (if DocketMath supports time-value modeling in your setup)
• Payment timing assumptions (lump sum vs. periodic assumptions, if applicable)

Mapping reminder: Ohio’s “default” framework

The jurisdiction note you provided indicates that no claim-type-specific sub-rule was found, so treat Ohio’s statute as the baseline mechanism rather than a separate specialty formula.

In other words, don’t look for a different “wrongful death schedule” inside Ohio law for different wrongful-death types; instead, use Ohio Rev. Code § 2125.01 as the statutory cause-of-action framework and model losses using the inputs you choose inside DocketMath.

How the calculation works

DocketMath’s wrongful death damages calculation is best understood as a structured assembly of components into a total. The Ohio-specific part in this workflow is the governing statutory framework in Ohio Rev. Code § 2125.01.

1) Start with Ohio’s statutory cause-of-action logic

Ohio Rev. Code § 2125.01 provides that when death is caused by wrongful act, neglect, or default that would have entitled the injured person to maintain an action and recover damages if death had not ensued, the responsible party—or the administrator or executor of the estate under the statute’s framework—may be pursued under Ohio’s wrongful-death statute.

For your DocketMath model, that means your damages categories should align with losses that would be compensable in a “damages-for-injury” world, and then translated into the post-death context your chosen damages modeling approach captures.

2) Build an “economic losses” block

A practical DocketMath workflow for economic damages typically looks like this:

1. Project gross earnings (or use a provided earnings figure)
2. Estimate personal consumption
3. Apply a support/relationship modifier (when the model captures partial reliance rather than full support)
4. Discount future amounts (if enabled in your DocketMath setup)
5. Add itemized expenses you choose to include (medical, funeral, and related costs), using your model’s specific input fields

Here’s a simple way to keep your run organized and internally consistent:

How outputs change:

• If you increase the earnings horizon, future totals usually rise (unless consumption/support assumptions decrease offsettingly).
• If you increase the personal consumption rate, available support for survivors usually falls.
• If you change discounting, long-term components can swing more than near-term expenses.

3) Add a “non-economic losses” block (modeled, not formula-driven)

Non-economic damages often aren’t produced by a rigid schedule in your workflow; instead, you model them using assumptions about intensity and duration.

In a DocketMath run, treat non-economic damages as:

• separate sub-components (for example, pain/suffering and companionship-type impacts), and
• a valuation approach you apply to duration and impact intensity.

Practical modeling tip: when testing scenarios, change one variable at a time (for example, non-economic duration from 5 to 10 years) so you can see how sensitive the total is to that specific choice.

4) Combine components into the total

Once DocketMath computes each bucket you selected, you get a combined wrongful-death damages output based on your inputs.

Because wrongful-death damages can be assumption-sensitive, it’s useful to run a small scenario set and compare outputs:

• Conservative: shorter horizon; lower earnings growth; lower non-economic duration
• Most likely: your best-estimate inputs for horizon and valuation factors
• Larger: longer horizon; higher earnings growth; expanded non-economic duration

5) Use sensitivity checks to validate your inputs

In most models, the biggest swings come from the projection levers. Prioritize sensitivity checks on:

• Earnings/work horizon
• Personal consumption percentage
• Discount rate / inflation assumptions (if time-value modeling is enabled)
• Non-economic duration and valuation factor(s)

If small changes to one assumption cause large changes in the total, that “hinge input” may require stronger factual support and clearer documentation.

Tool workflow (practical path)

Start from DocketMath’s wrongful-death flow:
/tools/wrongful-death-damages

If you also want to organize evidence and proof tracking alongside damages modeling, consider pairing the workflow with:
/tools/case-organizer

Common pitfalls

The following issues most often make wrongful-death damages models unreliable—especially when translating real-world facts into DocketMath inputs:

• Double-counting economic items

  • Example: including both “future earnings” and “future support” in a way that already embeds support reliance.
• Using the wrong earnings baseline

  • Example: entering an outdated income figure without updating for documented changes (raises, new role, or income trends).
• Over-precision in assumptions

  • Example: selecting a discount rate or consumption % with unjustified precision solely to make the output look exact. Scenario analysis should reveal instability.
• Inconsistent inclusion/exclusion of categories

  • Decide upfront whether you include medical/related costs and funeral/burial expenses, and whether pre-death losses are modeled in your chosen approach—then keep that consistent across scenarios.
• Treating Ohio as having a “one-size schedule”

  • Ohio Rev. Code § 2125.01 establishes the wrongful-death cause of action framework; it does not replace input-based modeling for separate economic and non-economic categories.
• Assuming a claim-type-specific sub-rule exists

  • Your jurisdiction note indicates no claim-type-specific sub-rule was found, so use the general/default statutory framework as the baseline for your model rather than a specialty formula.

Sources and references

• Ohio Rev. Code § 2125.01 — Wrongful death actions (general wrongful-death framework)
  https://codes.ohio.gov/ohio-revised-code/section-2125.01

Next steps

1. Decide your included damages categories (economic only; or economic + non-economic; or a