Advanced Product Quality Planning (APQP) is the structured, five-phase framework the automotive industry uses to develop a new part and its manufacturing process so that quality is planned in from the start rather than inspected in at the end. It runs from planning and design through process development and validation to launch, and its major output is a Production Part Approval Process (PPAP) submission that proves the process can make good parts consistently.
APQP exists because the cheapest place to fix a quality problem is on paper, before any tooling is cut. A defect designed out in phase 1 costs a meeting; the same defect found at launch costs tooling changes, sorted stock, and an unhappy customer. Developed and maintained by the Automotive Industry Action Group (AIAG), APQP gives cross-functional teams a common roadmap and a set of phase-gate reviews so nobody launches a part before the evidence says it is ready. It is a core expectation under the automotive quality standard IATF 16949 and it ties together the core tools, FMEA, MSA, SPC, the control plan, and PPAP, into one launch discipline.
What are the five phases of APQP?
APQP organizes a product launch into five phases, each with defined inputs and outputs and a review before the team moves on. The phases overlap in practice, but the sequence of what must be decided is fixed: you cannot design a process for a product that is not yet defined, and you cannot validate a process that is not yet designed.
- Plan and define the program. Translate the voice of the customer into design goals, reliability targets, and preliminary quality objectives. Gather customer requirements, business plan inputs, and lessons learned. The output is a clear program scope and preliminary bills of material and process flow. Get the customer's real requirements wrong here and every later phase inherits the error.
- Product design and development. Develop the design to near-final form. Run the design FMEA, define design verification and validation plans, review engineering requirements, and produce prototype builds and drawings. This phase produces a manufacturable design and the special characteristics that will need control downstream. See our guide to the design FMEA.
- Process design and development. Design the manufacturing process that will build the design at rate. Develop the process flow, the process FMEA the pre-launch control plan, measurement systems analysis (MSA) plans, packaging, and the floor plan. The phase ends with a process ready to make parts under near-production conditions.
- Product and process validation. Prove the process works by making parts on the production tooling and equipment at the quoted rate. Run a significant production run, conduct initial process capability studies, complete measurement systems analysis, validate the parts against all requirements, and assemble the PPAP. This is where evidence replaces intention.
- Launch, feedback, assessment, and corrective action. Ramp to full production, then use real production data to reduce variation, close out issues, and feed lessons back. This phase never fully ends; it is the bridge from launch into ongoing production and continuous improvement.
What does APQP actually produce?
APQP is often described by its deliverables, because each phase creates specific documents that the next phase and the customer rely on. The framework is not paperwork for its own sake; each output is a decision recorded so it cannot quietly reverse itself later. The key deliverables map to phases like this.
| Phase | Key outputs |
|---|---|
| 1. Plan and define | Design goals, reliability and quality targets, preliminary BOM and process flow, special-characteristics list |
| 2. Product design | Design FMEA, design verification plan, drawings and specifications, prototype control plan |
| 3. Process design | Process flow diagram, process FMEA, pre-launch control plan, MSA and packaging plans, floor plan |
| 4. Validation | Significant production run, initial process capability studies, MSA results, production control plan, PPAP |
| 5. Launch and feedback | Reduced variation, closed issues, lessons learned, ongoing production data |
Notice the control plan appears three times, as a prototype, pre-launch, and production version. That progression is the spine of APQP: the plan for how each characteristic will be controlled matures alongside the product and process, so that by launch there is a living document telling operators exactly what to check, how, and how often.
How is APQP related to PPAP?
PPAP is the output and the approval gate of APQP, not a separate program. Where APQP is the whole planning journey, the Production Part Approval Process is the standardized package a supplier submits to prove the journey succeeded: that the supplier understands every engineering and specification requirement and that the production process can make parts meeting those requirements at the quoted rate. A PPAP submission bundles the evidence, drawings, design and process FMEAs, the control plan, measurement systems analysis, initial process capability results, a sample of parts, and more, capped by a Part Submission Warrant (PSW) the supplier signs.
Customers set how much of that evidence they want to see through submission levels, typically Level 1 (warrant only) through Level 5 (full evidence reviewed at the supplier's site), with Level 3 (warrant plus product samples and complete supporting data) the common default. The customer's approval of the PPAP is what authorizes production shipments. Fail the PPAP and the part does not ship, no matter how good the design looks on paper, which is exactly the discipline APQP is built to enforce.
Who uses APQP, and does it apply outside automotive?
APQP is required across the automotive supply chain, driven by IATF 16949 and by OEM customer-specific requirements, and it is the framework suppliers are expected to follow for any new part or significant change. Its influence reaches beyond cars, though. Aerospace uses a closely related discipline (APQP4Wind and AS13100 borrow the ideas), and many general manufacturers adopt the phased, gate-reviewed launch approach because the logic, plan quality in, validate before you launch, is universal. The vocabulary is automotive; the thinking applies to any organization launching a product that has to be right at volume.
What are the most common APQP mistakes?
The failure patterns are consistent across launches. Teams treat APQP as a document-filling exercise for the customer instead of a real planning discipline, so the deliverables get created the week before they are due rather than driving decisions when it matters. They skimp on phase 1, capturing what they think the customer wants rather than confirming the actual requirements and special characteristics, and every later phase inherits that gap. They let the design FMEA and process FMEA become one-time artifacts that never inform the control plan, breaking the chain from risk to control. They run a validation build that is not truly representative, wrong operators, off-tools, or below rate, so the capability numbers flatter the process and problems show up after launch. And they skip the phase-5 feedback loop entirely, closing the program at PPAP approval instead of using early production data to drive out the variation the launch left behind. The antidote to all five is the same: keep the deliverables live and connected, and base the validation evidence on real production data rather than a staged demonstration.
What do the standards say?
Sources for APQP and PPAP
- APQP is defined in the reference manual maintained by the Automotive Industry Action Group (AIAG) which organizes product and process development into five phases with gate reviews.
- The Production Part Approval Process is a separate AIAG reference and is the approval output of APQP; it standardizes the evidence a supplier submits to prove the process can meet requirements (AIAG, PPAP).
- APQP integrates the automotive core tools, FMEA, MSA, SPC, the control plan, and PPAP, and is a core expectation of the quality management standard IATF 16949.
- Risk analysis within APQP now follows the AIAG-VDA FMEA seven-step approach, and process control is verified through statistical process control and initial capability studies.
How does a connected floor support APQP?
APQP lives or dies on evidence at the validation phase, and gathering that evidence, a real production run, capability studies, measurement data, is exactly the kind of work that stalls when the floor runs on paper. When the significant production run is captured digitally, capability studies read from real timestamped data instead of a hand-tallied sample, and the production control plan checks become live records rather than clipboard entries that may or may not reflect what happened. That makes the PPAP faster to assemble and more credible, and it makes the phase-5 feedback loop, reducing variation after launch, run on actual production signal instead of memory. Plants that moved from paper logs to real-time operational data, like the processor in our CLS case study close launch issues with evidence and tie them back to the supplier quality record. See how Harmony captures floor data without a rip-and-replace on our features overview.