Statute of Limitations for Securities Fraud (state Blue Sky laws) in Ohio

Overview

Run this scenario in DocketMath using the Statute Of Limitations calculator.

In Ohio, the statute of limitations framework you’d use for securities-fraud-type timing under state “Blue Sky” law is anchored to Ohio Rev. Code § 2901.13. Based on the jurisdiction data provided, the general/default limitations period is 0.5 years (about 6 months)—and no claim-type-specific sub-rule was found for a more specialized “Blue Sky securities fraud” clock.

In practice, this means DocketMath’s default assumption is appropriate as a starting point when you’re estimating deadlines for conduct-based securities fraud matters in Ohio, but you still need to confirm that your specific alleged conduct and legal posture match the limitation category you intend to apply.

Limitation period

Ohio Rev. Code § 2901.13 sets general criminal limitations periods by offense class. For your securities-fraud timing assessment using the data provided for this page, the tool uses the general/default SOL period: 0.5 years, which is approximately 6 months.

Because the content brief indicates no claim-type-specific sub-rule was identified, the 0.5-year figure is the baseline default for calculations on this page.

How the calculation “clock” is typically modeled (inputs you’ll use)

Most limitations calculations you run in workflows are based on:

1. Triggering event date: the date you believe starts the limitations clock (often the date of the alleged conduct or the last act tied to the theory).
2. Target filing date: the date you plan to file, or “today” if you want to see how much time remains.

DocketMath then applies the selected limitations duration to estimate whether filing would fall inside or outside the window. With a 6-month baseline, relatively small date shifts can change the screening result.

Quick modeling examples (what “0.5 years” means)

Assume a triggering date of January 15, 2026 and a 0.5-year (6-month) window:

• Filing on July 10, 2026 → likely within the window (example estimate)
• Filing on August 1, 2026 → likely outside the window (example estimate)
• Filing on July 15, 2026 → near the edge; exact outcomes can depend on counting conventions and the specific start-date interpretation your theory requires

Key exceptions

Even when you start with the general/default 0.5-year period, Ohio limitations analysis can be affected by timing rules that impact either when the clock starts or whether time is paused. Under a general § 2901.13 framework, exceptions often show up as:

• Tolling (pauses/extensions when a statutory condition applies)
• Accrual/start-point differences (when the limitations clock actually begins)
• Procedural effects (e.g., amendments, refiling, or relation-back concepts that affect practical deadlines)

Where exceptions commonly change securities-related timelines

For securities-related matters, these issues often matter because the “right” triggering date can be disputed. For example:

• Multiple alleged acts: If misconduct spans multiple dates, one theory might identify a different “last act” or “last relevant event” date.
• Uncertainty over the start date: Your model depends on whether your trigger is framed as the first act, last act, or another event tied to the theory.
• Procedural developments: Changes in posture (for example, amendments or refiling) may change how you should model what filing date matters.

Statute citation

The general limitations period referenced in the jurisdiction data is based on:

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

This page uses these provided data points:

• General SOL Period: 0.5 years
• General Statute: Ohio Rev. Code § 2901.13
• Default logic: No claim-type-specific sub-rule was found, so the page uses the general/default period

Use the calculator

Use DocketMath’s statute-of-limitations tool to estimate whether a securities-fraud-related timeline in Ohio fits within a 0.5-year (6-month) general limitations window tied to Ohio Rev. Code § 2901.13.

Start here: /tools/statute-of-limitations

Inputs you’ll typically provide

You can run the calculation once you identify the date(s) you’re modeling:

• Triggering event date (the date you believe starts the limitations clock)
• Target filing date (or use “today” if you’re checking remaining time)
• Baseline limitations duration: 0.5 years (used as the default for this Ohio page)

What outputs to look for

After running the tool, focus on:

• Estimated deadline date (end of the 0.5-year window)
• Time remaining (days/months remaining, if displayed)
• Inside vs. outside the limitations window (useful for triage)

How changing inputs changes results

Because the baseline is 6 months, changing the triggering date by a few weeks can shift whether filing is “inside” or “outside.” A practical approach when dates are uncertain:

• Run DocketMath using the earliest plausible triggering date
• Run DocketMath again using the latest plausible triggering date
• Compare outcomes to see the range of risk

This “two-scenario” method helps you avoid overconfidence when the facts don’t cleanly identify a single start date.

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