How to Run a Shift-Change Stop-Work Rehearsal in 20 Minutes

A shift-change stop-work rehearsal is a short, structured walk-through that checks whether the outgoing and incoming crews would stop the same job for the same reason, call the same person, and restart under the same rule. The point is not to inspect the form. The point is to test whether the decision survives the handover.

Most stop-work programs fail in the gap between policy and pressure. The rule exists, the poster exists, and the training deck exists, yet the moment a shift is late, a permit is incomplete, or a supervisor wants the job to start on time, the boundary gets negotiated again. Across more than 250 cultural transformation projects and 30+ countries of operating experience, Andreza Araujo has seen the same pattern repeat: when people rehearse the hard moment before it happens, the work is less likely to depend on courage alone. In Safety Culture: From Theory to Practice and The Illusion of Compliance, that gap between declared control and lived control is a recurring theme.

OSHA's worker participation guidance, ISO 45001:2018, and James Reason's latent-failure lens all point in the same direction. If a control cannot be explained, challenged, and restarted across a shift boundary, then the control is still too fragile for serious work. A stop-work rehearsal makes that fragility visible before the crew learns it the hard way.

Key Takeaways

• Run the rehearsal at shift change, because handover is where stop-work authority usually gets weaker.
• Use one real task with time pressure, not a low-risk example that makes the routine look better than it is.
• Put the outgoing and incoming supervisors in the same room, because the decision must survive the change in ownership.
• Test stop, escalation, and restart as three separate decisions, since many sites confuse them.
• Record one action that changes the work, not only the slide deck, the checklist, or the handover note.

What you need before starting

Gather one current task plan, one permit or job packet, one outgoing supervisor, one incoming supervisor, one worker who knows the task, a timer, and a blank action log. If the task involves contractors, include the host supervisor and the contractor lead. If the work is high consequence, include the person who can actually fund or delay a control.

This routine is written for shift supervisors, maintenance leads, warehouse leads, operations managers, and EHS partners who need a fast field proof that the stop-work rule is real. It fits plants, logistics yards, utilities, processing sites, and any operation where a crew changes hands while the risk stays in place.

Use this article together with Stop-Work Authority Explained: 4 Decision Gates That Keep It Real if you want the governance model behind the rehearsal. That article explains why the authority exists. This one shows how to test whether the authority still works at shift handover.

Step 1: Pick one task where the next shift could inherit real risk

Choose a task that will start within the next 24 hours and already carries meaningful exposure. A crane lift, an isolation boundary, a line break, a confined space entry, a mobile equipment interface, or a high-noise maintenance task are all better choices than a routine that nobody worries about. The rehearsal has to pressure the system, because calm scenarios teach you very little about decision quality.

The test is not whether the team can repeat the policy. The test is whether the task still makes sense after the handover has shifted the people, the timing, and the memory of what was said earlier in the day. If the job depends on the outgoing supervisor to explain it, then the incoming supervisor does not yet own it.

Step 2: Put both shifts in the same room and name the handover point

Bring the outgoing supervisor, the incoming supervisor, and one worker who will actually touch the job. If a contractor is involved, include the contractor lead. Write the exact handover point on paper: when does the outgoing shift stop owning the task, and when does the incoming shift begin owning it? Without that line, stop-work authority tends to become a soft suggestion that changes with the mood of the room.

OSHA's worker participation logic matters here, because people closest to the task usually know where the risk sits before the form shows it. ISO 45001:2018 also expects organizations to manage planned and unintended changes that affect occupational health and safety. A shift change is one of those changes. If the handover does not make the change visible, the system is pretending that the shift boundary is only administrative.

Step 3: Rebuild the task in plain language

Ask each person to explain the task without reading the permit. What will happen first, what will happen next, what could stop the job, and who will be told if the job stops? Keep the language plain. If the explanation needs the form to make sense, then the control lives on paper instead of in the work.

Andreza Araujo's experience across more than 250 transformation projects points to a simple rule: people repeat what they really own, not what they merely saw in training. In The Illusion of Compliance, the warning is that organizations often mistake clean documentation for real control. James Reason's work on latent failures gives the deeper reason, because a weak control often looks fine until the moment the work makes a demand on it.

Step 4: Test three stop-work triggers

Run three short scenarios and ask the crews to react in real time. First, the permit scope changes because the task steps into a new area. Second, a barrier, isolation, or line-of-fire condition changes. Third, the weather, lighting, traffic, or adjacent work makes the original plan weaker. For each scenario, ask who stops the task, how fast the stop is communicated, and whether anyone needs permission before speaking up.

The useful question is not whether the crew knows the slogan. The useful question is whether the crew can act before the consequence becomes visible. A good stop-work system does not depend on a heroic personality. It depends on a clear trigger, a clear response, and a clear expectation that the first pause is acceptable even when the shift wants to keep moving.

Step 5: Run one restart scenario

Stopping work is only half the test. Ask what has to happen before the task restarts. Who inspects the change, who confirms the boundary, who verifies the permit, and who makes the final call? If the restart owner is unclear, the site has not built stop-work authority. It has built a pause button with no release rule.

Across executive safety work, Andreza Araujo has seen that the restart decision is where fragile systems reveal themselves. Workers may be willing to stop, but they quickly learn whether the organization also supports the recovery path. If restart depends on whoever is most eager to finish, then the stop-work process is still trapped inside production pressure.

Step 6: Compare the paper boundary with the field boundary

Now compare the permit, the handover note, the radio message, the barricade, and the actual work area. They should tell the same story. If one says the task is in one zone and the field shows another, or if one says the isolation is complete while the crew is still treating the asset as live, the rehearsal has already found a serious problem.

If the table shows a mismatch, fix the mismatch before the next task starts. Paper that looks clean while the field tells a different story is a warning, not a success.

Step 7: Record one escalation path and one recovery owner

Write down who gets called when the task stops, who gets called if the stop seems unnecessary, and who owns the next move after the issue is reviewed. The point is to remove confusion from the first 10 minutes after the stop. If the crew has to invent the escalation path under pressure, the organization has already failed the rehearsal.

A site that rewards silence after a stop-work call will not get many future stop-work calls. People read the response, not the policy. If the first call produces annoyance, delay, or hidden blame, the system teaches workers to keep the next concern to themselves.

Step 8: Lock the rehearsal into the next handover

Finish by making one small change to the handover routine. Add the stop-work scenario to the next shift-start briefing. Add the restart owner to the handover note. Add one question to the supervisor checklist: what changed since the last review that would make us stop the task now?

This is where the rehearsal becomes a habit instead of a one-time event. In Safety Culture: From Theory to Practice, repeated decisions are what form culture. If the shift change never tests the stop-work boundary, the organization will keep learning that the boundary only exists when there is extra time.

Final checklist

• The task chosen for the rehearsal had real exposure and real time pressure.
• Both shifts named the same handover point and the same stop-work trigger.
• At least one restart scenario was tested, not only the stop scenario.
• The paper boundary and the field boundary told the same story.
• One owner was assigned to the escalation path and one owner to the recovery path.
• The next handover will ask the same question again instead of treating the rehearsal as finished.

FAQ

What is the main purpose of a shift-change stop-work rehearsal?

It tests whether the outgoing and incoming shifts would stop the same task for the same reason and restart it under the same rule. The rehearsal turns a policy into a field test.

How often should we run it?

Run it any time the site starts a high-risk task after a shift boundary, especially when the work depends on a permit, an isolation, or a handover that can drift between crews. Many sites will benefit from a weekly or monthly cadence on the highest-risk tasks.

Who should attend?

The outgoing supervisor, the incoming supervisor, one worker who knows the task, and the contractor lead if contractors are involved. If the task is serious enough to require resource decisions, include the person who can actually approve delay or additional control.

What if the team says there is no time?

That objection is the reason to run the rehearsal. If the site never has time to test the stop-work path, the first real stop will happen under the same pressure, only with a higher consequence.

Does this replace training or the permit-to-work system?

No. Training explains the rule, and permit-to-work manages the task, but the rehearsal checks whether the rule still works when the task crosses from one shift to another. It is a verification step, not a substitute.

Recommendation

Use the next shift handover to run the rehearsal on one high-risk task and then capture one field change that removes confusion. If the team cannot stop, explain, and restart with the same boundary, the site has found a control that still depends on memory instead of design.

That is the practical value of the exercise. It gives the next supervisor a clearer line, the worker a safer pause, and the leader a better answer than "we trained it already." If you want the decision model behind the rehearsal, keep Headline Podcast in the loop and pair this routine with the stop-work authority article before the next high-risk shift.