PPAP After Design Change: When to Resubmit and What to Redo

Contents
- Step 1: Confirm what your approval is anchored to (design record, submission level, customer-specific requirements)
- Step 2: Classify the change against AIAG notification and resubmission triggers
- Step 3: Notify the customer before implementing, and get the resubmission level in writing
- Step 4: Trace the change to the PPAP elements it touches (ballooned drawing, dimensional results, PFMEA, control plan, MSA, process studies)
- Step 5: Redo only what the change affects, and record why the rest is unaffected
- Step 6: Update the PSW and keep the design record, change documents and PPAP package linked
- Troubleshooting: common ways a PPAP goes stale after approval, and how to catch them earlier
- Conclusion
A signed Part Submission Warrant (PSW) clears one specific snapshot for production. Then a mechanical engineer widens a bore tolerance in CAD, an electrical engineer swaps a passive component, or a customer changes a surface finish requirement, and that baseline cracks. The PSW, dimensional results, control plan, and Process Failure Mode and Effects Analysis (PFMEA) still sit signed off in your quality archive. The part on the line no longer matches the approved design record.
Managing a PPAP after a design change means knowing whether the change needs an informal notification, a partial resubmission, or a full Level 3 production run. Suppliers usually get this wrong in one of two ways. They spend weeks on an unnecessary 18-element package for a cosmetic revision. Or they ship revised geometry without customer buy-in and get rejected on arrival.
This guide covers how to evaluate design changes against AIAG standards, get customer agreement, trace the change through the affected PPAP documentation, and record what stays untouched so your audits hold up.
Step 1: Confirm what your approval is anchored to (design record, submission level, customer-specific requirements)
Every Production Part Approval Process submission is tied to a precise design record. Before deciding how to handle a design modification, pull the approved PSW and read Section 1. Note the exact drawing number, drawing change level, revision date, engineering change order (ECO) reference, and customer part number. If your drawing revision was Rev C with ECO-1042, and engineering is now releasing Rev D, the current approval does not cover Rev D parts.
Next, check your original submission level as defined by AIAG. Most automotive and industrial equipment programs default to Level 3, which requires the PSW plus product samples and complete supporting data. Level 1 requires only the warrant. Level 4 or Level 5 involves custom requirements or on-site witness audits.
Finally, review your customer-specific requirements (CSRs). Stellantis, Ford, General Motors, and industrial OEMs each keep their own addendums to the standard AIAG guidelines. Some OEMs treat any change to a critical safety characteristic (such as inverted delta or diamond symbols) as an automatic Level 3 resubmission, however small the dimensional shift. Standard AIAG text does not override a signed OEM quality manual. Pin down your exact anchor points before you act.
Step 2: Classify the change against AIAG notification and resubmission triggers
AIAG PPAP 4th Edition addresses customer notification and submission requirements in Section 3, requiring suppliers to notify the authorized customer representative of planned design, process, or site changes. Sort your design change into one of three buckets: changes requiring prior notification and submission, changes requiring notification only, and changes handled entirely under internal change control.
Direct design changes almost always trigger notification. PPAP requires notifying the authorized customer representative of planned design, process, or site changes and obtaining approval prior to implementation. Even a relaxed non-critical tolerance that improves manufacturing yield means the part no longer conforms to the approved design record.
Separate design record changes from manufacturing-only adjustments. Modifying an internal cutter path without touching part geometry or surface finish might need only internal verification. But if the design change affects fit, form, function, durability, or government regulations, the AIAG standard requires written customer notification. Tandem links CAD changes in SolidWorks, Onshape, Fusion, or NX directly to engineering requirements and design intent. That shows whether an engineer altered a non-critical clearance or an active interface requirement before you classify the change.
Step 3: Notify the customer before implementing, and get the resubmission level in writing
Never ship parts with a design change on the strength of a hallway conversation with a resident engineer. Quality departments and supplier quality engineers (SQEs) run on documented approvals. Draft a formal design change notification with the current design record revision, the proposed revision, the technical rationale, and the target implementation date.
Ask your customer's SQE to define the resubmission requirements in writing. AIAG leaves the exact submission level for changes to the customer. The customer typically picks one of three paths:
Full PPAP resubmission (usually Level 3): common for structural revisions, material family changes, or safety characteristic shifts.
Interim approval or partial resubmission: common for minor feature adjustments, where the SQE asks for an updated PSW, ballooned drawing, and dimensional results for the affected features.
Written waiver: the SQE reviews your validation data, signs the change request, and lets you update your internal records under Level 1 retention without sending a physical binder.
Record the SQE's decision directly in your engineering change order system. If an audit comes two years later, an email from the SQE approving Level 1 retention protects your plant from a major non-conformance.
Step 4: Trace the change to the PPAP elements it touches (ballooned drawing, dimensional results, PFMEA, control plan, MSA, process studies)
Once the resubmission scope is confirmed, isolate which PPAP elements are affected. Don't guess. Follow the technical dependencies one by one.
Start with the design records. You need a newly ballooned drawing that matches the latest revision. Identify newly added dimensions, deleted callouts, and modified tolerances. Depending on the change and the customer's requirements, altered dimensions may require updated documentation for Element 9 (Dimensional Results). You measure the modified characteristics across a representative sample (typically 5 to 30 parts, depending on SQE instructions) and skip remeasuring every untouched dimension.
Next, check the process documentation. If geometry changed, determine whether the part now sits differently in machining fixtures or stamping dies. If it does, the Process Flow Diagram needs revision. Update the DFMEA to capture new failure modes or modified severity ratings, then cascade those updates into the PFMEA and Control Plan. If a new critical characteristic was established, run a Measurement Systems Analysis (MSA / Gage R&R) for the inspection gage and conduct initial process capability studies (Cpk / Ppk) to prove the process can hold the new tolerance. For verification test updates, cross-reference your DVP&R so test plans match the revised requirements.
Step 5: Redo only what the change affects, and record why the rest is unaffected
Resubmitting a PPAP after a design change doesn't mean starting from zero. Re-running a 1,000-hour corrosion test or redoing material characterization for a simple hole diameter shift burns engineering budget and delays the production schedule.
Point physical testing and data collection only at the affected features. If an ECO increases the chamfer on a non-critical edge from 0.5 mm to 1.0 mm, re-inspect that chamfer, update the ballooned drawing, and log the dimensional results.
To head off customer pushback or auditor scrutiny, build a clear Change Impact Assessment matrix and include it in your resubmission packet. For every unaffected element, state the technical rationale: "Element 10 (Material/Performance Test Results): Unaffected. Material composition, raw material supplier, and heat treatment specification remain identical to initial approval PPAP-2024-088." Documenting why an element was skipped shows you were thorough. Tandem gives mechanical engineers and quality leads an agentic engineering context layer to track CAD changes against linked requirements, so every downstream impact stays documented and the original design rationale stays intact.
Step 6: Update the PSW and keep the design record, change documents and PPAP package linked
The last operational step is completing the new Part Submission Warrant. In Section 1, enter the new drawing change level, the date of the change, and the customer ECO number. Check the box for "Engineering Change(s)" under Reason for Submission.
In the submission declaration section, verify that the tooling number, mold cavities, and manufacturing facility address are accurate. If the change used revised tooling or replacement inserts, declare the specific tooling identification. Put the customer approval letter or change authorization number on the warrant.
Keep a closed loop between your CAD system, PLM release records, and the quality archive. A common compliance trap: the plant produces parts against CAD Rev D while the quality department's folder still holds the Rev B PSW. Follow CAD revision history best practices to keep revision tags synchronized across engineering and quality files. File the customer-signed PSW, the change notification, the inspection reports, and the impact justification together under one change package identifier.
Troubleshooting: common ways a PPAP goes stale after approval, and how to catch them earlier
PPAPs rarely fail because a team forgot about quality requirements. They go stale through small disconnects that pile up across functional teams.
First, watch for tolerance creep in CAD models. A design engineer adjusts a fillet radius or clearance pocket in SolidWorks or NX to fix an assembly clash on the shop floor, but considers it too minor for an official drawing revision. Production machines the part to the new CAD geometry, and the approved drawing and dimensional results become invalid. Run scheduled CAD-to-drawing checks to catch unballooned geometry changes before parts reach the shipping dock.
Second, watch for tool maintenance drift. When an injection mold or stamping die wears down, tooling technicians recut cavities or weld inserts. If the recut tool moves the nominal feature dimensions away from the initial PPAP sample layout, process capability changes. Treat major tooling refurbishment as a potential PPAP resubmission trigger under AIAG Section 3.
Third, watch for informal supplier deviations. When Tier 2 suppliers substitute raw material grades because of supply chain disruptions, your Tier 1 PPAP is compromised. Enforce strict change notification protocols with sub-tier suppliers. Tandem helps hardware teams close these gaps by connecting requirements, CAD changes, and validation evidence in one system, so uncommunicated changes don't slip past quality gates.
Conclusion
A design change breaks your PPAP baseline the moment the CAD or drawing revision increments. Hiding minor changes or delaying customer notification invites recall liability and production holds. Your PPAP is not a static historical filing. It's an active contract tied to the current engineering state.
To keep your quality documentation, CAD models, and requirements in sync across engineering revisions, book a demo with Tandem at tandem.inc.
Visit Tandem
Tandem is the AI platform for hardware engineering — it connects requirements, CAD design changes, reviews, and engineering decisions in one system so design intent doesn't get lost. It sits inside real workflows (SolidWorks, Onshape, NX, plus PDM, Jira, Slack, Drive), captures CAD activity as Design Sessions that group related edits and explain what changed and why, and links those changes to a live Requirements Workspace and in-context Reviews. Built for hardware teams (Series A-C, 50-500 employees) moving from prototype to production.
Get startedSources
Frequently asked questions
When is a PPAP resubmission mandatory after a design change?
A resubmission is mandatory whenever a design change alters fit, form, function, durability, or material specifications, or when a drawing revision changes any dimension or tolerance. Under AIAG rules, suppliers must notify the customer prior to shipping production parts, and the customer determines whether a full or partial resubmission is required.
Does a minor drawing note change require a full Level 3 PPAP?
Rarely. While any change to the design record requires customer notification, customers typically assign a Level 1 submission (PSW only) or request a partial resubmission consisting of the revised ballooned drawing and updated PSW. Always obtain the customer's written agreement before assuming a Level 1 submission is acceptable.
Can I ship production parts while waiting for PPAP approval after a design change?
No, you cannot ship production parts to the new design revision without either an approved PSW or a formal interim approval. If production schedules require shipping before full PPAP sign-off, request a customer-signed deviation or interim approval sheet specifying the authorized quantity or date range.
What is the difference between interim PPAP approval and full PPAP approval?
Full approval means the part or material meets customer specifications and is authorized for production shipment, though the specific elements submitted depend on the assigned PPAP level and customer requirements. Interim approval permits a supplier to ship a specified quantity of parts or ship for a limited timeframe while non-critical documentation, tooling adjustments, or long-term capability studies are finalized.
Related reading
Written by
Tandem
Tandem is the AI platform for hardware engineering — it connects requirements, CAD design changes, reviews, and engineering decisions in one system so design intent doesn't get lost. It sits inside real workflows (SolidWorks, Onshape, NX, plus PDM, Jira, Slack, Drive), captures CAD activity as Design Sessions that group related edits and explain what changed and why, and links those changes to a live Requirements Workspace and in-context Reviews. Built for hardware teams (Series A-C, 50-500 employees) moving from prototype to production.