How Wrongful Death Damages rules vary in Tennessee

What varies by jurisdiction

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

In Tennessee, wrongful death damages rules aren’t a single, one-size-fits-all “headline” that changes for every case. Instead, the most meaningful jurisdiction-aware differences you’ll notice typically come from:

1. Timing rules tied to whether a claim can be filed, and
2. How damages are calculated once the claim is legally viable (i.e., the calculator math vs. the filing deadline).

This post focuses on the jurisdiction-aware parts you’ll see in DocketMath, keyed to Tennessee (US-TN), and explains how your inputs and outputs change when the timing rule varies across jurisdictions.

The timing baseline (Tennessee-specific)

A key Tennessee jurisdiction rule you should verify is the general statute of limitations (SOL) period. For Tennessee wrongful-death actions, the default timing rule provided by your jurisdiction data is:

• 1 year general SOL period

Source (as published by Justia): Tennessee Code Annotated § 40-35-111(e)(2)
https://law.justia.com/codes/tennessee/title-40/chapter-35/part-1/section-40-35-111/

Default period vs. claim-type-specific sub-rules (important)

Your jurisdiction data also states: no claim-type-specific sub-rule was found. That means the content should treat 1 year as the general/default period for Tennessee under this source—not as a special period limited to a particular sub-type of wrongful-death claim.

So, for DocketMath (US-TN) using the provided reference:

• Default SOL used by DocketMath (US-TN): 1 year
• No separate claim-type-specific SOL sub-rule identified from the provided statute reference

Why this matters for damages work in DocketMath

DocketMath’s wrongful-death-damages calculator can help you organize and estimate damages based on inputs (lost earnings, life expectancy assumptions, etc.). But the jurisdiction-aware rule—here, the Tennessee SOL baseline—affects whether the damages scenario is actionable, not just the numeric estimate.

A practical “compare states” effect:

• If you compare Tennessee to other jurisdictions, you may see different SOL windows.
• That means a damages projection can be numerically reasonable while still being non-viable if filed outside Tennessee’s deadline.

Inputs that commonly influence outputs (while timing governs viability)

Even when Tennessee’s SOL sets the viability question, damages outputs usually move when you change inputs such as:

• Economic losses (e.g., lost earnings or earning capacity)
• Non-economic components (only if your calculator framework allows it)
• Timing / life-expectancy assumptions used to spread losses over time
• Discount rate / present value assumptions (if included in the calculator)

DocketMath helps you keep assumptions consistent across scenarios, and then run sensitivity checks (for example: changing earning growth assumptions or life expectancy assumptions).

To get started in Tennessee, use: /tools/wrongful-death-damages.

What to verify

Before relying on any output, confirm the jurisdiction-aware pieces that affect whether a Tennessee damages scenario is usable.

• The governing rule or statute for the jurisdiction.
• Any local rule overrides or administrative guidance.
• Effective dates and whether amendments apply.

1) Confirm the SOL baseline (the 1-year default)

From the provided reference:

• Tennessee general SOL period: 1 year
• Statute reference: Tennessee Code Annotated § 40-35-111(e)(2)
  https://law.justia.com/codes/tennessee/title-40/chapter-35/part-1/section-40-35-111/

Practical verification checklist:

2) Confirm you’re applying the correct jurisdiction-aware rule set (US-TN)

Quick checks to ensure DocketMath isn’t using a mismatched baseline:

3) Separate “damages math” from “claim viability”

A clean way to structure your use of DocketMath:

• Step A (DocketMath math): compute/estimate damages using your chosen inputs.
• Step B (Tennessee timing): verify whether the claim would fall within the 1-year default timing baseline.

If Step B fails, you can still use Step A for planning or settlement-model discussions, but you should treat the scenario as not viable for filing purposes in Tennessee.

4) Document inputs for repeatable comparisons

When you change an input in DocketMath, record what changed so you can compare runs later. For example:

• Change in annual income assumption (e.g., $50,000 → $55,000)
• Change in work-life horizon or life expectancy
• Change in discount rate (if used)
• Re-run and save a consistent versioned set of assumptions

Related reading

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