APQP vs PPAP: how the framework and the evidence fit together

APQP and PPAP are mentioned in the same breath so often that people treat them as one thing. They're not. One is a process you follow; the other is a package you submit. Keeping them straight makes the whole launch easier to reason about.

APQP: the framework

Advanced Product Quality Planning is the method for developing a new part so that it meets requirements in production. It spans the entire program — from understanding the customer's needs, through design and process development, to validation and launch — organised into five phases. APQP is a verb: it's the work of planning quality in, phase by phase, and it runs for the life of the program.

PPAP: the evidence

The Production Part Approval Process is a deliverable — a standardized package of 18 elements that proves the process can make conforming parts at volume, submitted to the customer for approval before production ships. PPAP is a noun: it's a thing you assemble and send, at a defined submission level, at specific milestones (initial launch, an engineering change, a process move, a long production gap).

How they connect

PPAP is best understood as the proof that the APQP work was done. The package isn't generated from nothing at the end — its core engineering elements are produced during APQP's phases and simply collected for submission:

If APQP is done well, PPAP is mostly assembly. If APQP is rushed, PPAP becomes the painful moment you discover what's missing.

A simple analogy

Think of building a house. APQP is the construction process — the plans, the inspections at each stage, the sequence of trades. PPAP is the certificate of occupancy — the evidence pack you present so the inspector signs off that the house is fit to live in. You wouldn't generate the certificate without doing the build; PPAP without real APQP is the same hollow exercise.

Where teams get confused

• "We need to do a PPAP" used to mean APQP. The PPAP is the output; the work is the APQP behind it. Treating PPAP as a paperwork sprint at the end is how launches go wrong.
• Levels are a PPAP concept, phases are an APQP concept. The five submission levels decide how much of the package you send; the five phases are the development stages. Different fives.
• PPAP recurs; APQP plans for it. You re-submit a PPAP whenever the product or process changes materially — and a good APQP makes that re-submission cheap, because the model behind it is already current.

For the full picture of both, read The APQP & PPAP method, explained.