How to calculate pain and suffering damages in Tennessee

How to calculate pain and suffering damages in Tennessee

8 min read

Published May 4, 2026 • Updated April 23, 2026 • By DocketMath Team

Verification issue found

Trust release 4

This page includes a legal claim or source that failed the current primary-source review.

Direct answer

Run this scenario in DocketMath using the Damages Allocation calculator.

In Tennessee, you generally don’t calculate “pain and suffering” using a fixed statutory formula (like a set multiplier or per-day rate). Instead, pain and suffering is typically treated as non-economic damages, and the number ultimately comes from the evidence (testimony and records) and the fact-finder’s judgment.

The clearest Tennessee “number” you can anchor to from the jurisdiction data you provided is the 1-year general limitations period, which affects whether a claim can be filed on time—not how pain and suffering is computed once liability is decided. That timing reference is Tennessee Code Annotated § 40-35-111(e)(2) (1-year general SOL period).

You can still use DocketMath to model and allocate damages in a structured, auditable way (for example, keeping economic damages separate from non-economic damages), but think of DocketMath as a workflow and organizer for your inputs, not a replacement for jury evaluation.

Note: This is a practical guide to damage modeling workflows in Tennessee, not legal advice, and it can’t guarantee any outcome in court.

What you need to know

“Pain and suffering” is usually discussed as non-economic damages—the real-world impact that doesn’t come with a bill you can total up. Common examples include:

  • Physical pain (type, intensity, and how long it lasted)
  • Emotional distress / mental anguish
  • Loss of enjoyment of life
  • Disruption of normal life (sleep, mobility, concentration, daily activities)

When people say they want to “calculate pain and suffering” in practice, they’re usually doing one of these:

  • Estimating a settlement range based on evidence strength
  • Allocating damages across categories (economic vs. non-economic)
  • Building a defensible narrative linking symptoms to medical care and functional limitations

How the Tennessee rule you have fits in

The Tennessee statute you provided—Tennessee Code Annotated § 40-35-111(e)(2)—is about the general limitations period. Per your note, no claim-type-specific sub-rule was found, so the 1-year period is best treated as the default/general period.

That means your SOL analysis determines whether a claim is timely; it doesn’t give a damages math schedule for pain and suffering.

How DocketMath fits in

Use DocketMath (damages modeling tool) at /tools/damages-allocation to help you:

  • Enter economic damages (medical bills, wage loss, out-of-pocket costs)
  • Model non-economic damages as an allocation you justify using your evidence (duration, severity, and functional impact)
  • Run scenario comparisons to see how changes to non-economic assumptions affect totals

If you keep your inputs organized, DocketMath helps you avoid the most common modeling problems—especially mixing economic and non-economic impacts.

Step-by-step

Use this workflow to model and allocate pain and suffering damages in Tennessee with DocketMath.

1) Confirm your time window before you model

Start by separating timeliness from damages:

  • Tennessee’s default/general limitations period (from your provided data) is 1 year under Tennessee Code Annotated § 40-35-111(e)(2).
  • That timing affects whether your claim is fileable, not how pain and suffering is calculated once a claim is otherwise viable.

2) List economic damages first (to prevent double-counting)

In DocketMath’s /tools/damages-allocation workflow, begin with economic categories supported by objective evidence:

  • Medical expenses (billed/paid, plus reasonable related costs)
  • Prescriptions/therapy out-of-pocket costs
  • Wage loss (lost hours × hourly rate, or pay-stub summaries)

This matters because pain and suffering should generally represent the non-economic experience, not the same medical line items again.

3) Build an evidence inventory for the non-economic part

Next, translate “pain and suffering” into measurable (or at least clearly described) inputs:

  • Start date of symptoms and peak timing (early vs. later)
  • Severity level (how intense; use a consistent scale in your model)
  • Duration (how long the symptoms lasted and whether they resolved or persisted)
  • Treatment history (follow-ups, imaging, PT, medication, surgery if applicable)
  • Functional impact (sleep disruption, difficulty walking/lifting, missed activities, inability to concentrate, limits on driving/household tasks)
  • Credibility factors (consistency over time; alignment between symptom reports and treatment)

4) Choose a pain-and-suffering modeling approach (allocation, not magic math)

Since Tennessee does not give you a provided pain-and-suffering formula in your supplied rule, use an allocation method that tracks your evidence, such as:

  • Single-number non-economic allocation (based on your severity × duration narrative)
  • Range modeling (low/medium/high) for settlement discussion
  • Reallocation across categories if the evidence supports that one category is stronger than another (for example, stronger proof of functional limits than emotional distress)

5) Enter inputs in DocketMath and keep units consistent

When you get into /tools/damages-allocation:

  • Use the same time units across duration-related fields (days/weeks/months)
  • Keep medical and wage loss in their economic sections
  • Enter non-economic assumptions in the non-economic allocation section(s)
  • Document what you changed between scenarios (e.g., “severity assumed 6/10 instead of 4/10”)

The output should change in a predictable way:

  • Increase duration or functional impact → non-economic allocation should generally increase.
  • Change economic inputs → economic totals should change.

6) Run multiple scenarios (sensitivity testing)

At minimum, run 2–3 scenarios:

  • Low: shorter duration or milder functional impact
  • Medium: moderate duration and disruption
  • High: longer duration and stronger evidence of impairment

This helps you see how sensitive the total is to the pain/non-economic assumptions.

7) Do internal consistency checks

Before you finalize:

  • Are your “pain” duration and severity supported by treatment timing and follow-ups?
  • Did you avoid counting the same harm twice (for example, including medical costs both as economic damages and indirectly again via “pain” assumptions)?
  • Can someone reading your narrative map each non-economic assumption to a piece of evidence?

Key statutes and citations

Limitations period vs. damages computation

Tennessee Code Annotated § 40-35-111(e)(2) (as provided in your jurisdiction data) indicates a General SOL Period: 1 years, with a link here:
https://law.justia.com/codes/tennessee/title-40/chapter-35/part-1/section-40-35-111/

Important clarification for your calculator workflow:

  • This statute reference is about timeliness (when you must file), not a formula for pain and suffering.

No claim-type-specific sub-rule found

Per your note, no claim-type-specific sub-rule was found, so treat the 1-year period as the default/general limitations period in the way you frame timeliness—while handling damages allocation separately.

Common pitfalls

  • Pitfall: Using the 1-year SOL period as if it multiplies damages

    • The 1-year reference is a limitations concept, not a pain calculation method.
  • Pitfall: Double-counting medical impacts

    • Medical bills and wage loss typically belong in economic damages. Pain and suffering should reflect the non-economic experience (pain, distress, loss of enjoyment), not the same amounts again.
  • Pitfall: Vague pain duration

    • “Pain for months” without tying it to appointments, imaging, treatment frequency, or consistent symptom reporting often weakens the modeling logic. Your DocketMath inputs should mirror what your evidence can support.
  • Pitfall: Skipping functional limitations

    • Non-economic assumptions are easier to defend when they describe real functional changes (sleep, mobility, daily tasks, concentration).
  • Pitfall: Relying on one point estimate

    • Pain/non-economic damages often change as evidence is evaluated. Scenario runs show how totals shift and help you avoid overcommitting to a single number.

Run the numbers

Here’s a practical way to run the damages-allocation model in DocketMath for Tennessee.

1) Define your inputs (copy this as a checklist)

Use your evidence to fill these categories:

  • Economic

    • Medical expenses
    • Wage loss
    • Other out-of-pocket costs
  • **Non-economic (pain and suffering allocation inputs)

    • Pain duration
    • Symptom severity assumptions
    • Functional impairment duration
    • Ongoing vs. resolved status

2) Scenario table (how outputs should respond)

Use scenario planning in DocketMath by adjusting only the non-economic assumptions between runs:

ScenarioSymptom durationFunctional disruptionNon-economic allocation (pain)Expected output effect
LowShorterLess disruptionLower allocationSmaller non-economic total
MediumModerateModerate disruptionMid allocationMiddle non-economic total
HighLongerMore disruptionHigher allocationLarger non-economic total

Rule of thumb:

  • If you increase duration or functional impairment (and keep economic numbers steady), your non-economic allocation should generally increase without moving economic totals—unless you intentionally change them.

3) Sanity-check before you finalize

Before relying on your DocketMath output totals:

  • Do your pain assumptions line up with treatment timeline?
  • Did you use consistent severity/duration terms across the model?
  • Did you keep economic and non-economic categories separate to reduce double-counting risk?

Related reading