Stop-Work Authority That Actually Gets Used
Anyone can stop the job. Very few sites have made that true.
Most projects have the sentence.
Anyone can stop the job. It sits in the induction, the construction phase plan and the permit rules. It photographs well on a site board.
Then the client arrives, the crane is booked, and a supervisor sees something that is not right. That is the moment the sentence is tested. Not the audit. Not the policy review.
I have watched that moment go both ways. The difference is rarely courage in the abstract. It is whether the system has already decided what happens to the person who uses the authority.
Why the poster version fails
Construction treats stop-work as a right. High-hazard environments treat it as a controlled process.
A right with no rehearsal, no public backing and a messy restart is not a control. It is a hope. People can read the hope in the room. They wait to see whether the first person who stops a job is supported or quietly managed afterwards.
If they are managed, the authority dies. The next person will find a reason to keep going. The RAMS will still say stop-work applies.
That is how sites stay compliant on paper and silent under pressure.
A live example, without the theatre
On a multi-contractor commissioning site the lift looked ordinary on paper. The banksman flagged that the set-down would put the load over a route another crew still needed. The method statement had not caught the interface. The client was on the ground.
The supervisor paused the lift. Not a dramatic stand-down. A hand, a radio call, a ten-minute hold.
What mattered was the next five minutes. Nobody talked over him. The client asked what was needed to restart. The exclusion zone moved. The lift ran.
That is stop-work working. Short. Specific. No punishment. A controlled restart. The same behaviour as a nuclear permit hold, stripped of the mystique.
Four conditions that make it real
I keep seeing the same four conditions on sites where stop-work is used without a row.
It is named where work actually starts. Induction and permit board. Not only in a plan nobody rereads. People should be able to say the trigger out loud before they sign.
Supervisors are backed in public. Especially in front of the client. A private “well done” after a public sigh teaches the opposite lesson.
Restart is controlled. Stopping is half the job. Who holds the restart? What must change? Who briefs the change? A sloppy restart is how a good stop becomes the next incident.
Nobody is punished for a good stop. If the first use costs the supervisor politically, you do not have stop-work authority. You have a slogan.
Miss any one of those and the poster still looks compliant.
What high-hazard discipline adds
This is the sibling point to the nuclear confined-space lesson.
In those systems a hold is not an argument. It is expected. Competence is checked at the point of work, not assumed from a ticket. The permit is refused if the method in front of you does not match the plant in front of you. Restart is a second decision, not an automatic continuation.
Construction already has the language. Permits. RAMS. Briefings. Competence. The gap is usually discipline under social pressure, not missing clauses.
You do not need a nuclear site to copy the useful parts: name the hold, back the holder, control the restart, refuse the tidy permit that does not match the job.
A 90-second test before you sign
Before you approve a permit, a method statement or a briefing, ask:
If this goes wrong in the next hour, would someone junior actually stop it?
Would they still stop it if the client was standing there?
Do they know what “good” looks like for the restart?
If any answer is no, fix the system before you start the task. Do not add another sentence to the plan.
What I watch instead of the poster
Zero RIDDOR is a lagging number. I pay more attention to how often work is paused without a row, how often a permit is refused at the board, and whether briefing challenges come from the people on the tools or only from the person running the huddle.
Those measures look like friction if you only report output. They look like control if you have seen the alternative.
Stop-work authority is not a slogan to protect the file.
It is a behaviour you either support in the moment, or you train people to abandon.
What actually makes stop-work usable on your projects — not just permitted?