PPAP deliverable guide
How to complete Customer-Specific Requirements
Customer-specific requirements are the additional rules, forms, portals, labels, tests, records, and approvals imposed by a particular customer. They must be identified before PPAP evidence is assembled.
Complete the fields
- Requirement source
- Record customer document, portal instruction, purchase order, specification, revision, and effective date.
- Requirement statement
- State the required action in plain language, including the required form, format, quantity, or approval.
- Applicability
- Record why the requirement applies or does not apply to the part and submission.
- Evidence and status
- Link the supporting record, owner, due date, customer approval, and open issue.
Step-by-step completion sequence
- Collect current requirements from the customer’s official sources.
- Create a checklist that maps each applicable requirement to an owner and evidence.
- Resolve conflicts and missing information with the customer before the submission date.
- Complete the evidence review before signing the PSW.
- Retain the checklist and update it when customer requirements change.
PPAP control point: The customer’s current submission request, customer-specific requirements, and approved forms control. This guide explains a practical way to prepare the record; it does not authorize a substitute format or acceptance criterion.