Project Quality Plan (PQP) — A Practical Guide Connecting Milestones and Quality Gates in APQP

1. Project Quality Plan: The Most Overlooked Element 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 sits in the project folder, untouched and not updated monthly.

Typical scenarios:

• The project manager’s schedule is detailed, but the quality plan is only three pages stating “follow company procedures.”
• A significant deviation occurs during the prototype phase, only to find out that the quality gate (Gate) has never been properly reviewed.
• A customer requests the PQP, and the project team copies and updates the date from an old project, completely disconnecting it from current risks, resources, and verification strategies.

The essence of the Project Quality Plan is to clearly define the standards, responsible parties, verification times, and escalation procedures for the project, and to tie these to project milestones—it is the quality roadmap of APQP, not a condensed version of the quality manual.

2. Differences Between PQP, Project Plan, and Quality Manual

The PQP should reference procedures rather than repeat them, focusing 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)

1. Project Overview: Product, customer, factory, SOP date, team RACI
2. Applicable Standards and CSR: IATF, customer specifications, regulations, deviation approval path
3. Quality Objectives: FTQ, PPM, complaints, OTD, etc., with quantifiable targets and data sources
4. Phase Gates and Deliverables: Inputs and outputs for Concept / Alpha / Beta / PPAP / SOP gates
5. Verification and Testing Strategy: DVP links, DV/PV batches, full-size, reliability, Run@Rate
6. Supply Chain Quality: List of critical components, supplier PPAP plans, incoming material strategy
7. Change and Problem Management: ECN, deviations, 8D, escalation path
8. 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, due date).

4. RACI: Quality Roles Must Be Defined in PQP

Common Mistake: The PQP only lists responsibilities for the quality department, and the project manager signs without committing to participate in the Gate—this makes the gate review ineffective.

5. Designing Phase Quality Gates (Quality Gates)

It is recommended that each APQP phase have at least one formal Gate, with the 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 the FMEA have closure or mitigation plans
• Decision: Go / No-Go / Go with conditions (written conditions + responsible person + date)
• Output: Updated PQP, issue list, plan for the next phase

Before Gate 3 (Pilot Production): It must be confirmed that the PFMEA/CP are consistent, the MSA plan is in place, initial process studies are scheduled, and the PPAP level is aligned 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 production approval gate
• The PQP should specify: who approves the PSW, the number of pilot production batches, and whether they align with the production rate

Avoid the situation where the PQP specifies 50 pilot production pieces, but the PPAP uses data from 10 prototype pieces—both auditors and customers will question this.

7. Keeping the PQP as a Living Document

Versioning 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-Specific Considerations

• Automotive Tier 1/2: Customers often provide PQP templates, which must be aligned clause by clause
• Medical: References to design verification/confirmation and risk management documents are more stringent
• Consumer Electronics: Shorter cycles, PQP can be simplified but gates cannot be skipped

9. Common Misconceptions

Misconception 1: PQP = Compilation of Procedure Files 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 = Gate not conducted.

Misconception 3: Unmeasurable Quality Objectives “Meeting customer requirements” is not an objective; 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)

11. Case Study: Correct Use of No-Go at Gate 3

In a Tier 2 structural component project, the first-time yield (FTY) during the prototype phase was 92%, and the project manager wanted to “proceed to SOP and then supplement data.” The PQE listed conditional Go at Gate 3:

1. Complete 300 pieces of production rate PV within two weeks, with no fewer than the required CSR items having Ppk≥1.67.
2. Supplement the supplier’s heat treatment PPAP.
3. Any PFMEA RPN>100 items that are not closed must have a risk assessment and written customer approval.

Result: SOP was delayed by 3 weeks, but the PPM target was met in the first month of production; another project that “went ahead and supplemented data later” caused a 2-day customer production stoppage.

Insight: No-Go is not a roadblock by the quality department but a trade-off to ensure controllable risks.

12. PQP Quick Check (Printable)

13. Common Questions from Customers and Second-Party Audits (Regarding PQP)

• Please show the latest version of the PQP and change records.
• 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 or system links to these evidences in the PQP can significantly reduce the time required for audit preparation.

14. Template and System Recommendations

• Small projects: Excel/PPT PQP + Gate checklists are sufficient
• 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 multiple ledgers

Regardless of the tool, a living document + gate decision records is the baseline.

For Tier 1/2 automotive projects, it is also recommended to include 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 production starts. 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, CP, and PPAP have a ‘project context’—not three isolated folders.

Three Questions to Test the Effectiveness of the PQP: Does the gate have Go/No-Go? Are the quality objectives quantifiable? Who updated the latest version and when?

Knowledge Number: 8.1.2

Version: v20260702

Author: Quality Excellence Think Tank Quality Excellence Think Tank is dedicated to providing systematic professional knowledge, methodologies, and practical tools for quality management practitioners, helping companies continuously improve their quality capabilities.