How to run Wrongful Death Damages in DocketMath for West Virginia

Step-by-step

Use DocketMath’s Wrongful Death Damages calculator for West Virginia (US-WV) by running the inputs in a jurisdiction-aware workflow. This walkthrough assumes you’re calculating damages amounts and then running a separate timing risk screen for West Virginia.

1) Start the correct tool and confirm jurisdiction

1. Open DocketMath’s Wrongful Death Damages tool: **/tools/wrongful-death-damages
2. Set jurisdiction to West Virginia (US-WV).
3. Confirm you are using the Wrongful Death Damages calculator (not survival damages, personal injury, or another module).

Why this matters in DocketMath: jurisdiction selection often changes internal labels and the way timing references are presented. Even if the underlying math is similar, the “check” steps should be based on the selected jurisdiction.

2) Enter the damages components (and keep them consistent)

Wrongful death damages in a worksheet-style calculator typically include a set of categories (the exact names depend on the UI). Enter the values you intend to include, commonly such as:

• Loss of support / income contribution
• Services or benefits the decedent would have provided
• Economic impacts (for example, medical or funeral-related amounts if the tool’s model includes them)

Because each case inventory differs, focus on internal consistency:

• Use the same time basis for every economic input (e.g., all annual amounts).
• Keep units aligned (dollars vs. monthly vs. yearly).
• Only turn on optional fields (for example, “future period length” or “adjustments”) if you have support for those assumptions.

Practical workflow tip: if you’re pulling numbers from multiple documents (pay stubs, expert summaries, billing reports), capture the numeric amounts once and then paste/convert them consistently into DocketMath.

3) Set the time horizon and verify the model period

In wrongful death calculations, the “time horizon” is typically the number of years over which you model expected support/contribution.

If DocketMath asks for:

• Years of future loss (or similar), and/or
• A start date / end date (or equivalent),

enter values that match your damages theory and evidence. If you’re unsure what dates to use, align the horizon with what your team already documented in your case materials.

How outputs change: changing the horizon length often has a direct proportional effect on projection-based totals—longer horizons typically increase calculated damages.

4) Apply any discounting or adjustment parameters (if available)

Some calculators include:

• Discount rate / present value logic
• Inflation assumptions
• Offsets or reductions

If DocketMath provides these fields:

• Use the assumptions your case team has agreed to (or your standard internal methodology).
• Avoid mixing discounting assumptions from one model with inflation assumptions from another unless that’s intentional. Mismatched assumptions can distort present value.

Quick sanity checks:

• If you see unexpectedly large totals, try toggling optional “adjustment” parameters off to compare.
• If changing one parameter causes a dramatic swing, verify whether the field expects percent vs. decimal and whether units are correct.

5) Run the calculation and interpret the output breakdown

After you enter inputs, run the calculation. DocketMath should return:

• A total damages figure, and
• A component breakdown (depending on the fields you enabled)

Review the breakdown for reasonableness:

• Do the largest components align with your source evidence?
• Does the output reflect the horizon and assumptions you selected?
• Are any components unexpectedly zero because a required input wasn’t provided?

6) Add a West Virginia timing check using the general wrongful-death SOL rule

For this workflow, treat West Virginia’s timing check as a separate risk screen from the damages math.

West Virginia provides the general timing reference you were instructed to use:

• General SOL Period: 1 years
• General Statute: W. Va. Code §61-11-9
• Source: https://codes.findlaw.com/wv/chapter-61-crimes-and-their-punishment/wv-code-sect-61-11-9/

Important clarity: your jurisdiction notes state that no claim-type-specific sub-rule was found. So, this guide uses W. Va. Code §61-11-9 as the general/default period rather than treating it as a tailored wrongful-death-only rule.

Actionable timing workflow (math + diligence):

• Record the relevant event date you’re measuring from in your case management system.
• Compute event date + 1 year.
• If that date is close or already passed, flag the matter for heightened timing review in your internal process.

7) Document what you ran (so you can reproduce results)

Before you export, screenshot, or share results:

• Record the key input values (especially horizon years, income/support assumptions, and any discounting).
• Save the jurisdiction setting (US-WV).
• Note the date you ran the tool, since later updates to assumptions can change the output.

A reproducible record is critical if you later:

• update economic inputs,
• adjust the horizon,
• or re-run under alternative assumptions.

Common pitfalls

These issues frequently cause confusion when running wrongful-death damages calculators and timing risk screens.

• Mixing time units

  • Example: entering monthly income in a field that expects annual amounts.
• Using inconsistent horizon assumptions

  • Example: one input reflects years of support while another reflects months, inflating/deflating totals.
• Leaving optional adjustment fields enabled without intended assumptions

  • Discounting/inflation toggles can meaningfully change present value.
• Failing to document the exact inputs

  • Without an input log, it’s hard to explain why results changed after a revision.
• Assuming a claim-type-specific SOL rule was found

  • Your jurisdiction notes indicate no claim-type-specific sub-rule was located. This workflow uses the general/default period tied to W. Va. Code §61-11-9.
• Treating calculator output as “filing-ready” without aligning evidence

  • DocketMath output is a modeling result; your internal file still needs narrative and evidentiary support.

Try it

1. Open the tool at: **/tools/wrongful-death-damages
2. Set jurisdiction to West Virginia (US-WV).
3. Enter your damages components using consistent units (annual vs. monthly).
4. Set the time horizon to match your damages theory and supporting evidence.
5. If DocketMath includes discounting/adjustments, choose one of these approaches:

   • Use your agreed assumptions, or
   • Run a “no adjustment” baseline first, then re-run with adjustments enabled.
6. Run the calculation and review the component breakdown for reasonableness.
7. Perform the West Virginia timing risk screen using the general/default period:

   • 1 year, referenced to W. Va. Code §61-11-9
   • Use this general reference because no wrongful-death-specific sub-rule was found in the provided jurisdiction data.

Optional validation loop: run two scenarios and compare totals:

• Scenario A (conservative): shorter horizon or no adjustment toggles
• Scenario B (standard): your full horizon and intended adjustments

Confirm the directionality matches your expectations before finalizing internal notes.

Related reading

• Wrongful Death Damages Estimator Guide for Alabama
• Wrongful Death Damages Estimator Guide for Arizona
• Wrongful Death Damages Estimator Guide for Colorado