Skip to content

Free template

Updated

APQP checklist

APQP, advanced product quality planning, is a way of planning the quality of a new product before it goes into production. The work is split into five phases: plan and define, product design and development, process design and development, product and process validation, and feedback and corrective action. Each phase ends at a gate, a short review that asks whether the deliverables are done before the program moves on. This checklist lists 43 deliverables across the five phases in our own words, with a status, an owner, a due date and a place for the evidence. The Excel tracker flags late items, works out the percent complete for each phase and tracks the gate dates; the PDF is the printable version with a gate review record and a worked example. Your customer may require its own forms and dates, and where they differ, theirs win. This is general quality-planning knowledge, not the text of any manual.

Free to use: print it, copy it and edit it for your team. Enter your name and work email once to download.

Page 1 of the APQP checklistProgram header fields above a table of the five phases, each with a gate question, planned and actual gate dates, a deliverables count, pass, conditional or fail circles and a sign-off column.
Five phases and gates43 deliverablesStatus, owner and due dateLate flagPercent complete by phaseIssues logGate review recordWorked example
Filled-in APQP checklist: a bracket launch with phase 3 at 70%
The same sheet filled in with the worked example (page 5 of the PDF, illustrative numbers). Open full size (opens the picture in a new tab)

When to use it

When to use an APQP checklist

  • When you are launching a new part or product for a customer who expects a planned launch, such as an automotive or other regulated-supply customer.
  • When a launch is slipping and nobody can say which deliverable is holding it up.
  • To run the gate reviews of a program with a single list instead of a separate status in each person's head.
  • To plan the order of the quality documents: the FMEAs, the control plan, the gauge studies, the capability study and the part approval package.
  • Not for day-to-day production control, which belongs on the control plan and the shop floor checks.

How to fill it in

  1. 1

    Fill in the program header

    Name the project, the customer, the part and its revision, the program owner and the start of production date. One owner, by name.

  2. 2

    Set the gate dates backwards

    Start from the start of production and work back. Give each of the five phases a planned gate date, and leave room after phase 4 for the production run and the customer's approval.

  3. 3

    Give every deliverable an owner and a due date

    Go down the list and put a name and a date against each item. Mark the ones that do not apply NA and write why, such as a customer waiver.

  4. 4

    Update the status as work moves

    Use four states: not started, in work, done and not applicable. Done means the evidence exists and someone can find it, not that it is nearly finished.

  5. 5

    Hold the gate review on evidence

    Before each gate count the done items, review the open ones and decide: pass, conditional pass with named actions and dates, or fail. Record the decision and the sign-off.

  6. 6

    Log late items the same day

    Anything late, blocked or at risk goes on the issues list with an owner and a date. A conditional pass carries its open items onto the same list.

What's on the checklist

The 43 deliverables in the five APQP phases

Each phase ends at a gate. On the sheet every deliverable has a status (not started, in work, done or not applicable), an owner, a due date and a note of where the evidence is kept; the gate is passed when the phase's deliverables are done or marked not applicable.

Phase 1: Plan and define

Gate question: do we know what the customer needs, and can we commit to it?

  1. 1Customer requirements written down: function, appearance, volume, price target and delivery dates
  2. 2Design goals agreed: function, weight, cost and appearance targets
  3. 3Reliability and quality targets agreed, such as life, failure rate and defect rate or yield
  4. 4Preliminary bill of materials with the long lead-time parts flagged
  5. 5Preliminary process flow from receiving to shipping
  6. 6Preliminary list of special characteristics (safety, fit and function features that need tighter control)
  7. 7Benchmarking and lessons from earlier programs reviewed
  8. 8Program timing plan with gates, milestones and the start of production date
  9. 9Cross-functional team named and management support confirmed

Phase 2: Product design and development

Gate question: is the design proven and released, and is it possible to make?

  1. 10Design FMEA completed, with the high-risk failure modes actioned
  2. 11Design for manufacture and assembly review held
  3. 12Design verification results recorded against the requirements
  4. 13Prototype build done and a prototype control plan written, if prototypes are needed
  5. 14Engineering drawings and specifications released at a known revision
  6. 15Material and performance specifications agreed
  7. 16Special characteristics confirmed on the drawing
  8. 17New equipment, tooling and facility needs listed with owners and dates
  9. 18Gauge and test equipment needs listed
  10. 19Team feasibility review signed: the part can be made to the drawing at the volume

Phase 3: Process design and development

Gate question: is the process designed, with its risks and controls written down?

  1. 20Packaging standard and specification agreed
  2. 21Full process flow diagram, step by step
  3. 22Floor plan and material flow drawn
  4. 23Process FMEA completed, with the high-risk steps actioned
  5. 24Pre-launch control plan written
  6. 25Process instructions and work standards written
  7. 26Measurement system analysis plan and gauge plan written
  8. 27Process capability study plan written for the special characteristics
  9. 28Tooling and equipment installation and tryout schedule set
  10. 29Operator training plan written

Phase 4: Product and process validation

Gate question: does a production run prove the process meets the requirements?

  1. 30Production trial run done at the planned rate, with production tools, people and gauges
  2. 31Measurement system studies completed for the gauges in the control plan
  3. 32Process capability shown for the special characteristics
  4. 33Production part approval package submitted to the customer
  5. 34Production validation testing passed
  6. 35Packaging evaluated on a real shipment
  7. 36Production control plan signed off
  8. 37Quality planning sign-off and management support recorded

Phase 5: Feedback and corrective action

Gate question: is the launch stable, and what did we learn?

  1. 38Variation on the special characteristics watched after launch and reduced where needed
  2. 39Customer satisfaction and delivery performance reviewed
  3. 40Launch problems closed with corrective actions
  4. 41Lessons learned written down and fed back into the FMEA library and the next program
  5. 42Service and spare part support set up, if the part is serviced
  6. 43Program closed out with the final results reviewed

A filled-in example

Illustrative, not a benchmark

An example (illustrative): a made-up supplier launching a stamped bracket, checked about three months before the third gate.

  • Phases 1 and 2 are done and passed. One deliverable in phase 2 is marked not applicable because the customer waived prototypes.
  • Phase 3 has ten deliverables and seven are done, so it is 70% complete.
  • Two deliverables are late and shown in amber: the process FMEA revision after the die trial (14 days) and the gauge plan (6 days).
  • Phases 4 and 5 are not started and not yet due, so they are not counted as late.
  • Overall, 25 of the 42 deliverables that apply are done, about 60%.

The gate for phase 3 is flagged at risk two weeks before it is due, while there is still time to add people or move the gate.

Common mistakes

  • Treating the gate as a formality

    A gate that always passes teaches the team to stop reporting problems. Pass only on evidence and use a conditional pass, with dates, when something is open.

  • Marking items done without evidence

    If nobody can find the FMEA or the gauge study, it is not done. Write where the proof is kept in the evidence column.

  • Planning the gates forward from today

    Dates set forward from the start of design leave no buffer before launch. Work back from the start of production and let the early phases absorb the slack.

  • Leaving the gauge and capability work to the end

    The measurement plan, the gauge studies and the capability study need parts and gauges that take time to arrive. Plan them in phase 3, not the week before approval.

  • Ignoring the customer's own requirements

    A generic checklist is a start. Add the customer's required forms, submission levels and dates, and follow theirs where they differ.

Download the template

Free to use: print it, copy it and edit it for your team. Enter your name and work email once to download.

Run this template in LeanSuite

In LeanSuite quality issues are logged as tags, ranked in the QA Matrix and traced to their root cause, and digital instructions and checklists with number limits, required photos and signatures build quality into every task.

See it in a 45-minute demo

FAQ

APQP checklist: common questions

  1. APQP stands for advanced product quality planning. It is a structured way to plan a new product's quality before production starts, using five phases that each end at a gate review. It is widely used by automotive suppliers and other manufacturers with demanding customers.

  2. Plan and define, product design and development, process design and development, product and process validation, and feedback and corrective action. This checklist lists the deliverables of each phase in our own words.

  3. APQP is the whole planning process for a new product. PPAP, the production part approval process, is the evidence package a supplier submits to the customer, mostly in phase 4. The PPAP is one deliverable inside the APQP.

  4. No. It is a general checklist for planning and tracking. Your customer may require specific forms, submission levels and dates, and where they differ you follow theirs. Add any customer-specific items in the spare rows.

  5. Every deliverable that applies is done, with evidence that someone can find, and the percent complete for the phase is 100%. If something is still open, give a conditional pass with named actions, owners and dates, and log them on the issues list.

More free templates

All templates
Browse all 236 templates

Can't find the template you need?

Tell us what you're looking for. We'll make it and send it to your inbox, free.

A shift handover sheet, a red tag log, a changeover checklist for one machine: if your team uses it on the floor, ask.

By sending this form you agree to our Terms of Service and Privacy Policy.

Pass it on

We want LeanSuite to be the best place on the internet for lean help. If this was useful, send it to someone on your team or in your network who needs it.