A root cause analysis (RCA) is the structured way of answering one question after something goes wrong: not “how do we fix this?” but “why did this happen — and what stops it from happening again?” Fixing the symptom is taking aspirin; RCA finds the infection. The free templates below are editable MS Word documents built around the standard RCA report format, and beneath them you’ll find the two techniques nearly every analysis uses — the 5 Whys and the fishbone diagram — each explained with a worked example.

The 5 Whys: The Simplest RCA Technique

The 5 Whys works exactly as it sounds: state the problem, then ask “why?” repeatedly — about five times, in practice — until you hit a cause that, if fixed, prevents the whole chain. Here’s the classic example from manufacturing:

Notice what the chain buys you: stopping at the first “why” replaces a fuse — and the machine stops again next month. Reaching the fifth “why” prevents every future recurrence for the price of one filter. Three practical rules: follow the chain through facts you can verify (not guesses), stop when the answer is something you can act on, and be suspicious if your chain ends at “human error” — people-blaming answers usually have another “why” hiding underneath (why was the error possible? why wasn’t it caught?).

The Fishbone Diagram: For Tangled, Multi-Cause Problems

The 5 Whys suits problems with one linear chain of causes. When a problem has many potential contributing causes — a quality defect, a recurring delay, a customer-satisfaction drop — teams use a fishbone diagram (also called an Ishikawa or cause-and-effect diagram). The problem statement sits at the fish’s head; the diagonal “bones” are cause categories, and the team brainstorms specific causes onto each bone. The classic six categories:

• People — training, staffing, fatigue, communication
• Methods — procedures, instructions, process design
• Machines — equipment, tools, maintenance, software
• Materials — inputs, parts, suppliers, quality of stock
• Measurement — how things are checked, gauges, data accuracy
• Environment — workspace conditions, temperature, timing, external factors

The categories exist to force breadth: without them, teams pile every idea onto whichever cause was mentioned first. Once the bones are populated, the team picks the few most likely causes and verifies each against evidence — often running a 5 Whys down the strongest candidate. The two techniques aren’t rivals; the fishbone finds the right chain to pull, and the 5 Whys pulls it.

The RCA Report: What Goes in the Template

The templates below follow the standard report structure that turns the analysis into a document your organization can act on and audit later:

1. Problem statement — what happened, when, where, and the impact (downtime, cost, affected customers). Specific and factual; no causes yet.
2. Evidence and timeline — the sequence of events with times, plus the data, photos, or logs collected.
3. Analysis — the causes considered and the method used (5 Whys chain, fishbone categories), including causes examined and ruled out.
4. Root cause(s) — the verified cause, stated plainly. Some problems genuinely have two or three contributing root causes; list each.
5. Corrective actions — what will be done to eliminate each root cause, with an owner and a deadline per action.
6. Verification — how and when you’ll confirm the fix worked: the metric to watch, the review date, and who checks. This section is what separates organizations that do RCA from organizations that file RCA reports.

Free Root Cause Analysis Templates in MS Word

Every template below is editable in Word. Pick one matching the depth you need — a one-page 5 Whys form for quick incidents, a full report format for significant failures — and keep the verification section, even when you’re tempted to skip it.

 

5 Whys Root Cause Analysis Template

A one-page form: problem statement, five “why” lines, root cause, and corrective action with owner and date — for quick incident analysis.

 

Full Root Cause Analysis Report Template

The complete six-section report format — problem statement, timeline, analysis, root causes, corrective actions, and verification — for significant failures and audit trails.

 

Click on this download button for acquiring this Root Cause Analysis Template.

 

Click on this download button for acquiring this Root Cause Analysis Template.

 

Click on this download button for acquiring this Root Cause Analysis Template.

 

Click on this download button for acquiring this Root Cause Analysis Template.

 

Click on this download button for acquiring this Root Cause Analysis Template.

 

Corrective vs. Preventive Action

Quality systems (and ISO audits) distinguish the two: a corrective action eliminates the root cause of a problem that already happened — the filter installed after the machine failure. A preventive action eliminates a potential cause before any failure occurs — installing the same filter on the three identical machines that haven’t failed yet. A good RCA report ends with both questions: what fixes this instance, and where else does this root cause exist? Root cause analysis looks backward at what went wrong; its forward-looking twin is a risk analysis, which hunts the same causes before they strike — and if the fix requires closing a measured performance shortfall, a gap analysis structures that plan.

Frequently Asked Questions

What are the 5 Whys?

A root cause technique: state the problem and ask “why?” repeatedly — typically about five times — until you reach a cause that, once fixed, prevents recurrence. The worked example above shows a complete chain from “machine stopped” to “missing intake filter.”

What is a fishbone diagram?

A cause-and-effect diagram (also called an Ishikawa diagram) used when a problem has many possible causes: the problem sits at the head, and causes are brainstormed onto category “bones” — classically People, Methods, Machines, Materials, Measurement, and Environment — then the strongest candidates are verified against evidence.

What are the steps of a root cause analysis?

Define the problem factually; gather evidence and build a timeline; analyze causes using a technique like the 5 Whys or a fishbone diagram; verify the root cause against the evidence; implement corrective actions with owners and deadlines; and verify later that the fix actually prevented recurrence.

What is the difference between a root cause and a symptom?

A symptom is the visible effect (the blown fuse); the root cause is the underlying condition producing it (the missing filter). Fixing symptoms restores operation temporarily; fixing root causes prevents the problem from returning. If the same issue keeps recurring, you’ve been treating symptoms.

What is the difference between corrective and preventive action?

Corrective action eliminates the root cause of a problem that has already occurred. Preventive action eliminates a potential cause before any failure — typically by applying the lesson from one incident everywhere else the same condition exists.