A repeat escape means the same or a related defect reached the customer again after you thought it was contained or fixed, and OEMs treat it far more seriously than a first event. A repeat usually triggers escalation to CS2, resets any clean-day count, and puts your scorecard and quotes at risk. The response has to do two things at once: re-contain completely, and prove why the first fix did not hold.
Re-contain wider than before
A repeat means your first containment missed something: a location, a lot, a similar part, or a shift. Re-scope the suspect population wider than last time and re-verify every location, including any stock you previously certified. Treat previously certified inventory as suspect until you can show the corrective action actually covered it. Under-scoping again is the fastest way to a third escape.
Find out why the fix failed
Repeats almost always trace to one of three things: the root cause was wrong, the corrective action was not truly irreversible, or read-across was never done so the defect lived on a similar part. Re-open the 8D, challenge the original root cause with the new evidence, and check whether the fix was verified or just implemented. An honest re-analysis is what the customer is watching for.
Manage the escalation
Expect CS2 and a reset clean-day clock, and get ahead of it by showing fast, complete re-containment and a credible corrective-action revision. Independent, documented inspection helps here because the customer no longer trusts internal data after a repeat. Local crews that can hold the gate around the clock, plus a rigorous read-across, are what turn a repeat from a relationship-ending event into a recoverable one.