How to run Wrongful Death Damages in DocketMath for Washington

Step-by-step

This guide shows how to run Wrongful Death Damages calculations in DocketMath for Washington (US-WA) using jurisdiction-aware rules—starting from the statute basis for bringing the claim.

1) Open the Washington wrongful-death calculator

Start with the Washington wrongful-death tool here: /tools/wrongful-death-damages.

If you’re setting this up in a workflow, make sure you’re running the wrongful-death-damages calculator (not another damages template). In Washington, the wrongful-death action is brought by the personal representative, and the DocketMath run should be aligned to that wrongful-death structure.

2) Confirm the Washington legal basis used for the action type

Washington’s wrongful-death action authority is grounded in:

• RCW 4.20.010 — the personal representative may maintain an action for damages when death is caused by another’s wrongful act, neglect, or default.

RCW 4.20.010 (statute text summary): When a person’s death is caused by the wrongful act, neglect, or default of another, the decedent’s personal representative may maintain an action for damages against the person causing the death.

How this affects your DocketMath run: your goal is to align your claim structure with that wrongful-death action brought by the personal representative. Even though the specific numbers still come from the damages components and assumptions you enter into the calculator, the “wrongful death” setup is the jurisdiction-aware starting point you want for Washington.

3) Decide what damages categories you’ll run

Before typing anything into DocketMath, decide which components you want to model. DocketMath’s wrongful-death damages calculator typically works by combining multiple damage components you select and populate—for example, categories related to economic support and other loss categories (depending on what fields/options the tool exposes).

A practical approach:

• Decide whether you’re modeling past losses, future losses, or both
• Select only the components that match the evidence you have (employment/income records, household contributions, benefits, etc.)
• Use consistent assumptions across runs so you can compare changes reliably

4) Enter the decedent and beneficiary inputs

In the calculator, you’ll generally provide details that support time-based and earnings-based modeling. Common categories of inputs include:

• Decedent information (often age or an earnings-related horizon)
• Income / earning capacity inputs (or proxies)
• Survival period modeling (for past losses)
• Future horizon modeling (for future losses, if enabled)
• Loss allocation assumptions (who is impacted, if the tool supports multiple parties)

To keep the run auditable, jot down assumptions first, then enter them into DocketMath:

5) Model the time period(s) and keep them consistent

Wrongful-death calculations are especially sensitive to the modeled periods. When you set time horizons in DocketMath:

• Use a single clear “start” and end date strategy (even if you’re converting from age-based approximations)
• If you run past + future, confirm the calculator boundaries do not overlap (unless the tool explicitly supports overlap handling)

How outputs change: adjusting any of the following can shift totals quickly:

• The end date / modeled horizon
• The growth rate
• Whether you include categories that assume benefits/offsets (if the tool includes those options)

6) Run the calculation and review outputs

Once you run the calculation in DocketMath, review results in layers:

• Category totals for each selected damages component
• A grand total summing the selected components
• Any intermediate metrics the tool shows (for example, adjusted income streams)

A good workflow for stability:

• Run Scenario A with your base assumptions
• Run Scenario B with one or two controlled changes (e.g., shorter/longer horizon or different income assumptions)
• Compare differences and identify which category moved the most

7) Save or export results for drafting and analysis

After you get outputs that “fit” your assumptions, save the run (or export results if available). If you later revise evidence, you’ll want to quickly reproduce how the numbers changed.

At minimum, preserve:

• The assumption set used (growth rate, horizon, time split)
• The selected damages categories
• What changed between scenarios

This prevents confusion later when someone re-opens the run and sees updated numbers.

Common pitfalls

Even with a strong Washington setup, wrongful-death damage runs can go off-track. Use this checklist for Washington-specific and tool-specific issues.

• Using a non-wrongful-death calculator

  • Wrongful death has its own structure and inputs. Don’t use a general personal injury calculator and label it “wrongful death.”

• Forgetting the RCW 4.20.010 framework

  • Washington’s wrongful-death action is maintained by the personal representative for damages when death is caused by another’s wrongful act, neglect, or default (RCW 4.20.010).
  • If you’re not using the wrongful-death structure in DocketMath, your run may not reflect the intended Washington claim basis.

• Double-counting time

  • Past + future ranges can overlap surprisingly often. If the tool lets you set both, verify boundaries so you don’t accidentally count the same period twice.

• Assumption mismatch across fields

  • Example: you set earnings growth to 2.5% but set a different inflation/adjustment value in another field to 0%.
  • Keep growth and inflation-related assumptions consistent with how you intend the calculator to model earnings.

• Over-relying on one scenario

  • Damages can swing based on horizon and earnings assumptions.
  • At minimum, run a base and a sensitivity scenario so you can explain the range of results.

• Claim-type authority alignment (RCW 4.20.010)

  • Washington’s wrongful-death authority is tied to RCW 4.20.010. If the DocketMath run is pulling inputs from a different claim type (or using non-matching structure), the output structure you’re modeling may not reflect the wrongful-death action basis you intended.

• Statute period handling (general/default approach)

  • No claim-type-specific sub-rule was found for wrongful death damages period selection in the rule set you’re using.
  • Therefore, in this workflow you should treat RCW 4.20.010 as the general/default period rather than inventing a separate wrongful-death-specific override.

Try it

Get a feel for how DocketMath changes outputs by running controlled variations.

1. Open /tools/wrongful-death-damages.
2. Enter your base set of inputs for the decedent and time horizon.
3. Run once and note the grand total.
4. Change only one variable and run again:

   • Extend the future horizon by 3 years, or
   • Increase earnings growth by 1 percentage point, or
   • Shorten the modeled support period by 2 years
5. Record the change and repeat if needed.

Use this checklist while testing:

• Wrongful death calculator selected (/tools/wrongful-death-damages)
• Run is aligned to the wrongful-death action basis grounded in RCW 4.20.010
• Past and future periods do not overlap (unless the tool explicitly handles overlap)
• Earnings growth / inflation assumptions match across relevant fields
• At least 2 scenarios compared (base + sensitivity)

Tip: If you want to quickly sanity-check the “inputs → outputs” logic, run the tool first with baseline assumptions, then adjust one driver at a time to see which category totals respond.

Gentle disclaimer: This guide is for using DocketMath to structure a damages run and understand what inputs affect outputs. It’s not legal advice. If you’re dealing with an actual claim, consider consulting a qualified Washington attorney or using official legal resources.

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