LEGAL

Employment discrimination case timeline

An employment discrimination case timeline connects the administrative and litigation phases of a claim. It starts with the employment action that gave rise to the dispute, then records an EEOC charge and the right-to-sue notice before the federal complaint. The remaining events show disclosures, written discovery, a settlement conference and trial. This view helps counsel explain where a matter sits and plan evidence collection around the court schedule. A case can take a different path depending on the claims, forum and agency process, so the drawing should reflect the actual notice and scheduling order. Keep the timeline focused on procedural events rather than trying to summarize every factual allegation.

UPDATED 2026-09-24
EXAMPLEEmployment discrimination case timeline
Make this diagram your own.

Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.

CASE ANALYSIS

Scenario

Employment discrimination claim

Key decisions

  • Administrative filing: Record the EEOC charge.
  • Notice: Mark the right-to-sue notice.
  • Federal filing: Start the court case with the complaint.
  • Discovery: Track disclosures and written discovery.
  • Resolution: Show settlement and trial dates.

When to reuse this

Use it to coordinate an employment claim's administrative and court stages; confirm filing periods and deadlines for the applicable jurisdiction.

FAQ

Frequently asked questions

Why include the EEOC charge?01
For many federal employment claims, the administrative charge and resulting notice are key procedural steps before a lawsuit can proceed.
What is a right-to-sue notice?02
It is the notice that concludes or permits the next stage of the agency process; its date can affect the time to file suit.
Can the timeline include settlement?03
Yes. Mark a mediation or settlement conference as a point event, then update the case outcome if it resolves.
Open this example in the editor →

Tweak it with chat, export PNG/SVG, or fork it for your own use case.