Statute of Limitations for Continuing Violation Doctrine in Ohio

Overview

In Ohio, the “continuing violation” doctrine can come up when a plaintiff argues that wrongful conduct wasn’t just a one-time event, but part of a series of related actions that should be treated as one ongoing wrong for statute of limitations (SOL) purposes.

For practical use, the key takeaway is this: Ohio’s SOL analysis usually turns first on the underlying claim’s statutory limitations period, and then on whether the alleged facts fit within any recognized tolling or accrual rules. Your “continuing” theory typically affects the date of accrual or whether certain claims are time-barred—not the existence of a limitations clock that begins somewhere.

DocketMath’s statute-of-limitations calculator is designed to help you model that clock. You’ll enter relevant dates (and any applicable offsets/timing assumptions) to see which parts of the timeline fall within the SOL window.

Limitation period

Default SOL for Ohio (general rule)

Per the provided jurisdiction data, the general/default SOL period is 0.5 years. In other words, the default limitation window corresponds to six (6) months.

• General limitation period: **0.5 years (≈ 6 months)
• General statute: Ohio Rev. Code § 2901.13

The brief’s note is explicit: No claim-type-specific sub-rule was found. That means the content below uses § 2901.13 as the general/default period rather than attempting to map different claim types to different SOL lengths.

How “continuing violation” affects the timeline you should test

Even when you raise a continuing violation theory, the practical question remains:

• Which conduct dates are included?
• From what date does the SOL start running for each part of the alleged conduct?
• Does any tolling or accrual rule pause or restart the clock?

To model this concretely, think in segments:

• Segment A: earliest conduct alleged (e.g., actions in January)
• Segment B: later conduct alleged (e.g., actions in April)
• Segment C: most recent conduct alleged (e.g., actions in June)

A continuing violation argument may support the position that the “operative wrong” is ongoing, potentially shifting the relevant accrual date toward the later conduct. However, courts can still treat earlier conduct as time-barred if the plaintiff should have brought the claim sooner under the governing accrual rules.

What you should compare when reviewing dates

Use these check points in your own review (or in case triage):

• ✅ Start date of alleged misconduct (earliest event you want included)
• ✅ End date / last alleged wrongful act (often the anchor for continuing theories)
• ✅ Filing date (when the claim was brought)
• ✅ Any pause/tolling dates (if recognized under the governing rule)

Then compare:

• Whether the filing date falls within ~6 months of the relevant accrual date you’re asserting.
• Which segments (A/B/C) fit within that window.

Quick modeling example (illustrative)

Assume:

• Last alleged act: 2026-01-15
• Filing date: 2026-07-10

A 0.5-year default window (~6 months) would generally include conduct tied to an accrual date near mid-January and likely exclude earlier conduct more than ~6 months before filing, depending on how accrual is determined.

DocketMath helps you run this logic consistently across timelines.

Key exceptions

Because this page uses only the general/default period identified in the brief (Ohio Rev. Code § 2901.13, ~6 months), the “exceptions” here focus on what can change the clock even when you start from the default SOL.

Common categories that may matter in Ohio SOL analysis include:

• Accrual shifts: the date the claim is considered to have “accrued” can differ from the date of the first incident.
• Tolling: certain circumstances can pause the SOL clock.
• Equitable doctrines (fact-dependent): court-recognized fairness-based adjustments may apply in limited circumstances.

Practical exception checklist for your date inputs

When you run the calculator, consider whether your record supports any of the following:

• Is there a clear “last wrongful act” date? Continuing theories usually rely on an end point.
• Is the plaintiff alleging repeated conduct vs. a single event with lingering effects? The facts can affect accrual arguments.
• Are there documented reasons the plaintiff could not have filed earlier? If yes, that may affect tolling/accrual assumptions you model.

If you don’t have supporting details for tolling/accrual exceptions, it’s often safer to model the timeline under the default limitations period first.

Statute citation

Ohio’s general/default limitations statute referenced here is:

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

Based on the provided jurisdiction data for this brief:

• General SOL Period: **0.5 years (≈ 6 months)
• No claim-type-specific sub-rule included in the provided data; therefore this page treats § 2901.13 as the general/default SOL period for purposes of modeling.

Use the calculator

DocketMath’s statute-of-limitations tool can help you translate your fact dates into a clear “in-window vs. out-of-window” view.

Inputs to enter (typical)

Use these inputs to model a continuing violation timeline:

• Last alleged wrongful act date
• Filing date (or current date, if you’re screening timing)
• Default SOL period: use the calculator’s 0.5 years setting for Ohio based on § 2901.13 (general/default)
• Optional modeling assumptions (only if supported by facts), such as:

  • Tolling start/end dates (if you’re treating the clock as paused)
  • Accrual assumption (e.g., “accrues at the last act” vs. “accrues at the first act”)

How outputs change when you adjust dates

In practice, the calculator output shifts in predictable ways:

• If you move the last alleged wrongful act date forward, the SOL window typically shifts forward, increasing the chance that more conduct is “in window.”
• If your filing date is later, older conduct becomes harder to include under a continuing violation theory.
• If you toggle any tolling/accrual assumptions, the tool will effectively add (pause) or subtract time from the running clock.

A quick “what to test” approach

Check two scenarios side-by-side:

• Scenario 1 (earliest accrual): accrual tied to the first alleged act
• Scenario 2 (continuing-style accrual): accrual tied to the last alleged act

Then compare which scenario keeps your key conduct inside the ~6-month window under the default SOL period.

To run that workflow, start here:

• Primary CTA: DocketMath Statute of Limitations Calculator

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