What this is
What is an unsafe act report?
What is an unsafe act report?
An unsafe act report is a behaviour-based record that captures a way of working that puts someone at risk, logged at the moment it is seen rather than after the fact. It sits under ISO 45001 cl.5.4 (worker participation) because its value depends on workers being willing to raise what they see about each other's practice without fear of it becoming a disciplinary matter.
How is an unsafe act different from an unsafe condition?
An unsafe act is a choice in how work is done — bypassing a control, skipping PPE, taking a shortcut. An unsafe condition is a state of the workplace itself — a damaged guard, a spill, a blocked exit. The distinction matters because an act usually needs a conversation and possibly retraining, while a condition usually needs a work order.
Why does the form insist on behaviour, not the person?
Because the same phrasing that identifies a person as at fault also teaches everyone else watching that being observed is risky. The template's own instructional field states this directly: the record exists to change how work is done and is never used as a disciplinary file. Break that and the reporting rate collapses within weeks.
Scope
When is an unsafe act report required?
This record is one step in a larger programme. Using it for work that belongs to a neighbouring template produces records that are hard to report on later and, worse, blurs the line between coaching and discipline that the whole approach depends on.
Use this template when
- You observed someone working in a way that puts them or others at risk, whether or not anything went wrong
- The behaviour is worth surfacing even though no injury or near miss occurred
- You are running the Incident and Investigation programme and this is its behavioural-observation step
- A coaching conversation needs a record it can be tied back to
- A pattern of unsafe acts needs to be visible before it becomes a Corrective and Preventive Action
Do not use it for
- Hazard Report, which reports something that could hurt someone, before it does, rather than a way of working.
- Unsafe Condition Report, which reports a physical problem such as a damaged guard, a spill, poor lighting or a blocked exit.
- Stop Work Record, which records that work was actually stopped because it was not safe to continue.
- Witness Statement, which documents what someone saw for an existing investigation, not a fresh observation.
- Anything outside KnowSafe, which belongs in the workspace that owns that process.
Compliance mapping
Which ISO 45001 cl.5.4 requirements does this satisfy?
The template's structure tracks a specific line of reasoning: what was seen, whether it was normal, whether a workable procedure existed, and only then what response is proportionate.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 45001 cl.5.4 | Consultation and participation of workers in identifying hazards and risks | What was seen |
| ISO 45001 cl.7.3 | Awareness of workers' contribution to OH&S performance | What was seen |
| ISO 45001 cl.8.1.2 | Elimination of hazards and reduction of OH&S risks (hierarchy of controls) | Response |
| ISO 45001 cl.7.5 | Documented information kept current and controlled | What was seen |
| ISO 45001 cl.10.2 | Investigation of incidents and non-conformities, with corrective action proportionate to effect | Response |
| ISO 45001 cl.5.3 | Roles, responsibilities and authorities assigned for reporting | Report |
| ISO 45001 cl.6.1.2 | Hazard identification informed by how work is actually done | Where |
What it does not cover
- Practice Observed, which describes only an outcome ('near miss') rather than the actual behaviour that led to it.
- Was It The Normal Way, which is answered without asking anyone else who does the same job.
- Procedure Workable As Written, which is left unanswered when a Governing Document is cited, hiding a design problem inside a personal one.
- Conversation Held, which is marked yes with no note on what was actually said or agreed.
- Action Required, which is marked no purely because a coaching conversation happened, without checking whether the same act keeps recurring.
Global
Unsafe Act Report requirements by country
Behaviour-based observation programmes sit in different legal company depending on jurisdiction — in some places they sit close to a formal duty on workers, in others they are a voluntary management practice with no direct statutory hook.
Health and Safety at Work etc. Act 1974, s.7
Places a statutory duty on employees to take reasonable care for themselves and others, which gives an unsafe act report a direct legal anchor rather than just a management-system one.
A pattern of unsafe acts that goes unaddressed can itself become evidence of a systemic failure to discharge the employer's own s.2 duty, not just an individual lapse.
OSH Act General Duty Clause, s.5(a)(1)
Has no equivalent behaviour-reporting duty on the worker; behaviour-based safety programmes here are almost always voluntary, and OSHA has historically scrutinised incentive schemes that discourage reporting.
The report must stay strictly non-disciplinary in design, or it risks being read as suppressing hazard reporting rather than encouraging it.
Work Health and Safety Act (model law), s.28
Imposes an explicit duty on workers to take reasonable care and to comply with reasonable instructions, closer to the UK model than the US one.
A documented, coached response to a first unsafe act materially strengthens an employer's due-diligence position if the same worker later causes harm.
How to complete it
How to complete an unsafe act report, step by step
The fields that matter here are not the ones with the most detail to fill in — they are the four judgement calls that decide whether the record ends up defensible or just decorative.
Practice Observed has to describe the act, not the actor. A record that reads as a character judgement rather than a description of a method will not survive scrutiny if it is ever used to justify a coaching conversation, let alone a formal action.
Was It The Normal Way decides whether this is an individual conversation or a system finding. Answering it honestly sometimes means admitting the whole team works around a control, which is uncomfortable but is exactly the finding the field exists to surface.
If a Governing Document is cited, Procedure Workable As Written must be answered. Skipping it when the procedure genuinely cannot be followed on the shop floor converts a document defect into an unfair mark against the person who could not comply with it.
Action Required should stay No for a first, isolated act handled through a genuine conversation. It should flip to Yes only where the same behaviour repeats after coaching, or where the potential severity is high enough that a single occurrence justifies a formal corrective action.
What auditors find
Most common unsafe act report findings
The gaps that recur in audits of this record are less about missing fields and more about the judgement calls above being made too quickly.
| Finding | Clause | What fixes it |
|---|---|---|
| Behaviour Category selected without a matching Practice Observed narrative | ISO 45001 cl.5.4 | Require at least one sentence of free text describing the specific action before the category picklist can be saved. |
| Was It The Normal Way answered 'No, unusual for this person' with no corroboration from anyone else on the task | ISO 45001 cl.7.3 | Route a copy of the report to the task's other regular operators for a quick confirm/deny before the record is closed. |
| Procedure Exists marked Yes with the Governing Document field left blank | ISO 45001 cl.7.5 | Make Governing Document mandatory whenever Procedure Exists is Yes, so the citation cannot be implied without a reference. |
| Conversation Held marked 'Yes, at the time' with no Coaching Record ID attached | ISO 45001 cl.10.2 | Enforce the conditional link so a coaching conversation always produces a traceable coaching record, even a brief one. |
| Potential Severity left at a low band for an act that, on a different day, would have caused a lost-time injury | ISO 45001 cl.8.1.2 | Have the supervisor, not the reporter, confirm Potential Severity before the record closes, since the reporter is rarely positioned to judge worst-case outcome. |
| Repeated instances of the same Behaviour Category from the same task with Action Required left at No each time | ISO 45001 cl.10.2 | Add a rolling check that flags a task or area with three or more unsafe act reports in the same category inside a rolling period, forcing a CAPA regardless of individual severity. |
Case in point
Case in point: the shortcut everyone uses
A supervisor observes an operator reaching across a running conveyor to clear a jam rather than stopping the line first, and logs it as an unsafe act. Practice Observed is written up plainly, Behaviour Category is set to Bypassing a control, and the honest answer to Was It The Normal Way turns out to be 'Yes, this is how the team works' once two other operators are asked.
That single answer changes the whole shape of the response. Instead of a coaching note against one operator, Procedure Exists and Procedure Workable As Written point to a jam-clearing procedure that requires a full lockout most operators find impractical mid-shift. The unsafe act report becomes the input to a CAPA on the procedure itself, not a mark against the person who was simply doing what everyone does.
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.
4 sections
- Reference
- SAF-015
- Archetype
- Record
- Record ID
- CASE-2026-000
- Scoring
- Risk band
- Direction
- High is bad
- Singleton
- No
- Basis
- ISO 45001 cl.5.4
- Links
- Feeds coaching record, CAPA
- Tags
- Hazard, Behaviour
- Sections
- 4
- Fields
- 27
- Follow up fields
- 5
- Repeating sections
- 0
- Links out
- 5
Report
4 fieldsCase ID*
Auto sequence. Format CASE-2026-00000.
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
Date and Time*
Reported By*
Where
4 fieldsSite*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Area*
The area within the site.
Exact Location
Drop a pin for anything hard to find.
What was seen
10 fieldsFocus On The Work
Describe the practice, not the person. This record exists to change how work is done, and it is never used as a disciplinary file.
Practice Observed*
Behaviour Category*
- Bypassing a control0 pts
- Not using PPE0 pts
- Line of fire0 pts
- Shortcut under time pressure0 pts
- Improvised tool or method0 pts
- Unsafe posture1 pt
Was It The Normal Way*
If everyone does it this way, it is a system issue rather than an individual one.
- No, unusual for this person2 pts
- Sometimes1 pt
- Yes, this is how the team works0 pts
Task
Job ID
Format JOB-000.
Links to FDN-004 Job Task ID
Procedure Exists*
- Yes2 pts
- No0 pts
Procedure Workable As Written
A procedure that cannot be followed in practice is a design problem.
- Yes2 pts
- Mostly1 pt
- No, cannot be followed as written0 pts
Governing Document
Document ID
Format DOC-0000.
Links to FDN-008 Document ID
Response
9 fieldsConversation Held*
- Yes, at the time2 pts
- Yes, later1 pt
- No0 pts
Coaching Record ID
Links to SAF-044 Coaching ID
Potential Severity*
- First aid4 pts
- Medical treatment3 pts
- Lost time2 pts
- Serious injury1 pt
- Fatality0 pts
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Supervisor*
Signature*
SAF-015 · record IDs look like CASE-2026-000 · Feeds coaching record, CAPA
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form captures one observation. Keeping the coaching-first culture intact, connecting repeat patterns across shifts, and holding the evidence trail together is the part that actually slips.
Holds the unsafe act report library against your task and procedure registers, and flags when the same behaviour category recurs on the same task before it becomes a formal matter.
Turns a pattern of unsafe acts on a task into a targeted retraining trigger, so the fix reaches everyone who does the job, not just the person who was observed.
Tracks whether the governing procedure behind a repeated unsafe act has actually been reviewed and reissued, so a document defect doesn't sit open indefinitely.

Coordinates the crew, rolls completion and repeat-pattern exceptions into one view, 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
Unsafe Act Report definitions and key terms
- Behaviour-based safety
- An approach that manages risk by observing and adjusting how work is actually done, rather than relying only on after-the-fact injury data.
- Just culture
- A response model that distinguishes honest mistakes and system-driven behaviour, which are coached, from reckless or wilful risk-taking, which is treated as a conduct matter.
- Hierarchy of controls
- The ranked order of risk reduction measures — elimination, substitution, engineering, administrative, PPE — used to judge whether a proposed fix actually reduces risk or just shifts responsibility to the worker.
- Worker participation
- The ISO 45001 requirement that workers are consulted on, and actively involved in, identifying hazards, which is the basis for treating an unsafe act report as an input rather than an accusation.
- CAPA
- Corrective and Preventive Action — the formal record raised when a finding needs a tracked fix and a later check that the fix actually worked.
FAQ
Frequently asked questions about unsafe act report
What is the unsafe act report template based on?+
It is built against ISO 45001 cl.5.4, worker participation in identifying hazards and risks. That framing is deliberate: the standard treats reporting a colleague's practice as a contribution to hazard identification, not as a complaint against a person.
Does an unsafe act report always lead to disciplinary action?+
No. The default response is a coaching conversation, and the template's own guidance states the record is never used as a disciplinary file. A formal action is reserved for risk-taking that is both deliberate and repeated, which is a judgement made by a supervisor, not an automatic outcome of filing the report.
Who can complete an unsafe act report?+
Anyone who observes the act. It is not restricted to supervisors or safety staff, and encouraging peer-to-peer reporting is part of what makes the record useful as an early warning rather than a lagging one.
What happens if the same unsafe act keeps happening?+
A repeat of the same behaviour after a coaching conversation is the trigger for escalation to a formal Action Required and, from there, a CAPA. The severity of any single instance matters less than the fact that coaching alone did not change the practice.
What if there is no written procedure for the task?+
Procedure Exists is marked No and the record stands on its own — the absence of a procedure is itself worth surfacing, since it means the operator improvised a method with no documented basis to judge it against.
Can the unsafe act report template be changed?+
Yes. Every field, category, score and conditional rule is editable, and the links to Coaching Record and CAPA come with it. Most teams install it as it is, run it for a cycle, then adjust the behaviour categories to match what they actually see on the floor.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Incident and Investigation
Root Cause Analysis
Finds out why something happened rather than who was involved
Corrective and Preventive Action
The single action record used everywhere
Finding
Records a single deficiency picked up during an audit, inspection or check
Effectiveness Verification
Checks whether an action actually worked, some time after it was put in place
Just Culture Determination
Separates a system problem from a genuine choice to take a risk, using a consistent set of questions
Extent of Condition Review
Asks two questions after an investigation: where else does this same condition exist, and where else could this same cause bite us
More in Hazards
Hazard Report
Reports something that could hurt someone, before it does
Unsafe Condition Report
Reports a physical problem such as a damaged guard, a spill, poor lighting or a blocked exit
Stop Work Record
Records that work was stopped because it was not safe to continue
Safety Suggestion
Captures an idea for making work safer or easier
Housekeeping Deficiency Report
Reports untidy or obstructed areas that create slip, trip and fire risk
Ergonomic Concern Report
Reports a task or workstation that causes discomfort, strain or awkward posture

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 — cl.5.4 Consultation and participation of workers
- ISO 45001:2018 — cl.10.2 Incident, nonconformity and corrective action
- Health and Safety at Work etc. Act 1974 — s.7 Employee duties
- OSH Act of 1970 — s.5(a)(1) General Duty Clause
- Work Health and Safety Act (model law) — s.28 Worker duties
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.