Statute of Limitations for Breach of Fiduciary Duty in Utah
6 min read
Published October 18, 2025 • Updated March 22, 2026 • By DocketMath Team
Trust release 4
This page has legal or numeric text that still needs claim-level inventory before we can treat it as verified.
Overview
In Utah, a breach of fiduciary duty claim is usually treated like many other civil claims under the state’s general statute of limitations (SOL)—meaning the clock starts running when the claim “accrues” and you have a limited time to file in court.
DocketMath’s statute-of-limitations calculator is designed to help you translate those legal time limits into a concrete deadline. You’ll enter key dates (and, if applicable, choose any tolling-related inputs your situation supports), and the tool will compute the last day to file based on the rules you select.
Note: This page uses Utah’s general/default SOL. The jurisdiction data provided does not identify a claim-type-specific SOL rule for breach of fiduciary duty in Utah, so the analysis below follows the general rule referenced by the Utah courts.
Limitation period
Default SOL: 4 years
Utah’s general SOL period is 4 years for many civil actions. The Utah courts’ legal help materials describe the general statute of limitations as 4 years, and the statute cited for the general limitations framework is:
- Utah Code § 76-1-302 (general limitations statute, referenced in Utah court guidance)
Because no breach-of-fiduciary-duty-specific sub-rule is identified in the provided jurisdiction data, the default approach is:
- You generally have 4 years from accrual to file a breach of fiduciary duty lawsuit in Utah.
Accrual: the date that starts the clock
While the exact accrual trigger can be fact-intensive (for example, when the alleged breach occurred vs. when the plaintiff discovered it), the SOL calculation depends on the accrual date you select in DocketMath. Your deadline changes materially based on that choice.
Use this quick guide for planning:
- If you use an earlier accrual date, the SOL deadline will be earlier
- If you use a later accrual/discovery-related date (when you have a basis under applicable Utah doctrines), the SOL deadline will be later
Practical checklist for SOL inputs
Before you calculate, gather the dates that most often control the analysis:
- Breach/event date (e.g., transaction or act alleged to be the breach)
- Discovery date (if your situation uses a discovery-based accrual approach)
- Filing date (the date you plan to file or the date the complaint was actually filed)
Then run the DocketMath calculation to see whether the filing date falls before or after the computed deadline.
How DocketMath output changes with inputs
When you change inputs, the computed deadline shifts in a predictable way:
| Input you change | Likely effect on computed SOL deadline |
|---|---|
| Accrual date moves earlier | Deadline moves earlier (less time) |
| Accrual date moves later | Deadline moves later (more time) |
| You assume a tolling scenario | Deadline may move later (clock paused during tolling) |
| You use the computed “last filing date” | Helps you compare to actual filing timing |
Key exceptions
Utah SOL rules aren’t only about a number of years. Even when the general SOL is 4 years, exceptions and tolling doctrines can affect when the clock starts, pauses, or resets.
Tolling and other doctrines that may affect timing
Common categories that can change the practical deadline include:
- Tolling for certain protected statuses (for example, incapacity)
- Equitable doctrines (for example, where fairness concerns affect enforcement timing)
- Statutory tolling in specific circumstances created by Utah law
- Accrual/discovery-based timing where Utah doctrine allows a discovery-triggered accrual rather than a strict event date
Because this page is built from the general SOL rule identified in your jurisdiction data, it does not map every possible tolling doctrine to breach of fiduciary duty. Instead, think of this section as a guide for what to verify before relying on a deadline:
- Does your situation involve a reason the clock should not run from the breach date?
- Are you relying on a discovery-trigger rather than the date of the act?
- Is there a statute or court rule that clearly supports the tolling approach you intend to use?
Pitfall: Using the event date as the accrual date when the facts support a later accrual/discovery theory can produce a deadline that is too early—leading to unnecessary concern or mis-timed action.
Best practice for exception handling
If you suspect an exception applies, your goal is not just “pick a tolling option,” but to ensure the selected approach aligns with the specific Utah doctrine applicable to your facts. DocketMath’s calculator helps you model outcomes, but the legal fit of an exception still depends on the underlying facts.
Statute citation
- General SOL period: 4 years
- General statute referenced: Utah Code § 76-1-302
- Utah courts legal help page (general limitation guidance): https://www.utcourts.gov/en/legal-help/legal-help/procedures/statute-limitation.html
Because the provided jurisdiction data did not identify a claim-type-specific SOL for breach of fiduciary duty, the general/default 4-year rule is the baseline used here.
Use the calculator
DocketMath’s statute-of-limitations calculator turns the 4-year general SOL framework into a concrete deadline.
Primary CTA: statute-of-limitations tool
What to enter
To get the most accurate output, use the most defensible dates for your scenario:
- Accrual date (the date you want to treat as when the claim began)
- General SOL selection (default to the Utah general rule for 4 years)
- Any tolling-related choices supported by your facts (only select those you can justify)
What you’ll get back
After you submit inputs, DocketMath will calculate:
- Computed “last day to file” under the selected SOL rule
- A quick comparison point so you can assess whether a given filing date is likely within the time window
If you change the accrual date by even a few months, the deadline shifts by the same amount—so rerunning the calculator with alternative accrual assumptions can help you understand the range of risk.
Warning: A computed deadline is only as reliable as the dates and assumptions you input. Confirm your key dates (event date, discovery date, and filing date) before treating the output as definitive.
Related reading
- Choosing the right statute of limitations tool for Vermont — Tool comparison
- Choosing the right statute of limitations tool for Connecticut — Tool comparison
