Build an employment discrimination chronology by separating what happened, when it happened, who knew about it, and which source supports each proposition. Start with the challenged employment decision, then connect complaints, performance records, approval chains, policy departures, and relevant employee treatment without treating sequence as proof of causation. The deliverable is a source-linked event table that preserves competing accounts, distinguishes decision dates from communication and effective dates, and assigns unresolved evidence gaps. Counsel should be able to trace every material entry to an underlying record or an expressly identified uncertainty.
Use this workflow when employment counsel or an in-house team needs to test a narrative before an agency response, witness interview, deposition, or dispositive motion. Concrete triggers include conflicting termination explanations, disputed complaint notice, incomplete disciplinary histories, or documents identifying previously unknown decisionmakers.
The scope is event reconstruction, not a complete claims analysis. Identify the governing discrimination statute, asserted theories, challenged actions, and forum before selecting events. This guide emphasizes US federal district-court litigation. Federal civil and evidence rules do not automatically govern state proceedings, arbitration, or administrative investigations; check the applicable forum’s rules, controlling authority, and case-specific orders. See the Federal Rules of Civil Procedure, Rule 1 and Federal Rules of Evidence, Rules 101 and 1101.
Gather materials establishing employment events and the reliability of their dates:
Record custodians, systems, date ranges, and collection gaps. EEOC guidance describes post-charge retention of personnel or employment records relating to the investigation until final disposition, including records concerning employees holding or seeking similar positions. Verify employer coverage and applicable regulations; retention scope neither establishes substantive comparability nor completes litigation-preservation analysis. EEOC recordkeeping guidance.
Copy the Employment Discrimination Matters — Case chronology table into your working document or spreadsheet.
| Event ID | Event date | Record date | Source / pinpoint | Actors / knowledge | Event / account | Status / issue | Action / owner |
|---|---|---|---|---|---|---|---|
Keep event IDs stable when rows move. Event date identifies an exact date, range, or unknown date and whether the event is a recommendation, decision, communication, or effective action. Record date captures when the source was created; distinguish that date from a later export date.
Use Source / pinpoint for document ID, page or Bates number, and relevant timestamp or spreadsheet cell. Actors / knowledge identifies participants and supported awareness dates. Event / account states a neutral proposition. Status / issue distinguishes documented statements, disputed occurrence, inference, and unknown facts. Action / owner identifies the verification task and responsible person. Split different events or dates into separate rows; link supporting records through stable IDs.
Identify each challenged action: rejection, promotion denial, discipline, reassignment, or termination. Attribute the employer’s explanation to a source. Identify complaints and other events whose timing matters to the asserted theory, keeping legal characterization outside the factual description.
Set a provisional review period covering relevant employment history, decision development, and later explanations. Earlier evaluations may illuminate a performance rationale; later testimony may change the account. Avoid adding unrelated history merely to lengthen the timeline.
Template output: Enter anchor events, including unknown dates, and assign unresolved scope questions to counsel.
Assign each record a stable ID connected to native files, attachments, versions, and production identifiers. Distinguish an original message from a forwarded copy and an HR entry from an export displaying it. Preserve document-family relationships so an attachment does not become detached from its explanatory email.
Check truncated threads, missing attachments, and unavailable audit histories. Absence from the collected set is not proof that an event never occurred. In federal discovery, Rule 26(b)(1) limits discovery to relevant, nonprivileged matter proportional to the case; useful personnel records are not automatically available without those constraints. Federal Rules of Civil Procedure, Rule 26.
Template output: Populate source pinpoints and collection limitations. Assign targeted collection questions instead of treating incomplete evidence as verified.
Read surrounding text rather than relying on a highlighted sentence. Extract actor, action, date, recipient, and stated basis. Separate firsthand observations from allegations, retrospective accounts, and counsel’s inference.
“Manager wrote that targets were missed” differs from “employee missed targets.” The statement may be documented while the underlying performance remains disputed. An HR termination entry may establish a system transaction without identifying the approving decisionmaker.
Template output: Enter one material proposition per row. Preserve adverse evidence and inconsistent accounts. State whether the source establishes occurrence, reporting, or merely a later assertion.
Preserve original timestamps and document any timezone conversion. Distinguish incident, report, and system-entry dates. Do not substitute a file-modification date for an event date.
For discipline or termination, separate recommendation, approval, notification, and implementation. For complaints, distinguish submission, receipt, forwarding, and evidence of decisionmaker awareness. A copied recipient shows transmission, not necessarily reading or awareness of particular contents.
Template output: Record ranges or unknown dates where precision is unsupported. Link related events by ID and identify evidence needed to resolve ordering. Use a separate sorting convention for uncertain dates without presenting that convention as a factual finding.
Compare contemporaneous notes, approval chains, employee communications, agency submissions, discovery answers, and testimony. Attribute each explanation to its speaker and date. Determine whether a difference is a contradiction, added detail, or an account reflecting different knowledge.
In Reeves, a prima facie case combined with sufficient evidence that the employer’s justification was false could permit a finding of intentional discrimination, but did not require that finding. The decision involved an ADEA verdict reviewed under Rule 50; it does not supply every statute’s elements or causation standard. Reeves, 530 U.S. 133, 147–149.
Template output: Add explanation events and relevant employee-treatment events. Link contextual records addressing role, supervisor, decisionmaker, conduct, period, and disciplinary history. Preserve unknowns; do not declare legal comparability from job title alone.
Identify who can explain significant records’ origin and meaning. Flag screenshots lacking context, unexplained HR codes, embedded statements, and summaries without underlying records. Federal Rule 901 requires sufficient evidence that an item is what its proponent claims. Rule 803(6) separately addresses the regularly conducted activity hearsay exception; authentication does not itself resolve hearsay or other admissibility objections. Federal Rules of Evidence, Rules 901 and 803(6).
Separate factual entries from legal advice and unnecessary sensitive personnel details. Route potentially privileged material for counsel review before broader circulation; do not assume an internal label establishes protection.
Template output: Record foundation questions, controlled-source references, and reviewers. Retain necessary evidence without copying sensitive details into every version.
Read the chronology in date order and by decisionmaker. Check impossible sequences, duplicates, unexplained intervals, and explanations first recorded after the challenged action. Reopen pivotal sources and confirm that revisions preserve earlier IDs.
Classify the intended output: internal analysis, witness preparation, illustrative aid, or proposed evidentiary summary. Federal Rule 1006 concerns summaries of voluminous admissible materials that cannot conveniently be examined in court and requires access to underlying originals or duplicates. Rule 107 separately addresses illustrative aids. Neither makes a working chronology automatically admissible. Federal Rules of Evidence, Rules 1006 and 107.
Template output: Assign every material open issue. Record the review cutoff and version outside the table, with a revision record identifying changed accounts.
Fictional scenario: Mara Ellis alleges that fictional employer Alder Quay Instruments terminated her because of sex and retaliated after her discrimination complaint. The employer asserts performance reasons. Counsel has an HR complaint receipt, a manager’s email, and a termination letter. The fictional collection contains no approval record, underlying target data, delivery confirmation, or evidence of when the manager learned of the complaint.
| Event ID | Event date | Record date | Source / pinpoint | Actors / knowledge | Event / account | Status / issue | Action / owner |
|---|---|---|---|---|---|---|---|
| E-001 | Apr. 8, 2026: HR receipt | Apr. 8, 2026 | F-HR-01, p. 1, 10:14 a.m. | Ellis; HR intake; manager awareness unknown | HR acknowledges complaint of sex-based promotion treatment | Receipt documented; forwarding unproved | Obtain routing history to test awareness; associate |
| E-002 | Apr. 6, 2026: asserted decision | Apr. 10, 2026 | F-EM-02, p. 1 | Manager to HR; approval authority unknown | Manager states termination was settled Apr. 6 for missed targets | Retrospective account; contemporaneous approval absent | Seek approval chain and target data to test date and rationale; counsel |
| E-003 | Apr. 15, 2026: letter issuance | Apr. 15, 2026 | F-LT-03, p. 1 | HR signatory; Ellis’s receipt unknown | Letter states termination for performance, effective Apr. 17 | Issuance documented; delivery and implementation unverified | Verify delivery; add separate implementation event when supported; paralegal |
The chronology treats April 6 as an asserted decision date, not a verified fact or a date range invented from the email’s creation date. April 10 establishes when the manager recorded that account. April 15 establishes issuance of the letter, not Ellis’s receipt; April 17 remains the stated effective date until implementation evidence is reviewed.
Counsel therefore prioritizes routing history, approval records, and performance data rather than concluding that timing proves or defeats retaliation. The table also identifies which witness questions need documentary follow-up. These three records support no comparator conclusion, and the missing approval record does not itself establish that approval never occurred.
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, chronology, evidence analysis, and privilege and confidentiality analysis capabilities can support source review and event reconstruction. Counsel remains responsible for verifying dates, attribution, competing accounts, and legal significance. Explore the chronology viewer and trial preparation capabilities, or book a demo to discuss this employment chronology workflow.
Begin with the earliest event needed to understand the challenged decision, performance history, complaint sequence, or comparison. Expand when documents reveal earlier planning. Record the reason for the boundary; do not substitute an arbitrary lookback period for matter-specific analysis.
Include events illuminating the challenged decision. Link a separate contextual record when details become unwieldy. Preserve selection criteria, supervisor, period, conduct, disciplinary history, and unknowns; timing alone does not resolve comparability.
Keep both accounts and identify the precise conflict. Record which documents the witness reviewed. Test authorship, completeness, context, and timing rather than automatically treating either account as controlling.
Possibly, but not simply by deleting counsel’s comments. Identify the proposed use, then assess source foundations, applicable disclosure requirements, and forum rules. For federal proceedings, distinguish a Rule 107 illustrative aid from a Rule 1006 evidentiary summary. Federal Rules of Evidence.
This is a general professional workflow guide; its practical checks are recommendations, not independent legal requirements.
This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.