How to run Wrongful Death Damages in DocketMath for Oregon

Step-by-step

Run this scenario in DocketMath using the Wrongful Death Damages calculator.

Below is a practical workflow for running Wrongful Death Damages in DocketMath for Oregon (US-OR). This guide focuses on how to set up the run and how jurisdiction-aware rules affect the outputs. It’s not legal advice—treat it as a technical walkthrough of the calculator.

1) Start the calculator from the primary CTA

• Open DocketMath’s tool here: /tools/wrongful-death-damages
• Confirm you’re in the Oregon jurisdiction (US-OR) view. DocketMath uses the selected jurisdiction to apply Oregon-specific assumptions and formatting.

2) Identify what “wrongful death damages” you’re modeling

In DocketMath’s wrongful death damages workflow, you’ll typically enter inputs that map to components like:

• Economic losses (often tied to income/support)
• Non-economic damages (pain and suffering–type components, if the workflow supports them)
• Life expectancy / discounting period used to project forward
• Any offsets or constraints the calculator accounts for (if enabled)

Before entering numbers, decide what you intend to model:

• A full valuation (all components enabled), or
• A narrower estimate (e.g., economic only)

3) Enter the decedent’s base income information

Use the inputs that correspond to the decedent’s earnings:

• Annual income (or monthly income converted to annual, depending on what the tool expects)
• Whether the income is employment, self-employment, or mixed (if the calculator asks)
• Earnings growth assumptions (if available in the Oregon workflow)

How this changes outputs in DocketMath:

• Higher annual income generally increases projected future economic losses.
• If the tool lets you choose growth assumptions, it can materially change the magnitude over multi-year projections.

Checklist:

4) Set work-life / projection timing inputs

Next, provide the decedent’s timing inputs, such as:

• Age at death
• Work-life or life-expectancy basis (if DocketMath asks you to input a life expectancy or relies on a built-in table)

How this changes outputs:

• Younger ages typically increase the projection horizon and can increase total economic loss projections.
• Shorter projection horizons reduce total projected loss even with the same income.

Practical tip:

• Double-check that the age field is in years (not months) unless the tool explicitly says otherwise.

5) Add dependency / support assumptions (if enabled)

Some wrongful death worksheets include dependency concepts. If your DocketMath Oregon workflow includes:

• Percent of income that would have been contributed to beneficiaries (or similar “support” slider)
• Household or dependency factor

This changes outputs by:

• Scaling the economic-loss component up or down based on the support share.

Checklist:

6) Enter non-economic damages inputs (if supported in your run)

If the calculator includes non-economic categories, look for inputs such as:

• Pain and suffering / loss of companionship–type driver
• Severity level or dollar ranges (depending on DocketMath’s design)

How this changes outputs:

• Non-economic inputs can create substantial swings because they often aren’t tied to income or life expectancy in the same mechanical way as economic projections.

Checklist:

7) Account for Oregon-specific jurisdiction settings inside DocketMath

Because you selected US-OR, DocketMath will apply Oregon-aware formatting and any jurisdiction-specific calculation constraints built into the wrongful-death-damages calculator.

What you should do:

• Look for an Oregon toggle, “Oregon rules applied,” or a jurisdiction badge near results.
• Ensure you do not override Oregon-only defaults unless the tool provides a clear override switch.

8) Run multiple scenarios to understand sensitivity

For damages modeling, you rarely want a single number without context. In DocketMath, run 2–4 scenarios by varying the most sensitive inputs:

• Income (±10–20%)
• Projection horizon (age/life expectancy)
• Support/dependency percentage
• Non-economic level (if applicable)

A simple sensitivity plan:

• Scenario A: baseline
• Scenario B: lower income / lower support
• Scenario C: higher income / higher support
• Scenario D: alternate non-economic level

Compare outputs and record:

• Total damages
• Component breakdowns (economic vs. non-economic, if shown)
• Any intermediate figures like present value or projection totals

9) Review the breakdown and verify internal consistency

Before exporting or using the output:

• Verify that the breakdown sums to the total (if DocketMath displays a line-item table).
• Confirm no category shows $0 unexpectedly unless that was your intended selection.
• Check whether DocketMath shows an assumption summary (income basis, discounting, time horizon).

Quick validation checklist:

10) Save, export, and document your assumptions

Once your model is working:

• Save the run inside DocketMath (if your workspace supports it).
• Export results or screenshots if your workflow requires it.
• Document the key assumptions in a short note, such as:

  • Annual income used
  • Support percentage
  • Age at death
  • Scenario differences

This documentation makes it easier to explain why your totals change when inputs change.

Common pitfalls

Avoid these issues—most wrongful-death damages misfires come from setup errors, not “math mistakes.”

Even if the worksheet looks the same, jurisdiction-aware logic can alter defaults and output formatting.

Example: entering 35 where the tool expects 0.35 (or entering 0.35 where it expects 35%) can inflate or deflate projections dramatically.

If you input gross income but the calculator expects net (or vice versa), totals can be distorted. Align to the tool’s label.

Entering months into a years field (or vice versa) can change the projection window and present value.

If one scenario includes non-economic damages and another doesn’t, you can’t fairly compare totals.

If you change income and support but also adjust age or non-economic level, you lose clean sensitivity analysis. Change one variable at a time when possible.

DocketMath’s wrongful death calculator is built for its supported wrongful-death-damages structure. Keep your modeling aligned to the worksheet, not generic expectations.

Try it

Use this quick “first run” plan to confirm your DocketMath workflow works end-to-end for Oregon (US-OR):

• Annual income
• Age at death
• Support/dependency percentage (if prompted)
• Non-economic level (if enabled)
• Increase annual income by 10% (keep everything else the same)

If the results don’t change in the way you expect after a 10% income bump, pause and re-check:

• jurisdiction badge (US-OR),
• income units/basis,
• whether you edited the correct income field (annual vs. monthly, gross vs. net).

Related reading

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