After raising a concern at work: a neutral record of what changed

After you raise a concern, make a complaint, ask for an accommodation or take part in a workplace investigation, a neutral record compares how things were before with how they are after. It covers your schedule, duties, reviews, access to systems and meetings, and the tone and frequency of communications. Each change is written down as a dated fact, linked to the record that shows it.

The record should not decide why anything changed. Some changes after a complaint have ordinary explanations and some may not, and sorting one from the other is work for a qualified reviewer, such as an employment lawyer, a union representative or the relevant public body, not for your notes. What a careful record does is make that review possible.

Every before-and-after comparison needs a fixed point in the middle. Here, that point is the moment you raised the concern. Write it down first and in more detail than anything else, because every later entry will be read in relation to it.

• The date and time you raised it, and the channel: a meeting, an email, an online HR form, a union steward, an accommodation request form.
• Who received it, by role, and who else was copied or present.
• A short, factual summary of what you raised, and a copy of the written version if there is one.
• Any acknowledgement you received, with its date, and any reference or file number.
• Who else, as far as you know, became aware of it afterward, and how you know.

That last item is easy to skip and often matters. A reviewer looking at a change months later will want to know who made the decision and whether that person knew about the concern. You may not know the answer, and it is fine to write that you do not know.

Most people only start keeping notes once something feels different, which means the before side of the comparison is missing. You can usually rebuild it from records that already exist and were dated before the anchor entry. Look for things you received in the normal course of your job, not things you would need to go looking for in systems you do not usually use.

• Published schedules or shift rosters from the months before, showing your usual hours and days.
• Your job description, offer letter or most recent role change confirmation.
• Past performance reviews, goal documents and written feedback, including informal praise in email or chat.
• Recurring meeting invitations you were on, and distribution lists or channels you belonged to.
• Project or client assignments, territory lists or caseloads, with dates.
• A few ordinary emails from your manager, to show the usual tone and response time.

Write a short baseline entry for each area, dated today and clearly labelled as reconstructed from earlier records. Listing the source of each point keeps it honest: a reader can see that the before picture came from documents, not from memory coloured by what happened later.

Not every change belongs in the file, but these areas are the ones a reviewer most often asks about. Track each one separately so a pattern, or the absence of one, is visible at a glance.

• Schedule and hours: shift changes, reduced or added hours, changes to remote or on-site days, leave requests approved or refused.
• Duties: projects or clients reassigned, responsibilities added or removed, tasks outside your usual role.
• Reviews and feedback: the timing and content of reviews, new performance plans, written warnings, changes in how often you are checked on.
• Access: removal from meetings, channels, distribution lists, systems, training or tools you previously used.
• Reporting line and location: a new manager, a team move, a desk or site change.
• Pay-related opportunities: overtime offers, bonus criteria, commission territories, if these changed.
• Communications: tone, response time, who is copied, whether requests now need to go through someone else.

1. Create one row per change, not one row per day. A schedule that changed once and stayed changed is one row.
2. In the first column, write the area, such as schedule or access.
3. Under before, describe the earlier state and cite the record that shows it.
4. Under after, describe the new state, the date you noticed it, and the record that shows it.
5. Add the explanation you were given, word for word if it was written, or write that none was given.
6. Note whether the change applied only to you or also to others in a similar role, as far as you know.
7. Link the row to any related entry, such as a meeting note or an email in your records index.

A sample row, invented for illustration: Area: access. Before: invited to the weekly planning meeting every Monday from January to April (invites R-12 to R-15). After: not on the invite for 2026-05-11, 05-18 or 05-25; noticed 2026-05-11. Explanation given: in a chat on 2026-05-12 my manager wrote that the meeting was being reduced to team leads. Others affected: one other senior analyst also removed, as far as I know. Related: concern raised by email to HR on 2026-04-28 (R-11).

Notice that the row records the explanation and the fact that someone else was affected. Those details may point away from any connection to the concern, and that is exactly why they belong in the file.

Words like retaliation, punishment and payback are conclusions, and conclusions belong to a reviewer. Plain descriptions of what changed, when, and what record shows it are more useful to that reviewer and harder for anyone to dismiss. A few conversions show the difference.

• Instead of they are punishing me with bad shifts, write: from 2026-05-04, I was scheduled for four closing shifts a week; from January to April I was usually scheduled for one (rosters R-20 to R-24).
• Instead of my manager is freezing me out, write: three of my last five emails to my manager received no reply within a week; earlier replies typically came the same day (examples R-30 to R-34).
• Instead of they made up a bad review, write: my mid-year review on 2026-06-15 rated communication as needs improvement; my previous review on 2025-12-10 rated it as meets expectations (R-40, R-41).
• Instead of HR is covering it up, write: I asked HR for an update on 2026-06-01 and 2026-06-20; no update received as of 2026-07-01.

Include changes that went the other way too: a request approved, a positive comment, a problem fixed quickly. A file that only contains bad news reads as selective. A file that records everything relevant, good and bad, is easier for anyone to trust.

In the United States, the Equal Employment Opportunity Commission publishes a page on retaliation. It gives examples of activity it treats as protected, such as communicating with a supervisor about discrimination or harassment, answering questions in an employer investigation, or requesting an accommodation, and examples of actions that could be retaliation depending on the facts, such as a lower evaluation than deserved or increased scrutiny. The same page notes that raising a concern does not shield an employee from all discipline, and that employers may act for non-retaliatory reasons.

In Canada, the federal Canadian Human Rights Act, which covers federally regulated employers, includes a section on retaliation against a person who filed a complaint under it, and the Canadian Human Rights Commission describes how to make a complaint. Most workplaces in Canada fall under provincial or territorial human rights and employment laws instead, and those differ. Union members may also have processes under their collective agreement.

Many complaint processes have time limits, and they vary by body and place. This guide does not say which process, if any, applies to you or what it requires. Bring your record and your questions to a qualified reviewer for that.

• Keep your notes on a personal device or on paper, not only on a work system you could lose access to.
• Save copies of documents you were sent or given; do not search colleagues' files, shared drives or systems you would not normally use to find more.
• Write entries close to the event, and mark any entry written later with its real writing date.
• Keep the file to yourself and the people reviewing it; posting about it or discussing it widely at work can create new problems.
• Keep the tone of every work email calm and ordinary, as if it might be read aloud later.

My schedule changed right after my complaint. Is that retaliation? This guide cannot answer that, and neither can your notes. Timing is one fact among many. Record the change, the date, the explanation given and whether others were affected, and bring the record to a qualified reviewer.

Nothing has changed yet. Is it worth starting now? Yes, if you want a record at all. The anchor entry and baseline are easiest to write while the before picture is still current and the records are easy to find.

How do I record a change in tone? Use concrete examples instead of adjectives: the exact words of a message, how long replies take, who is now copied, whether a greeting disappeared. Save the messages themselves and quote them accurately.

Should I tell my employer I am keeping a record? That is your decision. The record described here is for your own files and for anyone you choose to share it with later.

SteadyFile is built for this kind of slow, dated record. You can start a private work file free in the browser at app.steadyfile.com, on a phone or a desktop, with no account needed to begin. The anchor entry and each change become dated entries with neutral, guided prompts, linked to the emails, rosters and reviews in a records index where every document gets an ID. Unanswered questions, such as who made a decision, go on a gaps list. With an account, each entry shows when it was created and keeps its edit history visible, which suits a record built over months. Your employer has no access to the file. When you want a review, you can export a chronological packet a lawyer or union representative can read in a few minutes. SteadyFile organizes facts; it never says whether something was retaliation.