Design review gates are one of those topics that quietly determine whether an industrial project succeeds on safety, cost, and schedule — or struggles with rework, late changes, and regulatory headwinds. In the UAE’s high‑hazard sectors — upstream oil and gas, petrochemicals, power generation, large construction programs, logistics terminals, and complex manufacturing — a clear, risk‑aware approach to phase‑gate decision making is central to technical integrity and compliance. This article explores what structured design gates look like in practice, how they connect to process safety studies (from HAZID and HAZOP to LOPA and QRA), and how teams can make them work effectively without turning them into bureaucratic checkboxes.
Who Does This Affect?

Although stage‑gate governance is typically championed by project management, its impact spans multiple disciplines and functions. Understanding how to prepare for and pass a gate effectively matters to anyone whose decisions affect hazard identification, barrier effectiveness, or readiness to build and operate. In the regional context, this often includes coordination with ADNOC group requirements and local authorities such as Dubai Municipality, Civil Defence, OSHAD (now under Abu Dhabi Public Health Center), and MOHRE, alongside corporate standards and international codes.
- Project directors and project managers who own the investment decision and must demonstrate due diligence, technical maturity, and ALARP reasoning at each hold point.
- Process safety engineers and technical safety specialists responsible for planning and integrating HAZID, HAZOP, LOPA, SIL determination and verification, Bowtie analysis, and QRA across the lifecycle.
- Discipline leads (process, mechanical, piping, E&I/controls, civil/structural, HVAC) who develop and freeze deliverables (e.g., PFDs, P&IDs, 3D model maturity, control narratives) to meet the criteria for passing a gate.
- Operations, maintenance, and commissioning teams who bring operability, maintainability, start‑up/shutdown, and handover realities into early design decisions and acceptance criteria.
- Procurement and contracts teams who need gate decisions to release long‑lead items, define safety‑critical equipment specifications, and lock vendor data requirements.
- EPC contractors, specialist vendors, and integrators who must align their internal readiness with the client’s governance, including constructability reviews, model reviews, FAT/SAT planning, and performance standards for Safety Critical Elements (SCEs).
Why This Matters

A well‑structured gate model enables organizations to make risk‑informed approvals at predictable points in the lifecycle — from concept selection to FEED, detailed design, construction, and pre‑startup. The alternative is unmanaged drift: design development outpacing hazard identification, safety instrumented system (SIS) decisions being made before SIL targets are set, or regulatory approvals lagging behind engineering. In the UAE, where regulatory engagement and third‑party approvals can be critical path items, missing a gate’s readiness criteria cascades directly into schedule and cost risk.
From a process safety standpoint, gates are more than governance rituals. They are where the business confirms that barriers are defined, credible scenarios are understood, safeguards are effective, and risks are demonstrably ALARP. This is where IEC 61511 lifecycle steps for instrumented functions are anchored to project milestones; where firefighting and gas detection philosophies are tied into model reviews; where human factors, layout spacing, and escape/evacuation provisions are validated; and where management of change ensures baseline integrity when design choices evolve. Done well, design gates stabilize the project while still allowing controlled learning and optimization.
Key Points to Understand

To move from theory to practical value, it helps to break the gate concept into its essential elements and see how they align with familiar deliverables and safety studies.
1) A lifecycle model with clear hold points
Most organizations use a variant of Front‑End Loading (FEL) and stage‑gate governance: Opportunity/Concept, Feasibility (FEL‑1), Select (FEL‑2), Define/FEED (FEL‑3), Detailed Design, Construction/Commissioning, and Pre‑Startup/Operations. Each gate asks: do we know enough, with sufficient quality and certainty, to commit the next tranche of cost and risk?
2) Safety is built into the criteria, not added after
Gate readiness criteria should embed process safety deliverables and decisions, not bolt them on. For example, concept and select phases need early HAZID, major accident hazard screening, and initial Bowties to identify Safety Critical Elements; FEED should confirm the safety philosophies, hazardous area classification, and initial SIL targets; detailed design should close the loop with HAZOP, LOPA, SIL verification, and functional design specifications for SIS; and construction/commissioning should close PSSR findings and verify barrier performance.
3) Evidence, not assertions
Gate packages should rely on verifiable data and traceable decisions: frozen PFDs/P&IDs, 3D model snapshots, consequence modeling/QRA extracts, cause‑and‑effect matrices, SCE performance standards, layout and spacing checks against recognized codes, and documented close‑out of previous gate actions. Independence and competence of reviewers also matter for credibility.
4) Alignment with recognized frameworks
Across the lifecycle, teams benefit from aligning their safety decision points to established guidance such as the Center for Chemical Process Safety’s risk‑based process safety framework. For background material and thought leadership on integrating process safety into project decisions, the resources of the Center for Chemical Process Safety (CCPS) are widely referenced by industry practitioners.
5) How gates sequence with core safety studies
The following table summarizes common project gates and highlights the typical safety emphasis, inputs, and outputs many teams expect to demonstrate. Local corporate standards, ADNOC requirements, and authority approvals may specify additional details, but the logic remains similar.
| Project Phase | Typical Gate | Primary Safety Focus | Key Inputs | Typical Outputs/Decisions | Triggered Studies |
|---|---|---|---|---|---|
| Opportunity / Concept | G0 / Concept Selection | Identify major accident hazards and show feasible inherently safer options. | Concept options, preliminary mass/energy balances, plot plans, major equipment lists. | Selected concept; initial barrier strategy; preliminary SCE list; risk acceptance basis. | Early HAZID, showstoppers assessment, preliminary Bowties, battery limit definition. |
| Feasibility (FEL‑1) | G1 / Feasibility Approval | Refine hazards; screen critical codes/standards and authority constraints. | Refined process data, outline layout, utility/load estimates, regulatory map. | Confirmed go/no‑go; targeted studies plan; initial QRA screening scope. | HAZID refinement, initial QRA screening, spacing checks, environmental screening. |
| Select (FEL‑2) | G2 / Option Select | Compare options using risk and lifecycle safety performance. | Option comparison dossier, capex/opex estimates, outline cause‑and‑effect. | Preferred option; preliminary SIF needs; firefighting/F&G philosophies drafted. | Constraint studies (e.g., EERA/TRA), preliminary SIL allocation basis, siting studies. |
| Define / FEED (FEL‑3) | G3 / FEED Freeze | Freeze safety philosophies; set SIL targets; align with authority approvals. | Frozen PFDs/P&IDs, layout, hazardous area classification, safety philosophies. | Approved design basis; authority submission basis; SCE performance standards v1. | Safety philosophy reviews, SIL determination, QRA update, firewater demand analysis. |
| Detailed Design | G4 / Design Maturity | Validate design through HAZOP/LOPA; verify SIF calculations and specifications. | Cause‑and‑effect, control narratives, instrument indexes, 3D model 60‑90%. | Closed HAZOP actions; SIL verification; procurement release for SCEs. | HAZOP, LOPA, SIL verification, F&G mapping, fire protection detailed design reviews. |
| Construction | G5 / Mechanical Completion Readiness | Confirm buildability and preservation of barrier intent. | Constructability reviews, redlines management, quality records. | Turnover package acceptance; punchlist strategy; commissioning plan. | Field hazard reviews, lifting plans, temporary systems risk assessments. |
| Pre‑Startup / Commissioning | G6 / ORR & PSSR | Verify that risks are controlled before introducing hazards. | PSSR checklist, procedures, training, MOC close‑out, instrument testing results. | Authorization to introduce hydrocarbons/energy; residual risk register. | Operational Readiness Review (ORR), PSSR, emergency response validation. |
How This Works in Practice

With the structure in mind, it helps to visualize a typical sequence on a brownfield modification for a gas processing plant or offshore platform in the Gulf. Early in concept, the team runs a focused HAZID to establish credible scenarios, especially around tie‑ins, confined spaces, and simultaneous operations. They outline new or changed SCEs (e.g., isolation valves, SIF for high‑high pressure trip, enhancements to F&G coverage) and agree a plan for studies. By the time the FEED freeze gate is reached, PFDs and P&IDs reflect agreed philosophies, hazardous area classification maps are baselined, and the authority path (for example, Civil Defence for fire protection) is aligned with the design basis.
As detailed design matures, engineering and operations collaborate on HAZOP and LOPA to confirm that intended safeguards meet risk targets and to assign SILs where necessary. Instrument engineers and functional safety specialists verify SIFs against target SIL through architectural constraints and probability of failure on demand calculations, while control narratives and cause‑and‑effect tables are finalized. Simultaneously, 3D model reviews at 60% and 90% maturity validate layout spacing, escape routes, access for maintenance, and hydrant/nozzle coverage in accordance with the approved fire protection philosophy. Any changes arising from vendor data, constructability inputs, or authority feedback flow through a disciplined MOC process to preserve the baseline and maintain traceability.
Closer to construction, constructability and field hazard reviews reduce the gap between drawings and reality. Tie‑ins are planned with clear isolation strategies, temporary systems are risk‑assessed, and lifting plans for heavy equipment are vetted, recognizing the constraints of brownfield areas. As the facility approaches energization or introduction of hydrocarbons, the Operational Readiness Review confirms that procedures, training, emergency response, and competency are demonstrably in place. The Pre‑Startup Safety Review then checks — with evidence — that actions from HAZOP/LOPA, vendor testing, and authority approvals are closed or risk‑managed to a defined standard before the system is made live.
Benefits and Practical Use Cases

When design gates are thoughtfully implemented, organizations see benefits that extend beyond governance comfort. They reduce late‑stage changes, align safety decisions with engineering maturity, and make regulatory interactions more predictable. The following scenarios illustrate common, concrete advantages.
- Brownfield tie‑ins: Linking early HAZID outcomes to the FEED gate prevents discovering clash issues or inadequate isolation points during construction, avoiding hot work deferrals and shutdown overruns.
- SIS lifecycle alignment: Setting and verifying SIL targets across FEED and detailed design gates ensures that SIF architectures, testing intervals, and proof test coverage are engineered in — not added after FAT/SAT.
- Authority approval readiness: Freezing fire protection philosophies and F&G mapping prior to model freeze reduces rework triggered by Civil Defence comments and eases final acceptance.
- Barrier health transparency: Maintaining SCE performance standards as a living dataset through gates allows operations to inherit well‑defined assurance tasks after start‑up.
- Constructability and maintainability: Early constructability workshops and 3D model reviews at gate milestones surface access, lifting, or egress constraints before they become site problems.
- Human factors integration: Embedding control room layout, alarm philosophy, and proceduralization reviews at the right gates reduces cognitive overload and operator error risks during start‑up.
Best Practices and Points of Caution

Earlier sections emphasized structure and application; here are pragmatic techniques that help design gates deliver value without bogging projects down. These recommendations reflect common pitfalls witnessed across refineries, petrochemical complexes, power plants, and complex construction projects.
- Define “ready” with measurable criteria. Vague acceptance conditions invite debate. Use quantifiable deliverable maturity (e.g., P&ID freeze index, 3D model % complete, action close‑out rates) and specify which safety decisions must be demonstrated at each gate.
- Link gates to the functional safety lifecycle. For instrumented functions, align your activities to IEC 61511 across definition, design, installation, validation, and operation/maintenance. Guidance from the International Electrotechnical Commission (IEC) helps establish the discipline for this linkage.
- Plan studies early and right‑size the scope. Over‑scoping a HAZOP too early or too late wastes effort and forces rework. Use HAZID and Bowties to focus later HAZOP nodes and LOPA on risk‑relevant scenarios once P&IDs and control narratives are mature enough.
- Secure independent, competent reviewers. Independence reduces confirmation bias. Competence matrices for reviewers (e.g., process safety, operations, electrical, controls) improve the quality of gate challenges and the credibility of outcomes.
- Make MOC your gatekeeper. Ensure all design changes, whether driven by vendor data or field conditions, are captured, risk‑assessed, and reconciled to the baseline. Unmanaged change is a leading cause of late surprises at PSSR.
- Treat authorities as stakeholders, not hurdles. Early dialogue with local regulators and code officials can de‑risk interpretations (e.g., NFPA applications, hydrant spacing, hazardous area classification considerations) before positions harden.
- Keep barrier intent visible. Track SCEs from concept through commissioning with their performance standards, impairment management expectations, and assurance tasks to avoid decoupling design intent from operability.
- Beware gate “theatre.” Passing a gate is not success if critical actions are deferred without risk‑based justification and a clear owner/due date. Documented, time‑bound action closure is part of the acceptance.
- Use data discipline. Version control, action logs, and structured tagging for SCEs, SIFs, alarms, and interlocks reduce confusion and speed decision making in reviews and audits.
- Integrate cybersecurity considerations. For modern IACS and SIS, ensure security requirements are defined and validated in step with safety lifecycle reviews to avoid late retrofits.
Frequently Asked Questions About Design Review Gates
How many gates should a typical capital project have?
While models vary, many industrial organizations use six to seven major gates from concept to pre‑startup, with interim holds as needed. What matters most is not the exact number but the clarity of decisions at each gate and the alignment of safety studies and approvals to those decision points.
What is the difference between a HAZOP and a gate review?
A HAZOP is a structured hazard analysis focused on process deviations and safeguards within a defined scope (often P&IDs). A gate review is a broader governance checkpoint that considers multiple inputs — including HAZOP results — to decide whether the project is mature and safe enough to proceed to the next phase.
When should SIL targets be assigned in the lifecycle?
Target SILs should be set by the end of FEED, once safety functions and risk criteria are clear and key process parameters are stable. Verification of those targets typically occurs during detailed design when sufficient detail exists to confirm architectures and failure probabilities.
How do design gates relate to Management of Change?
Gates and MOC are complementary. Gates freeze baselines and approve scope progression; MOC controls any changes to that baseline between gates. Effective projects treat MOC as the mechanism that preserves integrity and traceability of safety decisions across the lifecycle.
What happens if a project fails a gate?
Failing a gate does not end a project; it signals that critical readiness criteria are unmet. The review board should document required actions, owners, and due dates, with a plan for re‑review. The intent is to protect the organization from committing capital and risk prematurely.
How do authorities having jurisdiction fit into gates?
Authority engagement should be synchronized with gate timing. For example, fire protection philosophies and preliminary layouts should align with early submissions, while detailed design reviews and acceptance testing synchronize with later gates to avoid rework and schedule impacts.
Are gates only for major greenfield projects?
No. Brownfield modifications, debottlenecking projects, and even significant maintenance campaigns benefit from scaled gating. The scope may be lighter, but the discipline of deciding when hazards are sufficiently understood before introducing risk remains essential.
What documentation is typically required at a pre‑startup gate?
Common requirements include closed HAZOP/LOPA actions, PSSR checklist completion, commissioning procedures and training records, emergency response readiness, validated cause‑and‑effect testing, MOC close‑out, and confirmation that residual risks are documented and accepted per governance.
How should human factors be integrated into gates?
Introduce human factors early with layout and control room considerations, and then deepen the analysis with alarm philosophy, proceduralization, and workload assessments as design matures. Verification at model reviews and during commissioning ensures the intended operability is realized.
What is the role of SCE performance standards in gate reviews?
Performance standards translate barrier intent into measurable requirements for function, availability, reliability, and assurance. Presenting and maintaining them through gates keeps the organization focused on whether each safety‑critical barrier will actually perform when demanded.
Conclusion
Design review gates work when they are more than milestones on a schedule. They create structured moments to confirm that hazards are known, barriers are effective, and the project is mature enough — technically and organizationally — to move forward. When gates are tied to the right studies (from early HAZID and Bowties to HAZOP, LOPA, and SIL verification), anchored in recognized standards, and supported by disciplined MOC and authority engagement, they cut rework, reduce uncertainty, and elevate safety outcomes. Practitioners across the UAE’s high‑risk industries recognize that this is how technical integrity becomes visible, auditable, and sustainable across the lifecycle.
To go further on this topic, NPM’s broader HAZID Study Services UAE page covers this in more depth.
Our References
NPM’s portfolio spans complex, high‑hazard facilities worldwide, and our references reflect how rigorous stage‑gate thinking translates into safer, more predictable outcomes. Across upstream and downstream oil and gas, LNG processing, petrochemical units, storage and export terminals, combined‑cycle power stations, high‑rise and infrastructure construction, and advanced manufacturing, our teams have helped organizations structure gate criteria that connect engineering maturity with hazard knowledge. In practical terms, that has meant mapping early HAZID outcomes to option selection, aligning FEED freezes with safety philosophies and authority pathways, and ensuring detailed design gates close the loop with HAZOP/LOPA, SIL verification, and robust cause‑and‑effect logic. In brownfield settings, our work has focused on tie‑in readiness, constructability, and maintaining barrier intent under constrained conditions, from offshore platforms to congested process units. We believe references should do more than list project names; they should demonstrate an organization’s ability to align decisions, evidence, and risk acceptance across real‑world constraints. That is why NPM’s references highlight not only technical studies but also the orchestration of stakeholders — operations, maintenance, EPC contractors, and regulators — to move safely and decisively through gates. Whether your concern is a targeted modification or a multi‑billion‑dollar capital program, exploring our references provides a window into how lifecycle safety and design governance can work together without slowing momentum. The body of work shows consistent attention to Safety Critical Elements, performance standards, management of change, and the readiness reviews that precede safe start‑up, all grounded in recognized international standards and local regulatory expectations.
For more information about our references, visit Our References.
Speak with NPM
If you would like to discuss how to make your gates sharper, leaner, and more effective for process safety, our team is glad to exchange perspectives. We can talk through practical approaches that fit your project controls and regulatory context, from greenfield programs to brownfield upgrades. Questions are always welcome, whether you are refining criteria or planning upcoming studies.
For any further questions or to speak with our team, Contact Us.