How to run Wrongful Death Damages in DocketMath for New Jersey
6 min read
Published February 5, 2026 • Updated April 23, 2026 • By DocketMath Team
Trust release 4
This page has legal or numeric text that still needs claim-level inventory before we can treat it as verified.
Step-by-step
Run this scenario in DocketMath using the Wrongful Death Damages calculator.
This guide walks you through running Wrongful Death Damages in DocketMath for New Jersey (US-NJ), using the platform’s jurisdiction-aware setup and the general/default limitations period for wrongful-death claims in NJ.
Note: DocketMath focuses on calculations. This walkthrough explains how to set inputs and interpret outputs; it doesn’t replace legal advice for your specific facts.
1) Start in the right calculator
- Open DocketMath → Wrongful Death Damages.
- Use the primary call-to-action: /tools/wrongful-death-damages.
- Confirm your jurisdiction is set to New Jersey (US-NJ). If there’s a jurisdiction selector, choose US-NJ before entering any numbers.
2) Add the damages-related inputs
Wrongful death damages modeling typically requires separating categories of loss. In DocketMath, enter the values your case record supports.
Common inputs you’ll likely see in the wrongful-death workflow include:
- Economic losses (for example, expected income contribution)
- Non-economic losses (for example, loss of companionship, guidance, or similar items—if your DocketMath configuration supports these categories)
- Time horizon / duration (how long the model projects damages)
- Discounting / present value settings (if available)
Use consistent units:
- If DocketMath expects annual amounts, enter annualized figures (e.g., total projected income contribution per year).
- If you only have weekly or monthly figures, convert them to match the field’s unit before calculating.
3) Add time and limitation context (NJ default)
DocketMath may prompt you for timing details or may use timing to shape projections. For New Jersey, be aware of the general/default statute of limitations (SOL) used in this workflow:
- General SOL Period (NJ): 4 years
- Statute: N.J.S.A. 12A:2-725 (shown in your jurisdiction data as the default reference)
Important: Your jurisdiction data states that no claim-type-specific sub-rule was found. That means you should treat this 4-year general period as the default for running the calculator in this workflow, rather than assuming a special wrongful-death limitations rule exists in DocketMath’s rule set.
4) See how changing inputs affects outputs in DocketMath
After you enter inputs, DocketMath computes totals based on those values. Here’s what typically changes the output most, and why:
- Higher projected annual economic loss → higher total damages
- Increasing expected annual contribution usually raises totals proportionally (depending on any duration and present-value/discounting settings).
- Longer time horizon / duration → higher damages
- Extending duration often increases totals because more periods of loss are included.
- **Discounting / present-value settings → lower totals (often)
- If discounting is enabled, losses farther in the future generally count less in present-dollars.
Practical approach:
- Start with your best estimates.
- Run once to establish a baseline.
- Adjust one input at a time (often duration first, then annual economic loss, then any non-economic components).
- Compare the change in outputs to identify which assumptions drive the result.
5) Review the computed results before exporting or saving
Once DocketMath returns results, review:
- Category totals (economic vs. non-economic, if displayed)
- Net/projected total (the main figure)
- Assumption outputs (duration, any timing multipliers/time-to-incident settings, and present-value/discounting statements)
If DocketMath provides multiple scenarios:
- Use your baseline scenario for your primary work product.
- Use additional scenarios for sensitivity testing (for example, ±10–20% on projected annual economic loss) so you can explain how sensitive the output is to key assumptions.
6) Document your assumptions and conversions
For workflow consistency (and easier review), record:
- The numbers you entered
- Any conversions you made (monthly → annual, weekly → annual, etc.)
- Any changes you applied for sensitivity runs
This is not legal advice—it's a practical way to keep the calculation understandable as an internal work product.
Common pitfalls
Wrongful death damages calculations often fail at the “inputs and timing” layer, not the arithmetic layer. Here are common issues to watch when using DocketMath for New Jersey (US-NJ).
Your NJ jurisdiction data indicates:
- Only a general/default SOL period of 4 years was identified
- N.J.S.A. 12A:2-725 is the default reference used in this jurisdiction setup
If you assume a different wrongful-death-specific limitations rule is automatically applied, you can end up using the wrong timing context in your workflow.
Reminder: Don’t treat the calculator’s default SOL context as a guarantee that every wrongful-death timing nuance in New Jersey is the same. Your case facts may require additional legal analysis.
Pitfall 2: Mixing income units (monthly vs. annual)
If you enter monthly figures into a field expecting annual amounts, totals can be off dramatically (often by about a factor of 12). Before you run:
- Check whether DocketMath shows the unit for each field.
- Convert periodic numbers to the expected unit.
Pitfall 3: Inconsistent time horizon vs. timeline facts
If the model uses a projection duration (e.g., number of years), ensure it matches the scenario you’re modeling:
- How long you’re projecting damages (work-life expectancy, another duration basis, etc.)
- The timeline assumptions you’re using in the case
When duration and the economic inputs don’t align, the results can look plausible while representing a different scenario than intended.
Pitfall 4: Skipping sensitivity testing
One run can hide what the output depends on most. Do at least:
- A baseline run
- A second run adjusting duration
- A third run adjusting annual economic loss
This helps you evaluate whether the output is stable or dominated by one key variable.
Pitfall 5: Leaving discounting settings on defaults without verifying
Discounting (if available) can materially change totals. If DocketMath offers discount rate options or a present-value toggle:
- Verify what’s selected
- Record the discounting settings you used so your output is reproducible
Try it
Use this quick checklist to run a first pass in DocketMath for US-NJ:
Next, compare outputs:
- Does the total change mostly when you adjust duration?
- Do non-economic categories move consistently with their inputs (if included in the tool)?
- If discounting is enabled, do totals appear reduced relative to an undiscounted approach?
If you want to jump straight into the workflow, start here:
- /tools/wrongful-death-damages
