Build a workplace harassment chronology by separating alleged conduct from reports, employer knowledge, and response, then linking each factual proposition to an identifiable source. Keep incident, reporting, document-creation, and collection dates distinct; preserve conflicting accounts rather than selecting a preferred narrative. The deliverable is a dated working record showing what each source supports, what remains disputed, and who must resolve the gaps. It should support case assessment and witness preparation without treating allegations, repeated reports, or counsel’s inferences as established facts.
Use this workflow when counsel receives a harassment complaint, investigation file, agency charge, or litigation production and must reconstruct events across messages, interviews, personnel records, and HR activity. It serves employee-side counsel, employer-side counsel, and in-house teams reviewing supporting and adverse evidence.
The scope is factual chronology, not a complete investigation or claims analysis. The EEOC’s harassment overview describes hostile-environment harassment in terms of sufficiently severe or pervasive conduct, assessed in context across the record. Ordinary workplace mistreatment is not automatically unlawful harassment. The page carries an under-review notice; use controlling law to assess coverage, protected-characteristic nexus, and claim elements.
This guide uses a US federal framework. Confirm applicable state law, circuit precedent, forum requirements, administrative prerequisites, and limitation periods separately. Federal litigation rules do not automatically govern internal investigations, state proceedings, or arbitration.
Start with the complaint or charge, identified claims and defenses, relevant date ranges, and a custodian map covering the complainant, accused, witnesses, managers, HR, and relevant systems personnel.
Organize available materials into four groups:
Preserve originals separately from counsel’s summaries and identify unavailable sources. In federal litigation, Rule 26(b)(1) limits discovery to relevant, nonprivileged matter proportional to case needs. Do not treat the complaint as grounds to request every personnel file.
Use Workplace Harassment Matters — Case chronology as the working template. You can copy this table into your working document or spreadsheet. Use one row per discrete proposition, with stable event IDs in the event field.
| Incident date | Report date | Created date | Collected date | Event / people | Source / pinpoint | Issue | Status / limits | Next action / owner |
|---|---|---|---|---|---|---|---|---|
“Incident date” identifies when conduct or another substantive event occurred. “Report date” identifies when someone communicated it. Creation and collection dates describe the cited source, not the underlying conduct. Use “unknown,” “estimated,” or “not applicable” where appropriate.
Record a document ID and page, message timestamp, spreadsheet cell, or transcript line. Where sources have different provenance, use linked rows or a linked source inventory rather than assigning one creation date to several records.
Use “Issue” for conduct, notice, authority, response, employment action, or impact. “Status / limits” distinguishes allegations, firsthand accounts, documentary support, contrary evidence, and inference. Put the assigned reviewer and follow-up question in “Next action / owner.” Keep verification status there or in the status field.
Identify what the chronology must test: alleged conduct and protected-characteristic connection, frequency and context, reporting routes, recipient knowledge, actor authority, response, and subsequent employment changes. Include relevant precursors and follow-up without collecting every workplace disagreement.
Treat authority as a factual question. For Title VII vicarious liability, Vance v. Ball State University, 570 U.S. 421, 424 (2013) defines a supervisor by employer-conferred power to take tangible employment actions against the victim. A “team lead” title does not answer that question, and the definition is not universal across employment laws.
Record: issue tags and questions requiring authority records or clarification of the alleged conduct’s connection to the claim.
Assign stable document IDs before drafting entries. Preserve complete threads, attachments, original report versions, and available metadata. Cross-reference duplicates without counting them as independent evidence.
Maintain a linked inventory identifying custodian, system, date range, collection method, and omissions. If only selected screenshots exist, describe that limitation; do not call the conversation complete. Keep sensitive personnel information and potentially protected communications subject to counsel’s access and privilege review.
Record: document ID, pinpoint, collection date, and material limitations. Assign missing attachments, unavailable messages, or incomplete exports to a named reviewer.
Extract all four dates independently. An April report describing February conduct requires linked conduct and reporting entries: one places the allegation in February; the other shows the April communication. Neither establishes earlier employer knowledge without supporting evidence.
Preserve original timestamps and document time-zone normalization. If a witness says “the week after training,” retain that wording and label any derived range as estimated. Show competing dates with their respective sources rather than selecting one silently. Sort on the substantive event date, not collection date.
Record: each date’s basis and uncertainty, plus IDs connecting conduct, reporting, and later response entries.
Write “Chen reported that Ortiz made a comment about her religion,” rather than “Ortiz harassed Chen.” Separate the alleged remark from the documented act of reporting it.
Distinguish firsthand observation from information received from others. A manager’s email repeating the complaint may support notice to that manager without independently corroborating the incident. Identify whether an interview memorandum records the witness’s account or the interviewer’s characterization. Preserve differing accounts in separate linked rows.
Record: the speaker, knowledge basis, exact proposition supported, and contrary evidence. Label counsel’s inference separately from source language; do not convert an investigator’s conclusion into an independently established fact.
For each reporting event, identify recipient, route, content, and evidence of receipt. Link escalation, interim measures, interviews, findings, corrective measures, and follow-up. Distinguish instructions from implementation.
The EEOC’s employer-liability overview explains that liability for nonsupervisory employee harassment, or harassment by controlled nonemployees, can depend on actual or constructive knowledge and failure to take prompt, appropriate corrective action. Do not substitute that framework for supervisor vicarious liability.
Compare documented responses with later alleged recurrence or employment changes without treating sequence as proof of causation. Record: linked notice and response IDs, evidence supporting each connection, and any receipt or implementation gap.
Review gaps by issue, not merely by date. Ask whether apparent silence reflects no action, incomplete collection, withheld material, or an undocumented conversation. “No record located” does not mean “nothing happened.”
Frame focused questions: Who attended the briefing? Who authorized the schedule? Was workstation separation implemented? Where federal production objections affect completeness, check the response: Rule 34(b)(2)(B)–(C) requires specific objection grounds and disclosure of whether responsive materials are withheld on those grounds.
Record: competing sources, the clarification needed, and the responsible lawyer or investigator. Resolve discrepancies through evidence, not document count.
Reopen each source supporting a material proposition. Check surrounding text, attachments, dates, and whether the pinpoint supports the entry’s wording. Retain version history and distinguish restricted analysis from any circulation version.
For proposed exhibits, identify a potential authentication route. Federal Evidence Rule 901(a) requires sufficient evidence to support a finding that an item is what its proponent claims. Authentication alone does not resolve hearsay or other admissibility questions.
Record: verification status, evidentiary questions, intended recipients and use, and an owner for unresolved issues. Label the working record an internal analytical chronology rather than assuming it is courtroom evidence.
Fictional scenario: Counsel for fictional Harbor Loom Services reviews fictional employee Maya Chen’s complaint about team lead Leo Ortiz. Chen alleges repeated religious comments and an undesirable closing assignment after reporting them. The available file contains her sent complaint email, an HR instruction, and a published schedule. It lacks authority records, an interview memorandum, prior schedules, and the assignment decision-maker’s explanation.
All parties, records, dates, and identifiers below are fictional. These representative entries do not replace separate rows for the February 12 reporting event and each additional alleged incident.
| Incident date | Report date | Created date | Collected date | Event / people | Source / pinpoint | Issue | Status / limits | Next action / owner |
|---|---|---|---|---|---|---|---|---|
| Feb. 3, 2026, alleged | Feb. 12, 2026 | Feb. 12, 2026 | Mar. 2, 2026 | E01: Chen alleges Ortiz made a religious comment during briefing | HLS-014, p. 1, sent complaint | Conduct | Supports Chen’s account and sending; remark and HR receipt unverified | Interview named attendee; verify receipt; counsel Rivera |
| Feb. 13, 2026 | Not applicable | Feb. 13, 2026 | Mar. 2, 2026 | E02: HR directs manager to separate workstations and speak with Ortiz | HLS-019, p. 1, email | Response | Instruction documented; connection to E01, implementation, and interview unverified | Locate initiating report and implementation records; HR liaison Bell |
| Feb. 17, 2026, effective | Not applicable | Feb. 16, 2026 | Mar. 4, 2026 | E03: Published schedule assigns Chen to closing | HLS-027, cells B8:F8 | Assignment | Assignment documented; publication receipt, prior pattern, reason, and decision-maker unknown | Compare prior schedules; identify decision-maker; counsel Rivera |
E01 supports an allegation and its transmission, not independent proof of the remark or receipt. E02 documents an instruction but does not establish completed remediation or identify which communication triggered HR’s action. E03 places an assignment after the complaint without establishing a change from prior practice or retaliatory motive.
These distinctions change the next task. Counsel should prioritize implementation evidence, reporting receipt, prior schedules, and decision authority—not gather additional copies of the complaint. Ortiz’s title remains insufficient to determine his legal status.
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its litigation capabilities include document review, privilege and confidentiality analysis, chronology, evidence analysis, and deposition preparation. Use its chronology capabilities to support source-based organization and its trial-preparation capabilities for related preparation. Counsel retains responsibility for verification, legal classifications, and unresolved contradictions. To discuss this workflow, book a demo.
Yes, when relevant. Attribute them and identify their limits. Record the reporting event separately where it bears on employer knowledge. Repetition does not supply independent corroboration.
Create linked conduct and reporting entries. Preserve the earlier date as alleged or estimated and the later communication date as documented. Do not backdate employer knowledge.
No. Assess purpose, participants, and asserted protection individually. Rule 26(b)(5)(A) requires express protection claims and descriptions enabling assessment without revealing protected information; it does not establish privilege. Restrict disputed material pending counsel’s decision.
No. Rule 1006 concerns summaries of voluminous admissible materials that cannot conveniently be examined in court and requires access to underlying originals or duplicates. Illustrative aids fall under Rule 107. Assess intended use separately from the working chronology.
Scope: General professional workflow guidance, using an October 13, 2026 research cutoff; not advice for a particular matter.
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.