PPAP Explained: The Approval Process, the 18 Documents, and How to Run It Digitally
TL;DR
- PPAP (Production Part Approval Process) is the AIAG framework that requires a supplier to prove, with documented evidence, that a new or changed part can be produced consistently at the customer's specified rate and quality.
- The framework defines up to 18 required elements, from design records and FMEAs through the Part Submission Warrant (PSW), the cover document that carries the supplier's formal sign-off.
- Five submission levels, Level 1 through Level 5, determine how much of that documentation actually reaches the customer versus stays on file at the supplier's site.
- PPAP approval still moves through email and shared drives at most suppliers, which is where cycle time and audit risk both build up, not inside engineering or the lab.
- A governed digital workflow does not replace the PLM, QMS, or ERP that already holds the part record. It routes the submission, the approval chain, and the audit trail across every department and customer that has to touch it.
Best for: VPs of Quality, Directors of Quality Assurance, and Supplier Quality Managers at automotive and industrial parts suppliers who submit PPAP packages to multiple OEM or Tier 1 customers and need submissions to move faster without losing the paper trail an IATF audit will ask for.
PPAP, or Production Part Approval Process, is the AIAG-defined quality framework that requires a supplier to demonstrate, with a defined set of documents, that a production part and the process that makes it consistently meet a customer's engineering and quality requirements before mass production begins. Every automotive supplier, and most of their Tier 2 and Tier 3 suppliers, works against some version of this framework, because an OEM or Tier 1 customer will not release production volume on a part until PPAP is approved. This guide covers what PPAP requires, what the 18 documents actually are, how the five submission levels work, and why so many suppliers still lose weeks moving a completed package through internal and customer sign-off even after the technical work is finished.
What is PPAP, and why does it exist?
PPAP exists so a customer never has to take a supplier's word that a part is ready for mass production. The Automotive Industry Action Group (AIAG) publishes the PPAP manual that defines the framework, and it applies whenever a new part enters production, a design changes through an engineering change notice, tooling is replaced, a material or supplier source changes, or production moves to a new plant.
A part that passes inspection once, by hand, on a prototype line, is not the same as a part a supplier can make correctly at volume, run after run. PPAP forces the supplier to prove the second claim with evidence: design intent, process capability, measurement accuracy, and a formal declaration that the parts submitted represent what full production will actually look like.
Regulated sectors layer their own requirements on top. Automotive suppliers work against IATF 16949, the automotive quality management standard built around PPAP, APQP, and the other AIAG core tools. A supplier that fails an OEM's audit program, such as Ford's Q1 or General Motors' BIQS, often traces the finding back to a PPAP file that was technically complete but never properly maintained after initial approval.
How does the PPAP approval process work, step by step?
A PPAP submission moves through the same five stages regardless of company size or industry, and cycle time is usually lost at the handoffs between stages, not inside any single one of them.
- A trigger event occurs. A new part, an engineering change, a tooling replacement, or a supplier change creates the requirement for a new or revised PPAP.
- The supplier assembles the required elements. Design records, FMEAs, process flow diagrams, control plans, and the other elements the submission level requires are compiled into one package.
- Internal quality reviews and signs the package. A quality engineer checks that every required element is present, accurate, and consistent with the actual production process before it goes to the customer.
- The package is submitted at the required level. Level 1 sends only the PSW. Level 3, the most common default, sends the PSW plus samples and complete supporting data.
- The customer reviews and dispositions the submission. The outcome is Approved, Interim Approval (production may proceed for a limited time while an open item closes), or Rejected, which sends the package back for rework.
Every stage after the first is a handoff between people in different departments, different companies, and often different time zones. That is where a technically sound package sits for days waiting on a signature that has nothing to do with whether the part is actually good.
What are the 18 PPAP documents?
Not every submission includes all 18 elements. What level the customer requires determines how many actually leave the building. But every element must exist in the supplier's PPAP file regardless of submission level, because an auditor can ask for any of them at any time.
| # | Element | What it proves |
|---|---|---|
| 1 | Design records | The current engineering drawing and specification the part is built against |
| 2 | Engineering change documents | Formal authorization for any design deviation from the original release |
| 3 | Customer engineering approval | The customer's sign-off on the supplier's technical approach, where required |
| 4 | Design FMEA | A structured analysis of how the part design could fail and how severe each failure would be |
| 5 | Process flow diagram | A visual map of every manufacturing step from raw material to shipment |
| 6 | Process FMEA | The same failure analysis applied to the manufacturing process, not the design |
| 7 | Control plan | The operating document listing what gets monitored, how often, and what happens if a reading is out of range |
| 8 | Measurement system analysis | Evidence that the gauges and methods used to inspect the part produce reliable, repeatable data |
| 9 | Dimensional results | Actual measured values from production samples, checked against the drawing tolerances |
| 10 | Material and performance test results | Verification that the part meets chemical, physical, and performance specifications |
| 11 | Initial process studies | Statistical evidence, typically Cpk or Ppk, that the process is stable and capable at the required rate |
| 12 | Qualified laboratory documentation | Proof that any outside testing was performed by an accredited lab |
| 13 | Appearance approval report | Sign-off on color, texture, and other visual requirements, where the part carries them |
| 14 | Sample production parts | Physical parts pulled from an actual production run, not a prototype |
| 15 | Master sample | A retained, approved part that later production runs and inspections are compared against |
| 16 | Checking aids | Documentation of any calibrated fixture or gauge built specifically to inspect this part |
| 17 | Customer-specific requirements | Compliance evidence for anything the customer requires beyond the standard AIAG elements |
| 18 | Part Submission Warrant (PSW) | The summary cover sheet and the supplier's formal declaration that the submission is complete and accurate |
What is a PSW, and why isn't it the whole package?
A PSW, or Part Submission Warrant, is the single-page summary the supplier signs to declare that a PPAP submission is complete, accurate, and representative of what full production will actually produce. It is element 18 on the list above, the one document every submission level requires, and it is not a substitute for the other 17.
A Level 1 submission sends the customer nothing but the PSW while the supplier retains everything else on file, which is why the two terms get confused. A signed PSW with a thin or disorganized file behind it is exactly the gap an IATF audit is built to find. The warrant is the promise. The other 17 elements are the evidence the promise is true.
What are the 5 PPAP submission levels?
The customer, not the supplier, decides which level applies to a given part, and the level determines documentation volume, not documentation rigor. Every element still has to exist somewhere on file.
| Level | What goes to the customer |
|---|---|
| 1 | PSW only |
| 2 | PSW, product samples, and limited supporting data |
| 3 | PSW, product samples, and complete supporting data (the default for most new parts) |
| 4 | PSW plus whatever additional requirements the customer defines |
| 5 | PSW, product samples, and complete supporting data, reviewed on-site at the supplier's facility |
Level 3 is where most first-time production parts land and where coordination cost is highest: complete supporting data means every one of the 18 elements has to be current and gathered from whoever owns that piece of evidence, often three or four functions inside the same plant.
Why does a completed PPAP package still take weeks to close?
The technical work behind a PPAP submission, running the FMEAs, capturing dimensional data, proving process capability, is rarely the slow part. The slow part starts after the last data point is captured: routing a multi-department package for internal review, chasing a signature, resubmitting after a customer comment.
Across the Detroit-area automotive supplier base covered by Kissflow's own 2026 field research, a single PPAP package commonly takes eight or more weeks to move from trigger event to customer approval, and most of that time sits in the handoffs between quality, engineering, and the customer, not in the lab. That figure comes from Kissflow's internal Detroit-area field research, not a published external benchmark, and it should be read as directional rather than as a figure every plant should expect to match exactly.
Manufacturers are already spending on this problem. In Octave's Pulse of Quality in Manufacturing 2026 survey of 2,263 quality managers and directors across the United States, United Kingdom, and Germany, document automation was the single most common use case for AI in quality processes, ahead of defect detection and training. Suppliers are not short on urgency. They are short on a system that routes a package the way it actually moves: across departments, not through one inbox.
How does paper and email PPAP tracking compare to a governed digital workflow?
Most suppliers run PPAP one of three ways, and each has a real cost that shows up in a different place.
| Email and shared-drive tracking | PLM or QMS module alone | Governed digital workflow | |
|---|---|---|---|
| Where the 18 elements live | Scattered across folders, inboxes, and printed binders | Centralized in the PLM or QMS, but scoped to what that system owns | PLM or QMS stays the system of record; the workflow pulls status from all of them |
| Who is notified when a review stalls | Nobody, until someone chases it | Depends on module configuration and who has access | Automatic escalation after a set number of days |
| Cross-functional routing (quality, engineering, customer) | Manual forwarding and follow-up calls | Often scoped to one function by default | Built to route sequentially or in parallel across every function by design |
| Evidence for an IATF or customer audit | Reconstructed from email searches and folder digging | Present, but scoped to what that one system logged | A complete, timestamped record of every review, comment, and approval |
| Time to add a new approval step for a new customer's requirements | Not applicable | Usually requires an administrator or vendor change request | The quality team reconfigures the routing directly |
The middle column is where most established suppliers sit, and it explains why cycle time stays high even after a PLM or QMS investment: those systems manage the part record well, but neither was built for the cross-functional handoff a PPAP package needs to close.
Where does Kissflow fit in PPAP, and what does it not replace?
Kissflow does not store drawings, does not own the part's engineering record, and does not replace a PLM, QMS, MES, or ERP. It takes the PPAP submission and approval sequence and routes it as a governed workflow across every function that has to sign off, with automatic escalation when a review stalls and a permanent, timestamped audit trail attached to every step.
The same governed-workflow pattern already runs Kissflow's Corrective and Preventive Action app for the CAPA and SCAR cycles a rejected PPAP submission typically triggers next, so a supplier is not standing up a separate system for the corrective action that follows a failed submission. Godrej Consumer Products, a manufacturing customer running approval workflows on Kissflow, is a working example of the same pattern: quality and operations teams configuring their own routing logic directly, rather than filing a request with a system administrator every time an approval chain needs to change.
A manufacturing workflow platform that handles PPAP submission this way can route the supplier qualification process that precedes it using the same vendor qualification and onboarding logic, without a separate tool for each stage. Quality teams that need to change an approval chain without waiting on IT typically look at low-code platforms built for manufacturing for exactly this reason: the people who own the process can change the routing themselves.
How do you keep every PPAP file inspection-ready?
An IATF auditor does not ask whether a part is good. An auditor asks who reviewed a specific element, on what date, against what evidence, and whether the record still exists three years later. A workflow audit trail that logs every review, comment, and approval automatically answers that question without anyone assembling a binder the week before the audit window opens. That matters most for submissions that do not follow the standard path: an Interim Approval with an open item, or a resubmission after a customer rejection. A file that can only prove itself when someone reconstructs it by hand was never actually complete.
How can you cut PPAP approval time without cutting a review step?
These changes shorten cycle time without removing a review that protects part quality.
- Set a maximum review window per stage and escalate automatically. A four-day wait for one sign-off is the most common source of delay, and an escalation rule solves it faster than a policy memo.
- Route to every function at the same time the package is assembled, not after quality finishes its own check. Parallel review catches conflicts earlier than a sequential handoff does.
- Match review depth to the part's risk, not to one fixed process. A cosmetic trim piece does not need the same review chain as a safety-critical component.
- Keep the audit trail automatic, not manually assembled. If a package's history has to be reconstructed from email before an audit, the record was never complete.
- Track cycle time by stage, not just start to finish. The slow stage is rarely the one a team assumes it is until the data says otherwise.
Frequently asked questions
What is PPAP in manufacturing?
PPAP, or Production Part Approval Process, is the AIAG quality framework that requires a supplier to submit documented evidence proving a part and its production process can consistently meet a customer's engineering and quality requirements before mass production starts.
What are the 18 PPAP documents?
The 18 elements span design records, engineering change documents, customer engineering approval, Design and Process FMEAs, a process flow diagram, a control plan, measurement system analysis, dimensional results, material and performance test results, initial process studies, qualified laboratory documentation, an appearance approval report, sample production parts, a master sample, checking aids, customer-specific requirements, and the Part Submission Warrant.
What is a PSW in PPAP?
A PSW, or Part Submission Warrant, is the summary cover document a supplier signs declaring that a PPAP submission is complete, accurate, and representative of production. It is one of the 18 elements and the only one required at every submission level.
What are the PPAP submission levels?
There are five levels. Level 1 sends only the PSW to the customer. Level 3, the most common default, sends the PSW, samples, and the complete supporting data. Level 5 adds an on-site review of that same complete data at the supplier's facility.
When is a PPAP submission required?
A new PPAP is triggered by a new part entering production, a design change through an engineering change notice, a tooling replacement, a change in material or supplier source, or a move to a new production location.
How long should PPAP approval take?
There is no single universal target, since cycle time depends on part risk, submission level, and how many functions the package has to move through. What matters more than a fixed number is whether the delay is consistent and explainable, not an unescalated wait for one signature.
Does Kissflow replace my PLM, QMS, or ERP for PPAP?
No. The PLM or QMS remains the system of record for the part's engineering and quality data. Kissflow adds the routing, escalation, and audit-trail layer that moves a PPAP package across quality, engineering, and the customer, which is often the part those systems were not built to manage well.
What happens if a PPAP submission is rejected?
The customer returns the package with the specific gap identified, and the supplier typically opens a corrective action, often a CAPA or SCAR, before resubmitting. A governed workflow can route that corrective action the same way it routed the original submission, so the resubmission does not start the coordination problem over again.
Conclusion
The bottleneck in most PPAP submissions is not the engineering, the lab work, or the statistics. It is the handoff between quality, engineering, and the customer that a PLM or QMS was never built to manage, and it is exactly where cycle time and audit readiness are both won or lost. A governed workflow layer on top of the systems a supplier already owns, not a replacement for them, closes that gap: routing all 18 elements across every function on one timeline, escalating automatically when a review stalls, and building the audit trail as a byproduct of the process instead of a task done the week before an inspection. If the technical work behind a package already moves quickly but it stalls the moment it needs a second signature, that handoff is the place to fix first. For the corrective action cycle a rejected submission triggers next, see how manufacturing teams route CAPA and SCAR workflows alongside quality documentation.
About the author
Sreenidhe is Head of Content at Kissflow. This guide draws on Kissflow's own 2026 field research on PPAP cycle time among Detroit-area automotive suppliers, and on the named public sources cited throughout.
Sources
- Quality-One International: PPAP, Production Part Approval Process (18 elements and 5 submission levels)
- International Automotive Task Force: IATF 16949 automotive quality management standard
- Metrology News: Pulse of Quality in Manufacturing 2026 survey results (Octave, Q1 2026, n=2,263)
- LegalClarity: 18 Elements of PPAP Explained
