Mastering Root Cause Analysis with a Proven Template

Last updated: March 2026

Root cause analysis (RCA) is a structured method for determining why a workplace incident happened, not just what happened. The goal is to move past symptoms and surface-level explanations to find the underlying failures that, if corrected, will prevent the incident from recurring.

Most investigation reports that land on a safety manager's desk say something like: "Worker slipped and fell. Corrective action: remind workers to be careful." That is not a root cause analysis. That is a description of what happened followed by a hope that it will not happen again.

A real root cause analysis would ask: Why did the worker slip? The surface was wet. Why was the surface wet? A pipe had been leaking for three days. Why was the leak not repaired? It was reported but the maintenance request was never processed. Why? Because maintenance requests go through an email inbox that nobody monitors on weekends. Now you have a root cause you can fix: the maintenance request system has a gap that allows weekend reports to go unprocessed.

This guide provides three proven RCA methods, a practical template you can use immediately, and real Canadian workplace examples. If you are looking for broader guidance on the investigation process, start with our workplace incident investigation guide.

Understanding Root Cause vs. Causal Factors

Before selecting a method, clarify what you are looking for:

Root cause: The fundamental failure that, if eliminated, would prevent the incident from recurring. It is the primary driver. There may be one root cause or multiple root causes for a single incident.

Causal factors: Contributing conditions that played a role in the incident but are not the primary driver. Eliminating a causal factor would have reduced the severity or likelihood, but might not have prevented the incident entirely.

For example: a worker is struck by a reversing dump truck on a construction site.

• Root cause: The site traffic management plan did not designate separate pedestrian and vehicle zones in the loading area.
• Causal factor: The truck's backup alarm was not functioning (equipment maintenance failure).
• Causal factor: The worker was wearing earbuds and may not have heard the alarm (PPE/personnel issue).
• Causal factor: The spotter who was supposed to guide reversing trucks had been reassigned to another task (management/staffing issue).

A thorough RCA identifies the root cause and all significant causal factors, because fixing only one may not be enough. For a framework that systematically examines all five categories of causes (Task, Material, Environment, Personnel, Management), see our incident investigation guide.

📹 Watch: How to Write an Incident Report — 7 Essential Elements

Method 1: The 5 Whys

The 5 Whys is the simplest and most widely used RCA method. You start with the problem and ask "Why?" repeatedly until you reach a cause that the organization can directly control and fix. The name says "5" but you may need fewer or more iterations.

How It Works

1. State the problem clearly and specifically.
2. Ask: "Why did this happen?"
3. For each answer, ask "Why?" again.
4. Continue until the answer points to a system, process, or management failure that can be corrected.
5. When the answer stops changing or reaches something outside your control, you have likely found the root cause.

Example: Worker Fall from Scaffolding (Alberta)

Root cause: The safe work procedure for scaffolding does not address repositioning, leaving a gap where planks can go unsecured after a move.

Corrective action: Update the scaffold safe work procedure to require a full inspection and plank securement check after any repositioning. Add a scaffold repositioning checklist. Conduct refresher training for all crews.

When to Use the 5 Whys

• Straightforward incidents with a relatively clear causal chain
• Quick investigations where you need a structured approach without extensive documentation
• As a starting point before using more complex methods

Limitations

Root cause analysis is only useful if it leads to systemic fixes. SE-AI early access connects your investigation findings to training gaps, inspection failures, and program weaknesses across your operation.

The 5 Whys follows a single chain of causation. For complex incidents with multiple independent causes, you need a method that can handle branching, like a Fishbone diagram or Fault Tree.

Method 2: Fishbone Diagram (Ishikawa)

The Fishbone diagram, also called an Ishikawa diagram or cause-and-effect diagram, is a visual tool that maps all potential causes of an incident across multiple categories. It is especially useful for complex incidents where multiple factors contributed.

How It Works

1. Write the incident (the "effect") at the head of the fish.
2. Draw the main categories as branches (the "bones"). For workplace safety investigations, the standard categories are:
   • People: Training, experience, fatigue, behaviour
   • Process: Procedures, work methods, supervision
   • Equipment: Tools, machinery, PPE, maintenance
   • Environment: Weather, lighting, housekeeping, noise
   • Management: Policies, communication, resources, enforcement
   • Materials: Quality, availability, handling, storage
3. For each category, brainstorm all possible contributing causes. Write them as sub-branches.
4. For each possible cause, ask "Why?" to dig deeper (combining with the 5 Whys technique).
5. Identify the causes with the strongest evidence as root causes or key causal factors.

Example: Chemical Exposure Incident (BC)

Incident: Three workers experienced respiratory irritation after a solvent was used in an enclosed space on a renovation project in Vancouver.

• People: Workers were not trained on the specific solvent's hazards. The new worker did not understand ventilation requirements.
• Process: No confined space assessment was completed for the room. The safe work procedure for solvent use did not address enclosed areas.
• Equipment: Portable ventilation fan was available but not deployed. Respirators on site were not rated for organic vapours.
• Environment: Room had no operable windows. Temperature was 28°C, increasing evaporation rate.
• Management: Supervisor was managing two sites that day and did not conduct a pre-task review. Hazard assessments for enclosed work were not part of the standard FLHA.
• Materials: A higher-VOC solvent was substituted because the specified product was out of stock. No review of the substitute's SDS was conducted.

Root causes identified: (1) No confined space or enclosed area assessment process for renovation work. (2) Substitution of hazardous materials without SDS review or supervisor approval.

When to Use a Fishbone Diagram

• Complex incidents with multiple contributing factors
• When you want to involve a team in brainstorming (the visual format encourages participation)
• When you suspect multiple independent failures converged

Method 3: Fault Tree Analysis

Fault Tree Analysis (FTA) is the most rigorous method. It uses Boolean logic (AND/OR gates) to map how combinations of failures lead to the incident. It is typically used for serious incidents or systemic analysis.

How It Works

1. Define the "top event" (the incident).
2. Identify the immediate causes. For each, determine whether the causes are:
   • AND gate: All sub-causes had to occur for this cause to happen
   • OR gate: Any one sub-cause was sufficient
3. Continue breaking down each cause into sub-causes until you reach "basic events" (root-level failures).
4. The tree visually shows which combination of failures led to the incident and which single-point failures, if prevented, would have broken the chain.

When to Use Fault Tree Analysis

• Fatalities or critical injuries where regulatory investigation is involved
• Recurring incidents where simpler methods have not identified the pattern
• Systemic reviews of an entire process or operation

Root Cause Analysis Template: Step-by-Step

Use this template structure for any workplace incident RCA. Adapt the method (5 Whys, Fishbone, or Fault Tree) based on the complexity of the incident.

Download the full printable RCA template as part of our free Incident Investigation Kit.

Common RCA Mistakes to Avoid

1. Stopping at the first answer. "Worker was not paying attention" is a symptom, not a root cause. Ask why the worker was not paying attention (fatigue? distraction? unclear procedure?).
2. Blaming individuals instead of systems. If a worker made an error, ask what system allowed the error to happen. Were they trained? Was the procedure clear? Was there a check? People make mistakes; systems should catch them.
3. Insufficient data. An RCA is only as good as the evidence behind it. If you did not collect enough photos, statements, and documents during the investigation, the analysis will be superficial. See our guide to the essential elements of an incident report for what to capture.
4. Accepting "human error" as a root cause. Human error is always a causal factor, never a root cause. The root cause is whatever allowed the error to result in harm: a missing guard, an inadequate procedure, a lack of training, or a system without error-proofing.
5. Writing corrective actions that are vague. "Improve communication" is not actionable. "Conduct daily pre-shift briefings covering active hazards, assigned by the site superintendent, starting March 15" is actionable.
6. Not following up. A corrective action that is assigned but never verified is worse than no corrective action. It creates a paper trail showing you identified the problem and then did nothing about it.

Using Software for Root Cause Analysis

Paper-based RCA works, but digital safety management systems make the process more reliable and easier to maintain over time. With Safety Evolution, the entire workflow from initial incident report to investigation to RCA to corrective action tracking is connected in one system:

• The initial incident report automatically populates the investigation with the known facts, photos, and witness statements.
• Investigators can map causal factors and document the analysis within the investigation module.
• Corrective actions are created, assigned, and tracked with automatic reminders and completion sign-off.
• Historical investigation data is searchable, so you can identify patterns across multiple incidents (for example: three scaffold-related incidents in six months all pointing to the same procedural gap).

The ability to search and analyze past RCAs is where digital systems provide the most value. Patterns that are invisible in a filing cabinet become obvious in a dashboard.