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

Overview

If you believe you experienced employment discrimination in West Virginia covered by Title VII of the Civil Rights Act of 1964, the clock you care about is the deadline to file an administrative charge with the Equal Employment Opportunity Commission (EEOC) (or a substantially similar state/cross-filing agency process), before you can typically pursue later steps.

This article focuses on the federal Title VII statute of limitations in West Virginia—specifically, the timing framework you use when preparing to file a charge. It also explains how DocketMath’s statute-of-limitations calculator can help you compute key dates from your facts.

Limitation period

The default rule (general period)

For the purposes of this West Virginia-oriented timing guide, the general/default limitations period is 1 year. There is no claim-type-specific sub-rule identified in the provided jurisdiction data, so you should treat this as the default period for the limitations calculation described below.

What “1 year” means in practice

In a limitations workflow, you generally start counting from the date the actionable event occurred (for example, the discriminatory decision, denial, or other triggering event). Depending on the dispute, “triggering event” can be fact-specific—such as:

• the date you were notified of a termination, demotion, or denial
• the date the discriminatory act took place (if notification wasn’t simultaneous)
• the date of a discrete discriminatory action that you can point to

If you have more than one alleged act, your deadlines can depend on whether the acts are separate “discrete” events or part of an ongoing course. Because this page uses the provided jurisdiction data as the default, you should use the 1-year period as your baseline and then sanity-check the start date based on the exact facts you plan to rely on.

How DocketMath uses your inputs

DocketMath’s statute-of-limitations calculator is designed to convert your dates into computed deadlines. Typical inputs include:

• Start date: the date you believe the discriminatory act (or last relevant act) occurred
• Jurisdiction: set to US-WV
• Governing limitations period: the calculator applies the default 1-year period provided for this jurisdiction in this guide

Then the output usually includes:

• Deadline date: the last day to meet the default limitations period
• Time remaining (optional, depending on how you run the calculator): how much time is left from “today” to the deadline

If you change your start date, your output changes

To make the impact concrete:

• If your start date is Jan 15, 2025, a 1-year period yields a deadline in Jan 15, 2026 (subject to normal calendar day counting).
• If instead you pick Jan 20, 2025 as the start date, the deadline shifts to Jan 20, 2026.

Even a 5–10 day shift in the start date can move a deadline by the same number of days, which matters when you’re planning filing steps.

Key exceptions

This jurisdiction data set identifies the general/default 1-year period and indicates no claim-type-specific sub-rule was found. That means the “exception” work you’ll do here is less about alternate durations and more about confirming your start date and whether the facts you’re using actually fit the discrete event model that drives most limitation calculations.

Still, there are practical situations that often affect how people approach timelines, including:

• Multiple alleged acts: separate denials/terminations can create multiple candidate start dates, even if the story feels continuous.
• Notice vs. occurrence: if the discriminatory act was a decision date but the notice arrived later, you may need to confirm which date best matches the event you’re contesting.
• Late discovery arguments: some legal regimes use a “discovery” concept; others hinge on when the act occurred. Because this guide uses the provided jurisdiction default period and does not identify a discovery exception here, treat “1 year from start date” as your baseline unless your documentation clearly supports a different trigger.

For the safest planning workflow, document:

• the date of each relevant decision/action
• when you received notice
• what you filed (and when), if any

Then run the calculator using the most defensible “start date” for each discrete event you plan to rely on.

Statute citation

This West Virginia timing guide uses the provided general/default period and citation:

• General SOL period: 1 year
• General statute: W. Va. Code § 61-11-9
• Reference: https://codes.findlaw.com/wv/chapter-61-crimes-and-their-punishment/wv-code-sect-61-11-9/

Because no claim-type-specific sub-rule was found in the supplied jurisdiction data, W. Va. Code § 61-11-9 is treated here as the default limitations framework for the 1-year calculation described above.

Use the calculator

Use DocketMath’s statute-of-limitations calculator to turn your dates into a concrete deadline: **/tools/statute-of-limitations

1. Go to the tool: **/tools/statute-of-limitations
2. Set Jurisdiction: US-WV
3. Enter your start date (the date you believe the relevant triggering event occurred)
4. Confirm the limitations period used by the tool is the default 1-year period from this guide
5. Review the computed deadline date

How to choose the best start date (practical checklist)

Example workflow (date range planning)

If you have uncertainty about the “trigger” date, you can improve planning by calculating both:

• Scenario A: start date = date of the decision/termination action
• Scenario B: start date = date of notice/email/letter

Then compare which deadline is sooner—your planning should generally protect against missing the earlier deadline when uncertainty exists.

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