You exit CS2 by proving the defect is fixed with irreversible corrective action and a defined run of clean days, typically on the order of 20 to 30 consecutive clean days with zero escapes, as set by the customer. The exact number is defined by the OEM for your situation. What is universal is that clean days only count once permanent corrective action is in place, and a single escape resets the clock.
What the clean-day count really measures
The clean-day period is not a waiting sentence; it is a stability test. It asks whether your fix holds across shifts, operators, and lots without another escape. Because of that, clean days start at the clean point, the moment certified stock made under the corrective action begins, not at the day CS2 was imposed. Days of sorting before the fix do not count.
What resets the clock
Any escape of the same or a related defect during the clean-day period usually resets the count to zero and can extend the containment. That is why read-across matters: if the same failure mode can occur on a similar part, address it before it resets your exit. Gaps in the daily data, or inspection that drifts from the agreed criteria, can also invalidate days and push the exit out.
Building the exit package
The exit is a decision the customer makes from evidence. Give them a clean package: the corrective action and its verification, the defined clean point, daily inspected and rejected counts, the defect-PPM trend at zero across the required days, and confirmation that the redundant independent inspection stayed in place. Independent, complete data is what turns the clock into a release.