Statute of Limitations for Breach of Fiduciary Duty in Maryland

Overview

In Maryland, a claim for breach of fiduciary duty is generally treated like other civil disputes that must be filed within a set time after the claim “accrues.” In practice, that timing question often drives whether a case can proceed at all—because Maryland courts will dismiss untimely filings under the statute of limitations (SOL).

DocketMath can help you sanity-check the timeline by running the period under Maryland’s general civil limitations rule. This article focuses on that default rule because, based on the provided jurisdiction data, no claim-type-specific sub-rule was identified for breach of fiduciary duty.

Limitation period

Maryland’s general rule (default)

Maryland’s general limitations period for many civil actions is 3 years under:

• Md. Code, Cts. & Jud. Proc. § 5-106

Because the provided data indicates no claim-type-specific sub-rule for breach of fiduciary duty was found, you should start with this general/default 3-year SOL as your baseline.

What “3 years” usually means in real filings

The clock starts when the claim accrues, not necessarily when the alleged conduct first occurred. Accrual is commonly tied to when a plaintiff knows (or reasonably should know) of facts establishing the elements of the claim—though the exact accrual mechanics can become fact-sensitive.

To translate that into practical case management:

• Identify the “event date”: the date the alleged breach occurred (or the last date of a continuing breach, if applicable).
• Identify the “discovery/accrual date”: the date you can plausibly argue the claim accrued for SOL purposes.
• Count 3 years from the accrual date: then compare it to the intended filing date.

Quick timeline example (generic)

Assume a claimant would argue accrual occurred on January 15, 2023.

• Accrual date: Jan. 15, 2023
• 3-year deadline: Jan. 15, 2026
• If filed after that: likely beyond the default SOL baseline

Because accrual can be disputed, you should treat your accrual date as a key assumption you can document (emails, statements, accountings, demand letters, or other objective markers).

Inputs that change the output

Use DocketMath to reflect the key moving parts. Typical inputs include:

• Accrual date (or the best-supported date you think the claim accrued)
• Filing date you plan to use

Then DocketMath can output whether the filing appears:

• Within 3 years
• On the deadline
• After 3 years

Even if the general period is fixed, the accrual date selection is often the dominant driver of whether the result lands “timely” or “late.”

Key exceptions

Maryland SOL rules can include doctrines that extend or modify deadlines. Below are common categories to consider when you’re modeling timelines with DocketMath. This is not legal advice—think of these as issue-spotting checklist items.

Discovery and accrual arguments

If a plaintiff can argue that the claim did not accrue until later (for example, when the facts were discovered or became reasonably knowable), the 3-year deadline may shift.

• What to document: when relevant information surfaced; when accountings, records, or disclosures were received; when red flags were apparent.

Tolling due to special circumstances

Some circumstances can pause the limitations clock (tolling), such as statutory tolling rules. Whether tolling applies depends on specific facts and statutory triggers.

Continuing wrong and repeated conduct

Where there are multiple acts—for example, recurring account statements, repeated fiduciary decisions, or ongoing conduct—litigants sometimes argue for different accrual treatment for each act or for a continuing course. The exact outcome can be highly fact-dependent.

Forcing a later “start” via claim framing

Sometimes plaintiffs strategically frame the claim to align accrual with later events (like an accounting, repudiation, or demand/refusal). That can affect the accrual date model you input into DocketMath, but it must stay grounded in how the law treats accrual and the elements of the claim.

Statute citation

Use the Maryland general SOL citation as the baseline for breach of fiduciary duty timelines:

• Md. Code, Cts. & Jud. Proc. § 5-106 — 3-year general limitations period for covered civil actions

The jurisdiction data provided here indicates this is a general/default rule, and no breach-of-fiduciary-duty-specific sub-rule was identified. Accordingly, model your initial estimate using the 3-year baseline under § 5-106.

Use the calculator

DocketMath’s statute-of-limitations tool helps you compute a deadline using Maryland’s general 3-year SOL framework.

• Primary CTA: /tools/statute-of-limitations
• Inline link: **/tools/statute-of-limitations

Step-by-step: how to enter inputs

1. Accrual date (required)
   Enter the date you believe the breach claim accrued under the facts of your situation.
2. Filing date (recommended)
   Enter the date you plan to file (or the date you already filed).
3. Jurisdiction
   Select Maryland (US-MD) to apply Md. Code, Cts. & Jud. Proc. § 5-106.

How outputs should be interpreted

DocketMath will essentially test whether:

• Filing date ≤ accrual date + 3 years → likely within the default SOL baseline
• Filing date > accrual date + 3 years → likely beyond the default SOL baseline

If the calculator indicates “late,” that doesn’t automatically end the matter. Tolling, accrual disputes, or continuing conduct theories might shift the analysis—but those require careful fact alignment with Maryland rules.

What to record for a defensible timeline

Use a simple checklist before you rely on the result:

Sources and references

Start with the primary authority for Maryland and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

• Md. Code Ann., Cts. & Jud. Proc. § 5-101

Related reading

• Choosing the right statute of limitations tool for Vermont — Tool comparison
• Statute of limitations in Singapore: how to estimate the deadline — How-to guide
• Choosing the right statute of limitations tool for Connecticut — Tool comparison