Prepare a PPAP submission package for my customer
A checklist of every PPAP element at my submission level, the status of each, and a plan to close gaps before the due date.
The prompt
Help me prepare a Production Part Approval Process (PPAP) submission.
Customer and their requirements: [customer name and any customer-specific PPAP manual or portal rules]
Part number, revision, and description: [DETAILS]
Submission level requested: [Level 1-5; Level 3 if not stated]
Reason for submission: [new part / engineering change / tooling transfer / new supplier or material / process change]
Due date: [DATE]
What we already have: [LIST documents done, e.g. "PFMEA done, control plan draft, no MSA yet"]
Production trial run details: [planned or completed run size, date, line]
Give me:
1. A checklist of all 18 PPAP elements (design records, engineering change documents, customer engineering approval, DFMEA, process flow, PFMEA, control plan, MSA, dimensional results, material/performance test results, initial process studies, qualified lab documentation, appearance approval report, sample parts, master sample, checking aids, customer-specific requirements, Part Submission Warrant), marking which are required to be submitted vs. retained at my level.
2. For each element: status (done / in progress / missing), what "complete" looks like, and common rejection reasons (e.g. dimensional results not covering every print characteristic, capability studies from too few parts, MSA not on the gauges actually used, documents at different revision levels).
3. A backward-scheduled plan from the due date, showing the critical path (usually the trial run, then dimensional layout and capability studies).
4. A draft note to the customer quality engineer if any element will be late, asking about interim approval.
Check the customer's own manual, which overrides the generic AIAG requirements. Do not fill in results or approvals; mark them [ADD].
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- DETAILS
- Level 1-5; Level 3 if not stated
- DATE
- planned or completed run size, date, line
- ADD
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Price and document a change order before doing extra workA change order with cost breakdown, schedule impact, and justification that the owner or GC can approve quickly.
- Write an after-action report and improvement planAn after-action report that rates performance against each objective, finds root causes, and produces a tracked improvement plan.
- Write a control plan for a production processA control plan that turns my product and process characteristics into what to check, how, how often, and what to do when it fails.
- Write a shift handover note so nothing falls through the cracksA structured handover from one shift to the next covering open issues, safety, status, and what the next shift must do first.