Toolbox Talks / General Construction
General Construction

Stop-Work Authority

Workers should be able to stop a task when conditions are unsafe, unclear or different from the plan without waiting for an injury to prove the concern was valid.

Leader guideSuggested discussion: 8-12 minPrintable sign-off included

Read every Toolbox Talk online without limits. Guest PDF downloads: 1 per day. Verified free LidLog Tools account: up to 10 individual PDFs per day across English and Spanish combined.

Also available in Spanish.

Leader note: Do not read this sheet word-for-word. Pick the sections that match today’s task, point to the actual equipment/work area, and get the crew to answer the questions out loud.

Why this matters

Workers should be able to stop a task when conditions are unsafe, unclear or different from the plan without waiting for an injury to prove the concern was valid. A toolbox talk only works if the crew talks back. Good planning names the steps, hazards, controls and ownership, then changes when the work changes. The leader’s job is to get specific answers and make it safe for someone to say the plan does not fit the field condition.

A scenario to discuss

The plan for Stop-Work Authority was discussed at the start of shift, then the scope, crew, equipment, nearby work, or sequence changes. Everyone knows the job, but the written plan no longer describes the actual setup. What gets re-briefed before the next step?

Before work starts

  • Break the work into steps and have the crew identify hazards/controls for the actual field condition.
  • Name who owns each critical control and how the crew will verify it before exposure.
  • Ask what changed since the previous plan/shift and update the plan before continuing.
  • Stop the task when a serious hazard appears or a required control is missing.
  • Move to a safe location before discussing the problem.

Common failure points

  • Reading the sheet while the crew stays silent.
  • Leaving a critical control without a named owner.
  • Continuing with the original plan after the scope, crew, equipment or neighboring work changes.

Safe work sequence / controls

  • Stop the task when a serious hazard appears or a required control is missing.
  • Move to a safe location before discussing the problem.
  • Explain the condition clearly and involve the appropriate supervisor or competent person.
  • Do not restart until the hazard has been evaluated and the plan is corrected.
  • Treat stop-work concerns as useful information, not as blame.

Stop and reset the plan if...

  • The crew cannot explain the work sequence, main hazards or controls in plain language.
  • A scope, crew, tool, material, adjacent trade or site condition changes without updating the plan.
  • Workers raise a concern that has not been resolved or ownership for a critical control is unclear.

Questions worth asking the crew

  1. Can someone other than the supervisor explain the next work step, the main hazard, and the control we are relying on?
  2. What has changed since the plan was written or since the last shift, and did we actually update the plan for it?
  3. Which critical control has a named owner today, and what happens if that person/resource is not available?
  4. What concern, near miss, or field conflict raised by the crew should change how we do the work today?
  5. What is one concern about today’s plan that someone might hesitate to raise after production starts, and how do we want it handled?

Make it real on the job

Have a crew member, not the supervisor, explain the next step, hazard, control and stop-work trigger.

Close the talk

Before the crew starts, everyone should be able to explain the hazard, point to the control being used today, and name the condition that would make the work stop.

Related authoritative reference

OSHA Recommended Practices - Worker Participation · Open reference ↗

This is a practical discussion guide, not a substitute for required training, a competent person, permits, manufacturer instructions, employer procedures, or applicable federal/state/local requirements. Adapt it to the actual task and conditions.