Gate Review in Simple Terms
A product launch is split into phases, and each phase ends with a gate. At the gate, the team shows the status of every required deliverable, open risks and actions. Reviewers then decide: go, go with conditions, hold, or stop. In APQP, gates typically sit at the end of each of the five phases.
How It Works
- Prepare: the team updates the status of each deliverable, often shown as green, yellow or red.
- Present: the project lead walks through deliverables, risks, timing and cost.
- Decide: reviewers give a go, conditional go, hold or stop decision.
- Record: decisions, owners and due dates for open actions are documented.
Typical deliverables checked include the DFMEA, DVP&R, process flow, PFMEA, control plan and capability results.
Example
At the phase 3 gate for a new pump housing, the PFMEA and pre-launch control plan are complete, but the fixture for the leak test is two weeks late. Management gives a conditional go: the team can start the trial run preparation, but the fixture must be in place before the phase 4 gate.
Why It Matters
- Problems are raised while there is still time to fix them.
- Leaders make decisions on evidence, not opinion.
- Each gate creates a record of what was approved and when.
OperaHive APQP software manages phase tracking, deliverables and gate reviews. See the APQP guide for the full process.