Friday, 4:47 PM. The email subject line reads: "PSW Status: Not Approved — Resubmission Required." Your customer SQE has signed off on the rejection. Launch is in six weeks. Your operations team is already building inventory for ramp. Tooling is committed. And the next 48 hours will decide whether you launch on time or watch the program slip — sometimes permanently.
PPAP rejection at signoff is one of the highest-stakes events in automotive supply. The technical fix is rarely the hard part. The hard part is the credibility recovery — getting the customer to agree the next submission is worth their time to review, and then defending the program timeline through a process designed to slow you down.
Why PPAPs Actually Get Rejected
Customer SQEs do not reject PPAPs lightly. Rejection means more work for them too. When a PPAP comes back "Not Approved," one of five specific failure modes is almost always responsible:
Failure mode 1: Incomplete documentation
The most common rejection reason. A required element of the PPAP package is missing, incomplete, or fails to match the part being submitted. Common gaps: missing MSA data, incomplete control plan, design records that don't match the production drawing revision, PFMEA that wasn't updated after a process change.
Failure mode 2: Dimensional results not meeting print
Critical or significant characteristics outside specification, even on a sample basis. The customer cannot approve a part that doesn't meet print, even if the deviation is small. This rejection often surfaces a process capability issue that was masked during the initial PPAP runs.
Failure mode 3: Process capability below customer threshold
Cpk or Ppk values below the customer-required minimum (typically 1.33 for significant, 1.67 for critical). This is the rejection that scares experienced quality managers — it signals a process that may produce occasional defects in long-run production, even if the PPAP samples were all good.
Failure mode 4: Material certification or labeling issues
Material certs that don't trace cleanly to the lot used for PPAP parts, label format that doesn't match customer specification, or IMDS submission with errors. Often perceived as "administrative" but the customer can't sign off on parts they can't trace.
Failure mode 5: Customer-specific requirement missed
GM, Ford, Stellantis, Toyota, and Honda each have specific PPAP requirements above the AIAG baseline. Missing a customer-specific requirement (e.g., GM's GP-12 early production containment plan, Ford's Q1 elements, Stellantis's customer-specific PFMEA template) is a common rejection trigger especially for suppliers new to a customer.
The 48-Hour Recovery Sequence
The window matters. Customers expect a response within 48 hours of rejection. The supplier that responds in 48 hours with a clear plan looks competent. The supplier that responds in five days looks disorganized. Here is the sequence that works:
Hours 0-4: Decode the Rejection
Read the rejection notice with three of your most experienced quality people. Separate three categories:
- Issues you agree with and can fix
- Issues that are ambiguous or require customer clarification
- Issues you disagree with and need to push back on
Most suppliers go straight to fixing without sorting. That produces resubmissions that don't actually address customer concerns — leading to second rejections, which are far harder to recover from.
Hours 4-12: Internal Stakeholder Sync
Get the program manager, plant manager, quality manager, manufacturing engineer, and operations director in one room. Confirm:
- Production schedule impact if PPAP doesn't approve in time
- Tooling, fixtures, and inventory commitments
- Customer-side timeline pressure
- Resubmission target date
- Resources required to hit it
Hours 12-24: Acknowledge to Customer
Send a written acknowledgment to the customer SQE within 24 hours of rejection. This is not the resubmission. This is the document that proves you have a plan. Include:
- Confirmation you received and reviewed the rejection
- Your understanding of each rejection point (in your words, not theirs)
- Initial root cause hypothesis for technical rejections
- Resubmission target date
- Specific questions where you need clarification before resubmitting
Hours 24-48: Build the Resubmission Plan
Don't resubmit in 48 hours. Build the plan to resubmit. Most successful PPAP resubmissions land 10-21 days after rejection — long enough to actually fix the underlying issues, short enough to keep program credibility. The 48-hour milestone is when you have a credible plan, not a fixed PPAP.
What to Fix vs. What to Push Back On
Not every rejection point is fixable on the supplier side. Sometimes the customer has misunderstood, or the rejected element is actually compliant with a more recent specification. Pushing back is legitimate — but it requires care.
Fix without argument
- Missing documentation elements
- Format/labeling that doesn't match customer specification
- MSA or capability data that's obviously below threshold
- Material cert traceability gaps
Clarify before responding
- Ambiguous rejection reasons ("PFMEA insufficient" without specifics)
- Customer-specific requirements that aren't in published spec
- Rejections that reference older drawing revisions
Push back carefully
- Technical points where you have documentation showing compliance
- Specification interpretation differences (especially around appearance items)
- Process capability calculations where customer is using a different sample size
When pushing back, never argue. Present documentation, ask a question, propose a resolution. The phrase that works: "We may be interpreting requirement X differently than you. Here is our documentation showing compliance. Can we get on a 15-minute call to align?"
Common Mistakes That Make Things Worse
- Resubmitting too fast. A resubmission inside 5 days that doesn't actually address root cause produces a second rejection — which is 3x harder to recover from.
- Arguing with the rejection. Customers don't want defensiveness. They want acknowledgment plus a plan.
- Escalating internally without telling the customer. Customer SQEs hate finding out their counterpart's boss is involved through grapevine. Tell them.
- Treating each rejection point in isolation. Often three rejection points are surfacing one underlying issue. Address the root.
- Not bringing in outside eyes. A second-rejection recovery often benefits from a quality professional who hasn't been close to the program. Fresh perspective catches what the team can't.
When to Bring in a Quality Liaison
Three scenarios where outside quality liaison support consistently helps recover a failed PPAP:
- Customer relationship is strained. A neutral third party can sit between you and the customer SQE while internal trust rebuilds.
- You're geographically distant. Same as containment — distance from the customer plant during a PPAP recovery is expensive.
- The rejection touches multiple programs. If the same defect mode threatens parts beyond the rejected PPAP, you need coordinated read-across that's hard to run internally.
IDS supports Tier 1, 2, and 3 suppliers through PPAP recovery — including customer-facing communication, on-site presence at GM Spring Hill, Ford Kentucky Truck, Stellantis Detroit, and other major OEM facilities, and coordination of the resubmission package and customer site visits.