A root cause analysis template is a structured worksheet that guides an investigation from symptom to verified cause — a problem statement, evidence and timeline, candidate causes, a why-chain that drills to the systemic root, and a corrective action plan with owners and deadlines. Below you will find a free, method-agnostic RCA report template in Excel, Word, and PDF, plus guidance on when to use it versus a method-specific worksheet. No signup, no email.
Download free templates
All files use the same seven-section report layout: problem statement (5W+1H), evidence & timeline, candidate causes, 5 Whys chain, verified root cause, corrective action plan, and verification & follow-up. No signup, no email, direct download.
RCA Report Template — Excel
Editable .xlsx with all seven sections and a labelled Why 1–5 chain. Works in Excel, Google Sheets, and LibreOffice.
Download .xlsxRCA Report Template — PDF
Printable A4 worksheet for workshops and incident reviews. Fill by hand during the session, digitise the result after.
Download .pdfRCA Report Template — Word
Editable .docx for Microsoft Word or Google Docs — best when the RCA becomes part of a longer incident or quality report.
Download .docxGuided 5 Whys — Online
Run the why-chain interactively and export the result as an image. No account, nothing leaves your browser.
Open the toolRCA form, RCA report, RCA template — which one do you need?
Three words, one set of seven sections, three different states of the same document. The distinction is not vocabulary; it decides which file you should download.
- Template — the blank file before anyone touches it. That is what this page hands you.
- Form — the same file in the hands of whoever runs the investigation. A form has to be fillable: labelled fields, room to write, no prose expected. The Excel version and the printable PDF are the form.
- Report — the finished document somebody else reads: a manager, an auditor, a customer. A report has to be readable in order — conclusion near the top, evidence behind it, a name and a date at the bottom. The Word version is the report.
The common mistake is sending the filled-in form as the report. Someone who was not in the room does not want to reconstruct your reasoning from a grid — they want the verified cause, what changed because of it, and how you will know it worked. Practical sequence: fill the spreadsheet while the investigation is live, then move the last three sections into the Word file for the person who has to sign it.
Two neighbouring documents are not this one, and picking the wrong one costs a rewrite: a CAPA form is the regulated record of correction, corrective and preventive action, with an effectiveness check — use it when a quality system demands the record. An 8D report is the customer-facing format an automotive or aerospace complaint will be answered in.
Which file for which moment
| The moment | File | Why that one |
|---|---|---|
| Investigation still running, several people adding facts over days | Excel (.xlsx) | Rows can be added, sorted and filtered; the why-chain fields stay labelled while the evidence grows |
| Incident review with the team around a table | PDF (print) | One sheet, no laptop between people, filled as the discussion happens |
| Read-out to management, a customer or an auditor | Word (.docx) | Reads as a document, drops into a longer report, and carries a sign-off line |
What's inside the template
- Problem statement. What happened, where, when, how many — a measurable gap vs target, described as a symptom, not a suspected cause. (Weak problem statements doom the whole analysis; see how to write one that works.)
- Evidence & timeline. Key facts and data, the sequence of events, and what changed just before the problem appeared.
- Candidate causes. The brainstormed field of suspects — fishbone categories (Machine, Method, Material, People, Measurement, Environment) help ensure breadth.
- Why-chain (5 Whys). Labelled Why 1–5 fields that drill the most likely branch from symptom to systemic cause.
- Verified root cause. The systemic cause plus the evidence that confirms it — a root cause you have not verified with data is still a hypothesis.
- Corrective action plan. Actions with owner, due date, and status — targeting the process, not the person.
- Verification & follow-up. How you will confirm the fix worked, with a review date 2-4 weeks after implementation.
A filled-in example, section by section
The sections above are easier to judge when you can see them answered. The case below is an illustration written for this page — not a customer case study — but the numbers behave the way real ones do, and the failure it exposes is the one this template exists to catch.
| Section | Filled in |
|---|---|
| 1. Problem statement | Between 4 and 18 August, 23 of 1 840 outbound orders (1.25%) shipped with at least one wrong item, against a target of 0.3%. All 23 were picked on the late shift in Zone C. |
| 2. Evidence & timeline | Pick-scan logs for the period. The error rate steps up on 4 August and stays up. Zone C was re-slotted on 2 August. Two agency pickers started on 3 August. Zones A and B are unchanged at 0.2%. |
| 3. Candidate causes | Re-slotting placed similar SKUs side by side · the two new pickers are under-trained · the scanner beeps on a mismatch but does not block the pick · label printing runs late on the shift. |
| 4. Why-chain | Wrong items shipped → they were picked from the neighbouring bin → two look-alike SKUs now sit next to each other → re-slotting optimised walking distance only → the slotting rule has no constraint on visual or code similarity → nobody owns slotting quality; it is scored on travel time. |
| 5. Verified root cause | The slotting rule optimises travel time with no similarity constraint. Verification: all 23 errors map to six SKU pairs that share an eight-character prefix and sit in adjacent bins. The two new pickers made 4 of the 23 — roughly their share of the picks, so training is not the driver. |
| 6. Corrective actions | Separate the six pairs now (warehouse lead, 22 Aug) · add a similarity constraint to the slotting rule (systems, 5 Sep) · make the scanner hard-block a mismatched SKU instead of beeping (IT, 12 Sep). |
| 7. Verification & follow-up | Thirty days of pick-scan data after the last action. Acceptance criterion written in advance: error rate below 0.3% with no single zone above 0.5%. Review 20 September. |
Section 5 is the one that does the work. Anyone can write “new pickers, insufficient training” and close the file — it is plausible, it names a cause, and it would have survived a review meeting. Counting how the 23 errors actually distribute takes twenty minutes and kills the theory: the new pickers made their proportional share. A root cause you have not counted is still a hypothesis, and the corrective action built on it trains people who were not the problem.
Generic RCA template vs method-specific: which to grab?
This page's template is method-agnostic — one document covering the whole investigation, ideal for incident reports and management reviews. When the analysis itself is the focus, or a customer requires a specific format, grab the method-specific worksheet instead. If you do not yet know which cause to test, start wide with a cause-and-effect map and narrow from there:
| Template | Reach for it when… |
|---|---|
| RCA report (this page) | You need one end-to-end document: incident review, management summary, internal post-mortem |
| 5 Whys template | The cause is likely simple and you want the fastest structured drill |
| Fishbone (Ishikawa) template | The cause is unknown and you need to brainstorm breadth first |
| 8D report template | A customer or auditor demands formal corrective action (automotive/aerospace) |
| A3 template | You want the one-page Toyota problem-solving canvas |
| FMEA template | You are preventing failures proactively, with RPN scoring |
| Pareto chart template | You have counted data and need to find the vital few first |
How to use it well: three rules
Rule 1: write the symptom, not the theory. "Line 2 scrap rate rose from 1.2% to 4.8% between March 3-10" is a problem statement. "Operators are not following the SOP" is a theory wearing a problem statement's clothes — it pre-decides the answer before the analysis starts.
Rule 2: verify before you act. The template deliberately separates candidate causes (section 3) from verified root cause (section 5). The step between them — checking the why-chain against data — is where most analyses cut corners and most corrective actions miss. The failure modes are predictable enough to list: the seven ways a why-chain goes wrong covers stopping at human error, jumping branches, and confusing a cause with a missing safeguard.
Rule 3: no owner, no action. A corrective action without a name and a date next to it is a wish. The follow-up review (section 7) exists because "implemented" and "worked" are different claims.
Frequently asked questions
What is a root cause analysis template?
A structured worksheet that guides an investigation from symptom to verified cause: problem statement, evidence, candidate causes, a why-chain, the verified root cause, and a corrective action plan. It keeps the analysis documented, repeatable, and reviewable.
What should an RCA template include?
Seven sections: problem statement with measurable impact, evidence & timeline, candidate causes, a 5 Whys chain, the verified root cause with evidence, a corrective action plan with owners and dates, and verification 2-4 weeks after implementation.
Is there a root cause analysis form I can fill in?
Yes — the Excel file is the fillable form: seven labelled sections, a Why 1–5 chain with its own fields, and room for evidence next to each entry. The printable PDF is the same form for a review held around a table. Free, no signup, no email.
What is the difference between an RCA form and an RCA report?
The same seven sections in two states. The form is what the investigator fills in while the work is live — labelled fields, space to write: the Excel or printable PDF. The report is what somebody else reads afterwards — conclusion near the top, evidence behind it, a sign-off: the Word version. Sending the filled-in form as the report is the usual mistake, because the reader has to reconstruct your reasoning from a grid.
What does a completed root cause analysis look like?
It states the problem as a measurable gap, lays out evidence and timeline, lists the candidate causes considered, drills the most likely branch to a systemic cause, then verifies that cause against data before any corrective action is chosen. The worked example above shows all seven sections filled in, including the verification step that rules out the plausible-but-wrong explanation.
Generic RCA template or method-specific?
Generic when you need one end-to-end document (incident reports, management reviews). Method-specific (5 Whys, fishbone, 8D, A3, FMEA, Pareto) when the analysis is the focus or a customer requires that format — see the table above.
Can I use these in Google Sheets or Docs?
Yes — upload to Google Drive and open with Sheets (.xlsx) or Docs (.docx). Structure and formatting are preserved.
Are the templates free for commercial use?
Yes — personal and commercial use without restrictions: workshops, quality reports, client deliverables.
Related resources
- Root Cause Analysis: the complete guide — the 6-step process this template walks you through
- How to write a problem statement — the section-1 craft that makes or breaks the analysis
- Corrective Action Plan guide + free tracker — turning section 6 into fixes that ship
- All five RCA tools compared — picking the right method for section 4
- Free RCA tools — guided 5 Whys, Fishbone, Pareto, FMEA in the browser