How to calculate Wrongful Death Damages in Nevada

Quick takeaways

• Nevada wrongful-death claims are authorized by statute when death is caused by the defendant’s “wrongful act or neglect.” See Nev. Rev. Stat. § 41.085.
• Nevada’s statute focuses on who may sue, not on a detailed numeric damages formula. In practice, you’ll use DocketMath to structure the economic-loss inputs (income/earning capacity, support/services, and the damages horizon) and then align your output with Nevada’s wrongful-death framework.
• Your DocketMath output is driven mainly by the time horizon and the loss categories you select—especially any assumptions about future support/services and any economic losses you model.
• No jurisdiction-specific “sub-rule” period was found in the provided Nevada statute text (i.e., nothing that looks like a special calculation period for a particular claim type). Treat the general/default authorization as your baseline and focus on your inputs and supporting evidence.
• To improve clarity and defensibility, document your assumptions (work life expectancy or model horizon, earning rate, and—if used—discounting approach) and keep them consistent across scenarios.

Inputs you need

To calculate wrongful-death damages in Nevada (US-NV) using DocketMath, collect the data that drives economic-loss components and time-based assumptions. Depending on your DocketMath workflow, you’ll typically enter values in categories like the ones below.

1) Decedent’s economic profile (the “baseline”)

• Gross income / earning capacity (annual or monthly)
• Employment status (employed, self-employed, or other)
• Income variability (if earnings fluctuate, provide an average and the period used)
• Pre-death benefits relevant to support calculations (if your workflow allows inclusion)

2) Family/support relationship

• Who qualifies as heirs / representatives for the claim under Nev. Rev. Stat. § 41.085
• Support/services provided (if the model includes household services or non-economic support valued in economic terms, enter the estimated value)

3) Time horizon and survival assumptions

• Estimated start date for damages (commonly the date of death for the wrongful-death component)
• End date or period length (e.g., a modeled life expectancy window or the horizon you choose to calculate)
• Age at death (for scaling time periods and horizon length)

4) Offsets and adjustments (only if your DocketMath workflow supports them)

• Offsets (amounts already provided that may reduce damages, if the calculator includes subtraction fields)
• Discounting assumptions (if the calculator includes present value calculations), such as:

  • Discount rate
  • Compounding/annualization convention (if applicable)

5) Costs tied to damages (only if included in your model)

• Reasonable funeral and burial expenses (if your workflow includes a slot)
• Other documented economic expenditures attributable to the death (only if supported by your selected categories)

Nevada-specific anchor: who brings the action

Nevada’s authorization clause explains that heirs and personal representatives may maintain an action for damages when death is caused by the wrongful act or neglect of another. That’s the statutory permission to pursue damages—not, in the provided excerpt, a line-item damages formula.

• Nev. Rev. Stat. § 41.085: “When the death of any person … is caused by the wrongful act or neglect of another, the heirs of the decedent and the personal representatives of the decedent may each maintain an action for damages…”
  Source: https://www.leg.state.nv.us/nrs/NRS-041.html#NRS041Sec085

How the calculation works

Use DocketMath to turn your inputs into a damages total. While the exact on-screen field names can vary, most workflows follow the same logic: project economic loss across a damages horizon, then apply timing adjustments (such as present value) and apply offsets (if supported).

Below is a practical Nevada-aligned approach.

Step 1: Validate the Nevada wrongful-death premise (framework check)

Before entering numbers, confirm the core statutory trigger:

• Death must result from another party’s “wrongful act or neglect.”
• The claim must be brought by parties within the statutory categories described in Nev. Rev. Stat. § 41.085 (notably heirs and/or personal representatives).

Because the statute text provided here does not appear to create a special calculation sub-rule (e.g., a different time period for a particular wrongful-death damages “type”), treat the statute as the authorization/framework and perform the economic calculation using the categories and horizon structure you model in DocketMath.

Step 2: Build economic loss using your decedent inputs

In DocketMath, you’ll typically:

1. Compute a loss rate per time unit (monthly or annual) based on your inputs.
2. Multiply by the damages horizon (the period your model covers).
3. If present value is enabled, convert future totals to present value using your discount settings.

A conceptual flow looks like:

• loss per time unit × number of time units in horizon = projected loss
• then projected loss adjusted for discounting/offsets (if enabled)

Step 3: Add additional economic components (only if enabled)

If your wrongful-death-damages calculator supports modules for certain categories, add them consistently:

• household services/support valuation (if included in your workflow)
• funeral-related or other economic cost categories (if your workflow captures them)

Avoid double counting:

• If you already included income/earning capacity as a basis for support, don’t separately add another category that measures the same economic concept unless you can clearly justify that they are distinct.

Step 4: Apply offsets and adjustments (if your workflow includes them)

Some DocketMath runs allow offsets. Apply offsets carefully:

• Subtract offsets from the relevant loss category (or categories) they affect.
• Confirm the calculator’s offset field does what you intend (e.g., reduces total loss rather than changing the underlying time series incorrectly).

Step 5: Test sensitivity (what changes the output most)

After generating results, run targeted “what-if” scenarios focused on the biggest drivers:

• Earnings/earning capacity (small changes can move totals)
• Time horizon length/end date (often a major driver)
• Discount rate/present value settings (higher rates usually reduce present value)

Pitfall to avoid: Don’t change multiple assumptions at once during sensitivity testing unless you’re prepared to explain which change caused the difference. Keep changes isolated and document why.

Step 6: Produce a Nevada-aligned calculation narrative

Even though Nev. Rev. Stat. § 41.085 (as provided) does not prescribe a specific numeric damages equation, you can still align your output with Nevada’s framework by clearly stating:

• the statutory trigger (“wrongful act or neglect” causing death)
• the claimant category (heirs and/or personal representatives)
• the economic-loss categories and horizon used in DocketMath

Use the tool (inline CTA)

Open DocketMath wrongful-death damages here: /tools/wrongful-death-damages

Common pitfalls

1. Treating § 41.085 as a detailed damages formula

   • The provided excerpt establishes the right to maintain an action for damages by heirs/personal representatives when death is caused by wrongful act or neglect.
   • It does not provide a claim-type-specific numeric equation in the provided text.
   • Use the statute as the authorization/framework and rely on your DocketMath category/horizon build for the numeric structure.

2. Double counting support/services

   • Household services/support estimates can overlap with income-based support models.
   • If your calculator allows both, ensure your definitions are consistent (what one category measures vs. what the other measures).

3. Time horizon drift

   • Wrongful-death totals are often sensitive to the endpoint.
   • Keep the same method of choosing the horizon when comparing scenarios.

4. Unsubstantiated income projections

   • If you input projected income, be consistent about whether it reflects an average, includes growth, or accounts for irregularity.

5. Present value settings without documentation

   • If DocketMath uses discounting, document:

     • the discount rate
     • the timing convention used
     • the start date and horizon structure

6. Offsets entered without category mapping

   • Offsets should reduce the relevant part of the damages total.
   • If you enter an offset, verify it’s applied to the correct categories (or to the correct line item) to prevent over-reduction or inflating net figures.

Sources and references

• Nev. Rev. Stat. § 41.085 — Wrongful death action authorization; heirs and personal representatives may maintain an action for damages when death is caused by wrongful act or neglect.
  https://www.leg.state.nv.us/nrs/NRS-041.html#NRS041Sec085

Next steps

1. Open the Nevada wrongful-death calculator in DocketMath: /tools/wrongful-death-damages
2. Gather and verify your key inputs:

   • decedent income/earning capacity
   • age at death (and ages/time assumptions used)
   • damages horizon start/end dates (or length)
   • discount rate settings (if your run uses present value)
3. Run a baseline scenario.
4. Run 2–3 targeted sensitivity tests (income, horizon, discount rate).
5. Save your calculation narrative so it clearly ties back to:

   • Nev. Rev. Stat. § 41.085 (who may sue; wrongful act/neglect causing death)
   • the economic categories and time horizon you entered into Docket