What Actually Holds Up When a Workplace Complaint Lands

Key Takeaways

• "Keep records" is not a strategy. What protects an employer is documentation created at the time, describing specific facts, that shows the employee knew about the issue.

• Notes written after a complaint arrives carry far less weight than notes written when the events happened. Adjudicators can tell the difference, and so can opposing counsel.

• Vague, opinion-based entries like "bad attitude" tend to fail. Specific, factual, dated entries tend to hold.

• Documentation is not about building a case against people. It is about fairness: making sure a person knows where they stand and has a real chance to respond before anything serious happens.

• When a complaint or claim lands, the record you already have decides your options. You cannot build it after the fact.

  
  

A complaint lands. Someone asks for the file. And the manager who was sure they had documentation discovers that what they have is an offer letter, a couple of forwarded emails, and a performance review from fourteen months ago that says "meets expectations."

The records exist. They just do not say what needs saying. They are vague where the situation calls for detail, silent on the conversations that actually mattered, and in the worst cases written the same week the dispute started.

"Keep good records" is the advice everyone gives and almost nobody can act on, because it never explains the part that counts: which records survive scrutiny and which ones quietly collapse the moment someone reads them looking for holes. That is the whole game, and it is worth being specific about.

Why "keep records" misses the point

Most documentation is built for a filing cabinet. It exists to be stored, not to be read by someone whose job is to pick it apart, and those are very different design goals.

When a matter becomes contested, whether at the Alberta Human Rights Commission, in an employment standards complaint, through an occupational health and safety process, or in a courtroom, the record gets read by someone whose job is to test it. They are asking whether it was created at the time, whether it describes facts rather than impressions, and whether the employee actually knew there was a problem. A stack of paper that fails those questions does not help. Sometimes it hurts, because a thin or inconsistent record can undercut the very story the employer is trying to tell.

This is why "we have documentation" and "we have documentation that holds up" are two very different sentences.

The three things that separate a record that holds from one that doesn't

Sit through enough of these disputes and the same three qualities keep separating the records that carry weight from the ones that get waved away.

It was written at the time. Contemporaneous notes, made when the event happened, are treated as far more reliable than a summary assembled later. Memory fades, and when a story is written down only after a conflict begins, its timing alone invites doubt. A recent Alberta case saw a modest, roughly one-year employment relationship remain in active litigation more than a decade after it ended, and the court pointed out that the employer could have preserved recollections by making notes at the outset. The lesson is uncomfortable: the moment to write things down is the moment they happen, long before anyone imagines a dispute.

It describes facts, not feelings. "Difficult," "not a team player," and "bad attitude" are conclusions, and conclusions are easy to challenge. What holds up is specific and observable: what was said, what was done, when, where, and who was present. "On this date, during this meeting, the employee did this" is evidence. "The employee has a bad attitude" is an opinion that an adjudicator can set aside in a sentence.

It shows the person knew. This is the piece employers most often miss. A record of poor performance or misconduct means little if there is no evidence the employee was told, given a clear expectation, and offered a real chance to correct course. Documentation is not just about capturing what the employee did. It is about capturing that the employee understood the concern and had an opportunity to respond. Without that, even an accurate record can look like a case built quietly and sprung late.

What holds up and what doesn't

The record you have	Why it holds up, or doesn't
Dated note written the day an incident occurred, describing what was said and done	Holds up. Contemporaneous and specific. Hard to dismiss as reconstruction.
"Performance issues over the past year" written the week of termination	Weak. Created after the fact and vague. The timing alone invites doubt.
Signed acknowledgment that the employee received and understood an expectation	Holds up. Shows the person knew where they stood.
A manager's private impression that someone is "not working out"	Weak. An opinion with no facts, no dates, and no evidence the employee was ever told.
Investigation notes recording who was interviewed, when, and what each person said	Holds up. Neutral, factual, and consistent, which is what a defensible process looks like.
A conclusion reached before anyone was interviewed	Weak. Suggests the outcome was decided first and the process was for show.

The pattern is consistent. Specific, timely, and fair beats vague, late, and one-sided every time.

The fairness case, which matters more than the legal one

Read this as "protect yourself" and you will end up producing the exact documentation that fails: defensive, adversarial, written to justify a decision that was already made. The self-protective frame quietly corrupts the record.

The better frame is fairness. Good documentation exists so that a person is never blindsided. It means someone struggling hears about it early enough to change, understands what is expected, and gets a genuine chance to meet it. It means that if a complaint is made, everyone involved is treated consistently and the process can be trusted. The record is simply the evidence that people were dealt with fairly.

This matters because fairness and defensibility are the same thing viewed from two angles. A record holds up in a dispute precisely because it shows the employer acted reasonably, communicated clearly, and gave people a real opportunity to respond. You do not get a defensible file by trying to build a defensible file. You get one by treating people fairly and writing down what happened as it happens. The protection is a byproduct of doing the right thing, not the goal of it.

That is also why documentation cannot be reverse-engineered once a complaint arrives. By the time the file is being read by someone whose job is to test it, the record is already whatever it is. The work had to happen earlier, in the ordinary course, before anyone knew it would matter.

How to make this real without turning into a paperwork machine

This does not mean logging every hallway exchange or running your team like a legal department. A few ordinary habits carry most of the weight.

Write down the things that matter when they happen, in plain, factual language. When you raise a concern with someone, note that you raised it, what you said, and how they responded. When an expectation is set, make sure it is clear and, where it counts, acknowledged. When a complaint or incident occurs, record the process consistently: who, what, when, and what was decided. Keep it factual, keep it respectful, and keep it as something you would be comfortable having the subject of the note read.

Done this way, documentation stops being a defensive chore and becomes what it should be: a quiet record that people were treated fairly, which happens to be the strongest position to be in if anything is ever questioned.

Frequently Asked Questions

What makes employee documentation actually hold up in a dispute? 

Three things. It was written at the time the events happened, it describes specific facts rather than opinions, and it shows the employee was made aware of the issue and given a chance to respond. Records missing any of those are far easier to challenge.

Is it too late to document something after a complaint has already been made? 

Largely, yes, for the events that came before it. Notes created after a dispute begins carry much less weight because their timing invites doubt about accuracy and motive. You can and should document the complaint-handling process itself carefully, but you cannot retroactively build a contemporaneous record of earlier events.

What is wrong with writing "poor attitude" or "not a team player" in a file? 

They are conclusions, not evidence. An adjudicator cannot test a feeling. What holds up is the specific, observable fact behind the impression: what the person actually said or did, when, and in front of whom. Replace the label with the facts that led to it.

Do we need to document positive things too, or only problems? 

A record that only ever captures problems can look like a case being built. Fair, consistent documentation reflects the real picture, including acknowledgment of good work and improvement. Consistency is part of what makes a record credible.

How long should we keep employee records? 

Keep them well beyond the end of employment, because disputes can surface long after someone leaves. Certain records, such as workplace investigation files, carry specific retention expectations, and it is worth confirming the current requirements that apply to your workplace rather than assuming. When in doubt, keep more, not less.

Who should be responsible for getting this right? 

Everyone who manages people plays a part, because the most important records are often created by frontline managers in the moment. The consistency, quality, and fairness of that documentation is exactly the kind of thing an HR partner helps put in place before it is ever tested.

Stoppler Hughes helps Alberta employers build documentation and people practices that hold up when it matters, not because a dispute is coming, but because fair, consistent record-keeping is simply good management. If you are not confident your records would stand up to scrutiny, that is worth addressing now, while it is still routine.