You get pulled aside on a Tuesday afternoon. Your manager says someone reported you for "aggressive tone" in a team meeting. You know exactly which meeting, and you know you said nothing aggressive. But you have no notes, no dates, no witnesses lined up. Just a feeling of dread spreading through your chest.
Here's the uncomfortable truth: in a workplace dispute, the person with the better records usually wins. Not the better person. The better documentation. And that applies to workplace bias and discrimination as much as to false accusations. I learned this the hard way on a contract in 2024, when a colleague I trusted told HR I'd "made the atmosphere uncomfortable." I had nothing. No log, no dates, no screenshot trail. I spent two weeks reconstructing events from memory, and the reconstruction was shaky.
Ever since, I document. Quietly, methodically, and safely. This is what I've learned about how to do it without painting a target on your own back.
Key takeaways
- Document facts, times, and exact words — never conclusions or opinions.
- Keep your records off company devices and out of company systems if you can.
- Distinguish between bias (often not illegal on its own) and provable discrimination (which usually is).
- Capture digital evidence with metadata intact — headers, timestamps, screenshots.
- Share your log with a lawyer under legal privilege, not with colleagues over Slack.
Why documenting workplace bias and discrimination safely matters
Not every unfair treatment is illegal. That sentence frustrates people, but it's true and it matters for how you document. Bias — an assumption, a preference, a pattern of who gets picked for the good project — is often invisible to policy. Discrimination, in the legal sense, usually requires showing that a protected characteristic drove a decision.
The gap between "this feels wrong" and "this is actionable" is a paper trail. And the same paper trail can protect you from a false accusation if someone turns the story around.
What evidence is needed to prove workplace discrimination?
You need to show a pattern or a specific decision tied to a protected characteristic, plus a record of how you were treated differently. In practice that means dates, the exact words used, who witnessed them, and what happened to comparable colleagues. A single rude comment rarely proves anything on its own. A sequence of them, logged over months, starts to.
I made the mistake early on of writing "my manager is dismissive of my ideas" in a log. Useless. When I rewrote it as "March 12, 14:40 — manager responded to my proposal (email attached) with 'that's not what we're doing,' then approved a near-identical proposal from a colleague two days later (email attached)," it actually meant something. Facts travel; opinions don't.
What to write and what to leave out
Think of your log as a witness statement you might one day read aloud in a room with a stranger in it. Anything you wouldn't want repeated, don't type.
The five-field format that works
After a lot of trial and error, I settled on a format I've used for two years now. Every entry gets five fields:
- Date and time — down to the hour if you can.
- Location — office, video call, channel name.
- People present — full names, roles.
- What was said or done — verbatim where possible, in quotation marks.
- What you did next — "reported to HR by email at 16:12," "asked for clarification, no response."
That last field is the one most people skip. It's also the one that shows you behaved reasonably, which matters enormously if you're ever accused of overreacting.
What not to write
- Speculation about motive ("she's clearly biased against me").
- Character judgments of colleagues.
- Strong language, sarcasm, or anything that reads as unprofessional if forwarded.
- Copies of confidential company documents you weren't authorised to see.
That last point is a real trap. I once saved a colleague's performance review to my personal drive because it proved she was being treated differently. Technically that was a breach of confidentiality, and it undermined my case. Better to note that such a document exists and request it formally.
Where to store your records so they stay yours
This is the "safely" part that almost nobody talks about, and it's where most people slip up. If your notes live on a company laptop, in a company email draft, or in a company chat, your employer can access them. Not necessarily maliciously — routine IT discovery, an offboarding export, a manager's request — but the result is the same.
My rule: the log lives on a personal device, in an encrypted folder, backed up to a personal cloud account. Nothing on the work machine except the work. If I need to move a note off the work system, I type it fresh at home rather than copying a file.
Digital evidence and metadata
Emails and messages are the strongest evidence you'll get, but only if you preserve them properly. A screenshot of a message is weaker than the message's export with its headers. When something relevant lands in my inbox, I forward it to a personal address with full headers, and I screenshot the thread on the device where it appeared, timestamp visible.
For chat platforms — Slack, Teams, whatever your org uses — export the thread if you can. If you can't, screenshot with the channel name, date, and author visible. Save the original file, not a re-cropped version. The metadata is half the proof.
| Location | Access risk | Privacy | Practical recommendation |
|---|---|---|---|
| Company laptop drive | High — IT, managers | None | Avoid for anything sensitive |
| Company email drafts | High — server-side | None | Never store a log here |
| Personal encrypted cloud folder | Low if 2FA enabled | Good | My default for the master log |
| Paper notebook kept off-site | Low physical, no search | Good | Fine as a backup; scan and encrypt |
| Shared with a lawyer under privilege | Low | Strongest | Preferable once things escalate |
The line between bias, discrimination, and harassment
These terms get used interchangeably, and they shouldn't be. Getting the vocabulary right changes what you document and how you frame it.
Bias is an attitude — an assumption about who's capable, who's "a cultural fit." It's not necessarily illegal. Discrimination is a decision made on the basis of a protected characteristic: pay, promotion, hiring, discipline. Harassment is a pattern of conduct that creates a hostile environment, often tied to the same characteristic.
In my own log, I started tagging each entry with a label: "bias (opinion)," "possible discrimination (decision)," "harassment (conduct)." That discipline forced me to be honest about what I actually had. Half my early entries were bias — real, frustrating, but not something HR would act on. The other half, once tagged properly, showed a clear pattern I hadn't seen.
How to properly document workplace harassment
Harassment requires showing frequency and impact, not just one incident. Log the conduct itself — the words, the gestures, the timing — and then log how it affected your work: missed meetings, changed assignments, medical leave, requests to relocate. Contemporaneous notes matter enormously here, because memory degrades and retaliation happens months later. Write the entry the same day, even if it's three lines.
What to do with your log once you have it
A log you never use is just therapy. That's fine, actually — plenty of people document for their own sanity. But if you're going to act, act in the right order.
What are five steps to address inappropriate behavior in the workplace?
- Confirm the policy. Find your company's anti-harassment policy — usually in the employee handbook or intranet, and you can request a copy from HR in writing. It tells you the exact reporting channel and timeline.
- Assemble your timeline. Pull your log into a single chronological document. Facts only.
- Report in writing. An email creates a record. Keep it factual and reference the policy clause.
- Note every response — or non-response — with the date. Silence is itself evidence.
- Escalate if needed. A lawyer, a union rep, or the relevant external body, depending on where you are.
How can I effectively defend myself against false accusations at work?
The same log that documents bias also defends you. When someone accuses you of something, a dated, consistent record of what actually happened is the strongest tool you have. Reconstruct the specific meeting or interaction, quote yourself accurately (even if it's unflattering), and stick to the facts. Do not counter-accuse. Do not dramatise. And get everything in writing — a verbal defense disappears; an emailed one doesn't.
The retaliation trap
Retaliation is often easier to prove than the original discrimination. If you report something and then get a sudden performance warning, a demotion, a schedule change, or exclusion from a project, log that change with the same rigour. Keep the dates of your report and the dates of the change side by side. That temporal link is the whole case. If you've reported in good faith, most employment frameworks protect you from being punished for it — but only if you can show the sequence, which means documenting the "after" as carefully as the "before."
And one quiet thing I wish someone had told me earlier: tell at least one person you trust, in writing, that you're keeping records. Not the contents of the log — just the fact. It sounds paranoid. It has saved me twice.