SWIFT Methodology

Design Hazard Review for New Processing Facility

SWIFT Methodology is widely used as a pragmatic, structured way to identify hazards and operational vulnerabilities in complex industrial settings. In the UAE’s high-hazard sectors—upstream and downstream oil and gas, petrochemical plants, high-rise and infrastructure construction, heavy manufacturing, logistics hubs, and power generation—teams rely on this approach to quickly surface what could go wrong, why it could happen, and what barriers or safeguards are needed. While it is lighter-weight than a full HAZOP, it retains the discipline of a systematic prompt-based review and fits naturally into project, operations, and Management of Change workflows.

At its core, the Structured What-If Technique focuses on guided brainstorming anchored by prompt phrases. Instead of dissecting a process line by line with deviation guidewords (as in HAZOP), it uses targeted “what-if” questions—covering people, plant, procedures, and external factors—to build a credible picture of risk. It is especially useful when time is limited, when documentation is evolving, or when a design or operating mode does not warrant the intensity of a HAZOP but still demands a defensible hazard identification step aligned with standards and regulatory expectations.

For HSE leaders, plant managers, and compliance officers, this method is not a substitute for rigorous studies like LOPA or SIL verification under IEC 61511; instead, it is a complementary technique that screens issues early, prioritizes deeper analysis where justified, and captures practical actions that improve reliability, safety, and compliance.

Who Does This Affect?

SWIFT Methodology

Because the technique is deliberately cross-functional, it concerns both decision-makers and practitioners across the lifecycle of facilities and projects. Typical participants and stakeholders include:

  • HSE managers, process safety engineers, and PSM coordinators responsible for Process Hazard Analysis and risk registers
  • Plant managers, operations superintendents, and control-room leaders accountable for day-to-day risk controls
  • Project directors, engineering managers, and lead process/mechanical/E&I engineers during concept, FEED, and detailed design
  • Maintenance, reliability, and integrity teams managing critical equipment, SIS proof testing, and SCE (Safety Critical Elements)
  • Construction and commissioning managers overseeing high-risk work fronts and pre-startup reviews
  • HSQE and compliance officers aligning with OSHAD-SF, Dubai Municipality codes, Abu Dhabi Civil Defence approvals, MOHRE requirements, and ADNOC HSE guidelines

Operational contexts where it is especially relevant in the UAE include refineries and gas processing facilities, offshore platforms and onshore terminals, fuel storage tank farms, bulk chemical warehousing, LNG truck loading bays, power generation and desalination plants, and large construction projects with complex temporary works or concurrent operations.

Why This Matters

SWIFT Methodology

Compared with other process safety studies, this technique offers a high signal-to-effort ratio. It allows organizations to:

First, surface credible risks early. Early-stage design choices (layout, segregation, relief routing, utilities resilience) often have the greatest leverage on risk, cost, and schedule. A structured “what-if” review identifies red flags before they are baked into drawings and purchase orders.

Second, maintain compliance in a dynamic environment. UAE operators must demonstrate systematic hazard identification to multiple stakeholders—internal risk committees, corporate PSM frameworks aligned with API RP 754 metrics, and regulators such as OSHAD, Civil Defence, Dubai Municipality, and ADNOC HSE. When used appropriately, a well-documented session offers traceable evidence that new or modified operations have been risk assessed.

Third, enable proportionate analysis. Not every change needs a full HAZOP or QRA. A calibrated approach helps teams triage: some nodes or changes need deeper study (e.g., LOPA or SIL determination against IEC 61511), while others only need procedural reinforcement or minor design tweaks. This proportionality reduces analysis fatigue and keeps specialists focused where it matters most.

Finally, build operational foresight. Many incidents stem from deviations that were imaginable but not explicitly discussed—temporary bypasses, abnormal weather, simultaneous operations, power quality issues, contractor interfaces. A disciplined use of prompt phrases institutionalizes foresight, capturing both engineered and human/organizational vulnerabilities.

Key Points to Understand

SWIFT Methodology

What the Structured What-If Technique Is—and Is Not

SWIFT Methodology

The technique is a facilitated, prompt-driven team discussion to anticipate deviations and consequences. It is systematic but not as granular as a HAZOP. Teams use agreed “what-if” prompts to explore equipment failures, human errors, external events, and management system gaps. The outcome is a set of reasonably foreseeable scenarios with risk rank, safeguards, and actions. It is not a checklist audit, not a qualitative-only exercise devoid of rigor, and not a replacement for more detailed studies when complexity or risk profile demands them.

Core Prompt Categories

SWIFT Methodology

Prompts help the team cover the full spectrum of credible deviations. While each organization customizes them, common categories include:

  • Equipment integrity: What if a critical valve sticks open/closed? What if a heat exchanger tube leaks?
  • Instrumentation and controls: What if a transmitter drifts? What if the SIS trip setpoint is misconfigured?
  • Utilities and support systems: What if plant air or nitrogen is unavailable? What if cooling water is lost?
  • Human and organizational factors: What if the permit is issued for the wrong equipment? What if a bypass remains in place?
  • External events: What if flooding occurs? What if a third-party excavation damages a pipeline?
  • Chemicals and materials: What if the wrong grade is delivered? What if static accumulation ignites vapors?
  • Simultaneous operations and logistics: What if hot work coincides with tanker loading? What if traffic flows are reversed?

Inputs and Preparation

SWIFT Methodology

To be credible, the review depends on inputs that define scope and context. Typical inputs include P&IDs and PFDs for process reviews; cause-and-effect charts and safeguarding narratives for SIS-related discussions; layout drawings for construction or terminal operations; operating and maintenance procedures; and recent incident/near-miss data (aligned with ISO 45001 management review). Where safety critical equipment is managed under performance standards, alignment with IEC 61511 and corporate SCE frameworks helps the team map findings to existing barriers.

Outputs and Risk Treatment

SWIFT Methodology

Outputs must connect findings to the organization’s risk matrix and action management system. Scenarios are recorded with initiating causes, consequences, existing safeguards (engineering and administrative), risk ranking, and recommended actions. Some actions trigger deeper analyses—e.g., a proposed demand rate suggests LOPA to verify risk reduction credits; an instrumented function change suggests SIL review. Others translate into design improvements, procedural changes, competence checks, or inspection/test updates under ISO 45001 and ISO 14001 integrated management systems.

Where It Fits Among Other Techniques

SWIFT Methodology

It helps to position this method alongside other risk tools. The table below highlights typical use cases and outputs across common methodologies used in UAE industry:

Dimension SWIFT HAZOP HAZID LOPA
Primary Objective Structured brainstorming of credible “what-if” scenarios to screen and prioritize risks Systematic deviation analysis for process nodes using guidewords Broad, high-level hazard identification across project/site scope Semi-quantitative verification of risk reduction and IPL sufficiency
Typical Timing Concept design, MoC, pre-startup, operating mode changes Late FEED/detailed design, major modifications Early concept/FEED, master planning Post-HAZOP when risk credits or SIL targets must be confirmed
Effort Level Moderate; focused sessions with targeted prompts High; node-by-node multi-day workshops Moderate; breadth over depth Focused; depends on number of scenarios needing verification
Outputs Scenario list, safeguards, actions, escalation needs Detailed cause–consequence pairs, deviations, actions Hazard register, qualitative risks, recommendations Risk gap closure actions, IPL credits, SIL justification
Standards Link Supports PHA under corporate/OSHA/OSHAD frameworks Common PHA method; informs IEC 61511 safety lifecycle Front-end hazard basis for project risk Aligned with IEC 61511 and company risk criteria

Governance, Facilitation, and Independence

Credibility increases with clear governance—defined roles, independence of facilitation, and traceability of decisions. Many organizations keep a corporate playbook for PHA methods, including SWIFT prompt libraries, risk matrices, and action verification rules. For broader reading on governance and risk thinking that complements structured hazard reviews, practitioners sometimes consult external resources such as CABINET NPM.

Alignment with Local and International Expectations

In the UAE, regulators and industrial stakeholders expect risk-based, documented decision-making. A structured “what-if” review helps demonstrate due diligence to OSHAD/SF auditors, supports Dubai Municipality and Civil Defence submissions for high-risk activities, and aligns with ADNOC HSE expectations for PHA. Internationally, it dovetails with ISO 45001 clauses on hazard identification and risk assessment, integrates with API RP 754 process safety performance indicators, and feeds inputs to functional safety lifecycle activities under IEC 61511 when instrumented protection functions are involved.

How This Works in Practice

Translating the method into operational life starts with understanding the questions the organization needs to answer. If a change is proposed—say, adding a new chemical to a blending line at a storage terminal or introducing a temporary relief path during a shutdown—the team must decide whether the change introduces new hazards, affects safeguards, or creates concurrent operations conflicts. A structured “what-if” review offers a quick but systematic forum to make that determination.

Consider three recurring contexts in UAE facilities:

  • Management of Change (MoC): For piping reroutes, control logic tweaks, or vendor substitutions, a short, prompt-led review can reveal latent dependencies (shared trips, common mode failures, permit interfaces) that would be easy to miss in a document-only MoC.
  • Pre-startup and commissioning: Before energizing equipment or introducing hydrocarbons, a “what-if” session tests assumptions—Are interlocks enabled? Are bypasses cleared? Have fire and gas detectors been rebaselined? Do temporary blinds or scaffolds alter egress?
  • Operational mode changes: When moving from normal to degraded operation (e.g., single pump running after a failure), a quick review clarifies if risk remains tolerable and what compensatory measures (enhanced rounds, temporary alarms, job restrictions) are required.

A typical flow integrates with existing management systems: scope and objectives are framed; relevant drawings, procedures, and incident learnings are distributed; a cross-discipline group convenes with a facilitator; prompt categories are applied to each defined scope element; and actions are logged with owners and due dates in the corporate action tracker. Importantly, escalation criteria are explicit: triggers for HAZOP, LOPA, Bowtie development, or quantitative assessments like QRA are defined so that higher-hazard issues graduate to more rigorous analysis rather than lingering in a qualitative log.

Because human and organizational factors often dominate incident causation, experienced teams purposefully include control room operators, permit-to-work coordinators, and maintenance leads. These roles provide practical insight into bypass culture, shift handover realities, isolation challenges, and contractor interfaces—areas where deviations can bypass otherwise robust engineering barriers.

Benefits and Practical Use Cases

Applying a structured “what-if” approach yields tangible value when it is integrated into the rhythm of projects and operations:

  • Early risk visibility: Detects layout and integration issues in FEED (e.g., firewater loops, egress routes, vehicle flows at logistics yards) before costs to change explode.
  • Proportionate study depth: Screens for nodes or changes that genuinely require HAZOP or LOPA, focusing specialist time where risk justifies it.
  • Improved barrier management: Clarifies the health of engineered and administrative barriers, linking findings to SCE performance standards and testing regimes.
  • Faster decision-making: Enables informed Go/No-Go decisions for startup or temporary operations, with defensible documentation.
  • Regulatory confidence: Demonstrates a methodical approach consistent with OSHAD, Civil Defence, and ADNOC HSE expectations.
  • Better incident learning: Translates near-miss trends into targeted prompt phrases, strengthening the organization’s collective foresight.

Concrete use cases across UAE industry include screening battery limits between EPC lots on megaprojects to prevent interface hazards; challenging operational readiness at tank farms before hot work near flammable vapor zones (NFPA 30 context); exploring “what if” loss of instrument air during compressor restarts; reviewing construction sequencing to prevent simultaneous operations conflicts; and examining human error paths that could defeat fire and gas shutdowns during maintenance.

Best Practices and Points of Caution

To maximize value and avoid common pitfalls, seasoned teams apply a set of discipline practices:

  • Set clear boundaries. Define the physical and procedural scope so the session is focused but comprehensive within those limits.
  • Use a calibrated prompt library. Tailor prompt phrases to the facility type (offshore platform vs. warehouse), energy sources, and known vulnerabilities.
  • Bring the right mix of people. Include operations, maintenance, engineering, HSE, and supervision—diversity of perspective prevents blind spots.
  • Anchor to data. Use incident trends, alarm logs, bypass registers, and proof test results to validate assumptions about safeguards.
  • Document decisions rigorously. Record initiating causes, consequences, safeguards, and action logic against the corporate risk matrix.
  • Escalate explicitly. Define when a point shifts from “what-if” screening to HAZOP, LOPA, Bowtie, or QRA so higher hazards are treated with higher rigor.
  • Manage actions to closure. Tie actions to owners and verification steps; confirm the barrier has changed, not just a line in a log.
  • Refresh regularly. Revisit prompts after notable incidents or changes in standards (e.g., IEC 61511 updates) to keep the method current.

Caution is warranted in several areas. Over-reliance on experience can leave systematic design weaknesses undiscovered—balance practitioner insight with disciplined prompts and drawings. Treat “administrative controls” carefully; if a single procedure or toolbox talk is claimed as a major barrier, consider whether engineering controls or interlocks are more reliable. When instrumented protections are involved, avoid assigning credit without downstream verification through LOPA or SIL assessment aligned with IEC 61511. Finally, ensure that temporary conditions—scaffolding, temporary blinds, rental compressors—are explicitly considered, as they often shape risk more than steady-state design does.

Frequently Asked Questions About the SWIFT Methodology

How is a structured “what-if” review different from a HAZOP?

Both are systematic and team-based, but they differ in depth and granularity. A HAZOP analyzes defined process nodes using deviation guidewords like “No,” “More,” or “Less,” generating detailed cause–consequence pairs. A SWIFT-style review applies curated prompt phrases to a defined scope, emphasizing breadth and speed to screen issues and prioritize deeper studies where justified.

When should an organization choose this technique over HAZOP or LOPA?

Use it when the change or scope is moderate, documentation is evolving, or a quick, defensible screen is needed—concept design, MoC, pre-startup, or operational mode changes. If scenarios indicate high consequence or complex protection layers, escalate to HAZOP and verify protection credit through LOPA.

Is it acceptable evidence for regulators like OSHAD, Dubai Municipality, or ADNOC HSE?

Regulators expect systematic hazard identification proportional to risk. When properly scoped, documented, and integrated into the organization’s risk management system, a structured “what-if” review contributes credible evidence of due diligence. For high-hazard or complex systems, it should complement—not replace—more rigorous analyses.

Can this method address human factors and organizational issues?

Yes. Prompt sets intentionally cover human error paths, competence and staffing, shift handover, permit-to-work, alarms and bypass management, and contractor interfaces. Including operators, supervisors, and maintenance personnel is critical to surface practical vulnerabilities and realistic safeguards.

How are safeguards and risk rankings handled?

Each scenario records existing engineered and administrative safeguards, then applies the corporate or site risk matrix to estimate residual risk. If residual risk exceeds criteria, actions are defined—design changes, procedural controls, competency measures—or the scenario is escalated to deeper analysis (e.g., Bowtie or LOPA).

Does it integrate with IEC 61511 for Safety Instrumented Systems?

It can provide early identification of hazardous scenarios that might require instrumented protection functions. However, SIL determination, verification, and proof test planning must follow IEC 61511 through appropriate studies such as HAZOP and LOPA. Treat the “what-if” stage as a feeder and triage step, not the final basis of safety for SIS.

What kinds of documents should be prepared beforehand?

Provide relevant P&IDs, PFDs, cause-and-effect charts, layout drawings, operating and maintenance procedures, recent incident/near-miss summaries, and barrier performance information. When reviewing construction or logistics operations, include temporary works plans, traffic management maps, and SIMOPS schedules.

How are actions from the review kept from stalling?

Integrate actions into the site’s action tracker with owners, due dates, and verification steps. Link each action to a risk criterion so its priority is transparent. Include follow-up checks—audits, proof tests, or management reviews—to demonstrate effective closure.

Bringing the Threads Together

Used thoughtfully, the Structured What-If approach helps UAE industrial organizations navigate complex decisions at the speed of operations. Earlier sections highlighted how curated prompts reveal risks that line-by-line analyses might miss in fast-moving contexts; how integration with MoC, pre-startup, and operational change controls keeps actions grounded in reality; and why alignment with standards like ISO 45001, API RP 754, and IEC 61511 ensures that findings flow naturally into the broader safety lifecycle. The balance to strike is proportionate rigor—using “what-if” sessions to screen widely and rapidly, then escalating high-consequence or uncertain scenarios to HAZOP, LOPA, Bowtie, or QRA as needed. In practice, organizations that embed this discipline see tighter barrier management, clearer justifications for startup decisions, and stronger assurance when discussing risk with corporate leadership or regulators.

To go further on this topic, NPM’s broader SWIFT Study Services UAE page covers this in more depth.

Explore NPM’s References

NPM’s references illustrate how disciplined, proportionate hazard identification can drive better outcomes across different sectors and project phases. In upstream and downstream oil and gas, our work has spanned early-phase screening of processing concepts, integration checks for brownfield tie-ins, and operational readiness reviews before hydrocarbon introduction. In petrochemicals and bulk liquid storage terminals, we have helped teams balance throughput increases with safeguards integrity, connecting “what-if” findings to instrumented trip functions and fire and gas logic verified later against IEC 61511. Construction and logistics projects have benefited from scenario-based reviews of temporary works, traffic routes, and SIMOPS, where practical prompts—about access, egress, segregation, and permit interfaces—uncover issues that generic checklists miss. Power and water facilities have applied similar logic to utilities reliability, control room resilience, and emergency response integration with local Civil Defence. These references are not region-limited; they reflect lessons from a global portfolio of studies and operational engagements, giving readers a sense of how different organizations adapt the same core principles to their culture, standards, and regulator expectations. If you are scanning for projects that mirror your own challenges—tight timelines, evolving documentation, multiple stakeholders—the reference set offers concrete examples of how structured, prompt-led reviews underpin defensible decisions and measurable risk reduction without overburdening teams.

For more information about our references, visit Our References.

Speak With NPM

If you have questions about applying a structured “what-if” approach to your facility or how to integrate it with existing HAZOP, LOPA, or MoC processes, NPM is available to discuss practical options. We are glad to share perspectives tailored to your operating context, documentation maturity, and regulator expectations.

For any further questions or to speak with our team, Contact Us.