Root Cause Analysis Template: 5 Formats for Different Situations
You have an incident to investigate, a blank page, and a deadline. The hard part is rarely the analysis itself — it is knowing which format to put in front of your team so the investigation stays structured instead of drifting into opinion and blame. A good root cause analysis template forces the right questions in the right order. The problem is that one template does not fit every incident.
A simple slip-and-fall, a recurring quality defect, a catastrophic equipment failure, and a near-miss that "just happened after the new procedure rolled out" each call for a different analytical lens. Reaching for 5 Whys when the situation has multiple interacting causes produces a confident but wrong answer. This article gives you five RCA templates, when to use each, and a filled example for every one — so you can match the format to the situation rather than forcing every incident through the same funnel.
Skip the blank page entirely. WhyTrace Plus gives you guided 5 Whys, fishbone, and structured investigation workflows with AI-suggested causes and countermeasures built in. Start free and turn your next incident report into a finished analysis in minutes.
What a Root Cause Analysis Template Is (and Why You Need Five)
A root cause analysis template is a structured form that guides an investigation from a problem statement to verified underlying causes and corrective actions. It standardizes the questions asked, prevents the investigation from stopping at symptoms, and produces a documented record that an auditor or manager can follow.
OSHA's FactSheet on root cause analysis (OSHA 3895) is direct on the point: root causes "generally reflect management system or organizational failings" rather than individual error, and OSHA encourages employers to go beyond the minimum required investigation to find them. As of 2026, OSHA's incident investigation guidance continues to recommend structured RCA tools rather than a single mandated format — because incident types differ, and the right tool depends on the problem in front of you.
The five formats below cover the situations EHS and quality teams encounter most:
| Template | Best for | Output shape | Difficulty |
|---|---|---|---|
| 5 Whys | Single, linear cause chains | A vertical chain of "why" answers | Low |
| Fishbone (Ishikawa) | Brainstorming many possible causes | A categorized cause diagram | Low–Medium |
| Fault Tree Analysis | Complex failures, multiple contributing causes | A top-down logic tree (AND/OR gates) | High |
| Barrier Analysis | Incidents where a defense failed | A hazard-target-barrier map | Medium |
| Change Analysis | "It worked until something changed" | A before/after difference comparison | Medium |
You do not need to master all five before your next investigation. You need to recognize which one the situation calls for. The rest of this article walks through each.
The 5 Whys Template: For Single, Linear Cause Chains
The 5 Whys template asks "why" repeatedly — typically five times — to trace a problem from its visible symptom down to the underlying cause. It works best when an incident has a single, traceable cause chain without multiple branching contributors.
Use it for straightforward incidents: a leak, a missed inspection, a single machine stoppage. It breaks down when causes interact or branch, because the linear format forces you to pick one path and ignore the others. For a deeper walkthrough, see the complete 5 Whys guide.
Template structure:
| Field | Entry |
|---|---|
| Problem statement | (What happened — observable, specific) |
| Why 1 | Because… |
| Why 2 | Because… |
| Why 3 | Because… |
| Why 4 | Because… |
| Why 5 (root cause) | Because… |
| Corrective action | (Addresses the root, not the symptom) |
| Verification | (How you'll confirm it worked) |
Filled example — conveyor stoppage:
- Problem: Conveyor line 3 stopped during the morning shift, halting production for 40 minutes.
- Why 1: A bearing seized. → Because it ran without lubrication.
- Why 2: It ran without lubrication. → Because the scheduled greasing was skipped.
- Why 3: The greasing was skipped. → Because the PM task was not on the operator's shift checklist.
- Why 4: It was not on the checklist. → Because the checklist was last revised before line 3 was installed.
- Why 5 (root cause): The PM checklist revision process is not triggered when new equipment is commissioned.
- Corrective action: Add a commissioning-stage step requiring PM checklist updates before equipment goes live.
- Verification: Audit the next three commissioning events for completed checklist updates.
Notice that the root cause is a process gap, not "the operator forgot." That is the signal of a 5 Whys done correctly: the final answer points at the management system.
The Fishbone (Ishikawa) Template: For Brainstorming Many Possible Causes
The fishbone diagram — also called the Ishikawa diagram or cause-and-effect diagram — organizes potential causes of a problem into categories arranged around a central "spine." It is built for the early, divergent phase of an investigation, when you need to surface every plausible cause before narrowing down.
Use it when an incident likely has several contributing factors and you want a team to brainstorm systematically rather than fixate on the first explanation. The categories prevent the common failure of investigating only the most obvious cause. Common manufacturing and safety categories follow the "6 Ms": Manpower (People), Method, Machine, Material, Measurement, and Environment (Mother Nature). OSHA-oriented investigations often substitute People, Process, Equipment, Materials, Environment, and Management.
Template structure:
Manpower Method Machine
\ | /
\ | /
────────────────────────────────────────────────► PROBLEM (effect)
/ | \
/ | \
Material Measurement Environment
For each category, the team lists candidate causes on the diagonal "bones," then ranks the most likely ones for verification.
Filled example — recurring weld defects:
| Category | Candidate causes |
|---|---|
| Manpower | New welders not yet certified; shift handover gaps |
| Method | Weld procedure spec ambiguous on travel speed |
| Machine | Wire feeder calibration drift |
| Material | Incoming steel lot variation in coating thickness |
| Measurement | Inspection gauge not recalibrated this quarter |
| Environment | Drafts in the bay disrupting shielding gas |
The fishbone does not tell you which cause is correct — it tells you which causes are worth verifying. After building it, the team prioritizes and tests the most likely contributors, often handing the strongest candidate to a 5 Whys for deeper drilling. For how fishbone compares against other methods head-to-head, see the RCA method comparison.
Try AI-Powered Root Cause Analysis
Building these templates by hand works, but the slow part is generating candidate causes and not missing a category. WhyTrace Plus runs guided 5 Whys and fishbone workflows where the AI suggests likely causes from your incident description, flags shallow "operator error" conclusions, and proposes verified corrective actions — so your template fills itself out with prompts instead of a blank page.
The Fault Tree Analysis Template: For Complex, Multi-Cause Failures
Fault tree analysis (FTA) is a top-down, deductive method that starts with an undesired top event and maps every combination of contributing causes using logic gates. It is the right tool when a failure results from multiple causes acting together rather than a single chain.
Use FTA for high-consequence or complex events: process safety incidents, equipment failures with redundant systems, or any case where you need to understand which combinations of conditions could produce the outcome. It is the most rigorous of the five formats and the most demanding to build.
Template structure — the core logic gates:
- Top event: The failure being analyzed (placed at the top).
- OR gate: The event below occurs if any input occurs. Single points of failure.
- AND gate: The event below occurs only if all inputs occur simultaneously. Defense-in-depth.
- Basic events: The lowest-level causes that need no further breakdown (drawn as circles).
Filled example — pressure vessel overpressure (top event):
[ Vessel overpressure ]
|
(OR gate)
┌───────────┴───────────┐
[ Relief valve fails ] [ Inlet flow uncontrolled ]
| |
(AND gate) (OR gate)
┌──────┴──────┐ ┌────────┴────────┐
[Valve stuck] [No bypass] [Control valve [Operator
stuck open] override]
The AND gate under "relief valve fails" tells you something useful: overpressure from that branch requires both the valve stuck and no bypass — a designed redundancy. The OR gate under inlet flow shows two independent single points of failure. FTA's value is exactly this: it shows you where your defenses are layered and where one failure is enough.
Because FTA can be quantified (assigning probabilities to basic events), it is also used to prioritize which causes to address first. It is overkill for a simple slip-and-fall and essential for a process safety review.
From complex tree to closed-loop action. WhyTrace Plus captures structured investigations and links every identified cause directly to a tracked corrective action with a named owner and verification step — so the rigor of your fault tree does not evaporate once the report is filed. See how it works →
The Barrier Analysis Template: For Incidents Where a Defense Failed
Barrier analysis (also called barrier and control analysis) examines an incident by mapping the barriers that should have prevented the hazard from reaching the target, and identifying which ones failed, were missing, or were bypassed. It frames the incident around defenses rather than causes.
Use it whenever an incident involves a hazard reaching a person or asset that controls should have protected — which describes most safety incidents. It pairs naturally with the hierarchy of controls and is excellent for showing why existing protections did not work.
Template structure:
| Element | Entry |
|---|---|
| Hazard | (The energy or condition that caused harm) |
| Target | (The person or asset harmed) |
| Intended barriers | (Controls that should have prevented contact) |
| Barrier status | For each: present / failed / missing / bypassed |
| Failure reason | (Why each failed barrier did not perform) |
| Corrective action | (Restore, add, or strengthen barriers) |
Filled example — hand laceration on a guarded machine:
| Barrier | Status | Why |
|---|---|---|
| Fixed machine guard | Bypassed | Removed for a jam clear, not replaced |
| Lockout/tagout procedure | Not applied | Operator judged the jam "quick" |
| Interlock on access door | Failed | Defeated by a taped-down switch |
| PPE (cut-resistant gloves) | Present but inadequate | Rated for Cut Level A2; task needed A6 |
| Supervisor spot check | Missing | No coverage on that shift |
The barrier view makes a critical point visible: this was not a single failure. Four defenses were down at once. That pattern — a hazard reaching a target only because several barriers eroded together — is exactly what barrier analysis exposes and what a single 5 Whys would miss.
The Change Analysis Template: For "It Worked Until Something Changed"
Change analysis investigates an incident by comparing the situation as it was during the failure against a baseline when the same task or system performed without incident, then isolating what changed. It is built for problems that appeared after a modification.
Use it when something previously stable started failing: after a procedure update, a new supplier, a shift in staffing, a software release, or an equipment swap. The discipline of change analysis is that it forces you to find the difference, which is often where the cause hides. The RCA framework comparison covers how change analysis fits alongside the other structured methods.
Template structure:
| Factor | Baseline (no incident) | Incident situation | Difference | Relevant? |
|---|---|---|---|---|
| Personnel | ||||
| Equipment | ||||
| Procedure | ||||
| Materials | ||||
| Timing/schedule | ||||
| Environment |
Filled example — sudden rise in packaging seal failures:
| Factor | Baseline | Incident | Difference | Relevant? |
|---|---|---|---|---|
| Personnel | Trained line crew | Same crew | None | No |
| Equipment | Sealer at 180°C | Sealer at 180°C | None | No |
| Procedure | Same SOP | Same SOP | None | No |
| Materials | Film supplier A | Film supplier B (new lot) | New supplier | Yes |
| Timing | Day shift | Day shift | None | No |
| Environment | 45% RH | 45% RH | None | No |
The single relevant difference — a new film supplier — points the investigation straight at material specification verification, a cause that a generic 5 Whys might have buried under "the sealer settings." Change analysis is fast and underused, and it shines precisely when a stable process suddenly degrades.
How to Choose the Right Template
The choice is driven by the shape of the problem, not by preference. Use this decision guide:
| If the incident… | Use this template |
|---|---|
| Has one clear, traceable cause chain | 5 Whys |
| Could have many possible causes you need to brainstorm | Fishbone |
| Involves multiple causes combining (high consequence) | Fault Tree Analysis |
| Happened because protective controls failed | Barrier Analysis |
| Started after something changed | Change Analysis |
These are not mutually exclusive. Strong investigations often combine them: a fishbone to surface candidate causes, change analysis to confirm what differed, then a 5 Whys on the confirmed cause to reach the management-system root. The point of having five templates is not to pick one and stop — it is to stop forcing every incident through whichever format you happen to be comfortable with.
Frequently Asked Questions
Q. Which root cause analysis template is the easiest to start with?
The 5 Whys template is the most accessible. It requires no diagramming software, takes minutes for a simple incident, and the only discipline it demands is refusing to stop at "operator error." Start there for single-cause incidents, and graduate to fishbone or fault tree analysis as your investigations involve more interacting factors.
Q. Can I use more than one RCA template for the same incident?
Yes, and for significant incidents you usually should. A common sequence is a fishbone to brainstorm candidate causes, change analysis to confirm what actually differed, then a 5 Whys to drill the confirmed cause down to its systemic root. Each template answers a different question, so combining them produces a more complete picture than any single format.
Q. Does OSHA require a specific root cause analysis format?
No. As of 2026, OSHA's incident investigation guidance encourages employers to conduct root cause analysis and to go beyond the minimum investigation, but it does not mandate a particular template. OSHA's FactSheet (OSHA 3895) describes the goal — finding management-system causes rather than blaming individuals — and leaves the choice of structured tool to the investigator.
Q. How many "whys" do I actually need in a 5 Whys analysis?
Five is a guideline, not a rule. You stop when you reach a cause that the organization can act on through its management system — sometimes that is three "whys," sometimes seven. If your final answer is still an individual's behavior rather than a process, system, or design gap, you have not gone deep enough.
Key Takeaways
- A root cause analysis template standardizes investigation questions and forces the analysis past symptoms to management-system causes — but no single template fits every incident type.
- Match the format to the problem: 5 Whys for linear single causes, fishbone for brainstorming many causes, fault tree analysis for complex multi-cause failures, barrier analysis for failed defenses, and change analysis for problems that appeared after a change.
- A correct RCA ends at a process, system, or design gap — not at "operator error." OSHA 3895 frames root causes as organizational and management-system failings.
- Strong investigations combine templates: brainstorm with fishbone, isolate with change analysis, then drill with 5 Whys.
- The right template choice is driven by the shape of the incident, not by which method the investigator prefers.
Related Resources
| Resource | Description | Best For |
|---|---|---|
| 5 Whys Analysis: Complete Guide | Full walkthrough of the 5 Whys method with safety and manufacturing examples | Mastering the most common RCA template |
| RCA Method Comparison | Side-by-side comparison of 5 Whys, fishbone, fault tree, and barrier methods | Choosing between the five formats for a specific incident |
| RCA Framework Comparison | How structured RCA frameworks fit together across investigation types | Building a consistent multi-method investigation process |
For teams working across both safety and quality improvement, the analysis methods above pair well with structured cause-analysis tooling from GenbaCompass の現場改善・なぜなぜ分析ガイド（GenbaCompass）, and for capturing the tacit knowledge behind recurring failures, see 技術継承・ナレッジ管理を支援する know-howAI（know-howAI）.
Ready to stop starting from a blank template? WhyTrace Plus runs guided 5 Whys, fishbone, and structured investigations with AI-suggested causes and corrective actions, then tracks every action to verified closure. Start free — your next incident report can be a finished analysis today.
Sources: