4 min read · Practical guidance for Saudi organizations
In this guide
Root cause analysis (RCA) investigates why an incident happened and why the system allowed it to happen. Its purpose is to support effective prevention, not to stop at blame or a convenient label such as “human error.” A defensible analysis connects evidence, contributing conditions and corrective action.
Start with response, reporting and evidence
Protect people, make the situation safe and meet applicable reporting obligations. Preserve relevant evidence when it is safe and lawful to do so. Collect the task sequence, equipment condition, work instructions, permits, training and supervision information, and accounts from people involved. Distinguish established facts from assumptions.
ISO 45001 addresses incidents, nonconformity and corrective action in clause 10.2. Investigation does not replace regulatory notification. Use the Saudi compliance register to identify applicable reporting routes and deadlines.
Using the 5 Whys
The 5 Whys method follows a causal chain by repeatedly asking why an event or condition occurred. Five is a prompt, not a required number. Stop when the evidence supports an actionable system cause, not when a fifth question has been asked. Where several causes interact, explore more than one branch.
- Write a specific, neutral problem statement.
- Ask what caused that condition and identify supporting evidence.
- Check whether the answer explains the event rather than simply naming a person.
- Continue into the organizational conditions that allowed the failure.
- Validate the chain with the investigation team and the facts.
An illustrative scaffold incident
An investigation might find that access to an incomplete scaffold was not effectively controlled. Further questions could examine handover arrangements, inspection status, changes in work scope and responsibility for releasing the scaffold for use. These are investigation hypotheses, not conclusions to copy into a real report. Equipment condition, physical evidence and witness accounts must determine which causes actually apply.
Using a fishbone diagram
A fishbone diagram organizes possible causes into categories. Depending on the incident, categories might include people, methods, equipment, materials, environment and management. It helps a team avoid focusing too narrowly on the first explanation. An item placed on the diagram remains a hypothesis until evidence supports it.
| Method | Useful for | Limitation |
|---|---|---|
| 5 Whys | Exploring a specific causal chain. | Can oversimplify an event if treated as a single mandatory chain. |
| Fishbone | Exploring several categories and interacting contributors. | Brainstorming alone does not establish causation. |
From analysis to corrective action
Separate immediate correction from an action that addresses a cause. Removing an obstruction is a correction; improving the process that repeatedly allows the obstruction may be corrective action. Assign each action an accountable owner, due date and required evidence. Prefer measures that improve controls at source rather than defaulting to a reminder or another training session.
Link findings back to the risk assessment and any relevant permit, isolation, contractor or change-management process. Update the actual process and communicate changes to affected people.
Free ProSafe template
Incident root cause analysis template (Arabic)
An Arabic template for the event, evidence, fishbone analysis, 5 Whys, corrective actions and effectiveness checks.
Verify effectiveness, not only completion
An action can be completed without solving the problem. Define the effectiveness check before closing the investigation: what will be observed, by whom, over what period and against what acceptance criterion? Check for recurrence, worker understanding and actual use of the revised control. Use performance indicators as supporting evidence rather than treating a short incident-free period as proof.
Common investigation errors
- Writing “carelessness” or “lack of awareness” without examining conditions.
- Selecting causes before gathering evidence.
- Confusing consequences with causes.
- Assigning broad actions without owners or deadlines.
- Closing actions solely because a document was uploaded.
- Copying the same causes into unrelated incidents.
Frequently asked questions
Must there be exactly five whys?
No. The depth should follow the evidence and the complexity of the event.
What is CAPA?
Corrective and preventive action terminology describes processes for addressing problems and preventing recurrence or occurrence. Within ISO 45001, risk-based planning and corrective action should form a connected improvement process.
Can software determine the root cause?
Software may organize evidence, hypotheses and action tracking. Competent investigators must establish and validate the conclusions.