Project Quality Plan (PQP) — A Practical Guide to Connecting Milestones and Quality Gates in APQP
1. Project Quality Plan: The Easiest Part to Have Documents but No Control in APQP
In discussions about the five APQP tools, PFMEA, control plan, and PPAP often take up the most training time; however, the Project Quality Plan (PQP) is frequently reduced to a Word document that is "stored in the project folder and never updated monthly."
Typical scenarios:
- The project manager's schedule is detailed, but the quality plan is only three pages long, stating "follow company procedures."
- A significant deviation occurs during the prototype phase, only to realize that the quality gate (Gate) has never been truly reviewed.
- The client requests a PQP, and the project team copies and modifies an old project's PQP, which is completely disconnected from the current risks, resources, and verification strategies.
The essence of the Project Quality Plan is to clearly outline the "standards used, who is responsible, when verification will occur, and how to escalate" for the project, and to link it with project milestones—serving as the "quality roadmap" for APQP, not a condensed version of the quality manual.
2. Differences Between PQP, Project Plan, and Quality Manual
| Document | Questions Answered | Time Granularity |
|---|---|---|
| Quality Manual / Procedure | How the company generally operates | Long-term validity |
| Project Main Plan | When design, mold opening, and pilot production will be completed | Task/Week |
| Project Quality Plan | Special requirements, verification, and gate control for this project | Phase gates + key events |
The PQP should reference procedures rather than repeat them; the focus should be on the differences in this project: customer CSR, special characteristics, supplier scope, test batches, and audit arrangements.
3. Standard Structure of PQP (Suggested 8 Chapters)
- Project Overview: Product, customer, factory, SOP date, team RACI
- Applicable Standards and CSR: IATF, customer specifications, regulations, deviation approval path
- Quality Objectives: Quantifiable targets and data sources for FTQ, PPM, complaints, OTD, etc.
- Phase Gates and Deliverables: Inputs and outputs for Concept / Alpha / Beta / PPAP / SOP gates
- Verification and Testing Strategy: DVP links, DV/PV batches, full-size, reliability, Run@Rate
- Supply Chain Quality: List of key components, supplier PPAP plan, incoming inspection strategy
- Change and Problem Management: ECN, deviations, 8D, escalation path
- Audits and Reviews: Scheduling of internal audits, customer audits, and management reviews within the project
Each chapter should include at least one checkable output (document name, responsible person, deadline).
4. RACI: Quality Roles Must Be Included in PQP
| Role | Typical Responsibilities |
|---|---|
| Project Quality Engineer (PQE) | PQP maintenance, gate review organization, issue tracking |
| Design Quality | DFMEA, special characteristics, DVP alignment |
| Process Quality | PFMEA, control plan, pilot production verification |
| Supplier Quality | SCAR, PPAP plan |
| Laboratory / Metrology | MSA, testing resources |
| Project Manager | Resource, schedule, and quality gate decision-making |
Common Mistake: The PQP only lists the responsibilities of the quality department, and the project manager signs it without committing to participate in the Gate—making the gate review ineffective.
5. Design of Phase Quality Gates (Quality Gate)
It is recommended that each APQP phase have at least one formal Gate with the following minimum elements:
- Input Checklist: Whether the deliverables from the previous phase are complete and the versions are correct
- Risk Review: Whether the top risks in FMEA have closure or mitigation plans
- Decision: Go / No-Go / Go with conditions (written conditions + responsible person + date)
- Output: Update PQP, issue list, plan for the next phase
Before Gate 3 (Pilot Production), it is essential to confirm: PFMEA/CP consistency, MSA plan, initial process study schedule, and PPAP level alignment with the customer.
6. Interface with DVP and PPAP
- DVP (Design Verification Plan) test items should be mapped to phases and times in the PQP
- PPAP submission is not the end of the PQP but one of the inputs for the mass production approval gate
- The PQP should specify: who approves the PSW, the number of pilot production batches, and whether they align with the mass production rhythm
Avoid the situation where the PQP specifies 50 pilot production pieces, but the PPAP uses data from 10 test mold pieces—both audits and customers will ask questions.
7. Living Document: How to Keep the PQP Effective
| Trigger Event | PQP Update Action |
|---|---|
| Customer CSR Change | Chapter 2 + Verification Plan |
| Major ECN | Phase gates, PPAP resubmission scope |
| Supplier Change | Chapter 6 + Incoming Inspection Strategy |
| Pilot Production Failure | Objectives, verification batches, resources |
| Customer Audit Findings | Chapter 8 + Corrective Action Tracking |
Version Rule: The PQP version number should be linked to the project ECN or configuration baseline; only the latest controlled version should be used on-site.
8. Industry Differences
- Automotive Tier 1/2: Customers often provide PQP templates, which must be compliance matrices for each item
- Medical: Design verification/confirmation and risk management documents are more strictly referenced
- Consumer Electronics: Shorter cycles, PQP can be simplified but gates cannot be skipped
9. Common Misconceptions
Misconception 1: PQP = Compilation of Procedure Documents The PQP should highlight project-specific risks and differences; otherwise, it has no value.
Misconception 2: No Minutes After Gate Meetings No Go/No-Go record = No Gate conducted.
Misconception 3: Unmeasurable Quality Objectives "Meeting customer requirements" is not a target; it must include numbers and data sources.
Misconception 4: PQP Written Only Once at Project Initiation A living document is the essence of APQP.
10. 90-Day Implementation Path (For Companies with Existing NPI Processes)
| Week | Action |
|---|---|
| 1~2 | Release PQP template + Gate checklist; select one ongoing project for pilot |
| 3~6 | Complete Gate 1~2 drills; joint training for PQE and PM |
| 7~12 | Enforce PQP for all projects; conduct PPAP mock audits before Gate 3 |
11. Case Fragment: Correct Usage of a No-Go at Gate 3
In a Tier 2 structural component project, the first-time yield (FTY) of the test mold was 92%, and the project manager hoped to "start SOP and then supplement data." The PQE listed conditional Go at Gate 3:
- Complete 300 pieces of production rhythm PV within two weeks, with no fewer than the required CSR items having Ppk≥1.67.
- Supplement the supplier's heat treatment PPAP.
- Items in the PFMEA with RPN>100 that have not been closed must have a risk assessment and written customer approval.
Result: The SOP was delayed by 3 weeks, but the PPM target was met in the first month of mass production; a concurrent project that "started production and then supplemented data" caused a 2-day customer production stoppage.
Insight: No-Go is not a roadblock by the quality department but a way to exchange conditions for controllable risks.
12. One-Page PQP Checklist (Printable)
| Check Item | Yes/No |
|---|---|
| Quality objectives have numbers and data sources | |
| Each phase gate has input and output checklists | |
| DVP items are mapped to PQP | |
| PPAP level is consistent with the customer | |
| PQP update rules triggered by ECN | |
| PQE and PM co-sign the latest version |
13. Common Questions from Customers and Second-Party Audits (PQP)
- Please show the latest version of the PQP and the change record.
- Where are the Go/No-Go minutes for Gate 3?
- Who maintains the CSR compliance matrix for this project?
- What is the escalation path when quality objectives are not met?
- Are the pilot production batches in PPAP and PQP consistent?
Embedding index pages/system links to these pieces of evidence in the PQP can significantly reduce the time required for audit preparation.
14. Template and System Recommendations
- Small projects: Excel/PPT PQP + Gate checklist
- Multiple concurrent projects: Manage PQP versions using project modules in PLM or QMS
- Track issue lists, 8D, and ECN on the same platform to avoid three separate ledgers
Regardless of the tool, Living Document + Gate decision record is the baseline.
For Tier 1/2 automotive projects, it is also recommended to add a customer special characteristics list (SL/CC/KCC) and an annual re-verification plan in the PQP appendix to prevent the characteristics list from becoming disconnected from the CP after mass production. When replicating projects across multiple factories, the PQP must evaluate equipment and supplier differences for each factory and not be cloned in its entirety.
A well-written project quality plan ensures that PFMEA, control plan, and PPAP have "project context"—rather than being three isolated folders.
Three Questions to Test the Effectiveness of the PQP: Does the gate have Go/No-Go? Do the quality objectives have numbers? Who updated the last version and when?
Knowledge code: 8.1.2
Version: v20260702
Author: Quality Think Tank Quality Think Tank is dedicated to providing systematic professional knowledge, methodologies, and practical tools for quality management practitioners, helping companies continuously improve their quality capabilities.