Something happened at work that concerns you - a comment that crossed a line, a manager who keeps changing your schedule without notice, a safety shortcut you have been asked to take repeatedly. You are not sure yet whether it needs a formal complaint, but you know from experience that memory fades and details blur, so you want to write it down properly while it is fresh. AI is a genuinely useful tool for this specific, narrow task: turning your memory into a clean, organized, dated record. It is not a tool for answering the question underneath - is this actually against the rules, and what should I do about it - because that question requires knowledge of your specific employer’s policy, your jurisdiction’s law, and facts a general-purpose model has no way to verify.
This is a literacy article, not legal advice, and it stays that way deliberately. Nothing here tells you whether a specific situation is illegal, what any specific law entitles you to, or how a complaint should be worded to succeed. That is the entire point: those questions belong with people who are actually positioned to answer them for your specific situation.
Why a factual record matters, regardless of what happens next
A record made close to the event beats one reconstructed months later, and the reason does not require an appeal to authority. Exact dates, direct quotes, and the names of who else was in the room are all things you can still retrieve while the event is fresh and cannot reliably rebuild once it is not. Later recollection also gets reshaped by the conversations you have in between - which is precisely what makes a note written at the time harder to argue with than one written after you have already decided what the episode meant. This holds whether the issue resolves informally, becomes a formal HR complaint, or never goes anywhere at all. Writing it down well is worth doing even if you are not sure yet whether you will act on it.
Never ask an AI tool whether a specific situation is legally harassment, discrimination, retaliation, or a violation of a specific law, and never ask it to draft a formal legal complaint or tell you what you are entitled to. These require knowledge of your employer’s actual policies, your specific jurisdiction’s law, and case-specific judgment that a general-purpose model cannot reliably provide - and an incorrect answer here can cost you more than no answer at all. Take these questions to your HR department, your union representative, or a licensed employment lawyer in your jurisdiction.
What AI can actually help with
The narrow, useful task is organizing your own account into a clear structure, not generating or interpreting content:
I am going to describe something that happened at work. Organize
what I tell you into a clean, chronological, factual log with these
fields for each entry: date, time, location, who was present, what
was said or done (quote directly where I give you a quote), and any
documents or messages related to it. Do not add interpretation,
characterize the events as any category of misconduct, or suggest
what I should do about it - just organize the facts I give you into
this structure.
Here is what happened: [your account]
Read the output back against your own memory. Correct anything that drifted from what you actually said, and remove anything that reads as interpretation rather than fact - a model can slip a word like “aggressively” or “clearly retaliatory” into a summary even when your original account was more neutral, and that kind of characterization does not belong in a factual log.
A workplace issue log often contains sensitive personal information about you and about other people - health details, personal circumstances, allegations about someone’s conduct. Treat this document with the same caution as work secrets: if your employer has an approved, enterprise-grade AI tool with strong data-handling terms, use that; if not, consider drafting this document without AI at all, or using a local tool that does not send your text to a third party, given how sensitive the content usually is.
What to log, specifically
| Field | What to include |
|---|---|
| Date and time | As precise as you can recall; note if approximate |
| Location | Where it happened |
| Who was present | Names, roles - note if anyone else witnessed it |
| What was said or done | Direct quotes where possible, otherwise as close to verbatim as you can recall |
| Your response | What you said or did at the time |
| Related documents | Emails, messages, schedules, photos - reference where they are saved |
| Pattern, if any | Whether this is a first occurrence or part of a repeated pattern, with dates of prior instances |
Keep opinions, legal conclusions, and characterizations (“this was harassment,” “this was clearly retaliation”) out of the log itself. State what happened; let the people responsible for evaluating it - HR, a union representative, or a lawyer - apply the relevant standard.
Where this goes next is not an AI question
Once you have a clean factual record, the decision about what to do with it - raise it informally, file a formal complaint, consult a lawyer, or wait and keep documenting - is a judgment call that depends on your specific employer’s process, your relationship with the people involved, and factors only you can weigh. A few starting points, offered without assuming your specific situation:
- Your employer’s HR department or designated process is usually the first formal channel for a workplace complaint - check your employee handbook or intranet for the specific procedure, the same way finding your employer’s AI policy covers locating the actual document rather than guessing.
- A union representative, if you are in a unionized workplace, can advise you on process and may be able to accompany you to an investigatory interview. In the United States, a union-represented employee who reasonably believes an interview could lead to discipline can ask to have a representative present - but the right only operates if you actually request it, and your employer is not required to tell you it exists (see NLRB v. Weingarten, 420 U.S. 251 (1975); NLRB “Weingarten Rights” overview via Internet Archive). The rules differ by country and by whether you are represented at all, so ask your union or HR what applies to you rather than assuming this example transfers directly to your situation.
- A licensed employment lawyer in your jurisdiction is the right source for any question about what a law actually requires or permits in your specific case - a factual log like the one above is exactly the kind of material a lawyer would want to see first.
None of this means you must escalate immediately, or at all. Documenting well and deciding later is a normal, reasonable choice.
Two things people get wrong about documenting
The first is treating a well-organized AI-assisted summary as equivalent to legal or HR guidance, because it reads clearly and confidently. A model producing a tidy timeline has not evaluated your situation against any actual policy or law - it has organized text. The clarity of the output says nothing about whether the underlying situation meets any legal or policy threshold, and treating fluent organization as expert judgment is exactly the gap this article exists to close.
The second runs the other way: assuming documentation itself is an aggressive or premature step. It is not. A factual record made close to the event, kept privately until you decide what to do with it, protects you regardless of which path you eventually choose - including the path of doing nothing further.
Start the record now, while it’s fresh
Use the workplace issue facts log to capture what happened while your memory is clearest, using AI only to organize the structure, never to characterize or advise. When you are ready to decide what to do with it, take it to HR, your union representative, or a licensed employment lawyer - not back to the AI tool that helped you write it down.
