SafetyPro
  1. Home
  2. Blog
  3. Incident investigation and root cause analysis: a step-by-step guide
Blog

Incident investigation and root cause analysis: a step-by-step guide

The point of an investigation is not to find someone to blame. It is to understand why the incident happened and change the conditions so it does not happen again. This guide walks through the process.

SafetyPro Team · · 3 min read

Why investigations matter

Every incident and near miss is information about how work is really done. Organisations that investigate well find weaknesses in equipment, procedures, training and supervision before they cause serious harm. Organisations that stop at "worker did not follow procedure" usually see the same incident again.

Step 1: make the area safe and report

Look after injured people first and make the area safe so nobody else is hurt. Then report the incident quickly, even if details are incomplete. Fast reporting matters: memories fade, evidence is moved and some incidents must be notified to authorities within a set time.

Step 2: preserve and gather evidence

  • Photographs and video of the scene, equipment and conditions before anything is moved.
  • Statements from the injured person, witnesses and supervisors, taken separately and as soon as possible.
  • Documents: permits, risk assessments, method statements, training and competency records, maintenance logs.
  • Physical evidence: failed parts, tools and personal protective equipment.
  • Environmental conditions: lighting, weather, heat, noise and housekeeping.

Step 3: build a timeline

Put the events in order, from the planning of the work to the moment of the incident and the response. A clear timeline shows where the plan and the reality separated, and it stops the team from jumping to conclusions.

Step 4: find the root causes

The immediate cause is what directly led to the incident, such as a fall from an unguarded edge. Root causes are the underlying reasons the condition existed, such as no inspection of edge protection, unclear responsibility or a schedule that pushed crews to skip steps. Two common methods help:

  • 5 Whys: keep asking why until you reach a cause that, if fixed, would prevent many similar incidents. Five is a guide, not a rule.
  • Fishbone (Ishikawa) diagram: group possible causes under headings such as people, methods, equipment, materials, environment and management, then test each one against the evidence.

Example of 5 Whys: a worker cut a hand. Why? The grinder guard was missing. Why? It was removed to fit a larger disc. Why? The correct grinder was not available on site. Why? Tool requests take two weeks to approve. Why? There is no stock of critical tools on site. The fix is a tool supply process, not only a reminder to the worker.

Step 5: agree corrective actions

Choose actions that address the root causes and follow the hierarchy of controls: eliminate the hazard, substitute something less hazardous, use engineering controls, then administrative controls, and only then rely on personal protective equipment. Every action needs a named owner and a due date.

Step 6: verify and share the lessons

An action is not finished when someone ticks a box. Check that it was done and that it works, ideally with evidence such as a photo or an inspection. Then share the lessons across other sites and projects, because the same conditions usually exist elsewhere.

Common investigation mistakes

  • Stopping at human error instead of asking why the error was possible.
  • Investigating only injuries and ignoring near misses.
  • Corrective actions that are only retraining or a reminder.
  • No follow-up, so actions stay open for months.
  • Lessons kept inside one project instead of shared across the organisation.

HSE insights and practical guides

See it on your own projects

Tell us about your sites and we will show you how SafetyPro fits your HSE operations.