Your crew should understand the safety program, not the hazard alone

Teach a crew what a hazard is and they avoid it today. Teach them how the safety program works and they start fixing it for you. Most safety program training stops at the first one and calls the job finished.

TL;DR: Most crew training explains a hazard and stops there. OSHA also describes training as a way to build understanding of the safety and health program itself, so the people doing the work can help develop and implement it. A crew that knows how the program works can tell you where it breaks before an incident does.

Hazard training and program training are not the same job

A hazard briefing answers a narrow question. What is dangerous here, and what am I supposed to do about it. Tie off. Watch the edge. Inspect the ladder before you climb it. Cone off the drop zone. That information is necessary, and a crew that has it is better protected than a crew that does not.

Program training answers a wider question. How does this company decide what counts as a hazard, who writes it down, what happens after somebody raises a concern, who reviews it, and how does an answer get back to the field. One of those makes a worker a rule follower. The other makes them a participant.

The gap shows up the first time a job throws something at a crew that no rule anticipated. A hazard-trained worker looks for the rule that covers it. If there isn’t one, the decision drifts to whoever has the most years on the crew and whatever they feel like doing. A program-trained worker knows the mechanism, so the response is to run the situation through the process instead of improvising around it.

That is the part I care about as an executive. Rules cover the conditions you already thought about. The program is what handles the conditions you did not.

What OSHA says training is also for

This is not my invention. OSHA describes another role of education and training as giving workers and managers a greater understanding of the safety and health program itself, so they can contribute to its development and implementation. Read that second half again. Contribute to its development. Compliance with the program is one job the training does. Building the program is the other.

Most companies read the training section of a safety management system and hear one instruction: tell people about hazards. That instruction is real, and it is incomplete. The program itself is a subject to be taught, the same way fall protection is a subject to be taught.

Think about your orientation packet. If a new hire finishes day one able to describe five hazards and unable to describe how a hazard gets reported, reviewed, and closed, you taught half the material.

The crew already holds information your program needs

OSHA notes that workers often know the most about the potential hazards associated with their jobs, and that successful programs tap into that knowledge base. That is a statement about where the information lives.

It tracks with how the work goes. The person setting up a detail knows which step turns ugly when the wind comes up, and the person on that roof knows which deck section feels different than it did on the last visit. That knowledge is specific and current, and it sits in someone’s head instead of in your program documents.

Here is the catch. Knowing something and knowing where to put it are different skills. A crew member can be the best source of information about a hazard on that jobsite and still have no idea what to do with it. Not because they don’t care, but because nobody explained the mechanism. If the only channel they know is telling the foreman at lunch, that is the channel you get, and it ends wherever the foreman’s memory ends.

Program training is what connects the two, and it is the step that turns what the crew knows into something the program can act on.

What supervisor safety training should cover

Foremen and superintendents are where this works or dies, because they sit between the crew and the program and they are the ones who decide, day to day, whether a concern travels or stops.

If I were building supervisor safety training from scratch, these are the things I would want a foreman to explain without notes:

• The full path of a concern. A worker raises something at the start of a shift. Where does it go, who sees it, what gets recorded, who decides, and when does an answer come back.
• Who owns what. Which calls a foreman makes alone, which go to a superintendent, which go to whoever runs safety, and which stop the job.
• How the written program gets changed. If a procedure is wrong for the actual conditions on this building, what is the mechanism for changing the procedure instead of quietly working around it.
• What the company does with reports. Near misses, inspections, corrective actions. Where those land, and what they are used for after they land.
• What a useful report looks like. Enough detail that a person who was not standing there can act on it.
• What happens to the person who raises it. Say the protection out loud and in plain language. Then say it again.

None of those are hazards. They are all mechanism. A foreman who can walk a new hire through that list is running a program, and a foreman who can only recite the hazard list is enforcing one.

Which is why I have a problem with the phrase follow the program. It treats the program as finished. It tells a crew the thinking is done and their job is compliance.

A program is a living document about conditions that change. New building, new detail, new crew mix, new equipment, new weather. The moment you tell people the program is settled, you cut yourself off from the people who watch it meet reality.

The instruction I would rather give is harder. Understand how this works well enough to tell me where it is wrong. That asks the crew to know the program well enough to critique it, and it asks leadership to respond when they do. Ask for that and then sit on the answers, and you have taught the crew something worse than nothing.

How to tell whether program training changed anything

Training that cannot be measured tends to turn into a signature on a form. I wouldn’t measure this with a quiz score. I would measure it by what the field produces.

• Ask, do not test. Walk a jobsite and ask a crew member to explain what happens after they report something. The answer tells you whether the program lives in their head or only in a binder.
• Watch where reports come from. If concerns arrive from the same narrow set of people, the rest of the crew may not know the channel exists.
• Count suggestions, not only hazards. A crew that understands the program starts proposing changes to it. That is a different category of input than a hazard report, and it is the one that shows the training landed.
• Track what happens after a report. If concerns come in and nothing visibly moves, the flow tends to thin out on its own.
• Listen for the second question. “I told the foreman, what happened with that” is the sound of somebody who expects the mechanism to work. Treat it as a good sign and answer it.

None of that requires new software. It requires leaders who ask about process instead of only asking about incidents.

A practical place to start

If you want to move on this without rebuilding your whole training program, this is where I would begin.

1. Write down how a safety concern actually travels through your company, from the moment a worker notices it to the moment somebody closes it. Write the real path, not the one in the manual.
2. Compare that to what the manual says. Where the two don’t match, one of them is wrong, and it is worth finding out which.
3. Put the real path into orientation. Give it the same weight you give a hazard module.
4. Teach your foremen to explain the path, not only to enforce the rules. Have them walk you through it out loud.
5. Give the crew one clear route for concerns that doesn’t depend on catching a specific person at a specific moment.
6. Close the loop in public. When something a crew member raised changes a procedure, say so out loud and name where it came from.

That last one does more work than the rest combined. People repeat behavior that visibly matters.

Hazard training protects a crew from what you already know about. Program training gives you a crew that can find what you do not. The first keeps today’s job safe. The second is how the program gets better, and the people doing the work are the ones positioned to make that happen.