All posts

The Competence Series | Part III: Supervisors Help Shape Organizational Culture

A policy comes to life through the people closest to the work.

When a concern is raised, how the supervisor responds shows everyone watching what the policy really means in practice.

Supervisors are where an organization's values meet the actual shift. That's a meaningful role, and people often step into it without a title change or much preparation, so it deserves real support.

The role often starts before the title does

Ontario defines a supervisor as someone who has charge of a workplace, or authority over a worker. Either one is enough on its own. BC looks at whether you instruct, direct and control workers in how they do the job. Federally there's no separate supervisor category: if you're directing work, you're acting for the employer and carrying employer duties.

None of those definitions mention a title.

The legislation treats this role as a function rather than a rank.

That's worth naming, because supervisors need preparation, and preparation is something the organization provides.

What the rules ask of you

In plain terms, the requirements are much the same in Ontario, BC, and federally regulated workplaces.

Help make sure people work the way the procedures require, and use the equipment they're supposed to use. That means following up to see it's happening, not only mentioning it once.

Share what you know about dangers. If you're aware of a hazard and associated risks and the person doing the work isn't, passing that information along is part of your role. It's a communication duty, written into law.

Take every precaution reasonable in the circumstances. That's the same open-ended phrase Ontario applies to the employer. Other workplace parties carry their own duties, which makes safety a shared responsibility.

In BC, know the rules that apply to the work you're supervising. BC builds your knowledge directly into your duty, which is a good reason for employers and supervisors to invest in that learning together.

Consult and cooperate with the committee or the worker representative. The forum exists to support you, and working with it as a partner makes the whole system stronger.

Underneath all of it sits the Criminal Code provision that came out of Westray: anyone who directs how another person does work has a legal duty to take reasonable steps to prevent harm. We covered where that came from in the post on the Internal Responsibility System. It applies regardless of province, title or paperwork.

The support you should receive first

Ontario requires your employer to appoint a competent supervisor, and it defines the word: qualified by knowledge, training and experience, familiar with the rules that apply to the work, and knowledgeable about the actual and potential dangers in that workplace.

Three tests. All three are the employer's to support before the role begins.

Federally, the Code says the same thing from another direction. Your employer must train you and inform you of your responsibilities.

So if you stepped into a supervisor role without those things, that's something to raise with your employer, ideally in writing. It's a constructive conversation, and it's exactly how the system is designed to work.

Balancing priorities is part of the role

Supervisors balance two important priorities. Production needs the work moving. The crew wants to get home the way they arrived. Most days those fit together easily. Some days they don't, and you're the one helping find the path forward.

These situations usually aren't anyone's intention. They tend to come from ordinary planning realities: a deadline that assumed everything would go right, a resource that didn't arrive, a question about why the last job took longer than expected.

Talking openly about those realities is part of the job. If you're concerned that work can't be done safely under the current plan, share it in writing with the person who can adjust it. Hazard, risk, what you need, in a few sentences.

That helps the concern reach the people with the authority to address it, which is exactly what the system is built to do.

What the role asks of you as a person

Much of this isn't technical.

Receiving a concern well. This is one of the most valuable things you do. Someone has taken a step to share something with you. How you respond, in the first few seconds, helps them feel comfortable doing it again, and shows their coworkers it's worth doing too. You don't have to agree. You do want them to leave glad they said something.

Asking before telling. Some of the most useful safety conversations start with a question rather than an answer:

  • What makes this task hard to do safely?
  • Where do you see the biggest risk?
  • What are we making harder than it needs to be?
    The people closest to the work know things that never make it into a risk assessment. Asking is how you get to that knowledge, and it tells people their experience counts.

Getting curious about why. When something isn't being done the way the procedure says, start by understanding what made that choice feel like the easiest one. What looks like a behaviour issue from the office often makes complete sense from where the work happens. Often the fix belongs to the process rather than the person.

Explaining the why, not just the rule. People follow a procedure more consistently when they understand the risk behind it. Every toolbox talk should be able to answer one question: why should anyone care? A few examples of what that sounds like:

  • We follow the isolation procedure because stored energy doesn't forgive mistakes.
  • We stop the job because production can recover from a delay, and a person may not recover from a serious injury.
    And a signature on a sign-off sheet confirms someone was there. Asking them to walk you through it confirms it made sense.

Saying you don't know. Competence here isn't having every answer. It's knowing the work well enough to recognize when you need another one, and feeling secure enough to say so out loud. It can feel uncomfortable in front of a crew, and being open about it builds far more credibility than it costs.

Correcting with respect. You'll sometimes see something that needs adjusting while others are watching. Privately where you can, matter-of-fact where you can't, focused on the practice rather than the person. People remember the respect long after the correction.

Noticing what's going right. If people only hear from you when something's off, that shapes how they see safety. Recognize the person who stopped a job because something didn't look right. Thank the person who reported a hazard. Point out the crew that caught a problem and fixed it early. "I saw what you did. Thank you" is often enough, and people repeat what gets noticed.

Closing the loop, including when the answer is no. Go back to whoever raised it and let them know what happened. A no, explained, keeps the conversation open. Following up is what keeps people engaged.

Building trust. Being trusted and being liked often go together. Trust is what helps keep people safe, and it grows from being predictable: the crew knows how you'll respond when something goes wrong, because they've seen it before.

Noticing is an attention skill, not a knowledge skill

Sometimes what changes the risk on a shift isn't a gap in anyone's training. It's a change that was easy to miss.

The crew is different today. The weather turned. A piece of equipment was swapped for a similar one. The job is the same job except for one detail that changes things.

Procedures carry assumptions, and conditions can shift without anyone noticing. A rule you've used a hundred times was written for a particular set of circumstances, and today's may be slightly different. That's completely normal, and it's why the habit of pausing to ask whether today matches those assumptions is worth more than another binder.

In practice: walk the work rather than read about it, watch the task done once rather than confirm it's understood, and treat "we've always done it this way" as a starting point for a conversation.

Told isn't the same as trained

Supervisors are often the first to see the difference between someone who was told about a procedure and someone who can actually do it safely.

A worker can sit through a toolbox talk and still not be ready to run the equipment it covered. Before someone starts a task, it's worth confirming they've been trained on it, not just told about it, and that the training fits the actual job and equipment they'll be using.

Training also tends to drift gradually rather than all at once. A refresher gets pushed back. A new hire starts before their session is scheduled. A certification lapses without anyone noticing. None of it feels urgent in the moment, and supervisors are well placed to catch it early and flag it.

A good test: could this person still do the task safely on the busiest day of the year?

The bottom line

The policy sets the direction. You're how people experience it day to day.

Many of the legal duties come down to communication in practice: share what you know, help ensure what's required is happening, and work alongside the people whose role is to raise things.

If someone on your crew noticed something today, would they tell you, and what would they expect to happen next?

Want more like this? Check out our other posts on the VirtuOHS blog, Beyond the Binder.