Stop-work authority

Anyone can stop work they believe is unsafe — and here, that call is celebrated, never punished. Every stop is the right call: acknowledge it, resolve the hazard, resume the work.

Record a stop

1. On Stop-work authority, fill in the Record a stop-work event form: the site, what work was stopped, and the hazard that prompted it.
2. Who made the call is optional — pick the worker from the roster, or leave it blank; anonymous stops still count.
3. Workers in the field can also record a stop with no login: the site's QR field-capture page has an "I stopped work" option that files the event the same way, and it works for contractors too.

Thank the caller

• Open events show a Thank the caller button — the supervisor acknowledgment is a first-class action, stamped with the date in the Thanked column. Recognition is what keeps people willing to make the call.

Resolve before resuming

1. Unresolved events are highlighted yellow. Click Resolve.
2. Answer "How was the hazard resolved before work resumed?" and click Mark resolved — the record requires the fix, and the status flips to resolved with the resume date.
3. If the underlying hazard needs tracked follow-up, click Raise CAPA on the open event to create a corrective action; the row then links to it.

What happens automatically

• The dashboard counts stop-work authority exercised this quarter as a good number — each one is a hazard caught before it caught someone — plus the count of events awaiting resolution.
• Open stop-works appear on the huddle board as "good catches" and in the shift handover snapshot, so the incoming shift sees any work that's still stopped.

Related: observations for hazards spotted without stopping work.

Related

• Observations (BBS) — capture the good catch as a field observation
• Incidents — escalate a stop into an incident investigation
• CAPA (corrective & preventive actions) — correct the hazard that triggered the stop
• Learning teams (HOP) — learn how the work actually happened