Statute of Limitations for Revival / Window Legislation in Tennessee

5 min read

Published March 22, 2026 • By DocketMath Team

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

Overview

Tennessee “revival” and “window” legislation comes up when a case or judgment is already tied up with time limits, and a party later tries to re-start enforcement or revive an action. In practice, the key question is whether the filing happens within a specific limitations period that governs when the revival effort must occur.

For Tennessee, the general default rule referenced in the governing statute is short: 1 year. The statute’s framework is tied to timing rules for post-judgment or post-disposition actions, and Tennessee Code Annotated § 40-35-111(e)(2) is the relevant provision to start with.

Note: This post is written for research and planning—not legal advice. Revival/window questions often depend on procedural history (what happened, when, and in what court), so treat the timeline guidance here as a starting point for issue-spotting.

If you’re trying to determine whether your planned revival/window filing is timely, DocketMath can help you model dates quickly using the statute’s default period.

Limitation period

Default (general) SOL period: 1 year

Based on Tennessee Code Annotated § 40-35-111(e)(2), the general/default statute of limitations is 1 year. The jurisdiction data provided here did not identify a separate “claim-type-specific” sub-rule, so you should treat 1 year as the default baseline unless you uncover a different controlling rule from the same statutory scheme or a specialized procedural statute.

What “1 year” means in day-to-day workflow

In a practical timeline, “1 year” typically means:

Pick the correct start date tied to your procedural milestone (for example, an order, disposition, or the triggering event described by the statute).
Count 365 days (or the appropriate day-count by calendar, depending on how you’re computing “one year” for your internal workflow).
Plan to file the revival/window action before the end of that 1-year window.

Because revival questions can turn on which event counts as the start date, your input selection matters.

How the outcome changes based on inputs

Using DocketMath, two date inputs usually drive the output:

Trigger date (start date): the event date that starts the limitations clock.
Planned filing date: the date you intend to file or re-file to revive.

Your output will switch between:

Timely: planned filing date occurs on/before the end of the 1-year period.
Potentially untimely: planned filing date occurs after the 1-year window expires.

If you shift the trigger date by even a few days (e.g., between an entry date and a receipt date), the filing deadline can move accordingly.

Key exceptions

Tennessee’s revival/window timing is commonly affected by doctrines or specific statutory carve-outs. However, the provided jurisdiction data did not identify a claim-type-specific sub-rule within § 40-35-111(e)(2). That means you should not assume the 1-year rule automatically changes for different categories of claims based solely on “type.”

That said, real-world timing issues often come from these categories:

Start-date disputes
Revival statutes frequently hinge on which procedural milestone triggers the clock. Two records may look similar (e.g., order entry vs. final disposition), but the statutory trigger could be tied to one of them.
Procedural posture complications
If the underlying matter is not in the posture the revival statute contemplates, the court may view the revival attempt as not fitting the statute’s intended mechanism.
Record timing / “entry” vs. “notice”
Some time computations run from the date of an order’s entry rather than notice to a party. That can affect deadline calculations.

Warning: Don’t treat “1 year” as a guarantee of eligibility to revive. Even if your deadline looks timely, the revival mechanism can fail if the statute’s prerequisites aren’t met by the facts and procedural history.

Because revival/window rules can be highly fact-dependent, DocketMath’s calculator is best used to structure your timeline and test dates, not to replace a detailed procedural review.

Statute citation

The controlling default rule for Tennessee’s revival/window limitations period referenced in the provided dataset is:

Tenn. Code Ann. § 40-35-111(e)(2) — 1-year general/default period
Source: https://law.justia.com/codes/tennessee/title-40/chapter-35/part-1/section-40-35-111/

Use the calculator

Use DocketMath’s Statute of Limitations calculator to translate the 1-year period in Tenn. Code Ann. § 40-35-111(e)(2) into an actionable filing deadline.

Start here: **DocketMath — Statute of Limitations calculator

Suggested inputs

When you open the calculator, consider entering:

Trigger date (start date): the date that starts the limitations clock under your procedural timeline.
Period: set to 1 year (the default rule from § 40-35-111(e)(2)).
Filing date (planned): your intended revival/window filing date.

Reading the result

The calculator output typically helps you answer:

“What is the deadline date?”
“Is my planned filing on or before the deadline?”
“How sensitive is the result to small date changes?”

If your result indicates you’re near the edge of the window, tighten your review process by re-checking:

the exact entry/trigger date you selected, and
the planned filing method (date of filing vs. date of receipt).

Pitfall: Filing late by even a few days can move you outside a one-year statutory window. If your trigger date is ambiguous, run multiple scenarios (e.g., earliest plausible trigger date vs. latest plausible trigger date) to see how the deadline changes.