What this is
What is a safety stand down record?
What is a safety stand down record?
It is the record of a planned, site-wide pause in work called to discuss a serious event or an emerging risk, usually following an incident on site, in the group, or in the wider industry. It captures who called it, whether production actually stopped, attendance across shifts and contractors, what was raised, and what happened afterwards.
How is a stand down different from a safety moment?
A safety moment is a short, routine, low-stakes topic shared daily or weekly by whoever is on rota. A stand down is an exceptional, leadership-called event tied to a specific trigger, expected to stop production across all shifts and contractors, and expected to close with a documented feedback loop back to the workforce.
What makes a stand down defensible after the fact?
Not that it happened, but that it reached everyone it needed to. A stand down that covers day shift only, excludes contractors, or restarts work before concerns are answered undermines the message it was called to send, and a reviewer reading the record afterwards will look specifically for those gaps.
Scope
When is a safety stand down record required?
This is an exceptional, whole-site event, not a routine one. Using it for a topic that only needs a daily reminder, or skipping it in favour of a lighter record, produces evidence that misrepresents how the organisation actually responded.
Use this template when
- A significant incident, near miss, or emerging industry risk warrants a full pause in work rather than a routine reminder
- Site leadership needs to speak directly to the workforce, across all shifts, including contractors
- The trigger is serious enough to justify stopping production, not just raising awareness in passing
- A new record is needed and gets its own ID in the form SD-2026-000
- A linked case or CAPA needs this record to exist, because the stand down is the traceable response to a specific parent event
Do not use it for
- Safety Moment Record, which shares a short topic at the start of a shift or meeting and does not require production to stop.
- Safety Campaign Plan, which plans a dated, multi-week push on one topic with activities and measures, not a single reactive pause.
- Committee Action Log, which tracks follow-up actions from a standing safety committee, not a one-off leadership-called event.
- Leadership Safety Walk, which is a scheduled floor walk by a leader, not an announced, all-hands pause tied to a specific trigger.
- Anything outside KnowSafe, which belongs in the workspace that owns that process.
Compliance mapping
Which ISO 45001 cl.7.4 requirements does this satisfy?
The record maps to ISO 45001's communication and participation clauses, but its weight — attendance percentage, contractor inclusion, a committed feedback loop — reflects that a stand down is treated as a formal management response, not routine engagement.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 45001 cl.7.4.2 | Internal communication in response to a significant event must be recorded: who called it, when, and why. | Header |
| ISO 45001 cl.6.1.2 | An emerging risk identified through the trigger must be documented as the basis for the response, not just referenced informally. | Why |
| ISO 45001 cl.5.4 | Consultation and participation requires that all affected workers, including contractors, actually stop and take part, not a nominal subset. | Delivery |
| ISO 45001 cl.7.4.3 | External communication and language needs must be met, which is why translation coverage is scored, not optional. | Delivery |
| ISO 45001 cl.10.2 | Concerns raised during the stand down that indicate a nonconformity must be tracked to a corrective action, not left as a discussion note. | What people said |
| ISO 45001 cl.9.1 | Monitoring requires an attendance percentage the organisation can measure the response against, not just a headcount. | Delivery |
| ISO 45001 cl.5.4 | Participation requires the organisation to close the loop and tell people what happened with the concerns they raised. | Result |
What it does not cover
- Production Fully Stopped marked Partly or No, which scores zero because a stand down that lets work continue has not delivered the message it was called to send.
- All Shifts Covered marked Day shift only, which leaves the shifts least likely to be present for other communication uninformed of a serious event.
- Contractors Included marked No where contractors are present on site, which excludes exactly the group most exposed to an unfamiliar hazard.
- Follow Up Needed marked Yes with no CAPA ID attached, which breaks the link from a raised concern to the corrective action process meant to resolve it.
- Feedback Loop Date left as a formality with no evidence it was honoured, which tells the workforce their concerns were logged but never actually answered.
Global
Safety Stand Down Record requirements by country
A stand down is a management decision, but the duty to communicate a serious risk to the whole exposed workforce, including contractors, is a statutory floor in most jurisdictions that run this template.
ISO 45001:2018 cl.7.4 and cl.5.4
Treated as a formal, auditable response to a significant event under a certified management system.
An auditor will specifically check whether contractors and all shifts were covered, and whether concerns raised led to a documented corrective action.
Health and Safety at Work etc. Act 1974, s.2 and s.3
Duties extend to employees and, under s.3, to people not in the employer's employment — contractors on site.
A stand down that excludes contractors after a serious incident weakens the employer's position on the s.3 duty if a contractor is later exposed to the same risk.
OSH Act 1970, s.5(a)(1) (General Duty Clause)
A documented, whole-workforce stand down after a recognised serious hazard supports a defence that the employer acted promptly and comprehensively.
Partial coverage — one shift, no contractors — undercuts that defence and can itself become a line of questioning in an OSHA investigation.
How to complete it
How to complete a safety stand down record, step by step
The fields are straightforward to fill in; the judgement calls that decide whether the stand down actually did its job sit in how honestly those fields are answered.
A line paused while a supervisor talks over the noise of an adjacent line still running is not fully stopped. The bar is that the physical work covered by the trigger has genuinely halted for the duration of the discussion.
Marking Translated Where Needed as N/A should require confidence every attendee understood the primary language delivery, not an assumption that most people probably did.
A concern that names a specific unresolved hazard, not a general worry, should trigger Follow Up Needed and a CAPA ID before the stand down record closes, not after someone reviews it later.
A Feedback Loop Date that is never checked against an actual follow-up communication is worse than no promise at all, because it tells the workforce their input was logged and then dropped.
What auditors find
Most common safety stand down record findings
These are the patterns that surface once a run of stand down records gets read together rather than filed and forgotten.
| Finding | Clause | What fixes it |
|---|---|---|
| Production Fully Stopped is marked Partly on more than one occasion | ISO 45001 cl.7.4.2 | Require a written reason whenever the answer is Partly, and route it to site leadership for review before the record closes. |
| Contractors Included defaults to Not applicable regardless of who is actually on site | Health and Safety at Work etc. Act 1974, s.3 | Cross-check against the site's active contractor register before accepting Not applicable as the answer. |
| Concerns raised in What People Said rarely carry a CAPA ID even when Follow Up Needed is Yes | ISO 45001 cl.10.2 | Make CAPA ID mandatory, not conditional-optional, whenever Follow Up Needed is Yes. |
| Feedback Loop Date is set but no corresponding communication is ever logged | ISO 45001 cl.5.4 | Add a simple confirmation step at the Feedback Loop Date that records whether the promised update actually went out. |
| Work Restarted At is logged before all shifts have completed the stand down | ISO 45001 cl.7.4.2 | Block the restart timestamp from being entered until All Shifts Covered is marked Yes. |
| The same Trigger category is used for events of very different severity | ISO 45001 cl.6.1.2 | Pair the Trigger field with a short severity note so the emerging-risk basis for the stand down is distinguishable at a glance. |
Case in point
Case in point: the stand down that nearly missed the night shift
A near-miss on a cutting line prompted a same-day stand down, called by the site manager and delivered to day shift within the hour. The record showed Production Fully Stopped as Yes and Led By Senior Leader as Yes, which on paper looked complete.
It was the All Shifts Covered field that caught the gap: night shift hadn't started yet, and without a second delivery scheduled, the record would have closed showing Day shift only. The site manager returned for a second session at shift changeover, logged separately, and the Feedback Loop Date carried a committed update to both shifts on what the investigation found — the kind of follow-through the field exists to force.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
6 sections
- Reference
- SAF-130
- Archetype
- Record
- Record ID
- SD-2026-000
- Scoring
- Attendance percent
- Direction
- High is good
- Singleton
- No
- Basis
- ISO 45001 cl.7.4
- Links
- Links Case; feeds CAPA
- Tags
- Campaign, Culture
- Sections
- 6
- Fields
- 40
- Follow up fields
- 1
- Repeating sections
- 1
- Links out
- 3
Header
14 fieldsStand Down ID*
Auto sequence. Format SD-2026-0000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Date and Time*
Called By*
Duration Minutes*
Site 2*
Site ID 2*
Format SITE-000.
Links to FDN-001 Site ID
Case ID
The event that prompted this stand down.
Thread key. Every record in this chain carries this value
Parent Type
What kind of record this follows.
Parent ID
The reference of that record.
Immediate predecessor record
Raised Date*
Stop Everything
A stand down means production stops. That is the message. If work continues in the background, the stand down says the opposite of what you intended.
Why
3 fieldsTrigger*
Serious incident here, serious incident elsewhere in the group, industry event, or emerging risk.
What Happened*
What We Know So Far*
Be honest about what is not yet known. Speculation damages trust.
Delivery
8 fieldsProduction Fully Stopped*
- Yes3 pts
- Partly1 pt
- No0 pts
All Shifts Covered*
- Yes3 pts
- Partly1 pt
- Day shift only0 pts
Contractors Included*
- Yes3 pts
- Not applicable3 pts
- No0 pts
Workers On Site*
Workers Attended*
Attendance Percent*
Led By Senior Leader*
- Yes3 pts
- No0 pts
Translated Where Needed*
- Pass2 pts
- Partial1 pt
- Fail0 pts
- N/Aexcluded from denominator
What people said
Repeats5 fieldsConcern Or Question Raised*
Area
Answered On The Day*
- Yes3 pts
- Partly1 pt
- No0 pts
Follow Up Needed*
- No3 pts
- Yes1 pt
CAPA ID
Links to FDN-014 CAPA ID
Related records
1 fieldCampaign Plan ID
Where the stand down formed part of a campaign.
Links to SAF-128 Campaign ID
Result
9 fieldsConcerns Raised*
Actions Committed*
Feedback Loop Date*
When people will be told what happened with their concerns.
Work Restarted At*
Conditions On Restart
Called By*
Signature*
Site Manager*
Second Signature*
SAF-130 · record IDs look like SD-2026-000 · Links Case; feeds CAPA
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form is the easy part. Confirming every shift and every contractor was actually covered, and chasing a raised concern through to a closed CAPA, is the work that actually slips.
Holds the stand down record against the triggering case, flags partial coverage across shifts or contractors, and keeps every raised concern linked to its CAPA.
Cross-checks Contractors Included against who was actually on site that day, so the answer reflects the real contractor register, not a default.
Tracks the committed Feedback Loop Date against whether the follow-up communication actually went out, and rolls stand-down frequency into the audit evidence pack.
Coordinates delivery across shifts so a stand down doesn't quietly stop at day shift, and holds every write for your approval before it touches a record.
This template lives in KnowSafe — safety and compliance. Incidents, hazards, permits, inspections and the critical controls behind them.
Meet KnowSafe→Glossary
Safety Stand Down Record definitions and key terms
- Stand down
- A planned, site-wide pause in work, called by leadership in response to a serious incident or emerging risk, intended to stop production and speak directly to the exposed workforce.
- Attendance percent
- The scoring basis for this template: attendance measured as a share of workers on site, not a raw count, because coverage across the whole workforce is the point.
- Thread key
- A linking field, here the Case ID, that ties the stand down back to the incident, near miss or emerging risk that triggered it.
- Feedback loop
- The committed date by which leadership tells the workforce what happened with the concerns raised during the stand down, closing the participation cycle.
- CAPA
- Corrective and Preventive Action — the record a raised concern feeds into when it identifies a nonconformity needing formal resolution beyond the stand down itself.
FAQ
Frequently asked questions about safety stand down record
Who is authorised to call a stand down?+
Site leadership, typically the site manager or a senior leader on their behalf, not a supervisor acting alone. The Called By field should reflect that seniority.
Does a stand down have to stop the entire site?+
It has to stop the work covered by the trigger, across every shift and every contractor exposed to that work. Partial coverage undermines the point of calling it at all.
What happens to concerns raised during the stand down?+
Each one is logged individually in What People Said, and anything needing follow-up gets a CAPA ID so it is tracked to resolution rather than left as a discussion note.
How soon should work restart after a stand down?+
Only once every affected shift has been through the stand down and any immediate conditions on restart have been set and communicated.
How is attendance scored?+
As a percentage of workers on site who attended, which is a more honest measure than a raw count when shift sizes vary.
Can the template be adapted per site?+
Yes. Every field, option and conditional rule is editable, and its links to the triggering case and any CAPA travel with it.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Safety Culture and Engagement
Improvement Suggestion Record
Captures an improvement idea from anybody, with what it would change and who could own it
Safety Observation
A short record of how a task was actually done, noting both safe practice and risk
Behaviour Based Observation
Looks at a specific set of behaviours agreed with the workforce, such as line of fire, body position and tool use
Leadership Safety Walk
A senior leader spends time in the workplace talking with workers about how the work really goes
Safety Coaching Record
Records a coaching conversation after an at risk practice was seen
Critical Task Observation
Watches a high risk task from start to finish against its procedure
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 45001:2018 — Clause 7.4, Communication
- ISO 45001:2018 — Clause 5.4, Consultation and Participation
- Health and Safety at Work etc. Act 1974 — Sections 2 and 3
- Occupational Safety and Health Act 1970 — Section 5(a)(1), General Duty Clause
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.