Guide

Stage-gate reviews: a practical guide for 2026

Short answer

A stage-gate review is a planned decision point where a sponsor or board decides whether a project continues, changes or stops, against criteria agreed in advance. Keep each gate to one decision, five to seven criteria, and a written record of the outcome and any conditions.

What a gate is, and is not

A gate is a decision, not a document. The pack exists to answer one question: should we put the next tranche of money and people into this project?

A gate is not a status meeting. Progress updates belong in the weekly report. The gate asks whether the business case still holds now that you know more than you did last time.

What to check at each gate

Most PMOs need five gates. Use your own names for them, but keep the questions sharp.

Gate The question Evidence Who decides
1 · Idea Is this worth a business case? One-page idea, link to an objective Portfolio board
2 · Business case Should we fund it? Costs, benefits, options, top risks Investment committee
3 · Plan and design Are we ready to build? Baseline plan, design, resourcing Sponsor
4 · Go-live Is it safe to deploy? Test results, readiness, rollback plan Sponsor and operations
5 · Close Did we deliver, and what did we learn? Benefits plan, lessons, handover Sponsor and PMO

Who decides

One named decision-maker per gate. Committees can advise, but a gate with no single accountable person turns into a negotiation. Write the decision-maker into the charter at gate 1.

The three possible outcomes

  1. Go. The project moves to the next stage with its current baseline.
  2. Go with conditions. The project moves on, but each condition has an owner and a due date, and it is checked before the next gate opens.
  3. Stop or reshape. Stopping a project early is a good outcome when the evidence says so. Record why, so the portfolio learns from it.

Keeping gates light

  • Agree the criteria at gate 1, not on the day of the review.
  • Cap the pack at what the decision needs. If nobody reads a section, cut it.
  • Send the pack 48 hours ahead, and use the meeting to decide, not to present.
  • Record conditions with an owner and a date, and check them at the next gate.
  • Time-box the meeting to 30 minutes for most projects.

FAQ

How many gates should a project have? Five suits most PMOs. Small projects can combine gates 3 and 4; large programmes may add a gate per release.

Can a gate approve with conditions? Yes. Record each condition with an owner and a due date, and check it before the next gate opens.

Who should attend a gate review? The decision-maker, the project manager, the PMO and anyone whose sign-off is a criterion (for example security or finance). Everyone else can read the record.

Sources

  1. Project Management Institute, A Guide to the Project Management Body of Knowledge (PMBOK Guide). [editor: add edition and link]
  2. PeopleCert / AXELOS, PRINCE2 7th edition (2023): management stages and management by exception. [editor: add link]
  3. Robert G. Cooper, Winning at New Products: the Stage-Gate model. [editor: add edition]

See your portfolio the way your sponsor should

SprintPM opens soon, in English and Arabic. Join the waitlist to be among the first in.