Free Root Cause Analysis Template
Created by the 8Dflow team.
Use this Word RCA template to define the problem, record containment and evidence, document the occurrence cause supported by evidence, separate the escape weakness, and assign actions with verification and effectiveness before closure.
Free download · No signup · Editable Word document
On this page
- In summary
- What's inside the Word RCA template
- When a full RCA record is the right choice
- When a simpler action record may be enough
- How the RCA fits with NCRs, corrective action plans, SCARs, and 8D reports
- How to complete the template
- Completed RCA example
- Strong vs weak RCA entries
- Common mistakes to catch before RCA closure
- How 5 Whys and fishbone support the RCA
- When a Word RCA becomes hard to manage
- Templates and guides for RCA work
What is a root cause analysis template?
A root cause analysis template is a structured investigation record for defining the problem, recording containment and evidence, evaluating possible causes, separating the occurrence cause from the escape weakness, assigning corrective action, and documenting verification, effectiveness, and closure. This downloadable Word root cause analysis report template is designed for manufacturing quality investigations.
It is designed for customer complaints, nonconformance reports (NCRs), returned product, supplier issues, inspection escapes, repeat defects, scrap, rework, and corrective action investigations.
It is not just a brainstorming sheet. Fishbone diagrams and 5 Whys can help the team explore possible causes, but this template records the full investigation path from problem definition through closure.
For investigation method, evidence selection, and stop rules, read the Root Cause Analysis Guide.
A template does not prove root cause. It gives the team a structure for recording evidence, ruling out weak theories, and documenting the supported conclusion.
What's inside the Word RCA template
The downloadable RCA template is organized into practical sections that follow the investigation from issue definition through closure.
| Template section | What to enter |
|---|---|
| RCA summary and completion guidance | Records ownership, related records, status, and the completion order. |
| Problem definition | Captures the issue ID, customer, supplier, site, process, part, lot, batch, serial number, source, requirement not met, actual condition, affected quantity, suspect quantity, where found, and where made. |
| Containment / immediate action | Records what was checked, what was contained, clean point, owner, date, and evidence. |
| Evidence and facts log | Keeps photos, records, test results, customer information, supplier records, and other evidence linked to the investigation. |
| Cause analysis summary | Records supporting tools, possible causes, causes ruled out, and remaining uncertainty. |
| Occurrence root cause | Records the supported reason the issue happened, with evidence references. |
| Escape point / detection failure | Records why the issue was not caught before reaching the next process or customer. |
| Correction, corrective action, and preventive action | Separates correction for affected product, corrective action linked to the supported cause, and any broader prevention action. |
| Verification and effectiveness check | Records whether actions were completed and whether they worked over time. |
| Customer or internal response summary | Helps prepare a factual response using the evidence already recorded. |
| Approval and closure | Records final review, sign-off, closure notes, and any remaining follow-up. |
| Completed example and common mistakes | Provides a worked manufacturing example and a practical review checklist. |
Preview the RCA cause-analysis, response, and closure pages
These screenshots come from the downloadable Word file. Open a preview to check the field layout; use the HTML table above and the completion steps below for the instructions.
When a full RCA record is the right choice
Use this root cause analysis worksheet when the issue needs evidence-backed investigation. The template is most useful when several people need to agree on the facts, causes, actions, and evidence before closure.
- A customer complaint or return.
- A repeat internal defect.
- A nonconformance report (NCR) that needs cause analysis.
- A supplier quality issue or supplier corrective action request (SCAR) response.
- A corrective action investigation.
- A failed final inspection or test.
- Scrap or rework above normal limits.
- An inspection escape.
- An audit finding that needs corrective action.
When a simpler action record may be enough
Use a defect log, correction note, or action record when the requirement and actual condition are clear, the affected product is controlled, and the available evidence does not indicate a repeat or systemic process failure.
- The affected product is identified, contained, and dispositioned.
- The cause is directly observed and supported by the available record; no extended cause analysis is needed.
- There is no repeat history, customer escape, or wider suspect population.
- The risk assessment does not require formal corrective action.
- No customer, supplier, or QMS requirement calls for an RCA, SCAR, or 8D response.
Use a full RCA when the issue needs a defensible investigation trail
Use the RCA template when the cause is uncertain, the issue repeats, a control failed to detect it, several functions or a supplier must respond, or the action needs verification and an effectiveness result before closure.
Do not choose the record by defect size alone; use risk, repeat history, escape, and response requirements.
How the RCA fits with NCRs, corrective action plans, SCARs, and 8D reports
Use the RCA template to document the investigation. Use a nonconformance report (NCR) to control nonconforming product and disposition, a corrective action plan to track process changes, a supplier corrective action request (SCAR) when the supplier must respond, and an 8D report when the customer requires the D1–D8 format.
Use a nonconformance report (NCR) to record the requirement not met, actual condition, affected or suspect product, containment, correction, and disposition.
Open the Non-Conformance Report TemplateCorrective action planUse a corrective action plan after the cause path is supported and the process changes need owners, due dates, evidence, verification, an effectiveness review, and a closure decision.
Open the Corrective Action Plan TemplateSCARUse a supplier corrective action request (SCAR) when the supplier must respond with containment, an evidence-supported occurrence cause, an escape weakness where relevant, corrective action, evidence, and a closure response.
Open the Supplier Corrective Action Request Template8D reportUse an 8D report when the customer requires D1–D8, a cross-functional team is needed, or the response must formally cover containment, an evidence-supported occurrence cause, escape weakness, corrective action, verification, effectiveness, and closure.
Open the 8D Report TemplateHow to complete the Root Cause Analysis Template
Work through the template in order. Each step keeps the record factual and connects the supported cause to the right action.
- 1
Step 1 — Define the problem without assuming the cause
Start with the facts. Record what happened, where it was found, the part or product involved, the requirement not met, the actual condition, the affected quantity, and the suspect quantity.
Problem statement example
Receiving inspection found 27 BRK-2214 brackets from Northline Coatings shipment NC-2026-0712 with exposed base metal on the outside radius. Requirement: coating must be continuous with no exposed base metal and meet CS-17 Rev A.
- 2
Step 2 — Record containment and correction in separate fields
Containment controls suspect product and immediate risk. Correction deals with the affected brackets after disposition. Record both before moving to cause analysis.
Containment and correction example entries Field Example entry Containment Hold all 240 brackets from the shipment and sort them for exposed base metal. Correction Return the 27 affected brackets to Northline Coatings or rework them according to the approved disposition before release. For containment, record the location, quantity checked, quantity held, clean point, owner, date, evidence reference, and open risk. For correction, record the approved disposition applied to the affected product.
- 3
Step 3 — Start the evidence log early
Use evidence IDs from the start. For example:
- EVD-118-01 — Receiving photos.
- EVD-118-02 — Receiving inspection sheet.
- EVD-118-03 — Coating thickness readings.
- EVD-118-04 — Packaging/rack photos.
- EVD-118-05 — Supplier response.
- EVD-118-06 — SCAR closure evidence. This evidence is added after the 2026-08-30 effectiveness decision.
Evidence IDs make the RCA easier to review because the team can connect each claim to a record, photo, inspection result, or system setting.
- 4
Step 4 — List possible causes before confirming root cause
At this point, record possible cause paths, not root causes.
Possible RCA cause paths and evidence to review Path Possible cause to test Evidence to review Occurrence Temporary rack-spacer contact during shipment. EVD-118-01 receiving photos; EVD-118-04 packaging/rack photos; EVD-118-05 supplier response. Occurrence Coating thickness below CS-17 Rev A before packing. EVD-118-03 coating thickness readings; EVD-118-04 packaging/rack photos. Escape Final packing check omitted inspection under spacer contact points. EVD-118-04 packaging/rack photos; EVD-118-05 supplier response. Keep every tested path in the RCA with its status and evidence; do not silently delete a contradicted path.
- 5
Step 5 — Confirm the occurrence root cause with evidence
Confirm the occurrence cause only after the evidence has been reviewed. Record the cause in process terms and cite the supporting evidence.
Occurrence cause example
Northline Coatings used a temporary rack spacer that was not covered by PKG-NC-14 Rev A, allowing BRK-2214 brackets to rub during shipment.
- 6
Step 6 — Record the escape or detection weakness
For a supplier or downstream issue, record why the issue was not detected before the next process or shipment. Keep this separate from the occurrence cause.
Escape weakness example
The supplier final packing check did not include inspection under the temporary spacer contact points.
- 7
Step 7 — Assign corrective action to the supported cause
Corrective action examples with owners and due dates Cause addressed Corrective action Owner Due Occurrence cause Northline Coatings revised PKG-NC-14 to Rev B. Grace Patel 2026-07-26 Escape weakness Northline Coatings added rack-spacer contact inspection to the supplier final packing check. Grace Patel 2026-07-26 Use the preventive-action field only when the same control gap could affect another part, process, product family, or supplier. Do not repeat the corrective action in this field.
Do not use "tell the supplier to be careful" as the corrective action.
- 8
Step 8 — Verify completion
Verification checks whether the agreed process and inspection changes were completed and the required evidence was received.
On 2026-08-02, Grace Patel reviewed PKG-NC-14 Rev B, EVD-118-05 supplier response, packaging photos, and first-shipment inspection evidence.
- 9
Step 9 — Check effectiveness
Effectiveness checks whether exposed-base-metal damage recurred during the defined review window. Define the review window, acceptance criterion, evidence source, reviewer, and review date before closure.
At the 2026-08-30 review, Grace Patel reviewed BRK-2214 shipments received during the defined review window for exposed base metal on the outside radius. No repeat exposed base metal was found. The result was recorded in EVD-118-06 before closure.
- 10
Step 10 — Prepare the response and close the RCA
Build the customer or internal response from the approved investigation record, not raw triage notes. Include the problem, containment, correction, occurrence cause, escape weakness, corrective action, verification, effectiveness result, and evidence references.
- Containment is complete.
- Correction and disposition are complete.
- The evidence-supported occurrence cause is recorded.
- The escape weakness is recorded where the issue reached a downstream process or customer.
- Corrective action is complete and verification evidence is recorded.
- Effectiveness has been checked and the result is recorded.
- Required sign-off is complete.
Do not close the RCA only because the customer response has been sent.
Completed RCA example: damaged coating on supplier brackets
This completed example shows the field-level detail a reviewer should expect before closure: requirement, actual condition, containment, correction, evidence, occurrence cause, escape weakness, corrective action, verification, effectiveness, and closure.
Example records are fictional demonstration data.
Problem, containment, and correction
- Related NCR
- NCR-2026-118
- Linked supplier request
- SCAR-2026-044
- Supplier
- Northline Coatings
- Product / part
- BRK-2214 coated bracket
- Supplier shipment / PO
- Supplier shipment NC-2026-0712; PO-45872 line 30
- Where found
- Receiving inspection
- Requirement not met
- Coating must be continuous with no exposed base metal and meet drawing DRW-BRK-2214 Rev B and coating specification CS-17 Rev A.
- Actual condition
- 27 brackets from shipment NC-2026-0712 had exposed base metal on the outside radius.
- Affected quantity
- 27 damaged brackets found at receiving inspection.
- Suspect quantity
- 240 suspect brackets from shipment NC-2026-0712.
- Containment
- Hold all 240 brackets from the shipment and sort them for exposed base metal.
- Correction
- Return the 27 affected brackets to Northline Coatings or rework them according to the approved disposition before release.
Evidence and cause analysis
Evidence checked
- EVD-118-01 — Receiving photos.
- EVD-118-02 — Receiving inspection sheet.
- EVD-118-03 — Coating thickness readings.
- EVD-118-04 — Packaging/rack photos.
- EVD-118-05 — Supplier response.
- EVD-118-06 — SCAR closure evidence. This evidence is added after the 2026-08-30 effectiveness decision.
Possible cause paths considered
| Path | Possible cause tested | Status | Evidence reviewed |
|---|---|---|---|
| Occurrence | Temporary rack-spacer contact during shipment. | Supported occurrence cause. | EVD-118-01, EVD-118-04, and EVD-118-05. |
| Occurrence | Coating thickness below CS-17 Rev A before packing. | Not retained as the supported occurrence cause after evidence review. | EVD-118-03 and EVD-118-04. |
| Escape | Final packing check omitted inspection under spacer contact points. | Supported escape weakness. | EVD-118-04 and EVD-118-05. |
Occurrence cause supported by evidence
Northline Coatings used a temporary rack spacer that was not covered by PKG-NC-14 Rev A, allowing BRK-2214 brackets to rub during shipment.
Escape / detection weakness
The supplier final packing check did not include inspection under the temporary spacer contact points.
Corrective action, verification, effectiveness, and closure
Corrective action
| Cause addressed | Action | Owner | Due |
|---|---|---|---|
| Occurrence cause | Northline Coatings revised PKG-NC-14 to Rev B. | Grace Patel | 2026-07-26 |
| Escape weakness | Northline Coatings added rack-spacer contact inspection to the supplier final packing check. | Grace Patel | 2026-07-26 |
Verification
On 2026-08-02, Grace Patel reviewed PKG-NC-14 Rev B, EVD-118-05 supplier response, packaging photos, and first-shipment inspection evidence.
Effectiveness
At the 2026-08-30 review, Grace Patel reviewed BRK-2214 shipments received during the defined review window for exposed base metal on the outside radius. No repeat exposed base metal was found. The result was recorded in EVD-118-06 before closure.
Closure note
The RCA closed only after the 2026-08-30 effectiveness result was recorded in EVD-118-06 and linked to SCAR-2026-044.
Strong vs weak RCA entries
Use this comparison to keep each template field factual and evidence-backed. The strong entry states the process condition and the evidence needed to support it.
| Template field | Weak entry | Strong entry |
|---|---|---|
| Problem statement | Supplier sent bad brackets. | Receiving inspection found 27 BRK-2214 brackets from Northline Coatings shipment NC-2026-0712 with exposed base metal on the outside radius. Requirement: coating must be continuous with no exposed base metal and meet CS-17 Rev A. |
| Possible occurrence cause | Supplier mistake. | Temporary rack-spacer contact during shipment; check EVD-118-01, EVD-118-04, and EVD-118-05 before confirming the cause. |
| Possible escape weakness | Supplier check missed it. | The final packing check may omit inspection under spacer contact points; check EVD-118-04 and EVD-118-05 before confirming the escape weakness. |
| Evidence | Everyone says this is what happened. | EVD-118-01 receiving photos; EVD-118-02 receiving inspection sheet; EVD-118-03 coating thickness readings; EVD-118-04 packaging/rack photos; EVD-118-05 supplier response. |
| Occurrence root cause | Supplier made bad parts. | Northline Coatings used a temporary rack spacer that was not covered by PKG-NC-14 Rev A, allowing BRK-2214 brackets to rub during shipment. |
| Escape / detection weakness | Supplier check missed it. | The supplier final packing check did not include inspection under the temporary spacer contact points. |
| Corrective action | Tell supplier to be careful. | Northline Coatings revised PKG-NC-14 to Rev B and added rack-spacer contact inspection to the supplier final packing check. |
| Verification | Action complete. | On 2026-08-02, Grace Patel reviewed PKG-NC-14 Rev B, EVD-118-05 supplier response, packaging photos, and first-shipment inspection evidence. |
| Effectiveness check | Monitor going forward. | At the 2026-08-30 review, Grace Patel reviewed BRK-2214 shipments received during the defined review window for exposed base metal on the outside radius. No repeat exposed base metal was found. |
Common mistakes to catch before RCA closure
Use this checklist to avoid weak RCA records before closure.
| Mistake | Better practice |
|---|---|
| Starting with the assumed cause | Do not begin with “the supplier made bad parts” or “the operator made an error.” Start with the problem. Confirm or rule out causes using evidence. |
| Treating possible causes as confirmed root causes | A possible cause is only a theory until evidence supports it. Use the RCA template to show which causes were considered, which were contradicted, and which cause is supported. |
| Skipping containment | Containment protects the customer and next process while the investigation is open. Do not wait for root cause confirmation before checking suspect product, quarantining stock, or stopping the next shipment when risk is present. |
| Mixing containment and corrective action | Containment controls the immediate risk. Corrective action addresses the supported cause. If the action only checks or sorts product, it is usually containment or correction, not corrective action. |
| Stopping at operator error | “Operator error” is not a root-cause conclusion. Identify the process condition that allowed the error and the control that failed to detect it. |
| Ignoring escape or detection failure | For a downstream issue, record both why the issue happened and why it was not detected before the next process or customer. |
| Choosing actions that do not match the cause | If the cause is a temporary rack spacer that was not covered by the packing method, asking the supplier to be careful is weak. The action should address the system condition that allowed the issue to happen or escape. |
| Closing before effectiveness is checked | Verification records completion evidence. Effectiveness records whether exposed-base-metal damage recurred during the defined review window. Do not close on completion evidence alone. |
| Omitting causes that were ruled out | Keep ruled-out causes in the record. It shows what was checked and prevents the same theory being debated again later. |
| Writing the RCA only for the customer response | Build the customer or internal response from the approved investigation record. Do not close the RCA unless the process change, verification evidence, effectiveness result, and closure decision are recorded. |
How 5 Whys and fishbone support the RCA
Use 5 Whys or a fishbone diagram to develop possible cause paths. Keep the conclusion in the RCA only after evidence supports or rules out those paths.
| Method | Use it for | What belongs in the RCA | Guide |
|---|---|---|---|
| 5 Whys | Explore one possible cause chain. | Record each answer and the evidence checked; do not treat the final why as proof. | Read the 5 Whys Guide |
| Fishbone diagram | Map possible causes across categories. | Record which branches were tested, the evidence reviewed, and the supported conclusion. | Read the Fishbone Diagram Guide |
When a Word RCA becomes hard to manage
A Word template works well for a single investigation. It becomes harder to control when several RCAs are open, evidence sits in separate folders, owners miss due dates, or reviewers cannot see what changed. 8Dflow is being built to keep the RCA record, actions, evidence, review notes, and closure decision together.
Download the free Root Cause Analysis Template
Use this RCA template to document the problem, containment, evidence, evidence-supported occurrence cause, escape or detection weakness, corrective action, verification, effectiveness result, and closure.
Need to manage RCA follow-up across owners, due dates, evidence, and closure? 8Dflow is being built to help manufacturing quality teams keep 8D reports, NCRs, corrective actions, and evidence connected in one place.