How to run Wrongful Death Damages in DocketMath for New Jersey

Step-by-step

Below is a jurisdiction-aware walkthrough for running Wrongful Death Damages in DocketMath for New Jersey (US-NJ). This guide focuses on how to set up the calculator inputs and interpret the output—without providing legal advice.

1) Open the New Jersey Wrongful Death calculator

Start at the primary CTA so you land on the correct workflow:

• /tools/wrongful-death-damages

If you’re already using DocketMath, make sure you select the jurisdiction = US-NJ (New Jersey) inside the tool.

2) Confirm the claim basis under New Jersey law (what you’re modeling)

New Jersey’s wrongful death cause of action is anchored in:

• N.J. Stat. § 2A:31-1
  https://law.justia.com/codes/new-jersey/title-2a/section-2a-31-1/

The statute’s core premise is: when death is caused by a wrongful act, neglect, or default that would have entitled the injured person to sue for damages if death had not occurred, then the person who would have been liable for the injury is liable in damages for the death.

In practical terms for a calculator run, DocketMath is helping you translate assumptions into numeric totals. Your job is to provide the inputs that match the damages structure the tool uses (for example, economic loss components, dependency/loss-of-support style inputs, and any non-economic fields the tool includes).

3) Understand the default time-period rule used by the calculator

Per your jurisdiction data note: No claim-type-specific sub-rule was found. That means DocketMath should treat the general/default period as the applicable period in this run.

In other words, the calculator will use the standard/default damages period you select in the UI (rather than a special wrongful-death-only timing override).

If the tool offers a “damages period” field, populate it using your selected default period, consistent with the “general/default” approach.

4) Enter the damages inputs (category by category)

DocketMath’s wrongful-death calculator generally expects inputs in a set of categories (exact labels can vary by interface). Common buckets include:

• Economic damages inputs (often earnable amounts and time duration)
• Loss-of-support / earning-related assumptions
• Dependency-related assumptions (if the tool separates categories)
• Non-economic damages (if the tool supports them in a separate field)
• Any other adjustable components included in the New Jersey run

Use this checklist to reduce mistakes:

• Enter the correct time duration for the damages period you’re modeling
• Use consistent units (for example, dollars per year vs. dollars per month)
• If the tool asks for before/after adjustments (taxes, benefits, offsets, etc.), apply them consistently across categories
• If there’s an option for multiple beneficiaries, confirm whether amounts should be per person or aggregated
• If the tool provides discounting / present value, ensure the setting matches the method you intend to model (and keep it consistent across comparisons)

5) Set assumptions that drive the output totals

After you enter the category inputs, watch the outputs update in real time. In a typical wrongful-death model, totals are sensitive to:

• Annual (or periodic) earning assumptions
• Whether benefits are computed gross or net
• The length of the damages period (your default period)
• Whether discounting / present value is applied
• Beneficiary allocation method (if multiple people are modeled)

Quick sanity-check method: change one assumption slightly (for example, +$10,000 in earnings or +1 year in duration) and confirm the direction of change in the output matches expectations (higher earnings/duration should usually increase totals).

6) Review New Jersey-specific framing tied to § 2A:31-1

While DocketMath performs numeric calculations, your New Jersey linkage should reflect the statute’s framing.

N.J. Stat. § 2A:31-1 uses an “as if death had not ensued” concept: it starts with what the injured person could have recovered if they had lived, and then converts it into damages resulting from the death.

Practical translation for a calculator run:

• If you’re modeling future losses, ensure your assumptions reflect that underlying “would have been entitled to maintain an action” logic as represented by the tool’s structure.
• Keep the damages period consistent with the default/general period approach, since no special wrongful-death sub-rule was identified in the jurisdiction data.

7) Export / save results (if available)

Once your totals look consistent with your assumptions:

• Save the run
• Export a summary (PDF/CSV, if the interface supports it)
• Keep a record of your key inputs so you can re-run later with one change (for version control and comparison)

Reminder: DocketMath is for calculating numbers from entered assumptions. It does not determine legal eligibility. Be sure your inputs match the assumptions/theory you’re trying to model under N.J. Stat. § 2A:31-1.

Common pitfalls

Wrongful death runs often go wrong in predictable ways. Use these guardrails before relying on the output.

1) Using the wrong damages period rule

Because your jurisdiction note indicates no claim-type-specific sub-rule was found, the calculator should apply the general/default period.

• Double-check that you did not apply a special timing override not supported by the available approach
• Confirm the damages period you entered is the one actually being used in the calculation

2) Mixing unit systems

A single unit mismatch can skew the result.

Common examples:

• Entering annual income when the tool expects monthly
• Entering weeks when the tool’s period is months or years
• Confusing whether wage amounts are treated as gross vs. net

3) Inconsistent beneficiary allocation

If you have multiple beneficiaries:

• Verify whether the tool asks for inputs per beneficiary or total combined
• Ensure your allocation sums match the loss/support theory you’re modeling

4) Discounting / present value mismatch

If DocketMath offers a discounting/present value option:

• Keep the discount setting consistent across scenario reruns
• Don’t compare outputs calculated with different discount methods unless you explicitly intend to

5) Category double counting

Some layouts can overlap categories (for example, an “economic total” field might already incorporate components).

• Pitfall: double counting can happen when you enter both (a) a combined economic figure and (b) separate line items that the tool also includes elsewhere.
• If the tool shows subtotals, use them to confirm which fields feed into the final sum.

Try it

Ready to run a New Jersey scenario?

1. Go to: /tools/wrongful-death-damages
2. Select US-NJ
3. Enter baseline assumptions:

   • Choose your default/general damages period (because no special wrongful-death sub-rule was found)
   • Provide category inputs in consistent units
4. Run the calculation and review:

   • Total damages
   • Category subtotals (if shown)
5. Perform a quick sensitivity test:

   • Increase the earnings assumption slightly (for example, +5–10%)
   • Re-run and confirm the total damages changes in the expected direction

If results change “randomly” after a small adjustment, stop and re-check:

• units,
• period length,
• beneficiary allocation,
• and any discounting/present value settings.

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