Statute of Limitations for Breach of Fiduciary Duty in Tennessee

5 min read

Published March 22, 2026 • By DocketMath Team

Overview

In Tennessee, a claim for breach of fiduciary duty is subject to a statute of limitations (SOL)—a deadline for filing suit. Missing that deadline can lead to dismissal even when the underlying facts seem compelling.

DocketMath’s Statute of Limitations Calculator helps you apply Tennessee’s time rules to key dates (like the date of the alleged wrongful act, when the injury was discovered, and when the parties’ relationship ended). This guide focuses on Tennessee law and how to use the calculator effectively, not on legal strategy.

Note: The SOL rules you use depend on how Tennessee classifies the claim for timing purposes. This article describes the general/default SOL period applied when no claim-type-specific sub-rule is identified.

Limitation period

Default/general SOL period (no claim-type-specific sub-rule identified)

For Tennessee, the general SOL period referenced for this topic is:

  • **1 year (General SOL Period: 1 year)

The jurisdiction note you provided is clear: no claim-type-specific sub-rule was found, so the 1-year default is the best baseline to start with. In practice, this means the filing deadline is measured from the relevant trigger date the law uses (commonly tied to discovery or accrual concepts, depending on the statute and claim framing).

How the 1-year deadline typically affects planning

A one-year SOL can be tight. To manage the timeline, you’ll want to:

  • Identify the earliest date you can reasonably argue as the start of the clock (often the date of the wrongful conduct or the date the claimant discovered—or reasonably should have discovered—the problem).
  • Track when the injury became known (not just when the harm occurred).
  • Consider whether any event could alter the trigger date (see “Key exceptions” below).

Inputs that change the output in DocketMath

When you use DocketMath, the calculator output depends on what you enter. For example:

  • If you enter an earlier trigger date, the computed deadline will move earlier.
  • If you enter a discovery/notice date that is later than the conduct date, the computed deadline will move later.

A simple way to think about it:

  • Earlier trigger date → fewer days to file
  • Later trigger date → more time to file

Key exceptions

Even when a default period is 1 year, Tennessee timing rules may shift because certain doctrines can affect the deadline. Below are common categories to check when evaluating deadlines—use them as a checklist for what to verify with your documents.

Discovery-related concepts

Some statutes include timing language tied to when a claimant knows or should know of an injury. If the relevant Tennessee rule you’re applying is discovery-based, your “clock start” can be the discovery date rather than the act date.

Checklist:

Tolling and pauses in the clock

Tolling doctrines can pause or extend the limitation period under certain circumstances. These are fact-driven and depend on the specific statute and claim posture.

Checklist:

Fraud or concealment concepts

In some contexts, fraudulent concealment can delay accrual or trigger tolling. If there is evidence that key facts were actively hidden, the deadline may not run from the earliest possible conduct date.

Checklist:

Warning: Exceptions are highly sensitive to the exact legal theory and the statutory language applied. This guide does not decide which exception (if any) governs your situation—its purpose is to help you run the timing analysis correctly in DocketMath using documented dates.

Statute citation

The general/default SOL period referenced for this Tennessee timeframe is:

General SOL period used here: 1 year (General SOL Period: 1 year)

Important constraint based on your brief:

  • No claim-type-specific sub-rule was found, so this 1-year period is presented as the general/default baseline rather than a claim-specific conclusion.

Use the calculator

Use DocketMath’s Statute of Limitations Calculator to compute a deadline from the dates you have. Since you’re working with a 1-year baseline, the calculator’s core job is to:

  1. Accept your chosen start/trigger date (for example, discovery/notice or accrual date you intend to apply under the default rule)
  2. Add 1 year
  3. Output a calculated “latest filing date” based on the inputs

Practical input checklist (what to gather before you click “calculate”)

  • Date of the alleged breach (if you have it)
  • Date you discovered the breach (or the date facts became known)
  • Date the fiduciary relationship ended (sometimes relevant for trigger selection)
  • Any documentable events that support a later trigger (for example, when concealment ended)

How outputs change when you adjust inputs

  • Update the trigger date → the computed deadline shifts accordingly
  • If you use a later discovery/notice date instead of the act date, your “latest filing date” will move forward by the difference between those dates

Pitfall: Using an “assumed” discovery date (without any documentary support) can produce a deadline that’s later than what the court could accept. Prefer dates tied to emails, invoices, statements, account logs, or other records.

Primary CTA

To run the timing calculation, use DocketMath’s Statute of Limitations Calculator.

Related reading