Statute of Limitations for Employment Discrimination — Title VII (federal) in Ohio

6 min read

Published March 22, 2026 • By DocketMath Team

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

Overview

If you’re pursuing employment discrimination under Title VII of the Civil Rights Act of 1964 in Ohio, the time limits that apply are best understood in two layers:

Federal “administrative” deadline to file with the Equal Employment Opportunity Commission (EEOC) (and, where applicable, a worksharing state agency).
The general statute of limitations rule you may see referenced for Ohio-related filings—but note that employment discrimination under Title VII primarily runs through the EEOC process.

DocketMath’s statute-of-limitations calculator is designed to help you model the key timing dates you’re most likely to track in practice—especially the start date (usually when the discrimination decision was communicated) and the filing deadline that follows. This post focuses on the Ohio context and the general/default Ohio limitation rule you provided, while making clear that no claim-type-specific sub-rule was found for the Ohio item you supplied.

Note: Title VII cases involve federal administrative steps (commonly through the EEOC). Ohio’s general statute rules can matter for certain state-law claims, but the Title VII timeline most people track is the federal EEOC deadline.

Limitation period

1) Ohio general/default period (per the jurisdiction data)

Your supplied jurisdiction data identifies a General SOL Period: 0.5 years and cites Ohio Rev. Code § 2901.13 as the general statute.

General SOL Period: 0.5 years (about 6 months)
General Statute: Ohio Rev. Code § 2901.13
Claim-type-specific sub-rule: None found in your provided ruleset (so the discussion below uses this as a default/general limitation period rather than a specialized one).

Because the brief calls this the “general/default period,” the safest way to use it in DocketMath is to treat it as the baseline rule unless your matter involves a different statute or a more specific federal rule with its own deadline structure.

2) How to think about dates when using a calculator

When you enter dates into DocketMath, the critical variables usually include:

Event date: the date the discriminatory act occurred or when the decision was communicated.
Filing date: the date you filed (e.g., with an agency or in court, depending on the process you’re modeling).
Deadline duration: the calculator will apply the limitation period to compute the last “safe” filing date under the rule you select.

Practical example (how output changes)

Assume an event date of January 15, 2026.

Using a 0.5-year period (≈ 6 months), the calculated deadline would fall around July 15, 2026 (depending on how the tool computes “half a year” in calendar terms).
If you file on July 16, 2026, the calculator will typically treat the filing as outside the period under the default rule.
If you file on July 15, 2026, it should typically be treated as within the period.

The key point: even a 1-day difference can flip a “timely” result to “late” depending on how the underlying deadline is computed.

3) Don’t ignore the Title VII administrative step

Title VII does not work like a single “file in court by X date” scenario. Most Title VII employment discrimination matters require an administrative filing first (commonly with the EEOC). In that situation, the federal administrative timeline is often the true limiting factor for practical purposes.

DocketMath’s calculator helps you model the deadlines attached to the rule you select. If you’re using the Ohio general/default rule as your modeling baseline, you’ll want to use the correct “start” date (the date your relevant clock starts under that rule) and the correct “filing” event.

Warning: Entering the wrong “start date” (for example, when you later realized harm rather than when the employer communicated the discriminatory decision) can produce a misleading deadline. Use the date that best matches the rule’s trigger.

Key exceptions

This ruleset explicitly says: no claim-type-specific sub-rule was found. That means:

You should not assume there’s a specialized Ohio exception embedded in the provided general/default rule.
Instead, treat Ohio Rev. Code § 2901.13 here as the baseline limitation period until you identify a different, more specific statute that applies to the particular claim form you’re evaluating.

Even so, there are real-world timing “exceptions” and deadline-altering concepts that frequently come up, such as:

Tolling (pausing the clock)
Equitable doctrines (rare, fact-dependent)
Multiple filing tracks (administrative first, then judicial review)

Those concepts can exist in the broader legal framework, but none are specified in your provided jurisdiction data for Ohio Rev. Code § 2901.13 as a claim-type-specific carveout. So, in this post, DocketMath should be used to apply the default period you provided, while you separately verify whether your matter triggers a different deadline regime (especially under federal Title VII administrative requirements).

Pitfall: Relying on a single “general/default” limitation period for a Title VII matter without confirming the federal administrative deadline can cause you to calendar the wrong end date.

Statute citation

The general/default Ohio limitation rule referenced in the jurisdiction data is:

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

Per the jurisdiction data you provided:

General SOL Period: 0.5 years
General Statute: Ohio Rev. Code § 2901.13
Claim-type-specific sub-rule: Not found in the provided ruleset, so treat this as general/default.

Use the calculator

You can model your timing using DocketMath at: ** /tools/statute-of-limitations

What to enter (typical inputs)

Use the calculator to compute a deadline based on the 0.5-year period:

Start date (date the relevant limitation clock starts under the rule you’re modeling)
Rule selection: the general/default period associated with Ohio Rev. Code § 2901.13
Optional: filing date (to check “timely vs. late”)

How outputs change

Once you run the calculation, DocketMath will effectively answer questions like:

What is the deadline date?
(Start date + 0.5 years)
Is a given filing date within the limitation window?
If filing date ≤ deadline date → typically “within”; otherwise → “outside.”

If you shift either input date, the output changes immediately. In practice:

Later start date → later deadline
Earlier filing date → more likely “timely”

Quick checklist before you rely on results

Note: This is general information and calendar modeling—not legal advice. If your matter involves multiple procedural tracks (EEOC first, then federal court), you’ll want to ensure you’re modeling the correct deadline for the correct step.