APQP in a Spreadsheet Is the Most Common Automotive Launch Failure Mode
Every automotive supplier has a spreadsheet somewhere labeled “APQP Tracker.” It has five tabs, one per phase. It has a column for each of the 12 AIAG deliverables. It has a “Status” dropdown: Green, Yellow, Red.
The problem is not the spreadsheet. The problem is that a spreadsheet can’t enforce gates, capture signatures, or prove that a cross-functional team actually reviewed Phase 3 before production tooling was released. And that’s exactly what customer-specific requirements (CSRs) and IATF 16949 §8.3.4.1 are checking.
What APQP gate reviews are actually about
The AIAG APQP Second Edition framework defines five phases, each with a gate review before advancing. The gate review isn’t a milestone — it’s a documented, signed approval from the cross-functional team that the phase deliverables are complete and the program is ready to advance.
What auditors (and OEM customers) ask:
- Who approved Phase 3 before tooling was released?
- What was the date of approval?
- Were all required disciplines represented at the review?
- If Phase 3 was reopened after approval, who authorized the reopen and why?
A spreadsheet can show “Phase 3: Green.” It cannot show a timestamped signature from a named Quality Engineer, Process Engineer, and Customer Representative confirming that 12 specific deliverables were reviewed and accepted. That gap is what becomes a finding.
The reopen problem
One of the most common real-world scenarios in new product launch: a program passes Phase 3 gate review, production tooling is released, and then a design change or process change forces the team to revisit Phase 3 work.
In a spreadsheet, this typically means someone changes the tab back to “InProgress” — with no record of why, when, or who authorized it. In a subsequent audit or customer concern, the lack of that record creates ambiguity about whether the program was properly managed.
A proper APQP system should make gate reopens visible and traceable: who authorized the reopen, what the reason was, and what the approval path was to re-close the gate. That’s an immutable log entry, not a cell edit.
Deliverable tracking beyond a status column
The AIAG framework specifies 12 deliverables per phase. Some are mandatory for all programs; some depend on program type (New Part vs. Changed Part vs. New Process). Some can be waived with documented justification.
“Waived with justification” is a legitimate disposition — AIAG recognizes that some deliverables don’t apply to every program. But the waiver has to be documented: what was waived, the rationale, and who authorized the waiver. “We didn’t do the Prototype Build Plan because it wasn’t relevant” is not a waiver — it’s a gap.
A well-designed APQP system tracks deliverable status (NotStarted / InProgress / Approved / Waived / Overdue) with waiver justifications and signatures. The overdue flag is particularly useful — programs under schedule pressure tend to let deliverables slip into undocumented incompleteness.
The launch readiness scorecard
The Phase 5 gate review is the last opportunity to identify launch risks before SOP. A launch readiness scorecard should aggregate:
- Per-phase completion percentage
- Days remaining to customer SOP date
- Open high-priority PFMEA action items
- CAPA items that predate the program still unresolved
- MSA study results for process gauges
In a spreadsheet, assembling this scorecard requires pulling data from 4–5 different files and reconciling dates manually. In an integrated MES, it’s a query.
What to look for in APQP software
- Gate enforcement: Gates should block phase advancement without required signatures — not just track a checkbox
- Role requirement enforcement: The system should require specific disciplines at gate reviews, not just any 3 people
- Reopen log: Gate reopens should be immutable logged events with authorization signatures
- Waiver workflow: Deliverable waivers should require justification and sign-off
- MES integration: APQP deliverables like PFMEA, Control Plan, and MSA studies should link to live MES data — not be re-entered into the APQP tracker
See Qontiv’s APQP module for the five-phase gate framework, deliverable tracking, and launch readiness scorecard. For the full automotive quality module set (PFMEA, LPA, CAPA, MSA, Supplier Quality), see the automotive overview.
If you’re running a new program launch and want to see how a native-MES APQP workflow compares to your current spreadsheet approach, request a demo.