PPAP and Control Plans Explained: IATF 16949 Supplier Documentation
Direct Answer
PPAP (Production Part Approval Process) is the AIAG-defined procedure automotive suppliers use to prove, before mass production starts, that a part and its process consistently meet the customer's engineering and quality requirements. A Control Plan is the document that describes, phase by phase, how a supplier will control the process that makes that part — the characteristics measured, the method, the frequency, and the reaction if something drifts. Under IATF 16949, a part cannot be shipped in production volume until its PPAP package — built on evidence generated by the Control Plan — has been submitted and approved by the customer.
Anyone who has managed a supplier launch file knows the feeling: eighteen folders, a submission level nobody quite agrees on, and a customer portal that rejects the package for a formatting issue two days before the ship date. PPAP and Control Plans sit at the center of that friction, because they are where design intent, process capability, and customer-specific requirements all have to line up in writing — not just in the part.
What PPAP Actually Certifies
PPAP exists to answer one question for the customer: can this supplier's process reliably produce this part to spec, run after run, not just on a good day in the lab? The AIAG PPAP manual frames it as a checkpoint before regular production shipments, triggered by a new part, an engineering change, a tooling move, a new supplier location, or a process change that could affect fit, form, or function. It is not a one-time formality — it is re-triggered whenever the process that made the "approved" part meaningfully changes.
The general AIAG framework groups PPAP evidence into eighteen elements. The exact list, the required format, and which elements a given customer actually wants to see submitted (versus simply retained on file) vary by program and by customer, so this is presented as the general structure — always confirm the specific requirement in the customer's PPAP instructions or portal before assembling a package:
- Design records — drawings or CAD data for the part, including any supplier design responsibility documents.
- Engineering change documents — authorized change notices not yet reflected in the design record.
- Customer engineering approval — where required by the customer's process.
- DFMEA — the design failure mode and effects analysis, for parts with supplier design responsibility.
- Process flow diagram — every step from receiving to shipping, in sequence.
- PFMEA — the process failure mode and effects analysis tied to each step in the flow diagram.
- Control plan — the document covered in detail below.
- Measurement System Analysis (MSA) — studies such as Gage R&R confirming the gauges and methods used are fit for purpose.
- Dimensional results — actual measurements against every dimension on the drawing.
- Material and performance test results — evidence the part meets material specs and functional/performance requirements.
- Initial process studies — capability studies (such as Cpk) on characteristics identified as special or significant.
- Qualified laboratory documentation — accreditation or qualification records for labs that performed testing.
- Appearance Approval Report (AAR) — for parts where appearance is a customer-specified requirement.
- Sample production parts — physical samples from the significant production run, retained per customer instruction.
- Master sample — a reference part kept by the supplier for comparison, where applicable.
- Checking aids — records for any dedicated gauge or fixture used to check the part.
- Customer-specific requirements records — evidence of compliance with any CSR beyond the base AIAG elements.
- Part Submission Warrant (PSW) — the summary form and formal submission, referencing the reason for submission and the results of the other seventeen elements.
Some customer programs also request evidence for bulk materials, which follow a related but distinct submission structure. Again: treat this list as the general AIAG skeleton, not a universal checklist — a given OEM's supplier quality manual is the authority on what gets submitted, what stays on file at the supplier, and in what format.
The Five PPAP Submission Levels
Not every element travels to the customer for every part. AIAG defines five submission levels that set how much of the package is physically sent versus retained at the supplier:
| Level |
What is submitted to the customer |
| Level 1 |
Only the Part Submission Warrant (PSW). |
| Level 2 |
PSW plus product samples and limited supporting data. |
| Level 3 |
PSW plus product samples and complete supporting data — the default for most production parts. |
| Level 4 |
PSW plus other requirements defined by the customer, outside the standard levels. |
| Level 5 |
PSW plus complete supporting data reviewed at the supplier's manufacturing site, not shipped out. |
The customer specifies the required level, and it can vary by part or by commodity within the same program. Regardless of level, the full eighteen-element package normally still has to exist and be retained at the supplier — the level only controls what physically leaves the building at submission time. Confirm the required level and retention period directly against the customer's specific requirement rather than assuming Level 3 by default.
How the Control Plan Fits Into PPAP
If PPAP is the approval event, the Control Plan is the living document that makes the approval credible over time. It is a structured summary of the systems used to control a part's process — for every operation, it names the characteristic being controlled, the specification or tolerance, the measurement method, the sample size and frequency, and what happens if a result falls outside limits (the reaction plan).
AIAG defines three phases a Control Plan should cover as a part matures:
- Prototype — controls used while building prototype parts, generally covering dimensional measurements, material, and performance tests.
- Pre-launch — controls after prototype but before full production, typically tighter than production controls, used while the process is still being validated.
- Production — controls used during full-rate, ongoing production, including product and process characteristics, measurement systems, and statistical methods such as SPC where applicable.
The three phases are meant to build on one another: what gets learned about process behavior at prototype and pre-launch feeds into the final production Control Plan, rather than each phase being drafted in isolation. A Control Plan is also a living document — a customer-approved engineering change, a new failure mode caught in the field, or a process change all warrant a Control Plan review and, typically, a re-triggered PPAP.
Practical Impact: Where This Goes Wrong on the Floor
The gap between a PPAP package that reads correctly and a process that actually behaves the way the paperwork says rarely shows up at submission — it shows up months later, when an auditor, a customer engineer, or an 8D investigation asks for the evidence behind a specific line in the Control Plan and someone has to find it. For a supplier running dozens of active part numbers across multiple customer portals, each with its own CSR quirks, that evidence is often scattered across shared drives, email threads, and whichever engineer built the original submission.
Common Mistakes in PPAP and Control Plan Work
- Treating the submission level as the whole requirement. A Level 1 or 2 submission still implies the supplier holds the complete eighteen-element file — it just isn't shipped. Suppliers sometimes stop short of building the full package because the customer only asked for the PSW.
- Letting the Control Plan drift from the PFMEA. The two documents are meant to stay linked — a control without a corresponding failure mode, or a high-risk failure mode with no matching control, is a classic audit finding.
- Skipping the pre-launch phase. Jumping straight from prototype controls to production controls without a documented pre-launch stage removes the evidence a customer expects to see for how the process was validated at ramp-up.
- Not re-triggering PPAP after a change. A supplier-initiated process change, tooling relocation, or new sub-supplier can require a new PPAP submission even if the drawing hasn't changed — missing this is one of the more common causes of a customer stop-ship.
- Applying a generic checklist to every customer. Because customer-specific requirements modify the base AIAG structure, using one PPAP template across all customers without checking each CSR is a frequent source of rejected submissions.
- Losing traceability between elements. When dimensional results, MSA studies, and the Control Plan live in different systems without a shared part revision reference, reconstructing "what was actually approved" becomes a manual, error-prone search during an audit.
That traceability problem is exactly where a lot of supplier quality time disappears — not writing the documents, but finding and cross-checking them months or years later. This is the kind of gap Igera's AI is built for: it answers questions directly from a company's own PPAP files, Control Plans, PFMEAs, and customer-specific requirement documents, citing the exact source document and section rather than guessing, so a quality engineer can ask "what's the reaction plan for this characteristic in the current Control Plan?" and get an answer traceable to the actual file — instead of searching five folders during an audit.
Frequently Asked Questions
What triggers a new PPAP submission?
A new part or product, an engineering change affecting design records, a change in process or method, a new or relocated manufacturing site, a tooling change producing product outside original engineering specifications, or a change of sub-supplier or material source are all typical triggers under the AIAG framework. The specific list of triggers a customer will enforce should be confirmed against that customer's own requirements.
What is the difference between a Control Plan and a PFMEA?
The PFMEA identifies what can go wrong in a process, how severe and likely each failure is, and how well it would be detected. The Control Plan translates that risk analysis into an operational document: what is actually measured, how often, by whom, and what happens when a result is out of spec. They are meant to be reviewed together and kept consistent as the process evolves.
Does every part need a Level 3 PPAP submission?
No. The customer determines the required submission level, and it can differ by part, commodity, or program. Level 3 is common for many production parts, but the only reliable source for the required level on a specific part is the customer's own PPAP requirement or supplier portal instruction.
Who approves a PPAP submission?
The customer's supplier quality or product engineering function reviews the package and issues one of typically three dispositions — approved, interim approval, or rejected — often through a supplier portal rather than a paper process. An interim approval usually comes with a defined expiration and a corrective action expectation.
How long should PPAP records be retained?
IATF 16949 requires retention of PPAP-related records, but exact retention periods can be set by the customer-specific requirement and may exceed general regulatory minimums, particularly for safety-related or government-regulated characteristics. Confirm the applicable retention period in the relevant customer requirement or your organization's documented retention policy rather than assuming a single default.
Can a Control Plan be shared across similar parts?
A family Control Plan covering a group of parts made by a common process is permitted under the AIAG framework when the parts share the same process steps and controls, but any part-specific characteristic or tolerance still needs to be addressed. Whether a customer accepts a family plan for a given program is a question for that customer's requirements.
What happens if a characteristic goes out of control after PPAP approval?
The reaction plan documented in the Control Plan defines the immediate response — typically containment, notification, and root cause analysis — and depending on severity may require customer notification and a formal corrective action process. Repeated or unresolved excursions can lead to a customer requesting PPAP resubmission.
Disclaimer: This article is general information about the PPAP and Control Plan framework as described by AIAG and referenced within IATF 16949 and does not constitute professional, legal, or quality-certification advice. Submission elements, required levels, retention periods, and specific thresholds vary by customer and program. Always confirm requirements against the applicable customer-specific requirement, the current AIAG PPAP and APQP manuals, and, where needed, a qualified quality management professional or your certification body.
Stop searching five folders during an audit
Igera's AI answers questions directly from your PPAP files, Control Plans, and customer-specific requirements — citing the exact source.
See how Igera works for automotive suppliers
