Statute of Limitations for Breach of Fiduciary Duty in Ohio

Overview

In Ohio, the statute of limitations (“SOL”) for a breach of fiduciary duty claim is generally driven by Ohio Rev. Code § 2901.13 under the general/default limitations framework provided in your jurisdiction data.

For this topic, your instructions also note that no claim-type-specific “breach of fiduciary duty” sub-rule was found. That means you should treat the SOL as general (default) rather than a standalone fiduciary-duty-specific period, unless the facts and pleading map the claim into a different SOL category.

Practical pitfall: fiduciary-duty disputes are frequently pleaded under different legal theories (e.g., fraud-like conduct, contract-adjacent theories, or other wrongdoing). Those framing choices can affect which Ohio SOL category applies. So don’t assume any single “fiduciary duty SOL” automatically—confirm the category that matches the complaint and the facts.

Limitation period

Direct answer: use the general/default period tied to Ohio Rev. Code § 2901.13 (as described in the provided jurisdiction data), because no fiduciary-duty-specific SOL sub-rule was identified.

What “general/default” means here

Your jurisdiction data explicitly instructs:

• No claim-type-specific sub-rule was found
• Therefore, the period used is the general/default SOL framework for this subject

In practical terms, that means DocketMath’s statute-of-limitations calculator method should start with the general SOL period for the relevant Ohio limitations category (rather than a special “breach of fiduciary duty” category).

Inputs that affect the outcome (and why)

When you use a SOL calculator, the result typically depends on:

• Key date: often either

  • the date of the alleged breach/event, or
  • the accrual/discovery-related date you believe controls under Ohio accrual principles for the selected SOL category.
• SOL length: the tool’s selected period under the chosen statute/category.

Because SOL is usually measured as a time interval from the accrual/key date, changing the key date changes the computed “latest filing” deadline.

Example (illustrative)

Practical checklist for timing

To pick the correct input date(s), gather:

• the date of the allegedly disloyal act (or last act in a series)
• the date you learned (or reasonably should have learned) the underlying facts
• any demand dates (if relevant to the timeline you’re modeling)
• the date the complaint was filed (for verification and sanity-checking)

Key exceptions

Even where the general/default SOL framework applies, the effective deadline can shift due to doctrines that pause, delay, or reset the limitations clock.

Direct answer: In Ohio, the “4-year-style” general/default period may not run straight through in every case—tolling and accrual-related concepts can change when the clock effectively starts or whether it is paused.

Common exception categories to evaluate

Use this checklist to assess whether an exception might matter:

• Tolling (pausing): situations where Ohio law pauses the limitations period
• Accrual adjustments: doctrines that treat the claim as accruing later than the first wrongdoing date
• Discovery-type arguments: in appropriate circumstances, when “when you knew/should have known” affects accrual
• Pleading/theory mapping: if the complaint’s theory fits a different SOL category than the general/default approach

Disclaimer (gentle): This is not legal advice. SOL/tolling outcomes can be fact-specific and depend heavily on how the claim is framed and supported in the pleadings and evidence.

How to model exceptions with DocketMath

A practical way to test sensitivity:

1. Run a calculation using the earliest event date as a conservative starting point.
2. Run a second calculation using your best-supported accrual/discovery-related date.
3. Compare the results to see how much the deadline could move.

If the two outputs differ meaningfully, that’s a signal to re-check:

• the complaint’s legal theory,
• the selected SOL category,
• and the accrual rationale you’re using.

Statute citation

The key cited authority for the general/default SOL approach referenced in your jurisdiction data is:

• Ohio Rev. Code § 2901.13
  Source (authenticated Ohio Revised Code PDF): https://codes.ohio.gov/assets/laws/revised-code/authenticated/29/2901/2901.13/7-16-2015/2901.13-7-16-2015.pdf

Reconciling the “period” instruction

Your provided jurisdiction data includes a “General SOL Period” value, and it also instructs that no claim-type-specific fiduciary-duty sub-rule was found. For that reason, the calculator should be used to apply the statute/category logic consistently and compute a concrete deadline from your selected date(s).

Practical clarification: when you see any mismatch between a stated “period” and the narrative around a “default,” treat DocketMath as the source for the computed deadline and keep your inputs consistent with the facts you’re testing.

Use the calculator

Use DocketMath’s statute-of-limitations tool at /tools/statute-of-limitations to compute the Ohio deadline from your selected event/accrual date using the Ohio Rev. Code § 2901.13-based general/default approach.

Inputs to enter (what drives the output)

In DocketMath, check that you set:

• Jurisdiction: Ohio (US-OH)
• Statute/Category selection: tied to Ohio Rev. Code § 2901.13 using the general/default rule (since no fiduciary-duty-specific sub-rule was found)
• Key date: choose the date that matches your timing theory:

  • alleged breach/event date, or
  • accrual/discovery-related date you believe controls

How outputs change when inputs change

• Change the key date → the computed “latest filing date” shifts by the same delta.
• Change any tolling/accrual assumption (if the tool supports modeling it) → the deadline may extend or shift.

Primary CTA

Start here: **DocketMath – Statute of Limitations Calculator

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