How to run Wrongful Death Damages in DocketMath for West Virginia

Step-by-step

This guide explains how to run Wrongful Death Damages in DocketMath for West Virginia (US-WV) using jurisdiction-aware rules. You’ll map the case facts to the calculator inputs, then verify that the model’s assumptions align with West Virginia’s wrongful-death framework.

Start by opening the calculator here:

• Primary CTA: /tools/wrongful-death-damages

1) Confirm the case type is “wrongful death”

In DocketMath, choose the Wrongful Death Damages calculator. This tool is intended for cases where:

• a person’s death is caused by a wrongful act, neglect, or default, and
• the underlying conduct is the kind that would have entitled the injured person to sue if death had not occurred.

West Virginia’s wrongful-death framework is set out in:

• W. Va. Code § 55-7-5 — “Whenever the death of a person shall be caused by wrongful act, neglect, or default, and the act, neglect or default is such as would (if death had not ensued) have entitled the party injured to maintain an action to recover damages….”

2) Enter the “would-be plaintiff” damages inputs (economic loss)

Most wrongful-death damages models project losses attributable to the decedent’s life—especially earning capacity and economic contribution—then convert those projections into wrongful-death damages categories.

In the DocketMath interface:

• Enter decedent earnings (or the income measure you have in the record).
• Add employment income details you can quantify (for example, wages, salary, or other regular income sources).
• If the calculator requests a duration (work-life/duration) or a time period, enter the period DocketMath asks for based on your assumptions and evidence.

How outputs change:

• Higher projected earnings and longer modeled duration generally increase the damages.
• Lower verified earnings (or a shorter modeled duration) typically reduces the result.

3) Model income uncertainty using DocketMath controls

If DocketMath includes toggles or controls like:

• conservative vs. best-estimate assumptions,
• growth adjustments,
• reduction factors,
• or alternative modeling options,

use those controls consistently with the evidence and the story you’re building.

Practical workflow:

• Run Scenario A (best estimate) with your strongest supported inputs.
• Run Scenario B (conservative) with lower income, shorter duration, or more cautious adjustments—whenever the tool supports multiple scenarios.

This doesn’t change the legal basis—it changes the math inputs and helps you understand sensitivity.

4) Enter wrongful-death-specific categories (when available in DocketMath)

Depending on the exact DocketMath wrongful-death form, you may see additional category inputs beyond earnings/duration. Common examples include:

• loss of support / economic contribution
• household services (if the tool models it)
• other structured components provided by the calculator’s layout

Fill in every field you can support with record-based numbers. If a field is optional, leaving it blank will generally cause the total to reflect only the categories you did enter.

How outputs change:

• Adding an additional category (for example, household contribution) typically increases the total.
• Omitting unsupported categories generally reduces the total and may make the run more defensible.

5) Run the calculation and review component breakdowns

After you enter inputs, run the calculator and inspect:

• Total wrongful-death damages
• Component line items (how the tool breaks down the total)
• the assumptions summary (what DocketMath assumed and used)

Checklist:

• Do the assumptions match the scenario you intended (especially income, duration, and any growth/reduction settings)?
• Do the outputs clearly reflect your inputs?
• Are there any tool defaults you didn’t expect? If so, re-check the assumptions summary.

6) Sanity-check against West Virginia’s wrongful-death baseline

West Virginia’s wrongful-death cause of action is anchored in W. Va. Code § 55-7-5, which uses a “wrongful act, neglect, or default” framework and ties the claim to what the injured person could have recovered if death had not occurred.

Practical tie-back:

• If your DocketMath inputs model economic losses that trace to the decedent’s life circumstances (income capacity, contribution, and support), your modeling conceptually aligns with the statute’s premise.
• If your inputs rely on highly speculative projections (for example, unsupported growth assumptions), the output may still compute mathematically, but it may be harder to defend in a narrative tied to evidence.

7) Document your run for repeatability

DocketMath runs are easiest to use later if you can reproduce them.

Record from the results page:

• the income amounts and how they were treated,
• the duration/model period,
• any toggles or scenario adjustments, and
• the assumptions summary.

Simple notes format:

• “Scenario A: base earnings, duration = X, adjustments = Y → total = $Z”
• “Scenario B: reduced earnings, duration = X2, adjustments = Y2 → total = $Z2”

This supports comparisons without changing the underlying § 55-7-5 framing you’re applying.

Common pitfalls

Wrongful-death damages calculations often go wrong due to avoidable input issues or misunderstandings about what the tool is modeling. Watch for these when running DocketMath for US-WV.

• Not starting from the West Virginia wrongful-death calculator

  • Using a related-but-different calculator can produce output that doesn’t match wrongful-death category structure.

• Assuming a special WV sub-rule for wrongful-death damages

  • The materials provided establish the general wrongful-death baseline in W. Va. Code § 55-7-5.
  • Since no claim-type-specific sub-rule was provided here, treat the general framework as the default in this workflow.

• Mixing “decedent life” inputs with the wrongful-death output categories

  • DocketMath may organize numbers into categories internally. Make sure each number goes into the correct field (especially if household services or other components appear).

• Letting DocketMath defaults drive results silently

  • Tool defaults for growth, duration, or reductions can materially change totals. Always verify the assumptions summary after running.

• Using income figures that aren’t grounded in the record

  • Even if the tool accepts an input, credibility depends on quality—especially earnings and duration.

• Skipping scenario comparisons

  • A single run can hide sensitivity. If DocketMath supports scenario inputs, run at least one alternative set to understand the range of results.

Try it

Ready to generate a West Virginia wrongful-death damages run in DocketMath?

1. Open /tools/wrongful-death-damages.
2. Select the Wrongful Death Damages calculator.
3. Enter decedent-related economic inputs (earnings/support-related inputs) and any other category inputs the tool requests.
4. Review the assumptions summary displayed by DocketMath.
5. Run at least two scenarios if the tool supports them:

   • Scenario A (best estimate): strongest supported income and duration assumptions
   • Scenario B (conservative): lower earnings and/or modified duration/assumptions

Then compare:

• total damages, and
• component breakdowns (what drove the change—often duration and earnings assumptions).

Gentle note: This walkthrough is about using DocketMath and understanding how the statutory framework supports the modeling conceptually. It is not legal advice. For case-specific strategy or legal questions, consult qualified West Virginia counsel.

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 example with real statute citations