Statute of Limitations for Breach of Fiduciary Duty in Oklahoma

7 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

In Oklahoma, a “breach of fiduciary duty” claim is constrained by a statute of limitations (SOL)—a deadline for filing in court. If the deadline expires, defendants can typically seek dismissal or summary judgment based on timeliness. This article explains the Oklahoma SOL framework you can use when you’re trying to estimate whether a filing is timely, using the general/default limitations period stated in Oklahoma’s SOL statutes.

DocketMath’s statute-of-limitations calculator helps you turn the rule into a date range using an incident date and filing date. This is a practical tool for planning and case management; it isn’t legal advice.

Note: In the information provided here, no claim-type-specific sub-rule for breach of fiduciary duty was identified. The analysis below therefore uses Oklahoma’s general/default SOL period.

Limitation period

Oklahoma’s general/default SOL period: 1 year

The general limitations period referenced for Oklahoma is one (1) year. The general statute cited for the default period is:

22 O.S. §152 (general rule referenced for the one-year period)

Because no breach-of-fiduciary-duty–specific rule was found in the provided jurisdiction data, the guidance below applies the default 1-year deadline.

How to translate “1 year” into an actual deadline

A typical SOL calculation turns on two inputs:

Date of the alleged breach / wrongdoing (or the date the conduct giving rise to the claim occurred)
Date you plan to file (or the date the claim was received/initiated in court)

DocketMath will calculate whether the filing date falls within the one-year window. When you change either date, the output changes accordingly:

If you move the filing date later, the “within SOL” likelihood decreases.
If you move the incident/breach date earlier, the deadline effectively moves earlier relative to the filing date.

Practical checklist: what dates to use

Use the date that best matches your underlying facts. Common options include:

Date the fiduciary obligation was violated (e.g., the transaction date)
Date the fiduciary action was completed
Date the breach was discovered (only if a recognized tolling/delay doctrine applies—see exceptions below)

To keep your calculation consistent, pick one date category and apply it uniformly across scenarios (for example, test “incident date” and “discovery date” separately in DocketMath if you want to model both outcomes).

Key exceptions

Oklahoma SOL questions often hinge on doctrines like tolling, estoppel, or special statutory rules. This section flags the main categories you should evaluate—even though your baseline default is the one-year period.

Warning: An “exceptions” step can dramatically change the deadline. Even if the default SOL looks short (1 year), tolling or delay doctrines may extend it—while other facts may start the clock earlier than you expect.

1) Tolling doctrines (pause/extend the clock)

Consider whether circumstances justify pausing the running of the limitations period. Tolling can arise from things like:

Legal incapacity of the claimant
A statutory tolling provision (if applicable to the situation)
Courts treating the limitations clock as delayed due to specific facts

Because this post uses a default rule (no claim-type-specific sub-rule identified), you should treat tolling as fact-dependent and confirm whether the doctrine fits your scenario.

2) Discovery-based arguments (when the claim should accrue)

Some legal systems tie limitations to “accrual,” which can be connected to discovery. If you believe the breach wasn’t reasonably discoverable at the time it occurred, you may want to model an alternative accrual date in DocketMath.

Important: This blog entry does not assert that breach of fiduciary duty accrues on discovery in Oklahoma. Instead, it highlights discovery as a key modeling variable when exceptions are available.

3) Equitable estoppel (preventing a limitations defense)

If a fiduciary (or the opposing party) took actions that prevented timely filing—such as misleading conduct—some courts may apply equitable estoppel to stop the SOL defense from running.

Again, this is not automatic; it depends on evidence and timing.

4) Contractual terms (sometimes relevant)

In some contexts, parties may attempt to define when claims accrue or adjust timing through contract. Any such term must still align with Oklahoma law and public policy, and it may not be enforceable in every situation.

For deadline planning, you can treat contractual provisions as an additional input to review—not as a substitute for statutory limitations analysis.

Quick “exceptions to test” table

Scenario you’re evaluating	What to test in DocketMath	Why it matters
You learned about the breach later than it happened	Try both “incident date” and “discovery/notice date”	Changes start of the clock if accrual is delayed
A party’s conduct may have delayed filing	Consider tolling/estoppel models	Can extend or prevent SOL from running
A claimant’s capacity was legally limited	Model the effective start date	May delay commencement of the limitations clock
A statute other than the default applies	Verify whether the default should be replaced	A different statute can control the deadline

Statute citation

The default limitations period referenced in the jurisdiction data is:

22 O.S. §152 — general one-year limitations period

The jurisdiction data provided states:

General SOL Period: 1 years
No claim-type-specific sub-rule was found for breach of fiduciary duty
Therefore, the general/default period is used as the baseline.

If, after reviewing your particular facts, a different statute or tolling provision applies, the effective deadline can change.

For context, the source material linked for Oklahoma SOL discussion is: https://www.findlaw.com/state/oklahoma-law/oklahoma-criminal-statute-of-limitations-laws.html

(This link is provided for general Oklahoma limitations context; the specific statutory anchor used here is 22 O.S. §152.)

Use the calculator

Use DocketMath to compute whether your proposed filing date is likely within the default one-year SOL window under 22 O.S. §152.

Primary CTA: DocketMath Statute of Limitations Calculator

Inputs you’ll typically use

Check these before you click:

✅ Start date (default model): date of the alleged breach/triggering event
✅ Filing date: the date you plan to file or the date the action was initiated
✅ Jurisdiction: US-OK (Oklahoma)

How output changes when inputs change

After running the calculator:

If the filing date is more than 1 year after the start date, the result will move toward “outside SOL” (under the default model).
If you change the start date to a later discovery/notice date (for modeling purposes), the deadline shifts later and may change the outcome.
If you incorporate an exceptions scenario by using an adjusted effective start date, you can model extension effects—but only using start-date assumptions that match your facts.

Modeling workflow (practical)

To avoid relying on a single assumption:

Run 1: Incident/breach date → filing date
Run 2: Discovery/notice date → filing date (if facts support a delayed accrual theory)
Compare results and identify the “tipping point” date where the SOL flips from likely timely to likely time-barred.

This approach helps you see how sensitive the deadline is to the accrual timing.