Stage-Gate in Engineering Projects: Phases and Criteria

Learn how to apply Stage-Gate in engineering projects to define phases, criteria, evidence, authority levels, and advancement decisions.

Check it out!

Stage-Gate is a governance model that organizes a project into development phases and establishes formal decision gates between them. At each gate, the organization verifies whether the project has maturity, evidence, resources, and risks compatible with the next level of commitment.

In engineering projects, advancing to the next phase does not simply mean continuing the schedule. The decision may authorize additional studies, supplier contracting, detailed design development, construction mobilization, energization, commissioning, or entry into operation. Each advance increases committed costs, reduces flexibility, and amplifies the consequences of an incorrect assumption.

Therefore, the value of Stage-Gate is not in creating more meetings or forms. The model must prevent the project from assuming commitments greater than the quality of the available information. An effective gate connects strategy, scope, requirements, risks, estimates, schedule, contracts, engineering, operations, and decision authority.

When integrated with PMO, Project Controls, and Owner’s Engineering, Stage-Gate creates an auditable trail: the organization knows which evidence supported the decision, which reservations remained, who approved advancement, and how conditions will be addressed.

What is Stage-Gate?

Stage-Gate is a structure in which work is divided into stages and each transition depends on a formal review. Stages produce information, studies, designs, and deliverables. Gates assess whether those results are sufficient to authorize the next phase.

The logic can be summarized as follows:

develop → verify maturity → decide → record conditions → advance or correct.

The names and number of gates vary according to sector, criticality, project size, contractual model, and asset lifecycle. There is no universal sequence that should be copied without adaptation.

The system needs to define:

the objective of each phase;
required deliverables;
technical and management criteria;
minimum evidence;
those responsible for preparation and review;
the authority that decides;
possible gate outcomes;
treatment of conditions;
recording and traceability;
relationship with baselines, contracts, and investments.

What management problem does Stage-Gate solve?

Projects often advance under schedule pressure, budget availability, or stakeholder expectations even when requirements, scope, and risks have not reached sufficient maturity.

Management problem	Consequence	Stage-Gate response	Expected benefit
Advancing with incomplete requirements	Changes and rework in subsequent phases	Maturity criteria before authorization	Greater scope stability
Contracting before technical definition	Non-comparable proposals and change orders	Procurement readiness gate	Better commercial-process quality
Detailed design started on weak assumptions	Successive revisions and productivity loss	Validation of the design basis	Less multidisciplinary rework
Construction mobilized without releases	Idle crews and blocked work fronts	Construction readiness gate	More responsible mobilization
Equipment purchased with unresolved interfaces	Incompatibility and late changes	Technical and interface review	Lower exposure to changes
Known risks without responses	Materialization during execution	Acceptable residual-risk criterion	Conscious decision on exposure
Approvals without defined authority	Ambiguous responsibilities	Gate owner and formal authority levels	Accountability
Reservations forgotten after the meeting	Conditions are not addressed	Record, owner, deadline, and workflow	Traceable closure
Entry into operation without readiness	Failures, open items, and operational risk	Commissioning and operational-readiness gate	Safer transition
Continuation based on sunk cost	Unviable projects remain active	Options to redirect, suspend, or terminate	Protection of capital and capacity

Stage-Gate does not eliminate uncertainty. It makes explicit the relationship between uncertainty, evidence, risk, and the level of commitment being authorized.

The gate should limit commitment to the project’s actual maturity. Authorizing procurement, mobilization, or operation based on weak information transfers uncertainty to phases where changes become more expensive and harder to control.

Learn about A3A Engenharia’s Engineering Project Management service.

What is the difference between a stage and a gate?

The stage is the phase in which the team produces work. The gate is the point at which an authority evaluates the results and decides the next step.

Element	Function	Example
stage	develop information and deliverables	prepare a feasibility study
gate	assess maturity and decide	approve basic-design development
deliverable	record the result of the work	alternatives report
criterion	define the approval condition	preferred alternative technically justified
evidence	demonstrate compliance with the criterion	approved comparative analysis
condition	record an open item compatible with controlled advancement	complete survey before detailed issue
decision	authorize, restrict, or interrupt	advance subject to closure of the action

Confusing stage and gate leads to structures in which the meeting only presents deliverables without assessing whether the maturity level is compatible with the requested decision.

Is Stage-Gate the same as the project lifecycle?

No. The lifecycle describes the phases through which a project passes. Stage-Gate adds governance criteria and formal decisions between those phases.

A lifecycle may include:

concept;
feasibility;
basic design;
detailed design;
procurement;
construction;
commissioning;
assisted operations;
closeout.

The Stage-Gate model asks at each transition:

which results should be ready;
what maturity level has been achieved;
which risks remain;
what commitment will be assumed;
who has authority to authorize it;
which conditions are acceptable;
what the consequence of not advancing is.

Are a gate, milestone, approval, and acceptance criterion the same thing?

No. These mechanisms may be related, but they have different purposes.

Mechanism	Main question	Outcome
milestone	did a relevant event occur?	milestone recorded in the schedule
document approval	can the document assume a given status?	revision approved or rejected
workflow	what is the flow of states and owners?	operational approval trail
acceptance criterion	does the deliverable meet the defined requirement?	acceptance, rejection, or open item
gate review	is the project ready to assume the next commitment?	governance decision
baseline approval	which reference becomes official?	approved plan for control
contractual decision	is an obligation, change, or payment authorized?	legal and commercial effect

A gate may require approved documents and satisfied acceptance criteria, but its decision is broader. It evaluates whether the project as a whole is ready to advance.

What decisions can result from a gate?

Reducing the outcome to “approved” or “rejected” limits governance. A more complete model may provide for:

Decision	Meaning	Application
go	criteria met and advancement authorized	start the next phase
conditional go	advancement allowed with controlled conditions	proceed without waiting for non-critical open items
hold	decision deferred pending new information	keep the project active without increasing commitment
recycle	work returns for completion or correction	increase maturity before a new review
redirect	strategy, alternative, or scope needs to change	reorient the project
terminate	project should not continue	close and preserve lessons and useful assets
defer	opportunity remains valid, but timing is not appropriate	reposition in the portfolio

Each organization should define its terms and consequences. A “conditional go” decision must have actions, owners, deadlines, closure criteria, and clear limits. Otherwise, it becomes informal approval of an immature project.

What types of gates can exist in engineering projects?

Not every gate has the same nature.

Type	Focus	Example
strategic	alignment with objectives and portfolio	authorize feasibility study
economic	feasibility, budget, and benefits	approve investment
technical	maturity of requirements, design, and interfaces	release detailed design
contractual	scope readiness for procurement	issue tender or request proposals
construction	availability of design, area, materials, and permits	authorize mobilization or work-front start
assurance	independent review of quality and risk	confirm estimate reliability
safety	risks to people, assets, and operations	authorize energization
operational	readiness of systems, people, and procedures	release startup or entry into operation
closeout	completeness of deliverables, documents, and obligations	accept and close the contract

In critical projects, some gates may require independent review. In smaller projects, a single meeting may consolidate different dimensions, provided the criteria remain clear.

How should gates be structured throughout the lifecycle?

An illustrative architecture may include:

Gate	Main decision	Typical evidence
G0 — framing	does the opportunity deserve analysis?	problem, objective, sponsor, and strategic alignment
G1 — feasibility	is there a technically and economically feasible alternative?	diagnosis, alternatives, risks, initial estimate, and benefits
G2 — definition	does the selected alternative have a sufficient basis for detailing?	requirements, scope, assumptions, interfaces, and contracting strategy
G3 — investment authorization	should the project receive resources?	Business Case, estimate, schedule, risks, and capability
G4 — procurement readiness	does the package have sufficient definition for the market?	basic design, specifications, quantities, criteria, and contract draft
G5 — execution readiness	is it responsible to start fabrication, construction, or implementation?	released design, area, materials, permits, safety, and execution plan
G6 — commissioning readiness	can the system be energized or tested?	mechanical completion, prior tests, procedures, risks, and open items
G7 — operational readiness	can the asset enter operation?	performance, documentation, training, spares, and response plan
G8 — acceptance and closeout	have obligations been met?	punch list, As-Built, warranties, acceptance, lessons, and transition

This sequence is not mandatory. Engineering-consulting projects may have specific gates for concept, basic, detailed, and final issue. Corporate portfolios may include prioritization and benefits gates.

How should gate criteria be defined?

Criteria need to be objective enough to guide preparation and review, but not so mechanical that they eliminate technical judgment.

A good criterion should have:

a clear statement;
decision purpose;
required evidence;
owner responsible for production;
party responsible for verification;
minimum maturity level;
acceptable tolerance or condition;
consequence of noncompliance;
relationship with risks and commitments;
approval record.

Weak criterion	Problem	More robust criterion
design is advanced	subjective	deliverables defined in the plan have been issued and critical interfaces resolved
budget is adequate	no reference	estimate has class, assumptions, contingency, and documented reconciliation
risks are addressed	generic	critical risks have owners, funded responses, and accepted residual risk
operations agrees	informal	operational requirements have been reviewed and approved by the designated authority
documents are ready	does not define status	mandatory documents are at the revision and status defined in the gate checklist
construction can start	does not verify constraints	design released, area available, safety approved, and critical materials confirmed

Are gate criteria and acceptance criteria different?

Yes. An acceptance criterion verifies a deliverable or result. Gate criteria assess overall readiness to advance.

For example, a basic design may meet the document acceptance criterion, while the procurement gate may still be denied because:

quantities have not been consolidated;
the estimate lacks adequate contingency;
the contracting strategy has not been approved;
a permit has not yet been obtained;
interface risks remain without owners;
the schedule does not account for critical supplies.

The Requirements, Evidence, and Acceptance Criteria Management solution helps structure the evidence layer used by gates.

How can maturity be assessed without turning the gate into a bureaucratic checklist?

Checklists are useful to ensure coverage, but they should not replace integrated analysis.

A mature review needs to assess:

consistency across documents;
quality of assumptions;
completeness of interfaces;
residual risks;
reliability of estimates;
schedule feasibility;
organizational capability;
contractual readiness;
consequences of advancement;
available alternatives.

A score may support comparisons, but it should not allow many low-criticality items to compensate for a blocking gap. Criteria can be classified as:

Class	Treatment
mandatory	absence prevents advancement
critical with condition	advance only with formalized action, deadline, and owner
recommended	gap does not block advancement but must be monitored
informational	recorded for context and learning

Governance must define which items are truly blocking and prevent the decision from being manipulated by the average score in a spreadsheet.

A checklist does not replace technical judgment. A critical safety, interface, permit, or readiness gap can prevent advancement even when most gate items are formally satisfied.

Learn about the Project Review and Technical Validation — Design Review service.

Who participates in a gate review?

The composition depends on the decision and risks involved.

Role	Typical responsibility
sponsor	be accountable for objectives and resources
gate owner	convene, ensure independence, and formalize the decision
project manager	present status, alternatives, and recommendation
Project Controls	validate baseline, performance, estimates, and forecast
technical authority	assess technical consistency and compliance
Owner’s Engineering	represent the owner’s technical interests
operations and maintenance	assess operability, maintainability, and transition
procurement and contracts	assess strategy, market, obligations, and commercial risks
finance	assess investment, contingency, and capacity
safety and environment	assess applicable risks and authorizations
legal	assess legal and contractual effects when necessary
PMO	maintain method, quality, and gate history
independent reviewers	perform assurance on critical topics

The team that produced the deliverables may explain and defend the work, but the decision authority must retain the ability to challenge it independently.

How should the RACI matrix be used in gates?

The RACI Matrix in Engineering Projects should distinguish at least:

who prepares the materials;
who verifies the evidence;
who recommends the decision;
who approves;
who executes conditions;
who is informed.

At critical gates, it may also be useful to separate:

technical authority;
financial authority;
asset owner;
safety authority;
contract manager.

Responsibility for preparing the presentation should not be confused with authority to approve advancement.

Which documents make up the decision package?

The gate pack should be proportionate to the decision. It may include:

Block	Content
executive summary	requested decision, recommendation, and main reservations
objectives and benefits	expected outcomes and strategic alignment
scope and requirements	inclusions, exclusions, maturity, and changes
engineering	documents, revisions, interfaces, and open items
schedule	baseline, milestones, critical path, and forecast
costs	estimate, commitments, contingency, and exposure
risks	major risks, responses, and residual risk
contracts	strategy, packages, responsibilities, and commercial issues
quality	reviews, nonconformities, and assurance
safety and permits	authorizations and blocking risks
operations	readiness, people, procedures, and documentation
alternatives	options, consequences, and recommendation
conditions	action, owner, deadline, and closure criterion

The package should not repeat the entire project record. It needs to enable the authority to understand the decision and access the supporting evidence.

How should a gate review be prepared and conducted?

A consistent process can follow twelve steps:

define the objective and authority of the gate;
publish criteria and evidence in advance;
assign those responsible for preparation and review;
update scope, schedule, costs, risks, and contracts to the same data date;
perform a self-assessment by the project team;
perform technical review and assurance where applicable;
record gaps and classify blocking items;
prepare alternatives, consequences, and recommendation;
conduct a decision-oriented meeting;
formalize the outcome, reservations, owners, and deadlines;
control conditions through workflow;
verify closure and incorporate lessons into the next cycle.

The meeting should focus on exceptions, risks, and decisions. Full document review needs to occur before the gate.

What is a gate review and how should it be conducted?

A gate review is the formal review preceding the decision. It should not be confused with a periodic status meeting.

Status meeting	Gate review
tracks progress	decides whether to increase or reduce commitment
occurs at a regular frequency	occurs at defined transitions
addresses current actions and variances	assesses overall maturity and residual risk
may be coordinated by the project manager	must have defined gate authority
normally does not change the lifecycle	may authorize, condition, suspend, or terminate

The agenda may include:

requested decision;
changes since the last gate;
compliance with mandatory criteria;
major gaps and risks;
schedule, cost, and capability analysis;
alternatives and recommendation;
decision;
conditions and next steps.

How should conditional decisions be controlled?

Conditional approval is useful when a gap does not immediately compromise advancement and there is a safe period for treatment. However, it requires discipline.

Each condition should have:

an objective description;
origin in the gate criterion;
potential impact;
owner;
deadline;
closure evidence;
verifier;
consequence of delay;
escalation rule;
visible status.

5W2H applied to engineering structures the response. Workflow and approval flows control states, deadlines, and approvals.

Overdue conditions should not remain open indefinitely. Governance needs to define when the authorization loses validity or returns to the gate owner.

How does Stage-Gate relate to Project Controls?

Project Controls provides the analytical basis for the gate:

scope and WBS;
baselines;
schedule and critical path;
estimates and costs;
physical progress;
risks and contingencies;
changes and trends;
contracts and commitments;
forecast and scenarios.

The gate uses this information to decide. Project Controls does not replace authority, but it reduces decisions based on isolated perceptions.

A review may conclude that the project is technically mature but lacks budget, resources, or an execution window. It may also show that procurement is financially possible while the scope still does not allow adequate comparison of proposals.

How does Stage-Gate relate to the PMO?

The PMO may be responsible for:

defining gate methodology and taxonomy;
maintaining templates and checklists;
training teams;
planning the corporate calendar;
verifying package quality;
consolidating portfolio decisions;
tracking conditions;
preserving lessons and benchmarks;
auditing process compliance;
proposing improvements.

The Engineering PMO Implementation and Structuring solution can incorporate Stage-Gates into the corporate governance system.

The PMO should not turn the gate into an administrative activity disconnected from risk. The review level needs to be proportionate to the requested commitment.

How does Owner’s Engineering participate in gates?

Owner’s Engineering represents the owner technically and may:

review the design basis;
challenge contractor assumptions;
assess multidisciplinary interfaces;
verify document maturity;
review advancement criteria;
assess changes and risks;
confirm procurement or execution readiness;
participate in independent reviews;
recommend conditions to the gate owner;
verify closure of reservations;
support commissioning and acceptance.

Owner’s Engineering strengthens the independence of the decision, especially when much of the information is produced by the company responsible for execution.

The owner should not depend exclusively on the assessment of the party executing the work. Critical gates require independent capability to review assumptions, maturity, risks, and consequences before authorization.

Learn about A3A Engenharia’s Owner’s Engineering services.

How can Stage-Gate be applied to engineering consulting projects?

Studies and technical design projects also need to control maturity. One possible structure is:

Gate	Decision	Evidence
start	authorize surveys and requirements consolidation	scope, inputs, owners, and work plan
design basis	approve assumptions for development	criteria, data, interfaces, and risks
concept	select technical solution	alternatives and rationale
basic design	authorize detailing or procurement	design narratives, specifications, layouts, estimates, and requirements
detailed design	release for fabrication or construction	coordinated documents, calculations, lists, and revisions
final issue	incorporate into the official record	comments addressed, approvals, and traceability

Hours consumed do not demonstrate maturity. The gate should verify whether deliverables have reached the level required for the next decision.

How can Stage-Gate be applied to procurement?

Critical procurement packages may have their own gates:

authorization to approach the market;
approval of bidder list;
readiness of technical documentation;
approval of bid equalization;
authorization to award;
release for fabrication;
inspection readiness;
authorization for shipment;
receipt acceptance;
release for installation.

The procurement gate should verify whether the package allows comparable proposals. Scope, requirements, interfaces, responsibilities, measurement criteria, warranties, and acceptance conditions need to be clear.

The Contracts, Scope, and Deliverables Management solution integrates this preparation with commercial obligations.

How can Stage-Gate be applied to construction and implementation?

Authorization to start construction or a work front should consider:

released design;
available area;
resolved interfaces;
critical materials and equipment;
execution method;
risk analysis;
permits;
team and resources;
planned inspections and tests;
measurement criteria;
quality plan;
communication with operations;
contingencies.

Authorizing mobilization without an available work front creates cost, unproductivity, and pressure to execute on incomplete information.

Gates may be applied by system, area, contract, or critical milestone, not only to the entire project.

How can Stage-Gate be applied to commissioning and entry into operation?

Operational readiness requires integration among engineering, construction, commissioning, safety, operations, and maintenance.

Gate	Typical checks
energization readiness	installation complete, inspections, protections, permits, and risks
test readiness	procedures, instruments, interfaces, and initial conditions
startup readiness	auxiliary systems, team, communication, and failure response
operational readiness	performance, documentation, training, spares, and maintenance
provisional acceptance	classified open items, responsibilities, and warranties
final acceptance	closure of open items, documentation, and obligations

A system may be physically complete and still not be ready to operate. The gate should distinguish physical completion, test readiness, performance, and acceptance.

How should risks be integrated into gates?

The Risk Matrix in Engineering Projects supports classification, but the gate needs to assess whether residual risk is compatible with the requested commitment.

For each critical risk, the following should be known:

cause and event;
consequence;
owner;
response;
treatment deadline;
cost and resources;
trigger;
residual risk;
accepting authority;
impact on the gate.

Not every risk needs to be eliminated before advancement. However, risks without an owner, response, or explicit acceptance demonstrate a governance gap.

How should changes be integrated into gates?

Material changes may require returning to an earlier gate or performing a new readiness review.

Examples:

change to the selected alternative;
material increase in investment;
technology change;
revision of the contractual model;
capacity modification;
regulatory change;
addition of a new interface;
change in operational strategy;
significant schedule shift.

Change control should assess which prior decisions were affected. An approved change should not only update documents and the schedule; it may change the validity of the authorization granted.

Stage-Gate, prioritization matrix, and portfolio management: what is the relationship?

The Project Prioritization Matrix helps select initiatives. Stage-Gate verifies whether each initiative retains sufficient justification and maturity to continue receiving resources.

The sequence may be:

strategic planning → selection → prioritization → initial authorization → phased development → gates → benefits tracking.

Instrument	Main decision
strategic planning	which objectives will the organization pursue?
BSC and OKR	how are objectives translated into results and initiatives?
prioritization matrix	which initiatives deserve capacity first?
portfolio management	how should value, risk, resources, and dependencies be balanced?
Stage-Gate	is the project ready to assume the next commitment?
Project Controls	what is performance and forecast?
benefits management	is the expected outcome being realized?

Continuation should not be automatic simply because the project was approved at the beginning.

Which method should be used for each governance need?

Need	Method or instrument	Outcome
select initiatives	prioritization matrix	ranking and capacity decision
organize scope	WBS	controllable packages and deliverables
define responsibilities	RACI	roles and authorities
classify risks	risk matrix	criticality and response
control documents	EDMS and workflow	revision, protocol, and approval
verify deliverables	acceptance criteria	demonstrated compliance
assess maturity	checklist and assurance review	gaps and confidence in the basis
authorize advancement	Stage-Gate	formal commitment decision
measure performance	KPI and Project Controls	variances and forecast
identify concentrations	Pareto	focus of investigation
investigate causes	Ishikawa and 5 Whys	causal hypotheses
address conditions	5W2H	actions, owners, and deadlines
verify improvement	PDCA	effectiveness and standardization

No instrument replaces another. The gate integrates outcomes produced by different methods to support a decision.

How can Stage-Gate effectiveness be measured?

How can Stage-Gate and agile methods be combined without weakening governance?

Stage-Gate and agile methods do not need to compete for the same management space. In a hybrid architecture, gates remain formal decision points regarding maturity, risk, investment, scope, and authority, while adaptive practices may be used within stages to develop solutions, reduce uncertainty, and obtain feedback in shorter cycles.

Cooper and Sommer studied Agile–Stage-Gate models applied to physical-product development and observed that the combination requires adaptation: practices originating in software cannot simply be transplanted into contexts where prototypes, manufacturing, construction, safety, procurement, and physical changes have different costs and irreversibility. The same caution is essential for engineering projects.

Layer	Function in the hybrid model	Engineering examples
Gate	formal decision on advancement and commitment	approve FEL, freeze Basis of Design, release procurement, authorize fabrication or mobilization
Stage	window in which technical work is developed	studies, design, procurement, detailing, implementation, commissioning
Adaptive cycles	reduce uncertainty and anticipate feedback within the stage	short design reviews, technical backlog, Kanban, Rolling Wave, multidisciplinary workshops
Baseline and change control	preserve the approved reference and control material changes	scope, cost, schedule, requirements, configuration, and approved documents

The boundary matters: a team may use adapted Scrum in design activities, Kanban to control flow and WIP, or Rolling Wave Planning to progressively detail the plan. This does not eliminate the next gate or authorize a baseline change through an informal team decision.

What can be adaptive within a stage?

The degree of adaptation depends on the nature of the work. Concept studies, layout alternatives, multidisciplinary coordination, interface resolution, RFIs, and documentation development may allow short cycles and frequent feedback. By contrast, decisions associated with safety, regulatory requirements, long-lead procurement, contractual releases, manufacturing, and physical execution generally require greater formality and stability.

This combination is consistent with the broader logic of agile and hybrid management of engineering projects: the approach follows the nature of the work and the cost of change, not a single label applied to the entire project.

A gate is not a Sprint Review

A Sprint Review inspects results and guides adaptation of the work. A gate has a broader decision function: it verifies evidence, maturity, residual risk, resources, strategic alignment, and authority to assume the next level of commitment. The two mechanisms can coexist, but they are not equivalent.

In engineering, this distinction prevents two opposite errors: overusing gates to control routine decisions — bureaucratizing flow — or treating high-commitment decisions as if they were merely another adaptive team interaction.

The process should not be evaluated only by the number of meetings held.

Indicator	Management question
percentage of gates approved at first review	are criteria understood and properly prepared?
number of conditions per gate	is maturity sufficient, or is advancement excessively conditional?
time to close conditions	are reservations addressed before they create impact?
changes originating from earlier gaps	are gates preventing rework?
estimate accuracy between gates	does maturity improve reliability?
schedule variance after authorization	was the approved plan executable?
unidentified risks that materialized	did the review cover relevant exposures?
reversed decisions	is governance deciding on a weak basis?
decision lead time	is the process agile without losing quality?
benefits realized	does the project continue to deliver the approved justification?

Indicators need interpretation. Many gates approved at first review may indicate maturity or superficial review. Many conditions may demonstrate rigor or excessive tolerance for incomplete advancement.

What benefits does Stage-Gate produce?

Dimension	Benefit
strategy	keeps the project aligned with objectives and portfolio
scope	reduces advancement on incomplete requirements and boundaries
schedule	avoids schedules based on nonexistent releases
costs	increases reliability before committing resources
risks	makes residual risk and accepting authority explicit
contracts	improves package readiness and proposal comparability
quality	requires evidence and reviews before transition
resources	avoids premature mobilization and unmanaged competition
operations	includes operational readiness before entry into service
governance	records decision, authority, conditions, and rationale
Owner’s Engineering	creates formal points of independent validation
knowledge base	preserves decision bases for benchmarking and learning

The main benefit is aligning the level of commitment with the project’s actual maturity.

How does Stage-Gate create technical knowledge and benchmarking?

Gate history can record:

scope maturity by phase;
estimate quality;
time between gates;
main conditions;
causes of return and rework;
materialized risks;
variances after authorization;
phase productivity;
supplier performance;
approval lead times;
commissioning readiness;
acceptance open items;
benefits realized.

Benchmarking requires context. Projects should not be compared only by number of days or conditions. Complexity, contracting strategy, technology, location, maturity of inputs, and asset criticality need to be considered.

This knowledge base improves future criteria, estimates, work plans, and the design of the gates themselves.

How can the maturity of the gate process be assessed?

Level	Characteristics	Main limitation
1 — informal	decisions in meetings without criteria or records	dependence on individuals
2 — documented	standardized checklists and minutes	focus on formal compliance
3 — controlled	criteria, authorities, evidence, and conditions tracked	partial integration with controls
4 — integrated	gates connected to portfolio, contracts, risks, and baselines	need for data governance
5 — adaptive	proportionate criteria, benchmarking, and risk-based assurance	risk of excessive complexity

Maturity does not mean increasing the number of gates. It means applying reviews appropriate to the risk and commitment.

How can Stage-Gate be implemented in 12 steps?

Map critical decisions. Identify where the project assumes technical, financial, contractual, or operational commitments.
Define the lifecycle. Organize phases and expected products without copying incompatible models.
Design the gates. Relate each gate to the decision, authority, and consequence.
Establish criteria. Differentiate mandatory, conditional, and recommended items.
Define evidence. Relate documents, data, reviews, and owners.
Structure roles and authorities. Use RACI and technical, financial, and operational authorities.
Integrate Project Controls. Synchronize scope, schedule, costs, risks, and forecast.
Implement workflow. Control preparation, review, decision, and conditions.
Test on a pilot project. Assess workload, clarity, and decision quality.
Train teams and decision-makers. Explain purpose, criteria, and possible outcomes.
Monitor effectiveness. Measure rework, changes, time, and open conditions.
Adjust by risk and phase. Simplify or deepen according to criticality.

Implementation should begin with decisions that most expose the organization, not by creating an extensive document list.

Example applied to a multidisciplinary project

Consider an industrial expansion with engineering, equipment procurement, civil works, electrical installations, automation, integration, and commissioning.

Management intends to authorize the main procurement package. The schedule indicates urgency, but the readiness-gate review identifies:

operational requirements still divergent;
layout without final approval;
incomplete infrastructure quantities;
critical equipment with undefined electrical interface;
estimate without contingency for field conditions;
permit in progress;
risk of operational shutdown without a confirmed window;
acceptance criteria not incorporated into the contract draft.

The commercial team argues that the gaps can be resolved later. The gate owner needs to assess whether the market will receive a comparable scope and whether the owner will retain control over changes.

The decision is recycle, with a three-week deadline to:

consolidate operational requirements;
approve the design basis;
close equipment interfaces;
review quantities and estimate;
define the contingency strategy;
incorporate measurement and acceptance criteria;
update risks and schedule.

At the new review, mandatory criteria are met. Two non-critical conditions remain: issuance of an external authorization and completion of an additional survey before mobilization.

The gate authorizes approaching the market, but not mobilization. The conditions enter a workflow with owners, deadlines, and triggers. The next gate will verify execution readiness.

The model prevented schedule pressure from producing procurement on an insufficient basis without interrupting activities that could already advance safely.

Common mistakes when implementing Stage-Gate

Copying another company’s gates

The model does not represent the organization’s actual decisions, risks, and responsibilities.

Creating too many gates

The process increases administrative workload without improving decisions.

Treating a gate as a status presentation

The meeting reports progress but does not assess maturity or commitment.

Assessing only documents

The existence of a file does not demonstrate consistency, quality, or overall readiness.

Using an average score to offset a critical gap

Several approved minor items hide a blocking risk.

Allowing conditions without control

The project advances and reservations remain open until they cause impact.

Failing to define authority

Participants discuss, but no one assumes responsibility for the decision.

Excluding operations and maintenance

The project advances technically without considering operability and transition.

Ignoring contracts and the market

The technical gate approves a package that still cannot be procured on a comparable basis.

Repeating the same requirement in every phase

Criteria do not evolve with project maturity.

Confusing assurance with execution

The independent review starts producing the work it was supposed to assess.

Failing to record negative decisions

Suspended or terminated projects lose lessons and rationale.

When should specialized support be engaged to structure gates?

External support is especially useful when:

the organization lacks a standardized lifecycle;
projects advance with incomplete scope;
change orders and rework are recurring;
procurement criteria are weak;
a PMO exists but lacks decision authority or methodology;
projects combine multiple disciplines and contracts;
the owner needs independent technical review;
commissioning and operational gates are critical;
conditions are not tracked;
the portfolio competes for limited capacity;
there is a need to create a knowledge base and benchmarking;
audits identify decisions without evidence.

Support model	Application	Typical deliverables
maturity assessment	assess current process and gaps	assessment and roadmap
lifecycle design	structure phases, gates, and decisions	governance model
criteria definition	create checklists, evidence, and classes	readiness matrix
workflow implementation	control preparation and conditions	flows, states, and SLAs
gate facilitation	prepare and conduct reviews	gate pack, minutes, and decision
independent assurance	review maturity of a critical topic	opinion and recommendations
PMO support	institutionalize method and metrics	standards, training, and audit
Owner’s Engineering support	represent the owner	technical review and recommendation
continuous operation	maintain calendar and tracking	recurring governance

How should the responsible company or consultancy be evaluated?

The evaluation should consider:

experience in comparable projects;
understanding of engineering, contracts, and operations;
command of PMO, Project Controls, and risk;
ability to build verifiable criteria;
independence to challenge information;
technical track record and qualified team;
assurance methodology;
clarity about roles and conflicts;
ability to integrate different systems;
experience in commissioning and acceptance;
ability to facilitate executive decisions;
responsible use of benchmarking;
knowledge transfer to the client.

The proposal should define phases, gates, criteria, team, dedication, deliverables, calendar, systems, assumptions, exclusions, and acceptance criteria for the service itself.

How does technology support Stage-Gate?

Technology can control:

gate calendar;
checklists and criteria;
documents and revisions;
owners and authorities;
evidence;
risks and changes;
conditions;
decisions and minutes;
baselines;
indicators;
history and benchmarking.

The ENGiOS platform connects projects, contracts, documents, workflows, risks, actions, and indicators in a governance trail for engineering companies.

The tool should not automatically decide whether the project is ready. Its role is to organize information, apply rules, preserve traceability, and facilitate technical and management judgment.

Conclusion

Stage-Gate is a governance mechanism that relates maturity, evidence, risk, and authority to the advancement of engineering projects. It prevents schedule pressure, budget availability, or sunk cost from replacing a substantiated decision.

An effective process needs to distinguish development phases from decision gates, establish verifiable criteria, involve the correct authorities, and control conditions. It must also integrate Project Controls, PMO, contracts, requirements, risks, operations, and Owner’s Engineering.

The gate does not exist to confirm that the team worked. It exists to answer whether the project is ready to assume the next level of commitment and which conditions need to be preserved.

The final question is not only “have the documents been delivered?”. It is: is there sufficient maturity, evidence, capability, and acceptable residual risk to authorize the next step?

Technical references

[1] INTERNATIONAL ORGANIZATION FOR STANDARDIZATION. ISO 21502:2020 — Project, programme and portfolio management — Guidance on project management. Geneva: ISO, 2020.

[2] INTERNATIONAL ORGANIZATION FOR STANDARDIZATION. ISO 21505:2017 — Project, programme and portfolio management — Guidance on governance. Geneva: ISO, 2017.

[3] INTERNATIONAL ORGANIZATION FOR STANDARDIZATION. ISO 21504:2022 — Project, programme and portfolio management — Guidance on portfolio management. Geneva: ISO, 2022.

[4] COOPER, Robert G. Winning at New Products: Creating Value Through Innovation. 5th ed. New York: Basic Books, 2017.

[5] COOPER, Robert G. Perspective: The Stage-Gate Idea-to-Launch Process — Update, What’s New, and NexGen Systems. Journal of Product Innovation Management, v. 25, n. 3, p. 213–232, 2008.

[6] PROJECT MANAGEMENT INSTITUTE. The Standard for Portfolio Management. 4th ed. Newtown Square: PMI, 2017.

[7] PROJECT MANAGEMENT INSTITUTE. A Guide to the Project Management Body of Knowledge — PMBOK Guide. 7th ed. Newtown Square: PMI, 2021.

[8] COOPER, Robert G.; SOMMER, Anita F. Agile–Stage-Gate Hybrids: The Next Stage for Product Development. Research-Technology Management, v. 59, n. 1, p. 21–29, 2016. Available at: https://doi.org/10.1080/08956308.2016.1117317.

[9] COOPER, Robert G.; SOMMER, Anita F. The Agile–Stage-Gate Hybrid Model: A Promising New Approach and a New Research Opportunity. Journal of Product Innovation Management, v. 33, n. 5, p. 513–526, 2016. Available at: https://doi.org/10.1111/jpim.12314.

Frequently asked questions

What is Stage-Gate in projects?

It is a governance model that divides a project into phases and establishes formal decision gates to verify maturity, evidence, risks, and capability before advancement.

What is the difference between a stage and a gate?

A stage is the phase in which work and deliverables are developed. A gate is the review and decision point that authorizes, conditions, suspends, redirects, or terminates advancement.

Is Stage-Gate the same as the project lifecycle?

No. The lifecycle describes phases. Stage-Gate adds criteria, evidence, authority levels, and formal decisions between them.

What decisions can result from a gate?

Decisions may include go, conditional go, hold, return for completion, redirect, defer, or terminate.

Who should approve a gate?

Authority depends on the requested commitment. It may involve the sponsor, gate owner, technical, financial, operational, and other authorities defined by governance.

How should a conditional approval be controlled?

Each condition should have an owner, deadline, closure evidence, verifier, consequence of delay, and escalation rule in the workflow.

What is the role of Owner’s Engineering in gates?

Owner’s Engineering independently reviews maturity, interfaces, risks, and evidence and recommends decisions that protect the owner’s technical objectives.

When should support be engaged to implement Stage-Gate?

When projects advance with incomplete scope, changes are recurring, the PMO lacks a decision process, there are multiple contracts, or the owner needs independent assurance.

Complementary technical materials

1. Strategy, selection, and portfolio governance

2. Structure, responsibilities, risks, and evidence

3. Decisions, conditions, and effectiveness control

4. Solutions to institutionalize gates

5. Platform, management, and owner representation

6. Official references and external resources