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 can AI improve gate reviews?","answer":"
AI improves gate reviews by automating risk detection, surfacing budget anomalies and timeline slippage before the review meeting, and reducing the manual effort of compiling status reports. AI agents can monitor projects continuously between gates, flagging issues as they emerge rather than waiting for the next scheduled checkpoint. On monday AI Work Platform, features like monday agents, monday sidekick, and AI-powered dashboards give committees real-time, data-driven insights so they can make faster, more informed go\/no-go decisions.<\/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":"
Every project reaches a point where the question isn’t “how’s it going?” but “should we keep going?” That’s where gate reviews come in. A gate review is the structured moment when stakeholders review the evidence, like progress, risks, budget, and strategic fit, and decide whether a project moves forward, changes direction, or stops entirely.<\/p>\n
Without gate reviews, organizations end up funding projects on momentum instead of merit. Budgets quietly drift, scope creeps, and teams keep building things that nobody re-evaluates after the original business case is approved.\u00a0Gate reviews exist to prevent exactly that: they force a deliberate, criteria-based decision at the moments where it matters most.<\/p>\n
In this guide, you’ll learn what a gate review is, when to hold one, who should be involved, and how to run an effective gate review process from start to finish. We’ll also cover how teams use the monday AI Work Platform<\/a> to centralize gate decisions, automate governance workflows, and give stakeholders real-time visibility across projects and portfolios.<\/p>\nGet started with monday.com<\/a>\n"}]},{"main_heading":"Key takeaways","content_block":[{"acf_fc_layout":"text","content":" A gate review, also called a stage gate<\/strong> or phase gate<\/strong> review, is a formal go\/no-go 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-cost projects.<\/p>\n A gate review has five possible outcomes:<\/p>\n In a literal sense, it’s a gate between phases or stages of a project, where the gatekeeper decides whether the project should proceed to the next stage. You can’t 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 prevent projects from consuming 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.<\/p>\n Both types of gates serve as structured go\/no-go checkpoints that protect your budget and help you avoid moving projects forward solely 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<\/em> the work is progressing, while gate reviews question whether<\/em> the work should continue.<\/p>\n"}]},{"main_heading":"Gate reviews in Agile, hybrid, and portfolio management","content_block":[{"acf_fc_layout":"text","content":" Gate reviews aren’t limited to traditional waterfall projects. The core idea, i.e., pausing at defined points to make evidence-based go\/no-go decisions, applies just as well in Agile, hybrid, and portfolio-driven environments.<\/p>\n In Agile environments, gate reviews are usually aligned with major release boundaries, program increments, or large feature milestones rather than fixed project phases. Instead of approving a full phase upfront, stakeholders review evidence such as customer feedback, delivery velocity, quality metrics, and business impact before approving continued investment.<\/p>\n The goal isn’t to block iteration, but to ensure that ongoing work still delivers value and aligns with strategic priorities.<\/p>\n Many organizations operate in hybrid mode, combining Agile delivery with traditional governance requirements. In these cases, teams may work iteratively day-to-day, while formal gate reviews occur at key funding, regulatory, or cross-departmental checkpoints. This allows teams to move quickly while leadership retains decision-making authority over risk, budget, and scope.<\/p>\n At the portfolio level, gate reviews shift focus from individual project execution to investment prioritization. Leaders compare initiatives across the portfolio to assess which projects should receive additional funding, be paused, be re-scoped, or stopped entirely based on strategic value, risk exposure, and capacity constraints.<\/p>\n Used consistently, portfolio gate reviews help organizations dynamically rebalance work rather than lock in outdated priorities for the entire year.<\/p>\n"}]},{"main_heading":"Why gate reviews are important","content_block":[{"acf_fc_layout":"text","content":" So why should your organization invest time in formal gate reviews when project teams are already stretched thin?<\/p>\n Gate reviews help teams make deliberate, data-driven decisions about whether projects should continue, change direction, or stop. They protect budgets, focus, and trust by structuring how major commitments are made.<\/p>\n Here are some of the benefits of gate reviews:<\/p>\n In 2026, AI-augmented governance is making gate reviews even more valuable, teams can surface risks earlier and reduce reliance on manual status reporting, so the committee spends its time on decisions rather than data gathering.<\/p>\n"}]},{"main_heading":"When to hold a gate review","content_block":[{"acf_fc_layout":"image","image_type":"normal","image":226644,"image_link":""},{"acf_fc_layout":"text","content":" Gate reviews are most effective when they’re tied to moments where the project’s risk profile, investment level, or strategic commitment changes. In practice, this usually means holding a gate review at the end of each major project phase, before approving additional time, budget, or resources.<\/p>\n As part of project planning, teams should define both the phases of the work and the decision points between them, so gate reviews are expected, not reactive, throughout the project lifecycle<\/a>.<\/p>\n Typically, projects move through 5 high-level phases, each with a natural gate review moment:<\/p>\n A gate at the end of the project initiation<\/a> confirms that the problem is worth solving, the business case is sound, and the project is aligned with the current strategy before meaningful investment begins.<\/p>\n A gate at the project planning<\/a> phase validates that scope, timelines, costs, and risks are clearly understood and realistic, and that the team is ready to commit to execution.<\/p>\n Mid-execution<\/a> gate reviews assess whether delivery is on track, risks are under control, and assumptions made earlier still hold true before continuing at full speed.<\/p>\n Gate reviews at the project monitoring and control<\/a> phase focus on whether corrective action is needed, such as re-scoping, pausing, or reallocating resources, based on performance, risk, or external changes.<\/p>\n A final gate at the project closeout<\/a> confirms that objectives were met, deliverables are accepted, and lessons learned are captured before formally closing the project and releasing resources.<\/p>\n Note:<\/strong> Not every project needs a gate at every phase, but any point where failure, delay, or misalignment would materially impact the business is a strong candidate for a gate review.<\/p>\n"}]},{"main_heading":"The steering committee: Who to involve in a gate review","content_block":[{"acf_fc_layout":"text","content":" A gate review needs to be independent of the project’s day-to-day operations, so the project manager shouldn’t conduct it. Ideally, you want a steering committee<\/a> of independent reviewers with a stake in the business, because they’ll conduct a more rigorous review.<\/p>\n A steering committee typically includes C-level executives and departmental managers involved in the project. The gatekeeper, typically the most senior decision-maker on the committee, has final authority on the go\/no-go decision at each gate. But the committee can also include:<\/p>\n The main criteria are that they have sufficient seniority, experience, and time to conduct an effective review.<\/p>\n"}]},{"main_heading":"Portfolio-level gate reviews","content_block":[{"acf_fc_layout":"image","image_type":"normal","image":302098,"image_link":""},{"acf_fc_layout":"text","content":" While individual gate reviews focus on whether a single project should move forward, portfolio-level gate reviews look across multiple initiatives to determine where the organization should invest next.<\/p>\n At this level, decision makers assess projects collectively, comparing expected value, risk, strategic alignment, and resource demands, rather than evaluating each initiative in isolation. A project that passes its individual gate may still be paused or deprioritized if higher-impact work requires the same people or budget.<\/p>\n Portfolio-level gate reviews help organizations:<\/p>\n In large or fast-moving organizations, these reviews are essential for maintaining strategic focus as priorities evolve.<\/p>\n"}]},{"main_heading":"Seven steps to run an effective gate review","content_block":[{"acf_fc_layout":"text","content":" How do you move from understanding gate reviews to actually running one that drives results?<\/p>\n A gate review should feel like a structured, criteria-based decision workshop, not a routine status meeting. The goal is to decide whether the project should move forward, change direction, or stop, using evidence and predefined standards rather than gut feel.<\/p>\n Every organization will develop its own gate review process. However, a typical stage gate process includes the following steps:<\/p>\n Use these buckets to shape your criteria for each gate:<\/p>\n\n\n
\n
\n
Stage gates, phase gates, and other related terms<\/h3>\n
\n
\n
Gate reviews vs. regular project reviews<\/h3>\n
Gate reviews in Agile teams<\/h3>\n
Gate reviews in hybrid delivery models<\/h3>\n
Portfolio-level gate reviews<\/h3>\n
\n
Phase 1: project initiation<\/h3>\n
Phase 2: project planning<\/h3>\n
Phase 3: project execution<\/h3>\n
Phase 4: project monitoring and control<\/h3>\n
Phase 5: project closure<\/h3>\n
\n
\n
\n
Gate review criteria checklist<\/h3>\n