How to document a discrimination complaint
When discriminatory behavior happens in a workplace or institutional setting, the record you build often determines whether a complaint is taken seriously. Investigations rely on specifics - dates, exact language, context, witnesses. Memory alone, especially under the stress of an ongoing situation, tends to lose those specifics over time. A factual log, started as early as possible and maintained consistently, preserves what happened while the details are still clear.
This article covers practical documentation approaches. It is not legal advice.
Record each incident with specifics
For every incident of discriminatory communication or behavior, capture the following while it's fresh:
Date and time. As precise as possible. "March 3, 2025, during the 10am team standup" is far stronger than "sometime last month."
Exact language used. Direct quotes are the most useful form of documentation. If someone made a discriminatory remark, write down exactly what they said, in their words. "She said, 'We don't usually hire people like you for client-facing roles'" is a record. "She implied I wasn't suitable" is an interpretation. If you can't recall the exact phrasing, note that: "Words to the effect of..." followed by your best recollection.
Who was present. List everyone who witnessed the incident. Even if they didn't react or respond, their presence means there's someone who can potentially corroborate the account.
Context and setting. Where did it happen - in a meeting, in the hallway, over email, on a video call? What was the broader context? What was being discussed before the incident? This surrounding information helps establish that the remark or behavior wasn't taken out of context.
Your response. What did you say or do? If you didn't respond, note that too. There's no obligation to have reacted in the moment, but your response (or lack of one) is part of the complete record.
Impact. Briefly note the professional or personal impact. Were you excluded from a project afterward? Did the behavior affect a performance review? Was a promotion or assignment decision connected to the pattern?
Maintain a consistent log
Isolated incidents are harder to act on than documented patterns. A consistent log - updated each time something happens - reveals frequency, escalation, and context that a single entry can't.
Use a format you can maintain. A dedicated document, a spreadsheet, or even a running note on your personal device works. The key is that it's dated, chronological, and stored somewhere your employer can't access. Don't keep your documentation log on a work device, in a work email account, or on company cloud storage. Use your personal phone, personal email, or a personal cloud account.
Update the log as close to each incident as possible. Same-day entries carry more weight than reconstructions written weeks later. If you're catching up on past events, note when you're writing from memory and how confident you are in the details.
Save communication evidence
Discriminatory behavior often leaves traces in written communication. Save anything relevant:
- Emails, messages, or chat logs containing discriminatory language or exclusionary decisions
- Meeting invitations, project assignments, or team communications that show differential treatment
- Performance reviews, feedback emails, or written evaluations that seem connected to discriminatory patterns
- Company policies, handbook excerpts, or training materials relevant to the behavior you're documenting
Forward work emails to your personal email when your employer's policies permit it. If policies prohibit forwarding, take notes about the content including the date, sender, subject line, and key language. Some jurisdictions and employment situations affect what you can and can't take with you - if you're uncertain, consult a lawyer before copying company documents.
Screenshots of workplace chat messages are another common form of evidence. Capture the full conversation thread, not just the problematic message, so the context is preserved.
Document reporting and responses
If you report discriminatory behavior through internal channels - HR, a manager, a compliance line - document that process as thoroughly as the incidents themselves:
- Date and method of your report
- Who you reported to, by name
- What you reported (keep a copy of any written complaint you submit)
- The response you received, including timeline commitments ("We'll look into it and get back to you within two weeks")
- Any follow-up actions taken or not taken
- Whether the behavior continued or changed after your report
If the response was inadequate - if HR dismissed your complaint, if the investigation was cursory, if the behavior continued without consequence - that pattern of institutional response is itself important documentation for any external complaint.
How records support formal complaints
If you decide to file a complaint with the EEOC, a state civil rights agency, or pursue legal action, your documentation becomes the foundation of the case. These bodies evaluate complaints based on specific factual allegations, and they look for:
- A pattern of behavior, not just a single incident (in most cases)
- Specifics - dates, statements, witnesses - rather than general characterizations
- Evidence that the behavior was connected to a protected characteristic
- Records showing you reported the behavior and the response you received
A contemporaneous log - one written close to when events happened, maintained consistently - carries more weight than a narrative reconstructed months later. Investigators recognize the difference between real-time documentation and after-the-fact summaries, and they give more credibility to the former.
The goal of documentation isn't to build an airtight legal case on your own. It's to preserve the facts clearly enough that a lawyer, investigator, or adjudicator can evaluate what happened based on specifics rather than fading memory. The record does the work of remembering so you don't have to carry every detail in your head.