Statute of Limitations for Continuing Violation Doctrine in Michigan
6 min read
Published March 22, 2026 • By DocketMath Team
Overview
Michigan’s continuing violation doctrine is a way some plaintiffs argue that—when unlawful conduct happens over time—only parts of the alleged conduct fall outside the statute of limitations (SOL), while other parts remain actionable. The practical goal is usually to preserve claims tied to events within the limitations window, even if the overall pattern began earlier.
That said, Michigan courts do not treat the continuing violation doctrine as a free pass. It generally requires that the alleged conduct be the kind of ongoing practice that can be viewed as a single continuing wrong, not just separate discrete acts that happen to occur repeatedly.
DocketMath’s statute-of-limitations calculator helps you translate the doctrine’s “timeline logic” into concrete dates—by anchoring the analysis to Michigan’s default limitations period and letting you test how different “trigger” dates affect the outcome.
Note: DocketMath is a calculation tool for organizing timelines. This walkthrough is about how the SOL rules work in Michigan—not legal advice.
Limitation period
Michigan’s general/default SOL period is 6 years. In other words, for most civil actions covered by Michigan’s general limitations structure, the clock runs for six years from the relevant accrual/trigger date.
What this means for continuing violations
When someone argues a continuing violation, the typical framing is:
- If the conduct is treated as “continuing,” then the SOL analysis can be applied to the entire course of conduct, but
- Only the portion occurring within the six-year window (counting back from the trigger date) is often treated as potentially actionable.
Key practical inputs to model in DocketMath
To use DocketMath effectively for a continuing-violation timeline, you’ll usually need:
- Trigger/accrual date (the date you treat as starting the SOL clock)
- Earliest alleged act date (when the pattern began, if known)
- Latest alleged act date (when the pattern ended or the last occurrence)
- Any “event milestones” (e.g., a complaint date, notice date, or a final harmful act date) if your timeline analysis depends on when you consider the claim to have started accruing
Then you test how much of the conduct falls inside vs. outside the six-year window.
How the output changes based on inputs
Think of the calculator as doing a straightforward “lookback”:
- If you choose a later trigger date, the lookback window shifts later too—so more earlier acts may still fall within 6 years.
- If you choose an earlier trigger date, the lookback window shifts earlier—so more of the conduct may fall outside 6 years.
Even a difference of 30–365 days can determine whether certain alleged events are included or excluded in a timeline-based analysis.
Quick timeline example (general default rule)
Assume a trigger date of June 1, 2026.
- 6-year lookback window starts: June 1, 2020
- Conduct on or after June 1, 2020 is within the general SOL window
- Conduct before June 1, 2020 is generally outside the window under the default 6-year framework
Under a continuing-violation theory, the question becomes whether the alleged pattern can be treated as a continuing course such that the SOL is applied more flexibly—but the baseline 6-year structure remains the anchor.
Key exceptions
Michigan has additional rules that can affect SOL outcomes even when a continuing violation doctrine is argued. These typically arise in a few categories:
- Different SOL rules for different claim types
- Accrual rules (when the clock starts)
- Tolling (when the clock may be paused)
- Intervening procedural events that change the timing analysis
Important limitation: no claim-type-specific sub-rule found here
This page uses Michigan’s general/default SOL framework. You should treat this as the baseline rather than a guarantee for every claim category.
- General SOL period used here: 6 years
- General statute cited here: **MCL § 767.24(1)
- Claim-type-specific sub-rules: No claim-type-specific sub-rule was found for the continuing violation doctrine in the jurisdiction data provided.
Because SOL issues can be highly claim-specific, verify whether a different Michigan statute governs your situation. For most timeline planning, however, the six-year baseline is a useful starting point.
Procedural and timing pitfalls that often matter in continuing-violation arguments
A continuing-violation argument can fail if the evidence or pleadings frame the conduct as:
- Discrete acts occurring on identifiable dates (SOL may run from each act rather than from a “continuing” end point)
- An alleged pattern lacking continuity in time or context
Also, the way you identify the last harmful act (or other key date you treat as the accrual trigger) can materially change the window you’re trying to keep alive.
Pitfall: If your timeline analysis assumes a “continuing” end date but your record shows isolated incidents with clear individual dates, courts may treat the incidents as separate—shrinking what remains actionable within the SOL window.
Statute citation
Michigan’s general default SOL period used in this analysis is 6 years, grounded in:
- MCL § 767.24(1) (general statute referenced for the default period)
Jurisdiction data provided for Michigan indicates the general rule is 6 years and identifies MCL § 767.24(1) as the source statute.
For reference, the Michigan government provides statutory information through its official channels (e.g., https://www.michigan.gov).
Use the calculator
DocketMath’s statute-of-limitations calculator is designed to turn timeline facts into a usable SOL window—so you can see what falls inside versus outside the relevant period. Use it here: /tools/statute-of-limitations.
Suggested workflow
Check each checkbox as you build your inputs:
How the calculator output supports a continuing-violation timeline
While continuing violation arguments depend on legal standards and the characterization of the conduct, the calculator helps you do three concrete tasks:
- Lock in the baseline SOL window (6 years under the general default rule)
- Identify which events occur within that window
- Run scenario checks (e.g., if you use a different accrual/trigger date, or if the “last act” date changes)
Primary CTA
If you want to run the timeline now, go to:
What to do with the result
After calculating your window, you can map your alleged events to:
- Within the last 6 years of the trigger date
- Before the last 6 years (potentially time-barred under the default structure)
- Events near the boundary (where factual disputes about dates and continuity often matter most)
Warning: This timeline analysis uses the general/default 6-year SOL period. If a different Michigan statute applies to your claim type or if tolling/accrual rules change the clock, your SOL window may differ.
Related reading
- Choosing the right statute of limitations tool for Vermont — Tool comparison
- Choosing the right statute of limitations tool for Connecticut — Tool comparison
