Stage Gate Process: A Guide to Capital Project Approvals

Franzl Shannon
Post author:
Franzl Shannon
Doug Vincent
Contributor:
Doug Vincent
Jackson Row
Reviewed by:
Jackson Row
Published:
Oct 30, 2024
Updated:
Nov 3, 2026
Stage Gate Process: A Guide to Capital Project Approvals

The stage gate process divides a project into stages, with approval points that determine whether work can proceed. In capital projects, these gates help owners assess the proposal and its costs before authorizing further spending. Each decision should establish what can happen next and any conditions the project team must meet.

Key Takeaways
  • Each gate authorizes a defined next step. Approval to investigate a proposal does not commit funding for construction.
  • Agree on approval criteria before preparing submissions so the team knows what evidence decision-makers need.
  • A gate review can authorize progress, pause a proposal, request revisions, or stop further investment.
  • Match review requirements to project complexity. A refurbishment in an operating facility may need more oversight than a higher-value new build.
  • Record the approved scope, spending limit, and conditions so later commitments stay within the authority granted.

What Is the Stage Gate Process?

The stage gate process is a project management framework that separates project work into stages, with formal decisions between them. Also called a phase gate process, it helps owners decide whether a project is ready for its next commitment.

A stage contains the work needed to develop the project, such as investigating feasibility or preparing tender (bid) documents. A gate is the decision point where an authorized person or committee reviews that work and determines how to proceed.

Passing a gate authorizes a defined next step. For example, feasibility approval may release money for consultants to develop a detailed proposal. The full project investment requires a separate decision once that information is available. The number of gates and their approval requirements depend on the organization and the project’s complexity.

Feasibility investigation passes through a review and decision gate before detailed proposal development.
The stage gate process divides project work into stages, with approval decisions determining whether and how work can proceed.

What Decisions Can Be Made at a Stage Gate?

A gate decision determines whether the project can proceed, needs further work, or should stop. Completing a stage does not automatically authorize the next commitment. The main outcomes are:

Decision What It Means for the Project
Proceed Authorize the next stage, with an agreed scope and allocated resources.
Hold Pause the proposal until circumstances change, such as funding becoming available.
Revise and resubmit Request specific investigations or changes before reconsidering the proposal.
Stop End the proposal because further investment is no longer justified.

An owner may also approve a defined scope subject to conditions. The decision should state what work can proceed and what must be resolved before further commitments.

When Should You Use a Stage Gate Process?

Use a stage gate process when a project needs investment decisions as its scope, costs, and risks become clearer. It helps owners establish approval points before committing to further work or expenditure.

Staged approvals are particularly useful in these situations:

  • The project’s feasibility is uncertain: The owner can authorize investigations or preliminary design before deciding whether to fund the proposed development.
  • Financial commitments increase as work progresses: Separate approvals allow the owner to review the business case before commissioning detailed design or awarding a construction contract.
  • Several projects compete for funding: Decision points help owners assess which proposals are ready to proceed and how they fit within available funding.
  • Funding depends on specific approvals: Board committees or grant providers may require supporting evidence before releasing funds or permitting procurement to proceed.

Set the approval points early, before appointing consultants or approaching the market. Allow time for each review in the construction project schedule so the team can address questions before the next commitment.

How the Stage Gate Model Works in Project Management

The stage gate model divides project work into stages, with decisions about whether and how to proceed between them. Each gate reviews the available evidence and defines what the team is authorized to do next.

The model is most closely associated with Robert G. Cooper’s Stage-Gate work in new product development, which uses discovery plus five stages. Construction owners adapt the same idea to capital projects, with gates around the business case, procurement, and readiness for use.

Stage 0: Proposal

Identify the need or opportunity and outline the intended outcome. Prepare an initial scope and indicative cost, explaining why the proposal warrants further investigation.

Gate 1: Decision to investigate. The authorized decision-maker determines whether to allocate resources to develop the proposal. This may include limited funding for feasibility studies or preliminary consultant work.

Stage 1: Investigation

Assess whether the proposed project is feasible and justified. Investigate options and develop the business case, including estimated costs, funding requirements, and significant risks.

Gate 2: Decision to initiate. Review the findings and determine whether the project should proceed. Approval should specify the authorized scope, available funding, and any conditions requiring further work.

Stage 2: Planning and execution

Develop the project plan and deliver the approved work. In construction, this can include design development, procurement, and construction.

Additional checkpoints can sit within this stage. These may include project plan approval and reviews before major commitments. For example, the owner may require a separate tender approval before authorizing a construction contract.

Gate 3: Decision to launch or enter use. Assess whether the deliverable is ready for its intended purpose. For a constructed facility, the review considers commissioning results, operational readiness, and required approvals.

Readiness-for-service reviews are an established feature of capital project frameworks, such as the UK government’s Gate 4 readiness for service review.

Stage 3: Post-launch monitoring

In this model, the monitoring stage focuses on performance after launch or handover. Assess whether the deliverable meets its intended needs and identify outstanding issues requiring action.

Project monitoring also occurs throughout planning and execution. The separate stage shown here provides a period for assessing initial performance in use.

Gate 4: Decision to close. Confirm that project closure requirements have been met and assign responsibility for remaining actions. Some benefits may take longer to measure, so arrangements for reviewing them can continue after closure.

Stage 4: Lifecycle management

After project closure, the responsible operational team continues managing the delivered asset or service. Ownership of ongoing activities and outstanding obligations should be agreed before the project team finishes.

For a constructed facility, this includes maintenance and monitoring operational performance. Findings can inform future refurbishment or replacement proposals. Lifecycle management extends beyond the project itself and connects its outcomes with the organization’s longer-term needs.

Stage gate model with five stages and four gates, plus approval checkpoints during planning and execution.
Gate decisions establish whether a project can advance, while checkpoints during delivery address commitments within an approved stage.

Stage Gate Process Example: Staged Approvals in School Capital Projects

Our school capital program illustrates how staged approvals apply to project funding and procurement. Endorsing a master plan establishes the long-term direction for a campus. Individual projects then require separate decisions as schools seek funding for investigations and approval to proceed with construction. For projects requiring central approval, the process includes these decision points:

Decision Point What Happens
Master plan endorsement Schools identify projects and priorities over the next 10–15 years, with order-of-magnitude costs. Head office reviews the plan before the board considers it. Endorsement establishes the direction without committing a budget to each project.
Feasibility approval A school proposes a project with an initial justification and indicative cost. Approval allows limited consultant spending to develop a formal application.
Capital development approval The detailed application explains the educational need and financial implications, including borrowing requirements where relevant. A committee of the board considers this application.
Tender approval The project manager leads the tender review and provides a recommendation. Head office reviews it before the CEO’s decision. Following approval, we update the budget using the tender figures and arrange contract documentation.

To illustrate, a school might propose a covered court with an indicative cost of $750,000. The need could include shelter from rain and sun, alongside demand from community groups interested in using the facility.

We might authorize $50,000 for consultants to develop the proposal. Their work informs the detailed application and can identify additional requirements, such as lighting. The school then presents that information for the project approval decision.

School teams that manage these approvals across a whole program can track each project’s phases, stages and gates in project management software for education.

Benefits of the Stage Gate Process

A stage gate process helps owners make investment decisions as project information develops. It creates opportunities to address unresolved issues before committing to further work.

  • Controlled spending: Owners can authorize limited investigation or design work before deciding whether to fund a larger commitment.
  • Earlier resolution of scope issues: Reviews can identify missing requirements while the team still has time to investigate options and revise the proposal.
  • Clear approval responsibilities: Defined gates establish who can authorize the next step and what information they need to make that decision.
  • Better coordination across projects: Reviewing proposals against organizational priorities is a core part of construction portfolio management and helps owners consider competing funding needs and delivery capacity.

Gate reviews give owners a chance to reassess whether the expected benefits still justify the cost. If tender prices exceed the business case estimate, the owner can reconsider affordability before committing to the construction contract.

Challenges of the Stage Gate Process

Stage gates require time and resources to prepare submissions and make decisions. Poorly designed reviews can delay progress or add administrative work without resolving the questions that matter. The main challenges arise when review requirements and decision-making responsibilities are unclear:

Challenge How It Affects the Project
Delayed decisions Incomplete submissions or unavailable decision-makers can hold up consultant appointments, procurement, or other planned work.
Excessive documentation Requiring the same level of detail for every project can place unnecessary demands on smaller, straightforward proposals.
Unclear review criteria Teams may prepare information that does not address the decision being requested, leading to repeated submissions.
Outdated approval assumptions Changes in scope, pricing, or funding can undermine an earlier decision. The team needs to recognize when further approval is required.

When reviewers request further work, they should identify the specific gaps and the evidence needed for reconsideration. Clear feedback gives the project team a defined task and helps avoid repeated submissions that leave the same questions unresolved.

Stage gate benefits and challenges, comparing spending control and clear approval roles with delays and unclear review criteria.
Stage gates help owners control spending, but unclear criteria and excessive paperwork can slow approvals.

Tips for Managing Stage Gate Approvals

Before requesting approval, define the work the decision will authorize and the funding it requires. Reviewers also need enough information to assess whether the proposal is ready to proceed.

Limit consultant appointments to the next approval

Before approving a construction project, the owner needs enough information to assess its scope and cost. Preparing that information may require paid work from an architect or quantity surveyor.

In our process, feasibility approval allows a school to engage consultants to develop a detailed capital development application. A board committee then considers that application and decides whether the project can proceed.

The initial appointments should cover the work needed for that application. Keeping the scope limited controls how much the school spends before the committee makes its investment decision.

Involve a project manager while developing the proposal

Consider engaging a PM during feasibility, when consultants begin investigating the project and developing information for the investment decision.

Our process requires an external PM for projects over $2 million once the capital development application is approved. I see value in involving that person earlier, particularly for a complex build or refurbishment. Consultant work is already underway during feasibility, creating an opportunity for PM input before the detailed application is submitted.

Include the expected PM fees in the application’s project costing. The approval decision should account for the cost of managing delivery.

Assess delivery complexity alongside project value

A project’s budget helps determine who must approve it and whether an external PM is required. The work itself also affects how much oversight the owner needs.

For example, building classrooms on a new school site can be relatively straightforward. Refurbishing and extending a design and technology facility in an operating school requires coordination around existing facilities and school activities.

Assess whether the internal team has the construction expertise and available resources to manage that work. A school may choose an independent PM even when the project falls below its mandatory appointment threshold.

Identify grant approvals before planning the tender

Where a project receives grant funding, check whether the funding body must approve the release of tender documents. It may also require approval of the final tender selection.

These decisions sit alongside the owner’s internal approval process. Identify the required submissions and allow for the funding body’s review when setting tender and contract dates. The project team needs to know whose approval is required before each commitment.

Record the budget and conditions attached to tender approval

After approving a tender, update the project budget using the accepted tender figures. If the resulting project cost requires additional funding, provide a supporting case to the person authorized to approve the increase.

On one of our projects, the tender-based cost was higher than we had hoped. We approved the tender with a project cost target that required the team to preserve part of the contingency. Meeting that target meant carefully managing furniture, fittings and equipment, along with landscaping expenditure.

Record such conditions alongside the updated budget in a spreadsheet or project budgeting software. Later spending decisions need to account for the limits attached to the approval.

Prepare a focused gate review submission

Before preparing a submission, confirm the criteria the proposal must meet and who has authority to approve it. The required evidence should relate to the commitment being requested.

For example, a tender submission may include the tender evaluation report and an updated project budget. Reviewers assess whether the recommended tender meets the project requirements and whether the resulting commitment is affordable within approved funding.

Use the following checklist to organize the submission. Adjust the supporting documents to suit the decision and its approval criteria.

  • Decision requested: Specify the work or expenditure requiring authorization and the amount being requested.
  • Project justification: Explain the need and the outcome the proposed work should achieve.
  • Financial position: Provide the current estimate, available funding, and any borrowing or additional funding required.
  • Supporting evidence: Include the relevant feasibility findings, consultant advice, or tender evaluation.
  • Unresolved matters: Explain what remains uncertain and how it affects the requested commitment.
  • Approval conditions: Show whether earlier conditions have been addressed and identify any conditions proposed for the next stage.

Use a project stage gate template to document approval criteria and required deliverables, then record each gate decision and its conditions. For conditional approval, specify which work can proceed immediately and what must be resolved before further commitments are made.

Stage gate checklist covering the decision requested, project justification, financial position, supporting evidence, unresolved matters, and approval conditions.
A gate review submission should give reviewers enough evidence to assess the requested commitment, including uncertainties that could affect approval.

Make Each Stage Gate Decision Clear

Each gate should leave the project team clear about its authority to proceed and the conditions attached to that decision. For your next project, identify the commitments requiring approval and who can authorize them. Agree on the supporting evidence before scheduling each review, using the submission checklist above as a starting point.

FAQs About the Stage Gate Process

A milestone marks a significant event, such as completing a design package. A stage gate requires a decision about whether and how the project can proceed. A gate can appear as a milestone in the schedule, but reaching its scheduled date does not authorize further work.
No. The number and names of stages depend on the framework. The classic product development model uses five stages following discovery. Construction frameworks may organize reviews around business case approval, procurement, and readiness for use. The five-stage diagram in this article illustrates one arrangement.
A project manager can approve a gate only if the organization has delegated that authority to them. Otherwise, the PM prepares the submission and recommendation for the authorized decision-maker. In the school example above, the PM leads the tender review, while the CEO makes the approval decision.
Yes. An Agile Stage-Gate approach combines formal investment decisions with short cycles of development and feedback within stages. Teams can refine the solution through these cycles while retaining gates for decisions about continued funding and progression. Completing a sprint does not automatically mean the project has passed a gate.
A project stage gate template should map each stage to its required deliverables, approval criteria, and authorized decision-maker. Include space to record the decision, approved funding, and any conditions. Assign an owner and due date to outstanding actions so the team knows what must happen before further work proceeds.
Franzl Shannon

Written by

Franzl Shannon

A registered building contractor who spent more than twenty years running his own construction company, Franzl Shannon is now Director of Capital Projects at AngliSchools. A graduate of the Australian Institute of Company Directors, he also chairs the council of St Mark's Anglican Community School.

LinkedIn Icon
Doug Vincent

Contributions by

Doug Vincent

Doug Vincent is the co-founder and CEO of Mastt, the AI capital-project management platform used by governments, Fortune 500 companies, and consultancies across APAC, North America, and MENA. Before founding Mastt in 2019, he spent a decade at RPS delivering more than $2 billion in capital works, including the $2.1B Defence Navy Infrastructure program, and holds a CPSPM certification with the AIPM. He contributes content and speaks on AI in capital project delivery at Mastt.

LinkedIn Icon
Back to top

Take control of your next project

Get access to Mastt instantly and start automating work in minutes