PPAP tracking in a spreadsheet works until it doesn't

A supplier quality engineer at a Tier 2 stamping plant is prepping for a customer surveillance audit next week. She opens the PPAP tracker, an Excel workbook with a tab per part, and finds two control plan revisions attached to the same part, a PSW referencing a drawing revision superseded four months ago, and no record of who approved the change in between. The audit is in six days.

Why it happens

None of this usually starts as carelessness. A spreadsheet handles PPAP fine for a handful of parts and one customer. The trouble shows up as the part count, the revision history, and the number of OEMs all grow at once.

• One workbook, or one tab per part, with no single field that says which revision is the current, approved one
• Engineering changes that update the drawing or control plan without a matching, required update to the PPAP file
• Submission deadlines tracked in a separate calendar or inbox, disconnected from the document status itself
• No consistent naming or sign-off trail, so reconstructing what happened means searching old emails and asking around

What it costs

The most visible cost is hours: a supplier quality engineer spending half a day or more before every audit reconciling which revision actually shipped. The costlier version shows up downstream, when a missed submission deadline holds up a program launch, or an auditor finds a package that doesn't match the part running on the line, which becomes a finding of its own.

Diagnose before you automate

Before assuming the fix is new software, it's worth spending a few hours checking where the breakdown actually is.

1. Pull the PPAP status for your five most recently launched parts and check whether the revision level in the tracker matches the revision level on the current engineering drawing
2. Trace one engineering change order from approval to PPAP update and time how long it took, and who was responsible for making the update
3. Ask whoever preps for customer audits how much time goes to reconstructing history versus simply retrieving it
4. Check whether submission deadlines live anywhere other than a person's memory or a calendar reminder

Where automation helps, and where it doesn't

When it's a process fix

If the diagnosis turns up a missing step rather than a missing system, for example no rule that an engineering change triggers a PPAP review, or no single owner for the tracker, the fix is a process change. Define who updates the tracker when a drawing revises, and require a sign-off field before a submission counts as complete. That costs nothing to implement and is worth doing regardless of what tooling comes next.

When it's worth automating

If the number of parts, revisions, and OEM programs has grown past what one spreadsheet can track reliably, for example dozens of active parts across several customers, each with its own submission calendar, the case for automating is more straightforward: version control that locks a document once it's approved, a submission calendar that flags a deadline before it's missed, and routing that sends a document to the right approver automatically instead of by email. That's document routing and status tracking, not a judgment call, so it doesn't need AI to do the job.

The takeaway

A spreadsheet can carry PPAP tracking a long way. It usually stops working once the number of parts, revisions, and OEM requirements outgrows what one person can hold in their head or reconstruct from old emails. Before buying new software, it's worth checking whether the real gap is a process step nobody owns, since that fix is cheaper and often more urgent.