How to run Wrongful Death Damages in DocketMath for Tennessee

Step-by-step

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

This is a practical walkthrough for running Wrongful Death Damages in DocketMath for Tennessee (US-TN), using Tennessee’s jurisdiction-aware rules where they apply. This is a how-to guide—not legal advice—and it’s meant to help you set up inputs correctly and understand what the calculator is doing with its selected jurisdiction rules.

1) Open the correct calculator

Start at the primary call-to-action:

• /tools/wrongful-death-damages

If you’re navigating internally, you can also reach the same tool from within DocketMath by locating the wrongful-death-damages calculator.

2) Confirm you’re using Tennessee (US-TN) rules

On the calculator page, set the jurisdiction to:

• **US-TN (Tennessee)

DocketMath uses jurisdiction-aware defaults so your calculation stays aligned with the selected state.

3) Understand the Tennessee time rule used by the calculator

For Tennessee, wrongful death claims have a general default statute of limitations period of 1 year.

DocketMath will reflect the general/default period for the Tennessee rule you selected. The cited provision used here is:

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

Important note (based on the provided jurisdiction data): No claim-type-specific sub-rule was found in the jurisdiction data provided. That means the tool should be understood as using the general/default 1-year period for this setup, rather than a more specific wrongful-death override.

4) Enter the damages inputs the calculator requests

The wrongful death damages calculator will ask for several numeric inputs (you’ll see the exact fields directly in DocketMath). Use these steps to enter values accurately:

• Enter amounts as plain numbers
  If a field doesn’t accept punctuation, avoid commas (e.g., use 50000 rather than 50,000).
• Match the timeline to the SOL-related inputs the tool references
  When the UI asks about “date of death,” “filing date,” “event date,” “effective date,” or “time since death,” use the definitions implied by the field labels.
• Use consistent units

  • If the field asks for annual income/earnings, enter annual amounts.
  • If the field implies a different periodicity (like weekly/monthly), follow the label exactly.

Quick input checklist

Use this before running the calculation:

5) Review how outputs change when you adjust inputs

After you run the calculation, DocketMath computes damages based on the values you entered and the Tennessee jurisdiction defaults.

Common “knobs” that change the result:

• Timing inputs (SOL-related behavior):
  Changing the time between the event date (for example, death) and the filing/effective date can change whether the tool applies a 1-year default and whether it flags timing.
• Economic inputs (earnings-related totals):
  Higher earnings assumptions (or different time windows, if included) typically increase economic loss totals.
• Non-economic components (if the tool includes them):
  If the calculator includes non-economic damages as a separate line item, the overall result will vary based on the values you enter for those categories.

To understand cause-and-effect, adjust one variable at a time:

1. Run once.
2. Change only one input (for example, update the filing/effective date).
3. Run again and compare.

6) Export or capture the output for review

After running the calculation:

• Copy the results shown on-screen.
• Save a screenshot or export the output if DocketMath provides an option.
• Record the inputs used—especially the dates—because SOL timing is sensitive, and even small date changes can affect any timing flags.

Caution / disclaimer: This is a computational workflow guide. It doesn’t determine legal entitlement, eligibility, or the ultimate merits of a case. Treat the output as an estimate based on the inputs and Tennessee jurisdiction defaults you selected in DocketMath.

7) If DocketMath flags timing, interpret it using the 1-year default

If the tool indicates the matter may fall outside the applicable period, interpret that as the calculator’s result under Tennessee’s selected general/default 1-year rule:

• **1-year default based on Tenn. Code Ann. § 40-35-111(e)(2)

Because the provided jurisdiction data did not identify a wrongful-death-specific sub-rule, the tool’s behavior in this setup is best understood as applying the general/default 1-year period rather than a separate wrongful-death override (since none was provided).

Common pitfalls

These are the most common reasons people see unexpected outputs when running wrongful death damages in DocketMath for Tennessee.

• missing a required input
• using a stale rate or rule
• ignoring calendar or holiday adjustments
• skipping documentation of assumptions

If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.

Wrong jurisdiction selection (US-TN not set)

• If you run under a different state, the SOL/default rules won’t match Tennessee.
• Fix: Set the jurisdiction to US-TN before entering dates or damages inputs.

Date format errors or inconsistent event timing

• Even if you enter correct numbers for damages, SOL-related timing logic can change outcomes.
• Fix: Enter dates exactly as the tool expects, and ensure the “event date” and “filing/effective date” correspond to how the calculator labels those fields.

Assuming a claim-type-specific SOL override exists

• Your provided jurisdiction data explicitly states that no claim-type-specific sub-rule was found.
• Fix: Treat the calculator as using the general/default 1-year period under Tenn. Code Ann. § 40-35-111(e)(2) for this workflow.

Mixing annual and monthly figures

• If the field expects annual earnings but you enter monthly amounts (or vice versa), totals can be significantly off.
• Fix: Confirm the periodicity from the field label and enter values accordingly.

Editing multiple inputs at once

• If you change several inputs in one run, it’s hard to know which change caused the output to move.
• Fix: Make one change at a time and re-run so you can track deltas.

Try it

Use this quick “test run” method to validate your setup in DocketMath.

1. Open /tools/wrongful-death-damages.
2. Set jurisdiction to US-TN.
3. Enter your most important date pair (the calculator will label which dates correspond to the timing logic—e.g., event/death date and filing/effective date).
4. Confirm the timing rule shown aligns with the default 1-year period referenced by:

   • **Tenn. Code Ann. § 40-35-111(e)(2)
5. Enter one economic input (for example, earnings) and any required non-economic value (if the tool includes that field).
6. Run the calculation.
7. Make one deliberate change:

   • Example: move the filing/effective date by 30 days.
8. Run again and compare:

   • Did the calculator flag timing differently?
   • Did economic totals change in a way that matches your expectations?

Tip: When testing, prioritize date accuracy first. In a jurisdiction-aware SOL setup, small timing differences can affect flags and outputs more than small economic input tweaks.

Related reading

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