Subclause 10.2 is the most detailed and most audited part of clause 10. It is important to understand the distinction ISO 45001 draws between an incident and a nonconformity, because the standard treats them under a single, unified process but they are conceptually different:
- Incident: an occurrence arising out of or in the course of work that could or does result in injury and ill health. This includes accidents (where harm occurred) and near-misses (where harm could have occurred but did not, sometimes called "near-hits").
- Nonconformity: non-fulfilment of a requirement — either a requirement of the OH&S management system itself (a missing procedure, a control not implemented as designed) or a legal or other requirement the organization has committed to.
When an incident or a nonconformity occurs, ISO 45001 clause 10.2 requires the organization to:
- React in a timely manner — control and correct the incident or nonconformity, and deal with the consequences.
- Evaluate, with the participation of workers and the involvement of other relevant interested parties, the need for corrective action to eliminate the root cause(s) of the incident or nonconformity, so that it does not recur or occur elsewhere.
- Review existing assessments of OH&S risks and other risks, as appropriate.
- Determine and implement any action needed, including corrective action, in accordance with the hierarchy of controls (elimination, substitution, engineering controls, administrative controls, personal protective equipment) and the management of change process.
- Assess OH&S risks that relate to new or changed hazards before taking action.
- Review the effectiveness of any corrective action taken.
- Make changes to the OH&S management system, if necessary.
Practical tip
Do not let the investigation stop at "who did what." ISO 45001 explicitly ties corrective action back to the hierarchy of controls: before reaching for a training refresher or a new instruction sheet (administrative controls, near the bottom of the hierarchy), ask whether the hazard could instead be eliminated, substituted with something less hazardous, or controlled with an engineering solution (a guard, an interlock, ventilation). Auditors specifically look for evidence that this hierarchy was considered, not just applied by default to the weakest, easiest option.
Root cause analysis: the step organizations most often shortcut
The standard requires that the organization evaluate the need for action to eliminate the root cause(s) — plural, because incidents rarely have a single cause. A worker slipping on a wet floor is not just "a wet floor": it may also involve a missing drainage design, a delayed cleaning schedule, inadequate signage, or unsuitable footwear not flagged during risk assessment. Common root cause analysis methods used to satisfy this requirement include:
- The "5 Whys": repeatedly asking why a failure occurred until the underlying systemic cause is reached, rather than stopping at the first, most visible explanation.
- Fishbone (Ishikawa) diagrams: categorizing potential causes across people, equipment, methods, materials, environment and management to avoid tunnel vision on a single factor.
- Fault tree analysis: useful for more complex incidents with multiple contributing conditions, mapping how different failures combined to produce the outcome.
Whichever method is used, clause 10.2 requires worker participation in the evaluation — this is not a task to be completed solely by a safety officer at a desk. The workers involved in or familiar with the task where the incident occurred typically have the clearest view of what actually happened operationally versus what the written procedure says should happen.
The organization must retain documented information as evidence of:
- The nature of the incidents or nonconformities and any subsequent action taken.
- The results of any action and corrective action, including their effectiveness.
In practice this means an incident/nonconformity register that captures, at minimum: a unique reference, date and location, description of what happened, workers and interested parties consulted, root cause analysis performed, corrective actions decided (with the hierarchy of controls consideration visible), a responsible person and due date, and a subsequent verification that the action was effective — not just implemented, but actually effective at preventing recurrence.
10.3 Continual improvement: beyond reacting to incidents
Subclause 10.3 requires the organization to continually improve the suitability, adequacy and effectiveness of the OH&S management system by:
- Enhancing OH&S performance.
- Promoting a culture that supports the OH&S management system.
- Promoting the participation of workers in implementing actions for the continual improvement of the OH&S management system.
- Communicating relevant results of continual improvement to workers, and where they exist, workers' representatives.
- Maintaining and retaining documented information as evidence of continual improvement.
Two elements of 10.3 are distinctive to ISO 45001 compared to equivalent clauses in ISO 9001 or ISO 14001: the explicit reference to promoting a culture that supports the OH&S system, and the requirement to communicate results back to workers. This reflects the standard's underlying premise that an OH&S management system only functions if workers trust it and actively participate in it — a purely paper-based improvement process that never reaches the shop floor does not satisfy the intent of 10.3.
| Step |
Action required by 10.2 |
How to document it |
Mandatory |
| 1. Immediate reaction |
Control and correct the incident, deal with the consequences (first aid, area lockdown, containment) |
Incident report opened with date, time, location and immediate response logged |
Yes |
| 2. Worker-participated investigation |
Investigate with participation of workers and relevant interested parties |
Signed list of participants and interview notes |
Yes |
| 3. Root cause analysis |
Determine the root cause(s), not just the immediate cause |
5 Whys, fishbone diagram or fault tree recorded in the investigation file |
Yes |
| 4. Risk re-assessment |
Review existing OH&S risk assessments in light of the incident |
Updated risk register entry cross-referenced to the incident number |
Yes |
| 5. Corrective action via hierarchy of controls |
Determine and implement action, considering elimination before administrative controls or PPE |
Corrective action plan with responsible person and due date |
Yes |
| 6. Effectiveness verification |
Review whether the corrective action actually eliminated the root cause |
Follow-up verification record with date, verifier and result |
Yes |
Most common audit errors on clause 10
Across OH&S audits, the following patterns of nonconformity against clause 10 recur most often:
- Near-misses not investigated: the organization has a solid process for accidents that resulted in injury, but near-misses are logged and closed without any root cause analysis or corrective action.
- Root cause analysis stops at the immediate cause: the investigation identifies "worker did not follow procedure" and closes there, without asking why the procedure was not followed — was it unclear, impractical, or was the worker never adequately trained on it?
- Corrective action jumps straight to PPE or training: the easiest, cheapest fix (a new sign, a toolbox talk, a PPE reminder) is applied without documented consideration of elimination, substitution or engineering controls higher in the hierarchy.
- No effectiveness verification: the corrective action is implemented and the file is closed, but nobody goes back weeks or months later to confirm the same failure mode has not recurred.
- Continual improvement not communicated to workers: 10.3 requires results to be communicated to workers and their representatives, but improvements are often tracked only in management review minutes that never reach the shop floor.
// IgeraIndustria demo — incident and corrective action query
Safety Manager: Show me open corrective actions from incidents in the last quarter that haven't had effectiveness verification yet.
IgeraIndustria: 3 corrective actions pending effectiveness verification (clause 10.2). INC-2026-014 — near-miss, forklift aisle, root cause: inadequate line-of-sight signage. Corrective action: installed convex mirror + reduced speed limit signage, implemented 12/05/2026, verification due 12/06/2026 — overdue by 19 days. INC-2026-021 — minor laceration, packaging line, root cause: guard removed for maintenance access and not reinstalled. Corrective action: interlock added so guard removal stops the line, implemented 03/06/2026, verification due 03/07/2026 — overdue by 4 days. INC-2026-026 — near-miss, chemical storage, root cause: incompatible substances stored adjacent. Corrective action: segregated storage layout revised, implemented 20/06/2026, verification due 20/07/2026 — due in 3 days.
Auditor: Was worker participation documented for INC-2026-021?
IgeraIndustria: Yes. Investigation record for INC-2026-021 lists three participants: line operator L. Ferreira (injured worker), maintenance technician D. Solà, and shift supervisor as OH&S committee representative. Interview notes and signed acknowledgment attached to the incident file dated 04/06/2026.
Frequently asked questions about ISO 45001 clause 10
Does ISO 45001 require investigating near-misses the same way as accidents that caused injury?
Yes. Clause 10.2 applies to "incidents," a term the standard defines broadly to include occurrences that could result in injury and ill health, not only those that did. A near-miss where no one was hurt still triggers the same requirement: react, investigate with worker participation, determine root cause, decide on corrective action following the hierarchy of controls, and verify effectiveness. Treating near-misses as lesser events with a lighter process is one of the most common gaps auditors find.
What is the difference between a correction and a corrective action under ISO 45001?
A correction is the immediate action to control and correct the incident or nonconformity and deal with its consequences — for example, cleaning up a spill, providing first aid, or isolating a faulty machine. A corrective action goes further: it addresses the root cause so the same incident does not recur or occur elsewhere. Both are required by clause 10.2, and they are sequential — you correct first, then you investigate and correct the underlying cause.
Why does ISO 45001 specifically mention the hierarchy of controls in clause 10.2?
The hierarchy of controls — elimination, substitution, engineering controls, administrative controls, and personal protective equipment, in descending order of reliability — is a foundational OH&S principle because controls lower in the hierarchy depend on consistent human behavior to work, while controls higher in the hierarchy remove or reduce the hazard itself. ISO 45001 requires that corrective actions be determined in accordance with this hierarchy so organizations do not default to the easiest fix (retraining, a new sign) when a more reliable and permanent fix (removing the hazard, engineering it out) is feasible.
Who must participate in an incident investigation under ISO 45001?
Clause 10.2 requires evaluating the need for corrective action "with the participation of workers" and, where relevant, "the involvement of other relevant interested parties." In practice this typically means the worker(s) directly involved in or affected by the incident, workers familiar with the task or area where it occurred, any workers' OH&S representative or committee member, and — depending on the incident — supervisors, maintenance staff, or contractors if the incident involved contracted work. Excluding the affected worker's perspective from the investigation is a frequent nonconformity.
Is a root cause analysis method like the 5 Whys or fishbone diagram mandatory under ISO 45001?
No. ISO 45001 does not mandate a specific root cause analysis technique. It requires that the organization evaluate the need for corrective action to eliminate the root cause(s) of the incident or nonconformity, and retain documented information as evidence of that evaluation. Methods such as the 5 Whys, fishbone (Ishikawa) diagrams, or fault tree analysis are common, practical ways to demonstrate that a structured root cause analysis was actually performed, but the standard leaves the choice of method to the organization.
Clause 9 generates the evidence — monitoring and measurement results, internal audit findings, and management review conclusions — that clause 10 requires the organization to act on. An internal audit finding under 9.2, for instance, is a nonconformity that must be processed through the 10.2 corrective action requirements just like an incident would be. Clause 10.3's continual improvement obligation is, in turn, informed by the cumulative pattern of findings and corrective actions generated across clauses 9 and 10 over time — together they form the "Check" and "Act" stages of the OH&S management system's Plan-Do-Check-Act cycle.
Losing track of corrective actions and effectiveness verification deadlines?
IgeraIndustria centralizes every incident, nonconformity and corrective action record required by clause 10 — with automatic reminders for overdue effectiveness verifications — so nothing gets lost in spreadsheets before your next audit.
View ISO 45001 solution
Expert ISO 45001 · Updated 2026-07-31 · Step-by-step ISO 45001 series: Article 1 — Clause 4 · Article 2 — Clause 5 · Article 3 — Clause 6 · Article 4 — Clause 7 · Article 5 — Clause 8 · Article 6 — Clause 9