How to Run a Stage-Gate Quality Review
Use project gates as real quality decisions, not schedule checkpoints.
What a how-to is not
A how-to is SPEQ’s practitioner method, not a procedure. It does not replace your own SOP, it is not a validated approach, and the judgement calls in it belong to your quality unit.
A stage-gate quality review is the go/no-go decision at a project phase boundary, where quality confirms the deliverables and criteria for that stage are met before the project proceeds. Done well it prevents a project carrying unresolved quality risk into the next, costlier phase.
- 1
Define the gate criteria in advance
Define the gate criteria in advance and publish them, so that passing is a matter of evidence rather than of persuasion. Criteria set at the gate itself will be shaped by what has been achieved, which inverts the whole mechanism. Each criterion should name the deliverable and the state it must be in — approved, executed, closed — rather than describing a topic to be discussed.
- 2
Assess deliverables against criteria
Assess the deliverables against those criteria on evidence, with the assessors including people who are not accountable for the schedule. A gate reviewed only by the project is a self-assessment, and the pressure at a gate is always in one direction. Record what was examined, not only the conclusion, because the examination is what later makes the decision defensible.
- 3
Decide go / conditional / no-go
Decide go, conditional go, or no-go, and treat conditional as a real state with teeth rather than as a polite yes. A conditional pass must name the condition, its owner, its date, and what happens if it is not met — and someone must be willing to act on that last part. Conditions without consequences are how a gate becomes a formality.
- 4
Track conditions to closure
Track conditions to closure outside the meeting, with the same visibility as any other commitment, and verify closure on evidence. The characteristic failure of stage gating is a series of conditional passes whose conditions accumulate unclosed, so that by the final gate the project is carrying a backlog nobody has aggregated. Reviewing the open condition list at each gate prevents exactly that.
- 5
Document the decision
Document the decision, its basis, the dissent if there was any, and who made it. Gate records are among the first things an inspector or an auditor reads when asking how a facility came to be in its current state, and a record showing that a known gap was consciously accepted with a rationale reads very differently from one showing it was never discussed.
- !Gates treated as schedule formalities that always pass under deadline pressure.
- !Criteria negotiated at the meeting rather than defined in advance.
- !Conditional passes whose open items are never tracked to closure.
- !No quality independence, so the team reviews its own work.
How to Run a Stage-Gate Quality Review: frequently asked questions
Common questions on run a stage-gate quality review.
What is a stage-gate quality review?
A go/no-go decision at a project phase boundary where quality confirms the stage’s deliverables and acceptance criteria are met before the project proceeds. It stops unresolved quality risk from carrying into the next, more expensive phase.
What happens at a conditional pass?
The project may proceed but with defined open items that must be closed, each with an owner and due date, tracked to completion. Conditional passes are legitimate only when the conditions are genuinely tracked — otherwise they become a way to bypass the gate.
Why must gate criteria be defined in advance?
So the decision is objective. Criteria negotiated during the review under schedule pressure tend to drift toward "pass," defeating the gate’s purpose of catching quality risk before it advances.