Tolling the statute of limitations in Tennessee

Direct answer

Run this scenario in DocketMath using the Statute Of Limitations calculator.

In Tennessee, the default statute of limitations (SOL) period is 1 year under Tennessee Code Annotated § 40-35-111(e)(2). Using DocketMath (jurisdiction US-TN), you can model how tolling/suspension pauses may extend the deadline—but you’ll still need to confirm whether a tolling trigger legally applies to your specific situation.

A practical way to think about tolling: it’s not a universal “extra time” button. Tolling generally works by pausing the clock during a period the law recognizes, then resuming after that period ends. DocketMath helps you translate that into dates by building a timeline from your inputs.

Important note: The 1-year rule above is a general/default period. The provided jurisdiction data indicates no claim-type-specific sub-rule was found, so treat this as a starting point, not a guarantee for every possible Tennessee scenario.

If you want to run a timeline calculation now, start at: /tools/statute-of-limitations.

What you need to know

To do a tolling-aware SOL calculation in Tennessee with DocketMath, you typically need these inputs:

1. **Start date (accrual / triggering event date)
2. Base SOL length (for the provided default, 1 year)
3. Tolling/suspension intervals (dates when the SOL clock legally pauses)
4. Your relevant procedural date(s) (e.g., filing date you’re evaluating)

How tolling changes the deadline

When tolling applies, the SOL deadline often changes in a timeline-dependent way:

• The clock does not keep running during the legally recognized tolling interval.
• After tolling ends, the clock resumes.
• If the tolling period overlaps the last portion of the base SOL period, the adjusted deadline may shift forward by the most.

DocketMath’s role (and how to use it correctly)

DocketMath is designed to help you:

• keep one consistent timeline (start → base deadline → adjusted deadline),
• enter paused intervals as date ranges,
• and see how changing your inputs (especially tolling dates) changes the result.

Use it to answer: “Does my timeline (with tolling modeled) push the deadline past my filing date?”

Gentle reminder: This is a planning tool, not legal advice. SOL/tolling outcomes can be fact-specific, and the correct start date and tolling trigger matter.

Step-by-step

Follow this workflow using DocketMath for Tennessee (US-TN):

1. Open the SOL calculator

   • Go to: /tools/statute-of-limitations

2. Confirm the jurisdiction setting

   • Select Tennessee (US-TN) so the calculator uses the Tennessee/default framework.

3. Enter the start date

   • Use the date your SOL clock begins for your situation (often the accrual or a triggering event date).
   • If you’re uncertain, you can still model scenarios, but you should note the assumption so you can verify it later.

4. Set the base SOL period

   • For the default period provided, the base SOL is 1 year under Tenn. Code Ann. § 40-35-111(e)(2).
   • The jurisdiction data also says: no claim-type-specific sub-rule was found. That means you should treat 1 year as a default, not a universal rule for every claim type.

5. Add tolling (suspension) intervals

   • Enter the tolling start date and tolling end date (or use the calculator’s equivalent inputs).
   • If there are multiple tolling periods, enter each one so the timeline reflects them in order.

6. Review the results

   • Look for:

     • the base expiration date (no tolling), and
     • the adjusted expiration date (with tolling applied).

7. Stress-test your inputs

   • Adjust one input at a time to see sensitivity:

     • What if tolling starts 5 days later?
     • What if tolling ends 10 days earlier?
     • What if your start/accrual date is off by a couple of days?
   • This helps you understand which dates drive the adjusted deadline.

8. Document the timeline you modeled

   • Record:

     • your start date,
     • each tolling interval you entered, and
     • the resulting base vs. adjusted deadline.
   • If you later confirm facts or apply a different tolling rule, you can quickly update the calculation.

Key statutes and citations

For the default Tennessee SOL period used in the provided jurisdiction data, the baseline citation 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/

What the provided data does not confirm

• The jurisdiction data explicitly notes: “No claim-type-specific sub-rule was found.”
• As a result, the 1-year default should be treated as a general starting point, not a certainty that your scenario uses the same scheme.

If your case fits a specialized statutory category, the SOL (and the availability/type of tolling) may differ. A good workflow is: run the default in DocketMath, then verify whether a specialized rule overrides it.

Common pitfalls

These mistakes can make SOL/tolling results look reasonable while still being wrong:

• Using the wrong start date

  • A small shift can matter—especially when tolling ends near the base deadline.

• Treating tolling like a flat add-on

  • Tolling is usually modeled as a pause interval (clock stops/resumes), not a simple “add X days” without aligning to dates.

• Overlapping tolling intervals

  • If you enter two pauses that overlap, the pause duration can be double-counted unless the calculator merges/handles overlaps appropriately.

• Entering tolling dates without tying them to a legal trigger

  • If the tolling trigger doesn’t apply legally, the adjusted deadline you compute may be misleading.

• Assuming the default 1-year period applies universally

  • The provided data indicates it’s a default because no claim-type-specific sub-rule was identified.

Pitfall to watch: If you only know “how long” tolling lasted but not the actual start/end dates, you can place the pause in the wrong part of the timeline, producing a deadline that “moves” but moves to the wrong place.

Run the numbers

Here’s a practical way to sanity-check what DocketMath is doing when you toggle tolling.

Example A: No tolling

• Start date: 2026-04-15
• Base SOL: 1 year (default)
• Base deadline (no tolling): 2027-04-15

What you should see in DocketMath:

• Base expiration date = start date + 1 year
• Adjusted expiration date = same as base (because no tolling intervals were entered)

Example B: Single tolling interval

• Start date: 2026-04-15
• Base SOL: 1 year (default)
• Tolling interval: 2026-10-01 through 2026-12-31

How to think about it:

• The clock runs until the tolling start date (2026-10-01).
• It pauses during 2026-10-01 → 2026-12-31.
• It resumes after the tolling end date.
• The deadline shifts forward by the paused time according to DocketMath’s date-handling conventions.

Example C: Multiple tolling intervals (overlap check)

• Start date: 2026-01-10
• Base SOL: 1 year
• Tolling #1: 2026-03-01 to 2026-03-20
• Tolling #2: 2026-03-15 to 2026-04-01

Because these intervals overlap (2026-03-15 to 2026-03-20), you should verify DocketMath behavior:

• either it merges overlap automatically, or
• you need to adjust inputs so the pause isn’t double-counted.

Practical approach:

• Compare the deadline using your exact intervals,
• then compare against a “merged” interval version (if DocketMath doesn’t merge automatically) to ensure consistency.

Quick input checklist (before relying on the output)

Related reading

• Choosing the right statute of limitations tool for Vermont — How to choose the right calculator
• Statute of limitations in Singapore: how to estimate the deadline — Full how-to guide with jurisdiction-specific rules
• Choosing the right statute of limitations tool for Connecticut — How to choose the right calculator