How-to: Document a Workplace Concern for HR
A workplace concern is easier to handle when the record is clear. Dates, facts, and a calm tone give HR something they can act on. A long message about how upset you are, with no timeline, usually creates a second problem: nobody can tell what happened. This is a documentation method. It is education, not legal advice, and it is not a script for building a case. Your employer’s policy, and a qualified advisor if the stakes are serious, decide what the record means.
Use this when you need HR, your manager, or both to understand a concern: harassment, discrimination, retaliation, a safety issue that is also a people issue, a policy violation, or a pattern that is affecting your work. If someone is in immediate danger, use your emergency process or local emergency number first. Documentation comes after people are safe.
When to use this, and when not to
- Use it before or just after you report something, while details are still fresh.
- Use it when the same issue has happened more than once and you need to show the sequence.
- Use it when you were told “send me a summary” and you want that summary to be usable.
Do not use it to speculate about someone’s motives, to diagnose a medical or mental health condition, or to circulate accusations to people who do not need them. Do not secretly record a conversation unless you already know your location’s law and your employer’s policy allow it. Recording rules vary, and a recording that violates policy or law can become its own issue. The HR hub and when to talk to HR versus your manager help you choose the audience. They do not decide whether your facts violate a law.
Time box and materials
Plan 30 to 50 minutes for a first written timeline. You need a private place, your calendar, relevant emails or chat you are allowed to retain under policy, and names of people who were present. Stick to records you already have legitimate access to. Do not go into someone else’s mailbox, files, or devices to “complete the story.”
Step 1. Separate facts from impact and from guesses (10 minutes)
Make three short lists.
- Facts: what you saw or heard, who was there, the date and time or the best estimate, and where it happened.
- Impact: what changed in your work. Missed deadline, schedule change, lost account, inability to use a system, time away from the job.
- Guesses: why you think it happened. Keep this list in your notes if you need it, but do not lead the report with it.
A fact sounds like: “On March 3, at about 2:15 p.m., in the east conference room, Alex said [the words] to me. Jordan was in the room.” A guess sounds like: “Alex has always had it in for me.” HR can investigate facts. They cannot do much with a motive you cannot show.
Step 2. Build a timeline, oldest first (15 minutes)
One line per event. Include the date, the people, what was said or done, and whether there is a document. If you are not sure of the exact day, say “the week of March 3” rather than picking a date you do not remember. Wrong precision hurts you later, because the timeline and the calendar will not match.
Add what you already did. “I told my manager on March 4 in our 1:1” is a fact. “Nobody cares” is not. If you reported it before, note the channel and any reply you received, including a reply that said they would look into it.
If other people saw it, list them as witnesses. Do not coach them on what to say. You can tell a coworker you reported a concern. You should not hand them a script.
Step 3. Write the note in plain language (15 minutes)
Keep it to about one page unless the history is long. Use this order: what you are asking HR to do, the short timeline, the work impact, what you have already tried, and what you want next. Asking for a specific next step is more useful than asking HR to “make this right.”
Tone rules that hold up under stress: no insults, no sarcasm, no all-caps, no medical labels for another person, no threats. You can be direct. “I am asking for this to stop and for a written response on the next step” is direct. “You people always protect managers” is a fight, and it buries the incident.
A note you can adapt
Subject: Workplace concern for review, [topic in a few words]
Hello [name], I am writing to report a concern and to ask for the company’s process. On [date], at [place], [name] [what happened, in concrete words]. [Name] was present. I have [email, chat, or no document]. This has affected my work by [specific impact]. I first raised it with [name] on [date], and the response was [what they said or that you have not heard back]. I am asking for [the next step you want: a meeting, a separation of duties, a status update by a date]. I will keep this note factual and I am available [windows] to walk through the timeline. Thank you, [name], [role], [contact].
What good looks like
Someone who was not in the room can retell the sequence without calling you to decode it. Each event has a date or a honest range. The ask is specific. You kept a copy in a personal location your policy allows. You did not send the write-up to the whole team, the customer, or social media.
Watch-outs
- Write from memory first, then check it against email so you do not accidentally “remember” a cleaner version.
- Do not delete messages, wipe a device, or edit a document to make the story tidier. Preserve what you have.
- If the concern is about your manager, sending the note only to that manager may not match policy. Check the handbook for the reporting path, and copy HR when the policy says to.
- Protected leave, disability accommodation, and pay complaints have their own processes. A timeline still helps, but the label you put on the issue should match the policy you are invoking. If you are unsure, say what happened and ask HR which process applies. See the legal hub for how these topics usually sit next to HR, not for a legal conclusion.
- This article does not tell you whether you have a claim. If you need that answer, talk to a qualified attorney or an agency your situation actually calls for, with the real documents in hand.