Excel worksheet
Free 5 Whys Template
Created by the 8Dflow team.
Use this Excel worksheet to define a manufacturing quality problem, follow one occurrence cause path, document a separate escape/detection path when needed, and link evidence-supported causes to corrective action.
Free download · No signup · Editable Excel workbook
On this page
- What the worksheet records
- Preview the Excel workbook
- When to use the worksheet
- When a simpler record fits
- Choose the surrounding quality record
- Start with the problem facts
- Build the occurrence chain
- Why the issue was not caught
- Support each why with evidence
- Confirm the cause
- Completed leaking-housing example
- Strong vs weak entries
- Common mistakes
- When the Excel workbook becomes hard to control
- Related guides
What the 5 Whys worksheet records
Use this 5 Whys worksheet to investigate a defined manufacturing defect or escape recorded in a nonconformance report (NCR), customer complaint, corrective action request (CAR), supplier corrective action request (SCAR), or 8D. The worksheet follows one occurrence cause path and adds a separate escape/detection path when needed.
The workbook includes a Problem Definition / 5W2H sheet, 5 Whys Worksheet, Evidence Log, Corrective Action sheet, and a completed leaking-housing example.
Use it to document the analysis; the quality manager, engineer, or process owner still decides whether the evidence supports the cause and whether the action was effective.
From problem statement to confirmed cause: what the free 5 Whys template includes
These screenshots are taken from the downloadable Excel workbook. Use them to check the problem-definition format, the 5 Whys structure, Evidence Log fields, and action tracking before downloading. Click any preview to enlarge it without leaving the page.
When to use the 5 Whys Excel template
Use the worksheet when the problem is defined and the team needs to check one plausible cause path against records, observations, or test results before assigning corrective action.
- A customer complaint or returned part when the defect mechanism is not yet supported by evidence.
- A repeat internal defect where the same process condition may be recurring.
- An NCR that requires cause analysis beyond disposition of the affected product.
- A supplier issue where one cause path can be checked against supplier records or process evidence.
- A CAR investigation where the problem is defined but the occurrence cause or escape weakness is still uncertain.
- D4 analysis for a single, traceable 8D problem after containment and problem definition are in place.
When a separate 5 Whys investigation is unnecessary
Use the NCR or local correction record without a separate 5 Whys when the cause is already known and supported, the issue is isolated, the affected product can be dispositioned, and no repeat pattern or escape points to a process-control failure.
| Use the simpler record when | Use 5 Whys when |
|---|---|
| The cause is already known and evidenced. | The occurrence cause or escape weakness is still uncertain. |
| The issue is isolated and the affected product can be dispositioned. | The defect repeats or reached a customer or downstream process. |
| No systemic corrective action is required. | A process or detection control may need corrective action. |
Choose the record that controls disposition, response, and closure
The 5 Whys worksheet documents one cause path. Use the surrounding quality record to control the work that the worksheet does not: nonconformance and disposition, formal customer response, action ownership, review dates, and closure.
| Record | Use it when | What the 5 Whys contributes | Link |
|---|---|---|---|
| 8D report | Customer requires D1–D8, a cross-functional team is needed, or the response must formally cover containment, confirmed cause, corrective action, verification, and customer closure. | D4 cause analysis. | Open the 8D Report Template |
| Non-conformance report | The main job is to record a nonconforming product, lot, batch, process, or requirement before a disposition decision is made. | Cause analysis once the nonconformance is recorded. | Open the Non-Conformance Report Template |
| Corrective action plan | The issue needs formal corrective action ownership, due dates, verification, and management follow-up beyond a single worksheet. | Cause and escape analysis to inform the action plan. | Open the Corrective Action Plan Template |
| Root cause analysis record | The investigation spans several methods and evidence streams and needs one record from problem definition through closure. | One supported cause path as input to the broader analysis. | Open the Root Cause Analysis Template |
| Fishbone diagram | Several possible cause paths need to be mapped before selecting one candidate for 5 Whys and evidence review. | Evidence review and confirmation of one selected cause path. | Open the Fishbone Diagram Template |
Step 1
Start with the problem facts, not the assumed cause
Complete the D2-style problem definition before asking why. Describe the defect in factual, measurable terms — what happened, where it was found, the part and lot, the requirement not met, the actual condition, and the quantity affected.
Do not write the root cause you already assumed and then work backwards. The Problem Definition sheet also includes an optional Is / Is Not analysis for when the defect is unclear or hard to isolate.
Problem statement example
Apex Industrial returned 12 HSG-88 housings from HSG88-LOT-0726A that leaked at the seal interface during incoming test. Requirement source: DRW-HSG-88 Rev D. Requirement: the housing must seal at the mating face without leakage during the pressure hold test.
Problem Definition / 5W2H sheet. Complete this D2-style definition before the why chain begins. Step 2
Build one occurrence cause path and check each answer against evidence
Why 1 often records the failure condition. Continue only while each answer remains consistent with the evidence. Use Why 6 or Why 7 when the supported cause is still unclear; do not force the chain to stop at five.
Stop rule
Do not stop because you reached Why 5. Stop when the cause is evidence-supported, specific, and linked to a process control or escalation path. If the evidence points to a cause outside your control, record the boundary and escalate it; do not back up to a more convenient cause.
Step 3
Ask why the issue was not caught before the next process or customer
Use the optional escape / detection chain when the defect reached a customer or downstream process, or passed the inspection or test that should have detected it. Keep it separate from the occurrence chain so the corrective actions address both why the defect happened and why it was not caught.
Occurrence chain
Answers why the defect happened. In the worked example, a mis-seated seal reached the pressure test because WI-ASSY-221 Rev C did not require a seal-orientation confirmation.
Escape / detection chain
Answers why it was not caught. Final testing relied on the pressure test only and did not include a seal-face visual check before packing.
Two different controls may be required
Correct the process condition that created the defect, then close the detection gap that allowed it to pass. Do not use one action to cover both unless the evidence shows that the same control addresses both mechanisms.
Step 4
Support each why with evidence, not just logic
Record evidence IDs, observations, records, photos, inspection results, interviews, or document links in the Evidence Log. Mark each entry supported, contradicted, or still needs checking, and reference its ID on the matching why.
Include the functions needed to review the process and evidence. Do not let one person complete the chain from opinion alone.
Logic only
Everyone agrees the seal was mis-seated, so that must be it.
Evidence-backed
EVD-120-03 seal inspection photos show the seal was not seated at the sealing face; EVD-120-04 WI-ASSY-221 Rev C gap review shows the work instruction did not require a seal-orientation confirmation.
Evidence Log. Each why in the chain references an evidence ID here, so the conclusion is traceable. Corrective Action sheet. The confirmed cause links to actions with owners, verification, and effectiveness checks. Step 5
Confirm the cause only when the evidence supports it
Record the confirmed occurrence cause and, where relevant, the confirmed escape / detection weakness. Do not close on opinion alone — list the evidence IDs that support the decision, then carry each cause into the Corrective Action sheet.
Containment controls immediate risk. Correction deals with affected product. Corrective action changes the process or control that allowed the defect or escape. Verification confirms that the action was implemented as planned. Effectiveness checks whether the defect or escape recurred over the defined review window. If the action is not effective, reopen the investigation or revise the action.
Closed on evidence
EVD-120-03 supports the failure condition. EVD-120-04 supports the occurrence cause. EVD-120-05 supports the escape weakness. Link the process changes to ACT-3012; use EVD-120-06 as action-completion evidence.
Worked manufacturing example
Leaking housing: completed 5 Whys example
This is the worked manufacturing example included in the workbook. It shows the level of detail expected — an evidence-backed chain that separates occurrence from escape and links to corrective action.
Example records are fictional demonstration data.
Problem summary
- NCR / 8D ID
- NCR-2026-120 / 8D-2026-042
- Customer
- Apex Industrial
- Part / product
- HSG-88 housing assembly
- Lot / batch
- HSG88-LOT-0726A
- Process / area
- Cleaning, seal assembly, and pressure test
- Requirement source
- DRW-HSG-88 Rev D
- Affected / suspect quantity
- 12 returned / 48 suspect
- Owner
- Tom Alvarez
- Linked records
- ACT-3012 (seal process) / CAR-2026-031
- Problem statement
- Apex Industrial returned HSG-88 housings from HSG88-LOT-0726A that leaked at the seal interface during incoming test. Requirement: housing must seal at the mating face without leakage during the pressure hold test.
Occurrence why chain — why did the defect happen?
| Step | Why question and answer | Evidence status |
|---|---|---|
| Why 1 | Why did the returned housings leak at the seal interface?The seal was not seated at the housing sealing face after cleaning and assembly. | Supported by evidence (EVD-120-03)Occurrence — symptom, keep asking |
| Why 2 | Why could a damaged or mis-seated seal be installed before the pressure test?WI-ASSY-221 Rev C did not require a seal-orientation confirmation after the cleaning step, so a damaged or mis-seated seal could be installed before the pressure test. | Supported by evidence (EVD-120-04)System weakness — confirmed |
Rejected assumption
“The operator installed the seal incorrectly.” EVD-120-04 did not confirm an operator departure; it showed that WI-ASSY-221 Rev C omitted the seal-orientation confirmation step.
Escape / detection why chain — why was it not caught?
| Step | Why question and answer | Evidence status |
|---|---|---|
| Escape Why 1 | Why did leaking housings reach the customer?The team relied on the final pressure test alone, with no seal-face visual check before packing. | Supported by evidence (EVD-120-05)Escape condition — keep asking |
| Escape Why 2 | Why was there no seal-face visual check before packing?IP-HSG-88 Rev B required final pressure testing but did not require a seal-face visual check before packing. | Supported by evidence (EVD-120-05)Escape / detection — confirmed |
Confirmed occurrence root cause
WI-ASSY-221 Rev C did not require a seal-orientation confirmation after the cleaning step, so a damaged or mis-seated seal could be installed before the pressure test.
Confirmed escape / detection weakness
IP-HSG-88 Rev B required final pressure testing but did not require a seal-face visual check before packing.
System weakness (prevention)
WI-ASSY-221 Rev C and IP-HSG-88 Rev B did not require a seal-orientation confirmation or a seal-face visual check, so a mis-seated seal could reach the customer.
Problem evidence
EVD-120-01 customer return photos; EVD-120-02 leak test record; EVD-120-03 seal inspection photos.
Occurrence-cause evidence
EVD-120-04 WI-ASSY-221 Rev C gap review.
Escape evidence
EVD-120-05 IP-HSG-88 Rev B review.
Action-completion evidence
EVD-120-06 retraining record.
ACT-3012 actions and review checks
| Field | Linked record | Entry | Owner | Due / review date |
|---|---|---|---|---|
| Containment | NCR-2026-120 | Hold suspect HSG-88 stock and related WIP in the red-tag hold area; perform 100% seal-face visual check and leak test before release. | Tom Alvarez | 2026-07-03 |
| Corrective action | ACT-3012 | Update WI-ASSY-221 to Rev D and TC-SEAL-04 to Rev B; add seal-orientation confirmation and seal-face visual check; train assembly and test operators. | Tom Alvarez | 2026-07-17 |
| Verification | ACT-3012 | Verify first three batches after release. | Tom Alvarez | 2026-07-24 |
| Effectiveness target | ACT-3012 | No repeat leaks in 90 shipped units during the defined review window. | Tom Alvarez | 2026-08-21 |
| Closure criterion | ACT-3012 | Evidence reviewed before closure. | Tom Alvarez | 2026-08-21 |
A useful why answer names the process condition and evidence
Use this comparison to keep each why factual and evidence-backed. The stronger entry explains the process condition and references a record, not just a plausible story.
| Template field | Weak entry | Strong entry |
|---|---|---|
| Why 1 answer | The housings leaked. | The seal was not seated at the housing sealing face (EVD-120-03). This is a symptom, so the chain continues. |
| Operator step | The operator installed the seal incorrectly. | WI-ASSY-221 Rev C did not require a seal-orientation confirmation after the cleaning step (EVD-120-04), so a damaged or mis-seated seal could pass to the pressure test. |
| System link | Someone should have checked it. | IP-HSG-88 Rev B did not require a seal-face visual check before packing (EVD-120-05). |
| Supported cause | Why 5 is the root cause because we reached Why 5. | WI-ASSY-221 Rev C did not require seal-orientation confirmation after cleaning, and EVD-120-04 showed that step was absent from the work instruction. |
| Escape / detection | Final inspection missed it. | IP-HSG-88 Rev B required final pressure testing only and did not include a seal-face visual check before packing (EVD-120-05). |
| Evidence status | Everyone agrees this is what happened. | Each why is marked supported, contradicted, or needs checking, with a record ID in the Evidence Log. |
Mistakes that turn 5 Whys into guesswork
Use this checklist to keep the worksheet evidence-based before you confirm the cause.
| Mistake | Better practice |
|---|---|
| Writing the assumed root cause first and working backwards | Start with the problem facts in the Problem Definition sheet. Build the why chain forward from what you can show, not back from the answer you already decided on. |
| Stopping at operator error | Do not stop at the operator unless you also explain the process weakness that allowed the error. In the worked example, a mis-seated seal could pass because WI-ASSY-221 Rev C did not require a seal-orientation confirmation. |
| Confusing containment with corrective action | Holding and sorting suspect product are containment. Reworking affected product is correction. Corrective action changes the process or control that allowed the defect or escape. |
| Calling the fifth why the root cause automatically | Five is a guide, not a rule. Stop only when the cause is evidence-supported, specific, and linked to a process control or escalation path. If the evidence points outside your control, record the boundary and escalate it. |
| Ignoring the escape / detection weakness | When the issue reached the customer or the next process, ask why it was not caught. The escape chain explains the detection gap separately from why the defect happened. |
| Building the chain on logic alone | Each why should reference the Evidence Log. Mark every step supported, contradicted, or needs checking so the chain is traceable, not just plausible. |
When the Excel workbook becomes hard to control
The workbook works for one investigation when one owner keeps the problem statement, why chain, evidence, actions, and review dates together. It becomes harder to manage when several NCRs, CARs, or 8Ds are open, owners update separate copies, evidence sits in email or shared folders, and verification or effectiveness reviews are missed.
Ready to manage quality work beyond templates?
8Dflow is being built to keep the issue, why chain, evidence, action owner, due date, review, and closure decision together. The quality manager or engineer still decides whether the evidence supports the cause and whether the action was effective.
Download the free 5 Whys Excel template
Define the problem, build evidence-backed 5 Whys answers, separate occurrence from escape, and link the confirmed cause to corrective action — all in one Excel workbook.