3 Things Nobody Tells Your Team Before PPAP Submission

Many quality teams treat PPAP submission as the paperwork that follows a successful FAI.

Get the part to print, run the first article, document it, submit.

Logical sequence. Wrong mental model.

FAI does confirm your part. However, PPAP is evaluated as a package by different reviewers against different criteria, with failure modes that differ from those for dimensional inspection.

You can submit a dimensionally perfect part and still get rejected three times, even if every measurement is correct.

Here are the three places we typically see this happening.

Drawing Revision Lock Is a Package Problem, Not a Document Problem

This one costs teams weeks, and they never see it coming. When a revision change occurs during or after FAI — an engineering change order, a tolerance update, or a customer markup — the dimensional report might reference Rev C, while the PFMEA and control plan still show Rev B.

Every document in the package has to reference the same drawing revision. If they don’t, the customer’s receiving quality team rejects it for internal inconsistency before they’ve looked at a single measurement.

The part can be perfect. Doesn’t matter. A submission that contradicts itself is a disqualifying condition at most Tier 1 customers — not a condition for same-cycle revision and resubmission.

The fix is a revision audit before you assemble the submission package, not after the rejection lands. Pull every document that references the part drawing — dimensional report, PFMEA, control plan, inspection records — and verify the revision level is consistent across all of them.

If a change occurred midstream, the dimensional work may need to be rerun against the current rev. That’s painful. It’s less painful than a rejected PSW three weeks before a launch gate.

One pattern we see regularly is that teams will lock in the control plan early in the development cycle and never update the rev block when the drawing changes.

Your dimensional report has been updated because it’s generated from inspection data; however, the two most scrutinized documents in the package now describe different versions of the same part. That’s a rejection just waiting to happen.

Nobody Checks PSW Signatory Authority Until the Warrant Gets Rejected

The Part Submission Warrant has a signature line. Most teams know this. What most teams don’t check — until they’re already drafting the PSW — is who the customer specified as the required signatory in their Customer Specific Requirements.

A quality engineer signs. The customer’s CSR says program manager or above. Rejected.

Not for a technical or process reason, but because the wrong title was signed on the warrant.

Now you’re back-channeling internally to escalate the signature, restarting the customer’s intake clock, and explaining to program management why the submission failed on a line in a document nobody read.

CSRs are customer-specific documents. AIAG provides the PPAP framework, but every OEM and most Tier 1s layer their own requirements on top of it.

Signatory authority level, required submission elements, specific approval timeline expectations: these live in the CSR, not the PPAP manual. Building to the standard while ignoring the CSR is building to the wrong spec.

Pull the CSR at the start of submission prep. Confirm the signatory requirement. Get the right person aligned and aware before the PSW exists — not after it’s been kicked back.

By that point, you’re already behind the launch schedule, the fix requires coordination across multiple teams, and the root cause could have been caught in a 30-minute pre-submission audit.

A Significant Production Run Is an Eligibility Gate, Not a Production Milestone

This is the failure that doesn’t look like a failure on the floor.

PPAP requires that submission samples come from a Significant Production Run — a minimum of 300 consecutive parts, produced over one to eight hours on production tooling by production operators using production materials at the quoted production rate. Customer-specific counts can vary. The structure doesn’t. The run has to look like the run that will fulfill orders.

Tooling tryout samples don’t qualify. Pilot runs don’t qualify. Parts pulled from a longer engineering run don’t qualify. The parts can be dimensionally perfect, made on the right tool, and visually indistinguishable from production. They still don’t satisfy the requirement because it’s about conditions, not parts.

Schedule the Significant Production Run as its own gated event, not a milestone you back into after everything else is ready. Operators on the clock. Materials drawn from production inventory. Cycle times match the quote. Documented start and stop.

If the customer requires a witnessed Run @ Rate on top of it — and most major Tier 1s do — they may want to attend in person or via remote audit. That’s a separate lead time problem stacked on top of the run itself.

All three are discovered the same way — after the rejection. Revision inconsistencies surface when the customer’s document control team reads the package. Signatory issues surface during intake review. Significant Production Run gaps surface when the reviewer cross-checks your capability data against the run documentation, and the dates don’t agree.

The submission is the product. Build it that way.

Most PPAP failures are discovered after the package leaves your building. By then, the launch clock is already burning. H&H Molds works upstream of submission day — where revision control, process alignment, and approval timing are all still recoverable. Contact us anytime for assistance with your PPAP Submission. We love to get involved early to help you avoid pain later.