Root Cause Analysis Template (Free, Copy-Paste)
A root cause analysis template is a structured document that walks a team from “what happened” to “what we’re changing” — problem statement, containment, data, a 5 Whys or fishbone analysis, a root cause statement, corrective actions, and sign-off. Below is a copy-paste version, followed by a fully worked packaging-line example.
What is a root cause analysis template used for?
An RCA template exists so that every investigation — whether it’s a scrapped batch or a customer complaint — produces the same structure of evidence. Without one, teams jump straight to “we think it’s the operator” and skip containment, data collection, and verification. The template forces those steps in order, which is also what auditors and customers expect to see in an RCA report.
The copy-paste root cause analysis template
Copy the sections below into a document or spreadsheet and fill them in as you investigate. Each section maps to a step most quality teams already follow informally — this just makes the steps explicit and traceable.
1. Problem statement
Write one or two sentences stating what happened, when, and the impact. Then complete the is/is-not table to bound the problem before you start guessing at causes.
| Is | Is Not | |
|---|---|---|
| What (defect/symptom) | ||
| Where (line, station, location on part) | ||
| When (shift, date, time first observed) | ||
| Extent (how many units, % of lot) |
2. Immediate containment actions
| Action | Owner | Date/Time Completed |
|---|---|---|
3. Data collection
List what evidence was pulled before drawing conclusions: process parameters, inspection records, batch/lot travelers, operator interviews, equipment logs, incoming material certs.
| Data Source | What It Showed |
|---|---|
4. 5 Whys analysis
| Why # | Question | Answer |
|---|---|---|
| Why 1 | Why did [problem] happen? | |
| Why 2 | Why did [answer 1] happen? | |
| Why 3 | Why did [answer 2] happen? | |
| Why 4 | Why did [answer 3] happen? | |
| Why 5 | Why did [answer 4] happen? |
5. Root cause statement
One or two sentences naming the specific, actionable root cause — not “operator error” or “machine issue,” but the underlying condition that let the failure occur.
6. Corrective actions
| Action | Type (correction/corrective/preventive) | Owner | Due Date | Status |
|---|---|---|---|---|
7. Verification of effectiveness
Describe how and when you’ll confirm the corrective action actually worked — a follow-up sample size, a re-audit date, or a control-chart review window.
| Verification Method | Review Date | Result | Verified By |
|---|---|---|---|
8. Sign-off
| Role | Name | Date |
|---|---|---|
| Quality Lead | ||
| Operations/Production Lead | ||
| (Optional) Customer/Regulatory Reviewer |
Worked example: pouch seal-strength failures
Here’s the template filled in for a plausible scenario: a food-packaging line where pouches are failing seal-strength checks during in-process quality control.
Problem statement. On July 8, second-shift QC found 14 of 200 sampled pouches (7%) failing the minimum 3.5 lb/in seal-strength pull test on Line 2, above the 2% alert threshold.
| Is | Is Not | |
|---|---|---|
| What | Seal strength below 3.5 lb/in on pull test | Seal appearance defects (wrinkles, burn-through) — those were normal |
| Where | Line 2, jaw stations 3 and 4 | Line 1 or Line 3 — both sampled normal |
| When | Second shift, July 8, starting ~10:40 PM | First shift, July 8 — no failures |
| Extent | 14 of 200 sampled (7%) | Not 100% of output — most pouches passed |
Immediate containment actions.
| Action | Owner | Date/Time Completed |
|---|---|---|
| Quarantine all Line 2 output since 10:00 PM | Shift Supervisor, R. Alvarez | 7/8, 11:15 PM |
| Increase pull-test sampling on Line 2 to 100% until root cause found | QC Lead, T. Nguyen | 7/8, 11:20 PM |
| Notify shipping to hold affected lot 2207-B | Warehouse Lead | 7/8, 11:30 PM |
Data collection.
| Data Source | What It Showed |
|---|---|
| Sealer temperature log, jaws 3-4 | Temp dropped from 285°F to 268°F starting ~10:15 PM |
| Maintenance log | PM on dwell-time cylinder completed at 9:45 PM, same shift |
| Film supplier cert, roll #4471 | Within spec; same roll used on Line 1 with no failures |
| Operator interview | Confirmed no recipe or speed change; noticed slower cycle after PM |
5 Whys analysis.
| Why # | Question | Answer |
|---|---|---|
| Why 1 | Why did seal strength drop below 3.5 lb/in? | Seal jaw temperature was running below the 275-295°F process window |
| Why 2 | Why was jaw temperature below the window? | The heater controller on jaws 3-4 was cycling below setpoint after the 9:45 PM PM |
| Why 3 | Why did the controller cycle below setpoint after PM? | The dwell-time cylinder swap disturbed the thermocouple mounting, giving a false high reading that made the controller under-fire |
| Why 4 | Why wasn’t the thermocouple reseated correctly checked after PM? | The PM checklist for that cylinder doesn’t include a post-swap temperature verification step |
| Why 5 | Why doesn’t the checklist include that step? | The checklist was written for the original cylinder design and was never updated after a 2024 equipment change added the adjacent thermocouple mount |
Root cause statement. The Line 2 jaw 3-4 PM checklist lacks a post-maintenance seal-temperature verification step, so a thermocouple disturbed during a routine cylinder swap went undetected and caused under-temperature sealing for roughly 45 minutes.
Corrective actions.
| Action | Type | Owner | Due Date | Status |
|---|---|---|---|---|
| Reseat and calibrate jaw 3-4 thermocouple | Correction | Maintenance Tech, D. Osei | 7/9 | Complete |
| Add post-PM seal-temperature check (pull-test 5 pouches before line restart) to PM checklist for all cylinder-adjacent thermocouples | Corrective | Maintenance Supervisor | 7/15 | Open |
| Audit PM checklists on Lines 1 and 3 for the same gap | Preventive | Quality Engineer | 7/22 | Open |
| Retrain maintenance techs on updated checklist | Corrective | Maintenance Supervisor | 7/18 | Open |
Verification of effectiveness.
| Verification Method | Review Date | Result | Verified By |
|---|---|---|---|
| Review seal-strength SPC data for 2 weeks post-fix | 7/29 | Pending | T. Nguyen |
| Confirm updated checklist used on next 3 PM events | 8/5 | Pending | Maintenance Supervisor |
Sign-off.
| Role | Name | Date |
|---|---|---|
| Quality Lead | T. Nguyen | 7/10 |
| Operations Lead | R. Alvarez | 7/10 |
How do 5 Whys and fishbone fit inside this template?
The template’s analysis section (step 4) can hold either method — swap in whichever matches how well-understood the causal chain is.
| Situation | Better fit |
|---|---|
| One suspected chain of cause and effect (a parameter drifted, a step was skipped) | 5 Whys, straight down one branch |
| Causes could come from several unrelated categories (people, machine, method, material, environment) | Fishbone diagram first, then 5 Whys on the strongest branch |
| Team disagrees on where to even start looking | Fishbone to structure the brainstorm before drilling down |
For a deeper walkthrough of the 5 Whys method itself, see the 5 Whys template and the fishbone diagram template. If you’re still deciding which method fits your problem at all, root cause analysis tools compares them side by side.
Filling in the 5 Whys or fishbone section by hand works, but teams often stop two or three Whys too early because nobody in the room pushes back. QualityManager.AI’s free AI-guided 5 Whys and Fishbone tools prompt the next question, flag when an answer restates the symptom instead of a cause, and export the finished analysis straight into a report.
When is this template overkill — and when do you need 8D?
This RCA template is sized for a single nonconformance with one investigation team. It’s overkill for minor, low-risk issues: a mislabeled carton caught before shipment just needs a correction note, not a full is/is-not table and sign-off chain.
Reach for an 8D report instead when the problem spans a cross-functional team, involves a customer complaint that needs a formal response, or requires a documented interim containment action separate from the permanent fix — 8D’s eight disciplines (team formation, problem description, interim containment, root cause, permanent corrective action, implementation, prevention, and team recognition) are built for that heavier, multi-stakeholder case. For a single-line defect one quality engineer can close out in a few days, this template is the right size.
Frequently asked questions
What goes in an RCA report?
A complete RCA report includes a problem statement with is/is-not scoping, immediate containment actions, data collected during investigation, the root cause analysis itself (5 Whys or fishbone), a root cause statement, corrective actions with owners and due dates, a verification-of-effectiveness plan, and sign-off from quality and operations leads.
5 Whys vs fishbone inside a template — which should I use?
Use 5 Whys when the problem has one clear causal chain, like a single machine parameter drifting. Use a fishbone diagram first when causes could span multiple categories (people, machine, method, material) and you need to brainstorm broadly before drilling down with 5 Whys on the most likely branch.
Should I use Excel or Word for an RCA report?
Word or a document format works best for the narrative sections (problem statement, root cause statement, sign-off) because they read like a report. Excel or a table-based format suits the corrective action tracker, since you'll filter and sort by owner and due date across multiple open items.
How long should an RCA take?
A straightforward RCA on a single-line defect with available data typically takes 1-3 days from containment to a signed root cause statement. Complex or cross-functional problems — multiple shifts, multiple failure modes, supplier involvement — can take 1-2 weeks, especially if new data needs to be collected.
When is a root cause analysis template overkill?
Skip the full template for one-off, low-risk nonconformances with an obvious fix, like a mislabeled box caught before shipment. A quick correction note is enough. Reserve the full RCA template for recurring defects, customer complaints, or anything that could trigger a regulatory finding.