Root Cause Analysis Explained

Root Cause Analysis Explained

Root Cause Analysis, commonly called RCA, is a systematic method used to understand why an incident, accident, failure, or unwanted event happened. Instead of stopping at the obvious cause, RCA looks deeper into the conditions, decisions, systems, and behaviors that allowed the problem to occur.

In health and safety management, Root Cause Analysis is especially important after incidents, near misses, equipment failures, environmental events, and serious unsafe occurrences. The objective is not simply to identify who made a mistake. The real objective is to understand why the mistake or failure was possible and what needs to change to prevent a similar event from happening again.

What Is Root Cause Analysis?

Understanding the Basic Concept

A workplace incident normally has more than one contributing factor. For example, a worker may fall from a platform because there was no proper guardrail. However, stopping the investigation at “missing guardrail” does not explain the complete story.

A deeper investigation may discover that:

• The work platform was modified without approval.
• The supervisor did not inspect the platform.
• The inspection checklist was incomplete.
• Workers were not properly trained.
• The risk assessment did not consider the modification.
• Management did not establish an effective inspection system.

The missing guardrail is an immediate cause, but the investigation needs to continue until the underlying and root causes are understood.

The Main Purpose of RCA

The purpose of RCA is to identify the fundamental reasons behind an unwanted event and establish corrective actions that address those reasons.

A successful RCA should answer questions such as:

• What happened?
• What went wrong?
• Why did it happen?
• What conditions contributed to it?
• Which controls failed?
• Why did those controls fail?
• What can be changed to prevent recurrence?

Why Root Cause Analysis Is Important in HSE

It Prevents Repeated Incidents

One of the biggest benefits of RCA is preventing the same type of incident from happening again.

If an organization only corrects the immediate problem, the same failure may return. For example, replacing a damaged electrical cable may solve today’s problem, but it does not solve the reason why damaged cables were repeatedly being used.

A proper RCA could identify weaknesses in inspection, procurement, maintenance, storage, or supervision.

It Improves Safety Management Systems

RCA can reveal weaknesses in existing safety systems.

An investigation might show that:

• Risk assessments are not reviewed regularly.
• Procedures are not practical.
• Training is inadequate.
• Supervisors are overloaded.
• Inspection systems are ineffective.
• Permit controls are poorly implemented.

These findings allow management to strengthen the overall safety management system.

It Encourages Learning Instead of Blaming

A good investigation should focus on learning rather than automatically blaming an individual.

Workers can make mistakes, but workplace systems should be designed to prevent a single mistake from becoming a serious accident.

This approach helps create an environment where employees are more willing to report near misses, unsafe conditions, and mistakes.

Immediate Cause, Underlying Cause and Root Cause

Immediate Cause

The immediate cause is the unsafe condition or action that directly contributed to the incident.

For example, a worker may receive an electric shock because they touched an exposed conductor.

The exposed conductor is an immediate cause.

Underlying Cause

The underlying cause explains why the immediate cause existed.

The investigation might discover that the electrical equipment was damaged and had not been identified during the previous inspection.

The ineffective inspection process could therefore be an underlying cause.

Root Cause

The root cause goes deeper. It identifies the fundamental weakness that allowed the underlying causes to exist.

For example, the organization may have no effective system for assigning responsibility, tracking electrical inspections, and verifying corrective actions.

That management system weakness may be identified as a root cause.

A Simple Example of Root Cause Analysis

The Incident

Imagine a worker slips and falls while walking through a construction area.

At first glance, the incident appears to be caused by water on the floor.

However, a professional investigation should continue.

Asking Why the Floor Was Wet

The investigation may ask why the water was present.

The answer could be that a temporary water hose was leaking.

The next question is why the leaking hose was not repaired.

The investigation may discover that workers had reported the leak several times, but there was no formal system for tracking maintenance requests.

Looking Deeper

The investigation may then discover that the project had no clear responsibility for temporary utility inspections.

This means the problem was not simply “a worker slipped on water.”

The event may have involved weaknesses in temporary facility management, inspection, reporting, maintenance, and supervision.

This is the value of RCA. It moves the investigation from the visible event toward the organizational conditions behind it.

Common Root Cause Analysis Methods

The Five Whys

The Five Whys is one of the simplest RCA techniques.

The investigator repeatedly asks “Why?” until the underlying reason becomes clear.

For example:

Why did the worker fall?

Because the worker slipped.

Why did the worker slip?

Because oil was present on the walkway.

Why was oil present?

Because a machine was leaking.

Why was the machine leaking?

Because preventive maintenance was overdue.

Why was preventive maintenance overdue?

Because the maintenance tracking system was not effectively monitored.

The exact number of questions does not always have to be five. The important point is to continue asking meaningful questions rather than stopping at the first obvious answer.

Fishbone Diagram

The Fishbone Diagram, also called an Ishikawa Diagram or Cause and Effect Diagram, helps investigators organize possible causes into categories.

Common categories include:

• People.
• Equipment.
• Materials.
• Methods.
• Environment.
• Management.

This method is particularly useful when an incident has multiple contributing factors.

Fault Tree Analysis

Fault Tree Analysis works from an unwanted event and moves backward to identify combinations of failures that could have produced it.

It is particularly useful for complex technical systems where several failures may occur together.

For example, an equipment failure might result from a combination of poor maintenance, component failure, incorrect installation, and inadequate inspection.

Incident Timeline

A timeline can help investigators understand exactly what happened before, during, and after an incident.

It may include:

• Work preparation.
• Permit issuance.
• Toolbox talk.
• Equipment inspection.
• Start of work.
• Changes in conditions.
• Incident occurrence.
• Emergency response.

A clear timeline often reveals missed controls or decisions that would otherwise be overlooked.

How to Conduct an Effective Root Cause Analysis

Secure the Incident Scene

The first priority after a serious incident is to protect people and control the area.

Where appropriate, the scene should be preserved so that investigators can collect reliable evidence.

Photographs, equipment conditions, positions of materials, warning signs, and environmental conditions may all be important.

Collect Facts

Investigators should collect evidence before forming conclusions.

Useful information may include:

• Photographs.
• Witness statements.
• Inspection records.
• Training records.
• Permit documents.
• Risk assessments.
• Method statements.
• Equipment records.
• Maintenance history.
• Relevant procedures.

Facts should be separated from assumptions.

Interview People Properly

Interviews should focus on understanding what actually happened.

Investigators should avoid aggressive questioning that makes people feel they are being accused.

Open questions are generally more useful than questions designed to confirm a predetermined conclusion.

Identify Failed Controls

Every investigation should examine which controls were supposed to prevent the incident.

For example, controls may include:

• Engineering safeguards.
• Procedures.
• Permit systems.
• Competency requirements.
• Supervision.
• Inspections.
• PPE.
• Emergency arrangements.

The investigator should determine whether each control existed, was suitable, was understood, and was actually implemented.

Determine the Root Causes

Once the evidence is collected, investigators can identify the immediate, underlying, and root causes.

It is important to avoid choosing a root cause simply because it sounds reasonable. The conclusion should be supported by evidence.

Develop Corrective Actions

Corrective actions should address the identified causes.

For example, if an investigation identifies inadequate machine guarding, simply reminding workers to be careful may not be enough.

A stronger action may involve installing an appropriate engineering guard, verifying its effectiveness, updating inspection requirements, and establishing responsibility for maintaining the control.

Common Mistakes During Root Cause Analysis

Blaming the Worker

One of the most common mistakes is concluding that an incident occurred because “the worker was careless.”

This explanation is often incomplete.

Investigators should ask why the unsafe behavior occurred and what workplace conditions influenced the decision.

Stopping at the First Cause

Finding an obvious cause does not necessarily mean the investigation is finished.

A broken sling may explain why a load fell, but investigators should also examine inspection, storage, selection, maintenance, training, supervision, and lifting planning.

Recommending Only Training

Training is useful when lack of knowledge or competency is genuinely part of the problem.

However, training should not automatically be selected as the solution to every incident.

If the real problem is poor equipment design, inadequate guarding, excessive workload, or a weak management system, training alone may not prevent recurrence.

Writing Corrective Actions That Are Too General

Actions such as “improve safety awareness” or “conduct regular training” may sound positive but are difficult to measure.

A good corrective action should clearly explain what needs to change, who is responsible, and how completion and effectiveness will be verified.

Root Cause Analysis vs Incident Investigation

How They Are Different

Incident investigation is the broader process of understanding an event.

Root Cause Analysis is one of the important methods used within that investigation to identify the deeper reasons behind the event.

An investigation may involve evidence collection, interviews, scene examination, documentation review, causal analysis, and corrective action development.

RCA focuses particularly on understanding why the incident was able to occur.

Why Both Are Important

A strong investigation supported by RCA provides a better understanding of the event and helps the organization improve its controls.

The objective is not simply to produce an incident report. The objective is to learn something that can make future operations safer.

How Safety Officers Can Improve Their RCA Skills

Learn to Ask Better Questions

Good investigators are curious.

Instead of asking only “Who did this?”, they ask:

• What happened?
• Why did this condition exist?
• What should have prevented it?
• Why did the control fail?
• Was the procedure practical?
• Was the worker adequately supported?
• Did management know about the hazard?
• Were previous warnings ignored?

These questions encourage deeper thinking.

Study Previous Incidents

Past incidents provide valuable learning opportunities.

Safety professionals can review previous investigations and identify patterns involving equipment, supervision, procedures, human factors, and management systems.

Avoid Personal Bias

Investigators should remain objective.

The conclusion should come from evidence rather than assumptions about a particular worker, department, contractor, or supervisor.

Verify Corrective Actions

Closing an action in a tracking system does not necessarily mean the problem has been solved.

Safety professionals should verify whether the corrective action was actually implemented and whether it effectively controls the original risk.

What Makes a Good Root Cause Analysis?

It Is Evidence Based

Every important conclusion should have supporting evidence.

A strong RCA does not rely on rumors, assumptions, or personal opinions.

It Looks Beyond Human Error

Human error can be part of an incident, but it should not automatically be treated as the final explanation.

The investigation should examine the workplace conditions and systems that influenced the error.

It Produces Practical Improvements

The final outcome should lead to meaningful changes.

A good RCA should help the organization improve equipment, procedures, training, supervision, planning, communication, or management systems where necessary.

It Prevents Recurrence

The ultimate test of an RCA is whether it contributes to preventing a similar event.

If the same incident repeatedly occurs despite previous investigations, the organization needs to question the quality and effectiveness of its previous root cause analysis.

Final Thoughts on Root Cause Analysis

RCA Is About Learning, Not Blaming

Root Cause Analysis is one of the most valuable tools available to Safety Officers, HSE Managers, supervisors, and organizations that are serious about preventing accidents.

The most important lesson is simple. Do not stop when you find the person who made the mistake or the condition that directly caused the incident. Keep looking for the reasons behind that mistake or condition.

A strong Safety Officer does not ask only, “Who is responsible?”

They ask, “Why did our system allow this to happen, and what can we change so that it does not happen again?”

That mindset turns an incident into a learning opportunity and helps build a stronger, more proactive safety culture.

Risk Matrix Explained with Practical Examples