You're three months into Controlled Shipping Level 2. Third-party inspection is set up at your dock, the customer's dock, and a holding area in between. Direct monthly containment burn is substantial, indirect exposure is worse. Your customer Quality Engineer has stopped returning calls. And the program your account team has been quietly chasing for the past year just went to a competitor.
CS2 is not just an inspection program. It is the most operationally intense 90 days a Tier 1 supplier can have, and the shadow reaches deep into the next 12 months. This article covers what CS2 looks like from the inside, how long it actually lasts, the 30/60/90-day exit playbook, and the common mistakes that turn 90 days into 9 months.
CS1 vs CS2: What Actually Changes
Both CS1 and CS2 are customer-imposed containment programs that require 100% inspection of shipped parts. The difference is who pays for the inspection and how visible the supplier failure becomes.
Controlled Shipping Level 1 (CS1)
- Inspection: 100% by the supplier, internally
- Verification: Documented results sent to customer
- Cost: Internal labor + sort area + documentation
- Visibility: Limited - typically known to plant quality team only
- Scorecard impact: Moderate, often informal
- Typical duration: 30-90 days
Controlled Shipping Level 2 (CS2)
- Inspection: 100% by an independent third party, at supplier expense
- Verification: Third-party reports go directly to customer SQE
- Cost: Third-party inspector hourly rate, often with markup, plus sort area, plus supplier oversight labor
- Visibility: High - every Tier 1 in the supplier park hears about it
- Scorecard impact: Severe and formal
- Typical duration: 60-180 days
What CS2 Actually Looks Like from the Inside
Most CFOs underestimate CS2 exposure by a wide margin. They focus on the third-party inspection invoice and miss everything else. Here is the realistic exposure structure for a Tier 1 supplier shipping a moderate-volume program in CS2:
Direct exposure categories (monthly)
- Third-party inspection labor across every shipping shift, scaled to volume and inspection criteria complexity
- Third-party project management overhead layered on top of inspection labor
- Internal containment oversight requiring at least one full-time quality engineer
- Sort area lease or facility use for the containment footprint
- Documentation and reporting labor generating daily and weekly outputs
- Premium freight for rush replacements when defects are caught downstream
- Defective material impact covering scrap, rework, and replacement components
Direct monthly containment burn compounds fast. For high-volume programs or technically complex parts, the operational load exceeds what most internal quality organizations were sized to carry.
Indirect exposure (often the killer)
- Lost program opportunities: CS2 suppliers are systematically excluded from new program sourcing for 12-24 months after exit
- PPAP holds: Customer may suspend new PPAP approvals across all programs until CS2 closes
- Internal team burnout: Quality team works the customer issue instead of structural improvement work
- Customer relationship damage: Plant personnel develop a permanent skepticism that takes years to repair
- Insurance and bonding implications: Some customers require additional financial guarantees post-CS2
How Long CS2 Actually Lasts
Customer documentation will say "until exit criteria are met." That's true and useless. Here are the realistic durations by industry and OEM:
Typical duration by OEM
- GM (PRR-driven CS2): 60-120 days minimum, often extended to 150+ days
- Ford (Q1 status loss + CS2): 90-180 days, with strict exit gates
- Stellantis: 60-90 days nominal, often 120+ days in practice
- Toyota / Honda: 90-180 days, with rigorous re-qualification requirements
- Tier 1 to Tier 2 CS2: 30-90 days, more flexible exit criteria
Why CS2 extends
CS2 doesn't end because time passes. It ends because the supplier demonstrates two things consistently: zero defect escapes for the agreed window, and a sustainable system change that eliminates the root cause. Suppliers that extend their own CS2 typically make one of these mistakes:
- Treating CS2 as an inspection event rather than a system-level change
- Pulling internal resources off CS2 too early ("the inspectors are catching everything, we're fine")
- Failing to deliver a credible 8D that addresses systemic causes, not just symptoms
- Underestimating customer skepticism - customers want to see proof, not promises
- Letting communication slip into monthly updates instead of weekly visibility
The 30/60/90 Day CS2 Exit Playbook
This is the sequence that consistently produces 90-day exits. Each phase has a specific objective. Compressing phases produces extensions, not faster exits.
Days 1-30: Stabilize and Demonstrate Control
- Third-party inspection process locked in with documented criteria
- Internal containment team in place with one named owner
- Weekly customer status meeting on the calendar
- Initial 8D draft submitted by Day 14, addressing the immediate cause
- Daily defect rate trending visible to customer (containment data + escapes)
Days 30-60: Prove System Change
- Final 8D approved with systemic root cause identified
- Permanent corrective action implemented in production
- First two PPAP-equivalent verification runs documented
- Customer site visit scheduled to validate corrective action in production
- Defect escapes trending toward zero in third-party data
Days 60-90: Build Exit Case
- Three consecutive shipping weeks with zero customer-confirmed defects
- Formal exit request submitted with full documentation package
- Customer SQE site visit completed and signed off
- Read-across analysis completed for related programs and parts
- Post-CS2 monitoring plan agreed (typically 30-60 days of heightened reporting)
When to Call for Outside Help
Most suppliers try to run CS2 internally. About a third succeed at exiting in under 120 days. The rest extend. Outside help makes sense in three specific scenarios:
- Distance: Your quality team is more than 4 hours from the customer plant where containment is happening. Daily presence is impossible internally.
- Bandwidth: Your team is already running another CS1 or CS2 event. Splitting attention extends both.
- Credibility: The customer has lost confidence in your reporting. A neutral third-party representative restores trust faster than your own team can.
IDS provides on-site CS2 containment management, customer-facing communication, third-party inspector coordination, and weekly status reporting for Tier 1 suppliers at GM Spring Hill, Ford Kentucky Truck, Stellantis Detroit, and other major North American OEM facilities.