The customer opened another 8D this morning. Same part family, same failure mode, the 3rd time since launch. Their supplier quality engineer wants to know why the fix did not hold. Your plant manager wants to know if there will be a 4th.
This guide is for the VP or Director of Quality who owns that answer. It covers the 3 root causes every 8D needs, lessons that never reach the FMEA, unverified fixes, missing read-across, and a 12-month review of your 8Ds.
The short version
- A repeat means the last 8D fixed 1 of 3 root causes, or fixed it in 1 place.
- Every 8D needs 3 answers: why it occurred, why it escaped, and why the system allowed it.
- Close a corrective action when production data shows it holds, not when it is installed.
- A lesson is learned when it changes the FMEA, the control plan and the master FMEA.
- Review 12 months of 8Ds by failure mode and cause. The repeats show where the system leaks.
Why the Same Failure Comes Back
The earlier 8D stopped short. It fixed a cause on 1 line and closed, and the system that let the failure through stayed as it was. Look for 5 patterns:
- Only the occurrence cause was fixed. Nobody asked why the part escaped or why the system allowed it.
- The lesson stayed in the 8D. The FMEAs kept their old causes and ratings.
- The fix was implemented, not verified. It closed the day it went in.
- The fix stayed where it was found. Other lines, parts and plants with the same cause never heard about it.
- The fix wore off. A new operator, a tool change or a line move undid it.
IATF 16949 clause 10.2.3 covers each pattern. It asks for systemic corrective actions that consider similar processes and products, verification of their effectiveness, and updates to documents such as the PFMEA and control plan. The SMMT Industry Forum guidance on IATF corrective actions quotes the clause in full.
Did the 8D Find All 3 Root Causes?
Check every 8D for 3 separate root causes. An 8D with 1 root cause leaves 2 doors open.
The SMMT guidance asks for 3 types of root cause. The 3-legged 5 Why runs a chain for each.
- Occurrence: why the problem occurred, at the process step where it happened.
- Escape: why the part reached the customer. Ford’s Global 8D calls it the escape point, where the effect should have been detected and contained, but was not.
- Systemic: why the system or the planning process allowed it. A cause the PFMEA never listed, a rating that called it unlikely, or a change that skipped review.
Each leg gets its own corrective action: the process, the detection control, and the FMEA or the change process.
Quality Magazine’s guide to the 3-legged 5 Why walks through each leg. A chain that stops at “operator error” has not reached a root cause.
Lessons Learned That Never Reach the FMEA
A lesson is learned when the next engineer meets it without looking for it. That place is the FMEA row, not a slide or a lessons-learned folder.
- Where it starts. Ford’s Global 8D asks for technical lessons learned in D7 and D8. Where they land decides whether anyone uses them.
- Write it as FMEA content. The cause, the prevention and detection controls that now work, and the ratings that follow.
- Put it where the next program starts. The part’s PFMEA, the master or foundation FMEA, and the DFMEA if the design allowed the failure.
The test: open the FMEA for the next similar part. If the cause and the control from the last 8D are not there, the lesson was not learned.
Was the Fix Verified, or Only Implemented?
Implemented means it is on the line. Verified means production data shows the failure stopped and stays stopped.
- Ford’s Global 8D separates the 2. D5 verifies that the corrective action will work without undesirable effects. D6 implements it, validates that it is effective and monitors the long-term results.
- Define the proof before the action goes in. Which data, over what period, and which result counts as success.
- Use production data. Not the parts the team watched during the change.
- Check again after the next event that could undo it. A tool change, a new shift, a line move or a supplier change.
- Close on the verification date. Not on the implementation date.
The Read-Across That Never Happened
The fix reached the line with the complaint. The other lines, parts and plants with the same cause did not, and 1 of them produced the next 8D. IATF 16949 and Ford’s D7 both ask for it.
- Make it a list on the 8D. Each similar part, line and plant, with an owner, date and status.
- Allow 3 statuses. Changed, not applicable with a reason, or open with a date.
- Close the 8D when the list is closed. Not before.
For where to look, see step 3 of how to link 8Ds back to the PFMEA.
Review the Last 12 Months of 8Ds
Put 12 months of 8Ds in 1 table, grouped by failure mode and cause. Then score every repeat on 5 checks.
- Export. Every customer and internal 8D. A row each: part, process, plant, failure mode, the 3 root causes, actions, verification, FMEA row and read-across.
- Group. By failure mode and cause, across parts, lines and plants. Every group with 2 or more 8Ds is a repeat.
- Score each repeat on 5 checks. All 3 root causes found. Fix verified on production data. PFMEA, control plan and DFMEA changed. Read-across closed. Fix still in place after later changes.
- Mark the 1st failed check. That is why the group came back.
- Count failed checks across all groups. The biggest count is your systemic problem, and the 1st to fix.
Write the result on 1 page: the repeat groups, why each came back, the systemic fix, an owner and a date.
Same failure, another 8D?
Get the 12-month 8D review sheet: find the repeats, the read-across nobody did and the fixes nobody verified.
We email you the PDF. No newsletter. Privacy policy
What to Tell the Customer
Do not send the 3rd 8D in the same format as the last 2. Show what is different this time, in 5 lines:
- Why the earlier fixes did not hold: the root cause they missed.
- The systemic action: what changed in the FMEA, control plan or change process.
- The verification: which data, over what period, and the result to date.
- The read-across: the other parts, lines and plants checked and changed.
- The owner, and the date of the next review.
If the customer has already escalated, see how to exit controlled shipping.
How Tacit AI Approaches This
Tacit AI imports your 8Ds, complaints, NCRs and warranty claims and links each record to the FMEA row it belongs to. Regression detection flags a control that failed again, and FRACAS (failure reporting and corrective action) is built in. Your engineers approve a fix once and it reaches the master and every derived FMEA. Nothing is written to your record without approval. It works on top of the FMEA tool you already run.
At a Top 10 Global Pharma, data quality rose 170% across 20,000 failure reports. A Top 20 Global OEM builds FMEAs 8× faster with it, with 26% fewer actions after customer review.
If 1 failure keeps coming back, book a working session and bring its 8Ds and the PFMEA rows they touched. Related: how to link 8Ds back to the PFMEA and root cause analysis methods compared.
Same failure, another 8D?
Get the 12-month 8D review sheet: find the repeats, the read-across nobody did and the fixes nobody verified.
We email you the PDF. No newsletter. Privacy policy
Frequently Asked Questions
Why do corrective actions fail to prevent recurrence?
Look for 5 gaps: only the occurrence cause fixed, no FMEA update, no verification on production data, no read-across, or a later change that undid the fix. Each shows up in a review of the repeat 8Ds.
What is the 3-legged 5 Why?
It runs 3 separate 5 Why chains on 1 problem: why it occurred, why it was not detected, and why the system allowed it. Each leg ends in its own corrective action.
What does IATF 16949 require for recurring problems?
Clause 10.2.3 requires root cause analysis, systemic corrective actions that consider similar processes and products, verified effectiveness, and PFMEA and control plan updates where needed.
How long should you monitor a corrective action before closing an 8D?
There is no universal period. Ford’s Global 8D asks teams to validate the actions and monitor the long-term results. Agree the data and the period with your customer before closing.