Gates are predefined checkpoints between project phases where stakeholders decide whether the project should move forward, change direction, pause, or stop. They\u2019re used to review progress, risks, and the business case against clear criteria before committing more time and budget.<\/p>\n"},{"question":"What is a stage gate?","answer":"
A stage gate is a go\/no\u2011go decision point in a structured Stage\u2011Gate\u00ae\u2011style process, often used in product development. At each gate, decision makers review results from the current stage and decide whether to release funding and resources for the next stage.<\/p>\n"},{"question":"What is a phase gate?","answer":"
A phase gate sits at the end of a project phase \u2014 such as initiation, design, or planning \u2014 and confirms that the work for that phase is complete and meets agreed standards. Only once the phase gate is passed does the project move into the next phase.<\/p>\n"},{"question":"What are the basic steps of a gate review?","answer":"
Gate reviews typically involve three high-level phases \u2014 preparation, evaluation, and decision-making \u2014 which are carried out through a structured, multi-step process. In practice, this includes defining criteria, reviewing evidence, assessing risks, and documenting a clear go\/no-go decision with next steps.<\/p>\n"},{"question":"How many gate reviews should a project have?","answer":"
Most projects benefit from 3\u20135 gate reviews aligned with major milestones, such as post\u2011charter, end of design, mid\u2011execution, pre\u2011launch, and post\u2011implementation. More complex or higher\u2011risk initiatives may add extra gates at critical technical or regulatory points.<\/p>\n"},{"question":"What happens if a project fails a gate review?","answer":"
If a project fails a gate review, it might be stopped entirely (Kill), sent back for rework in the current phase (Recycle), or put on hold until specific issues are resolved (Hold). In some cases, it receives a \u2018Conditional go\u2019 with clear remedial actions and deadlines before it can fully proceed.<\/p>\n"},{"question":"Can gate reviews work with Agile methodologies?","answer":"
Yes. In Agile environments, you can align gate reviews with major release boundaries, program increments, or key feature deliveries rather than traditional waterfall phases. The mindset is the same \u2014 use evidence and criteria at key points to make informed go\/no\u2011go decisions without unnecessarily blocking iterative delivery.<\/p>\n"},{"question":"How do teams manage gate reviews across multiple projects?","answer":"
Teams typically use standardized templates, shared criteria, and portfolio-level dashboards to track gate outcomes across projects. Centralizing gate reviews in one system makes it easier to compare initiatives, spot risk patterns, and ensure decisions are applied consistently.<\/p>\n"}]}],"activate_cta_banner":false,"hide_time_to_read":false,"disclaimer":"","cornerstone_hero_cta_override":{"label":"","url":""},"menu_cta_override":{"label":"","url":""},"show_contact_sales_button":"default","override_contact_sales_label":"","override_contact_sales_url":"","custom_header_banner":false,"parse_from_google_doc":false,"show_sidebar_sticky_banner":false,"sections":[{"acf_fc_layout":"content_1","blocks":[{"main_heading":"","content_block":[{"acf_fc_layout":"text","content":"
Gate reviews allow stakeholders to decide whether to continue, change, or stop a project at specific checkpoints.<\/p>\n
Projects often fail not through lack of effort, but because nobody formally stops or reshapes work that\u2019s no longer worth doing. Over time, these \u201czombie\u201d projects quietly absorb budget, focus, and capacity.<\/p>\n
In this guide, we\u2019ll explain what a gate review is and why they are so important. Then we\u2019ll discuss who, when, and how you should conduct a gate review effectively.\u00a0 Plus, we\u2019ll show you how to make gate reviews consistent, visible, and much easier to run at scale with a platform like monday work management.<\/p>\nGet started<\/a>\n"}]},{"main_heading":"Key takeaways","content_block":[{"acf_fc_layout":"text","content":" A gate review in project management is a formal go\/no\u2011go decision point between project phases. Independent stakeholders assess progress, risks, and the business case against predefined criteria to decide whether the project should continue, change direction, or stop, strengthening governance<\/a> and preventing sunk\u2011cost projects.<\/p>\n A gate review has 5 possible outcomes:<\/p>\n In a literal sense, it is a gate between phases or stages of a project, where the gatekeeper decides whether the project should proceed to the next stage. You can\u2019t complete a phase or stage and cross to the next one until you pass through the gate.<\/p>\n"},{"acf_fc_layout":"image","image_type":"normal","image":302087,"image_link":""},{"acf_fc_layout":"text","content":" (Source)<\/a><\/p>\n By enforcing these decisions at clear checkpoints, gate reviews keep governance robust and stop projects that consume budget without delivering value.<\/p>\n In many organizations, stage gates and phase gates are used interchangeably, but they describe slightly different perspectives on the same idea.\u200b\u200b<\/p>\n Both types of gates act as structured go\/no\u2011go checkpoints that protect your budget and help you avoid pushing projects forward solely based on time and money spent.<\/p>\n Other common terms for gate reviews include:<\/p>\n While both meetings involve project data, their fundamental purpose and authority levels differ significantly. Regular reviews focus on how<\/i> the work is progressing, while gate reviews question if<\/i> the work should continue.<\/p>\n\n\n
\n
Stage gates, phase gates, and other related terms<\/h3>\n
\n
\n
Gate reviews vs. regular project reviews<\/h3>\n