Layered PPAP Submission Audit

It covers a Level 3 PPAP package review from the submission warrant through closure. The template checks administrative alignment, design records, PFMEA, control plan, dimensional evidence, capability data, material and test records, and any customer-specific requirements. It is built to verify that the submitted package is complete and internally consistent before customer review.

Yes, it is structured for a Level 3 submission, where the full package is typically expected. If your customer requests a different submission level, you can clone the template and remove or add evidence requirements as needed. The audit logic still helps for other levels, but the checklist is tuned to Level 3 expectations.

Quality engineers, supplier quality engineers, manufacturing engineers, or APQP/PPAP coordinators usually run it. The reviewer should understand the part, the process flow, and the customer’s specific submission rules. For high-risk parts, it is useful to have both quality and manufacturing sign off before the package is released.

Run it before every customer submission and again whenever the package changes after review. It is also useful after engineering changes, process changes, tooling moves, supplier changes, or when a previous submission was rejected. For recurring parts, many teams use it as a gate before each resubmission.

Common misses include mismatched part numbers across documents, outdated revisions, PFMEA and control plan not matching the actual process, missing special characteristic traceability, and incomplete dimensional evidence. Teams also overlook customer-specific forms, missing approval signatures, or capability studies that do not meet the stated acceptance criteria. This template is designed to surface those gaps before the customer does.

The template is organized around the standard PPAP element set used in AIAG-based submissions. It helps confirm that the required documents are present, current, and consistent with the submitted part and process. It does not replace the customer’s own PPAP manual, so customer-specific additions should still be checked.

Yes, and you should if the customer has a unique index, naming convention, or evidence order. Add fields for customer portal IDs, approval references, special test methods, or required attachments. The structure is flexible enough to support automotive, industrial, and other supplier submission workflows.

Yes. The checklist can be used alongside PLM, QMS, shared drives, or supplier portals as long as the reviewer can verify revision status and traceability. Many teams link each checklist item to the source document, file path, or approval record so the audit trail is easy to follow.

Record the deficiency clearly, identify the missing or mismatched evidence, and assign an owner and due date before the package is released. If the issue affects a special characteristic, capability result, or approval status, treat it as a blocking non-conformance until corrected. The goal is to close gaps before submission, not after customer rejection.