What If Analysis Checklist

Design Hazard Review for New Processing Facility

What If Analysis Checklist is a practical tool HSE leaders and process safety professionals use to drive consistency and completeness in a What‑If review, especially when time is limited and operations are complex. For asset owners and EPCs across the UAE’s oil and gas, petrochemical, construction, manufacturing, logistics, and power generation sectors, a robust checklist helps teams ask the right questions at the right time — from design and commissioning through day‑to‑day operations and change management — without turning the exercise into a box‑ticking ritual.

At a glance, the approach is simple: pose structured “what if…” deviations against a system and capture credible causes, consequences, safeguards, and actions. In practice, the quality of outcomes depends on the prompts embedded in your checklist, the cross‑functional expertise in the room, and how well the session is anchored to recognized standards like ISO 45001, ISO 14001, IEC 61511, API RP 14C, and local regulatory expectations (OSHAD in Abu Dhabi, Dubai Municipality, Civil Defence, and MOHRE requirements). This article unpacks how to design, use, and maintain a checklist that genuinely improves risk identification and action tracking — not just during formal PHAs, but also during Management of Change (MoC), pre‑start‑up safety reviews (PSSRs), and incident learnings.

Who Does This Affect?

What If Analysis Checklist

Because a What‑If review cuts across process, people, equipment, and environment, the implications reach far beyond the HSE team. In UAE industrial settings, the following functions and roles are typically involved:

  • HSE managers, process safety engineers, and PSM coordinators accountable for corporate standards and regulatory alignment (e.g., ADNOC HSE expectations, OSHAD SF).
  • Operations managers, control room supervisors, and field operators who understand how systems are actually run, started up, and shut down.
  • Maintenance, inspection, and reliability engineers responsible for integrity management of rotating equipment, pressure systems, and SIS/SIF devices under IEC 61511.
  • Project managers, EPC engineers, and construction safety leads delivering brownfield tie‑ins, debottlenecking, and high‑risk site activities (lifting, hot work, confined space).
  • Fire and life safety specialists, including those interfacing with Civil Defence approvals and NFPA‑based design/maintenance practices (e.g., NFPA 30, NFPA 72).
  • Environmental coordinators focusing on emissions, effluents, and waste streams in line with local permits and ISO 14001 aspects/impacts.
  • Facility types such as refineries, gas processing plants, petrochemical crackers, tank terminals, offshore platforms and FPSOs, power stations (including black‑start systems), manufacturing lines involving solvents, and logistics hubs storing hazardous materials.

This diversity of stakeholders is exactly why a good checklist matters: it creates a shared frame, reduces blind spots, and ensures that concerns from operations, maintenance, safety, and engineering are considered on equal footing.

Why This Matters

What If Analysis Checklist

If the previous section established who must weigh in, the next question is why. A structured prompt set reduces the chance that a major accident hazard slips through unnoticed during time‑pressured reviews. In high‑hazard industries, we are typically dealing with loss of primary containment (hydrocarbon release, toxic gas, flammable vapors), fire and explosion risks, as well as occupational exposures and environmental incidents. A single oversight — an isolation valve left non‑lockable, an ESD logic gap, a temporary bypass “forgotten” after maintenance — can translate into severe consequences for people, the environment, assets, and reputation.

A well‑constructed prompt list links directly to process safety objectives supported by standards and good practice. Where HAZOP provides a node‑based, guide‑word approach, the What‑If method deliberately broadens prompts to include human factors, external events, and organizational controls. When your checklist reflects recognized expectations — from API RP 14C safety devices offshore to IEC 61511 lifecycle duties for SIFs, and from OSHAD obligations to ADNOC HSE’s process safety elements — you gain two advantages: more comprehensive hazard identification and easier demonstration of due diligence to regulators, insurers, and corporate oversight.

There is also a performance dimension. Using the same prompt “spine” from design through MoC and PSSR creates a single language for risk. That continuity improves learning transfer, trend analysis across facilities, and the ability to connect PHA outcomes to downstream tools like Layer of Protection Analysis (LOPA), Bowtie diagrams, and Quantitative Risk Assessment (QRA). Done right, the checklist becomes a bridge between analysis and action — a way to verify that safeguards are not only theoretically present but functionally available, independent, and auditable.

Key Points to Understand

What If Analysis Checklist

To avoid turning a checklist into a checkbox exercise, it helps to clarify what a What‑If prompt set should and should not do, how it differs from HAZOP, and how it anchors to your management system.

Scope and Purpose

What If Analysis Checklist

What‑If analysis is scenario‑oriented. Rather than starting with specific process deviations alone, it asks broad but targeted questions: What if the nitrogen purge fails? What if the permit lapses mid‑task? What if a simultaneous operation (SIMOPS) introduces conflicting energy states? Your checklist provides these triggers, organized by thematic areas such as people, plant, process, protection, procedures, and environment.

Relationship to HAZOP, HAZID, and LOPA

What If Analysis Checklist

A HAZOP is guide‑word driven and very effective at interrogating design intent deviations (e.g., pressure high, flow low). A What‑If review complements this by casting a wider net over operational and organizational scenarios, including abnormal situations, human performance variability, and external impacts. In practice, teams often combine methods: start with a HAZID for early concept risk mapping, use What‑If prompts for construction/commissioning and operational contexts, and feed candidates into LOPA when safeguard independence and Probability of Failure on Demand (PFD) need quantification for SIL targets per IEC 61511.

Checklist Structure

What If Analysis Checklist

Strong checklists are modular and traceable. Typical sections include:

  • Energy sources and isolations (electrical, mechanical, hydraulic, pneumatic, thermal).
  • Containment and transfer (lines, hoses, tanks, relief paths, overfill/overflow controls).
  • Control systems and alarms (DCS, ESD, instrument air, cybersecurity considerations).
  • Protection layers (PSVs, dikes, gas detection, firewater/foam, interlocks, SIS).
  • People and organization (competence, fatigue, supervision, contractor interfacing, language barriers, simultaneous operations).
  • Procedures and permits (PTW, LOTOTO, confined space, hot work, excavation, lifting plans, traffic management).
  • Environment and community (emissions, effluents, noise, odors, sensitive receptors, waste handling).
  • Emergency response and recovery (Muster, fire team readiness, spill kits, mutual aid, ERP alignment with Civil Defence).

In many organizations, evidence packs and templates are curated centrally. When teams want examples of prompt sets or action tracker formats, they often turn to document hubs and knowledge libraries; for instance, internal or partner repositories like CABINET NPM are used in some programs to maintain controlled versions and revision histories of best‑practice materials that inform front‑line workshops, without replacing engineering judgement.

Recording Outcomes

What If Analysis Checklist

Clarity in documentation enables follow‑through. A practical What‑If worksheet will capture the scenario, its causes and consequences, the safeguards credited (and their type), an action if risk is not as low as reasonably practicable, the action owner, and a due date. A simple table format helps maintain discipline and enables later aggregation for KPI reporting under process safety management frameworks (e.g., API RP 754 for metrics).

Node/System What‑If / Deviation Causes Consequences Existing Safeguards Risk Rank Action Owner Due Date
Tank TK‑101 (Diesel) What if overfill occurs during transfer? Gauge failure; valve left open; pump run‑on Spill to bund; fire; environmental release High‑level alarm; independent high‑level switch; bund Medium Verify proof‑test interval of IHL; install automatic cut‑off Inst. Eng. 30‑Sep
Offshore Separator What if instrument air is lost? Compressor trip; header isolation Valve fail states; process upset; flare load Fail‑safe positions; ESD; flare capacity High Review fail positions and ESD logic; add low IA alarm to CCR Process Eng. 15‑Oct
Construction Lifting Area What if wind exceeds limit mid‑lift? Forecast miss; sudden gust Load swing; collision; dropped object Lift plan; anemometer; exclusion zone Medium Define real‑time wind hold points; train banksman; revise SIMOPS matrix Constr. Mgr 05‑Nov

How This Works in Practice

What If Analysis Checklist

With the structure in mind, implementation becomes a matter of disciplined preparation and facilitation. Organizations that consistently extract value from What‑If reviews typically follow a repeatable flow that aligns with their PSM or EHSMS framework.

  1. Define scope and objectives: Is this a design package, a PSSR for a brownfield tie‑in, a temporary operation, or a routine MoC? Clarify system boundaries and success criteria.
  2. Assemble the right team: Blend operations, maintenance, instrumentation, safety, and engineering. Include contractors where the activity is contractor‑executed, and ensure someone can speak to regulatory commitments (e.g., OSHAD, Civil Defence).
  3. Gather inputs: P&IDs, cause‑and‑effect charts, layout drawings, plot plans, procedures, SIMOPS matrices, lifting plans, PTW templates, ERP extracts, integrity records, and recent incident learnings.
  4. Perform a site walkdown (when applicable): Validate that drawings reflect reality. Identify temporary connections, isolation points, access/egress, and emergency equipment.
  5. Work through the prompt set: Use your checklist methodically but allow digressions where credible scenarios arise. Record safeguards against categories (prevention, control, mitigation) and check independence where LOPA may follow.
  6. Risk rank and act: Apply your corporate matrix aligned with ISO 31000 and local expectations. If risk is not ALARP, capture a corrective action with a clear owner and due date.
  7. Validate safeguards: Where a safeguard is credited, confirm its proof‑testing, impairment management, and bypass control, particularly for SIS loops under IEC 61511.
  8. Close‑out and learn: Integrate actions into your CMMS or action tracker, monitor closure, and share learnings across similar assets or projects.

Real‑world examples bring the above to life:

Refinery debottlenecking: During a tie‑in to a kerosene rundown line, prompts about temporary blinds, pressure relief capacity, and simultaneous hot work led to adding a secondary isolation and a gas testing regime after breaks. The review also flagged that the existing flare header study assumed lower peak loads; a focused check averted an exceedance during start‑up.

Offshore platform utility air: A “what if instrument air fails” prompt triggered a deeper dive into fail‑as‑is valves on critical skids. The session resolved to change a fail position and improve CCR alarm rationalization, preventing spurious trips and ensuring safe states during loss of air.

High‑rise construction lifting: Asking “what if wind conditions change mid‑lift” prompted a review of in‑field anemometer calibration, crane derating, and communication protocols. The checklist made the team identify an exclusion zone shortfall relative to the lift radius and downwind hazard footprint.

Manufacturing paint line: Prompts about solvent storage and transfer caught a missing bonding/earthing step for drum changes and an out‑of‑date hot work procedure. The facility implemented a revised LOTOTO checklist and upgraded leak detection.

Power generation black‑start: Considering “what if diesel quality is degraded” led to improved filtration and periodic sampling, while “what if the UPS fails” drove a redundant supply check on the critical control PLC.

Benefits and Practical Use Cases

With consistent application, a well‑built prompt set delivers more than a tidy workshop record. It has material impacts on safety, compliance, and operational performance.

  • Completeness: Systematically prompts less obvious scenarios — e.g., common cause failures, power loss states, or contractor interfaces — that HAZOP alone may not surface.
  • Consistency across sites: Using a common core allows corporate teams to benchmark risks and safeguards across refineries, terminals, and manufacturing plants, enabling targeted campaigns (e.g., alarm management, PSV proof‑test optimization).
  • Traceability and auditability: Clear linkage from scenario to action supports audits by ADNOC group companies, OSHAD verifiers, or Civil Defence inspectors, and provides defensible evidence of duty of care.
  • Speed with rigor: Teams move quickly through frequently recurring questions while diverting time to unique, high‑energy hazards — valuable during PSSRs and tight shutdown windows.
  • Integration with the safety lifecycle: Items that escalate to LOPA or SIL allocation are naturally captured with the context needed for IEC 61511 justification.
  • Better change management: Embedding the prompt set in MoC workflows ensures temporary and permanent changes receive equivalent scrutiny.

Applied examples include using the prompt list as a SIMOPS screen for a tank farm expansion; as a targeted review for temporary operations like nitrogen purging or mobile flare stacks; as an onboarding tool for new operations teams to learn “how risk looks” at their facility; and as a structured learning review after near‑misses to update prompts and safeguards.

Best Practices and Points of Caution

The advantages above only hold if teams avoid complacency and treat the checklist as a living, evidence‑based guide rather than a static form. The following points reflect lessons NPM has seen repeatedly across industries:

  • Anchor to credible sources: Map each prompt to a standard, code, or internal requirement. Examples include IEC 61511 for SIS, API RP 14C offshore, NFPA 30 for flammable liquids, and corporate PSM elements. This helps justify prompts and sustain them through audits.
  • Design for modularity: Keep core prompts consistent across the enterprise, and add annexes for context (offshore SIMOPS, construction lifting, cryogenics, combustible dusts).
  • Balance breadth and depth: A 50‑page list is unusable in the field. Prioritize high‑energy scenarios and allow facilitators to expand based on process knowledge.
  • Preserve facilitator discretion: The checklist should guide, not constrain. Create space to pursue emergent scenarios — especially human factors and organizational drift.
  • Verify safeguards before credit: If a safeguard is claimed, confirm proof‑testing, bypass control, and impairment management. For alarms, check rationalization and operator response windows.
  • Keep it current: After incidents, MoCs, and regulatory updates, revise the prompt set and highlight deltas for users. Build version control and communicate changes.
  • Integrate with action management: Link outcomes to your CMMS or risk action tracker, and define closure evidence (photos of tags, test certificates, DCS screenshots).
  • Mind interfaces: Construction/operations, contractor/company, and multi‑site boundaries are common failure points. Add explicit prompts for handovers and responsibilities.
  • Respect local requirements: OSHAD codes of practice, Dubai Municipality approvals, and Civil Defence guidance shape minimum expectations; include them directly in your prompts where relevant.
  • Test usability: Pilot the checklist on a small scope. If the team needs frequent clarifications, refine language and sequencing before wider rollout.

Finally, treat the prompt set as intellectual capital. Curate it centrally, ensure controlled access, and maintain a change log so frontline teams know what has evolved and why. Reference repositories and knowledge libraries help, but they do not replace the need for subject matter oversight and periodic technical stewardship.

Frequently Asked Questions About What‑If Analysis Checklists

How is a What‑If checklist different from a HAZOP guide‑word list?

A HAZOP guide‑word list interrogates deviations from design intent at specific nodes (e.g., pressure high, level low). A What‑If checklist is scenario‑driven and broader, intentionally covering human factors, organizational controls, temporary operations, and external impacts. Many organizations use both: HAZOP for design rigor and What‑If for operational completeness.

Where should the checklist be used — only in PHAs?

It is useful in PHAs, but also in MoC reviews, pre‑start‑up safety reviews, SIMOPS planning, contractor onboarding, and post‑incident learning reviews. Using the same prompt set across these activities builds a consistent risk language and improves capture of learnings.

What level of detail is appropriate for the prompts?

Prompts should be specific enough to trigger meaningful discussion (e.g., “What if instrument air fails?”) yet general enough to apply across systems. Organize them by theme and add annexes for unique hazards such as cryogenic systems, combustible dust, or offshore lifting. Excessive granularity can slow sessions without adding value.

How do we prevent the checklist from becoming a “tick‑box” exercise?

Enable facilitator discretion, keep the list prioritized by risk, and emphasize evidence when crediting safeguards. Rotate participants, include operators and maintainers who know real‑world practices, and continuously refresh prompts based on incidents and MoC outcomes.

Which standards should inform a strong prompt set?

Common references include IEC 61511 (SIS lifecycle), API RP 14C (offshore production safety systems), ISO 45001 and ISO 14001 (management systems), NFPA codes relevant to your hazards (e.g., NFPA 30 for flammables), and local requirements such as OSHAD SF, Dubai Municipality technical guidelines, Civil Defence fire/life safety expectations, and MOHRE worker welfare obligations. Where quantitative justification is needed, link to LOPA and QRA practices.

How should actions and safeguards be recorded and followed up?

Use a structured worksheet with scenario, causes, consequences, safeguards, risk rank, action, owner, and due date. Integrate the list with your CMMS or action tracker, assign accountable owners, and define closure evidence. Periodically report status against process safety KPIs and ensure overdue items receive escalation.

Can a single corporate checklist work across refineries, offshore platforms, and construction projects?

A common core can, but include modular annexes for context‑specific risks. Offshore SIMOPS, marine operations, lifting in congested construction sites, or combustible dust in manufacturing lines each require tailored prompts. Keep the backbone consistent while enabling local additions.

How do we connect What‑If outcomes to SIL and LOPA decisions?

When a scenario’s residual risk appears high or relies heavily on instrumented protection, feed it into LOPA to evaluate independent protection layers and target SILs per IEC 61511. Ensure safeguards credited in the What‑If are categorized (prevention, control, mitigation) and check for independence before LOPA quantification.

Final Thoughts and Next Steps

Building and using a What‑If prompt set is not about paperwork; it is about asking better questions, more consistently, across the lifecycle of your assets. As discussed earlier, the value comes from integrating broad scenario prompts (beyond pure process deviations), anchoring them to standards (IEC 61511, API RP 14C, ISO 45001/14001), and applying them where it counts — during design reviews, PSSRs, MoCs, and operational planning. The examples from refining, offshore, construction, manufacturing, logistics, and power settings show how targeted questions expose hidden couplings, safeguard gaps, and assumptions. Equally, the cautions above remind us that complacency is the enemy: keep the list living, verify safeguards before credit, and let facilitators pursue credible scenarios beyond the page. Used this way, a What If Analysis Checklist becomes a practical engine for risk reduction, regulatory confidence, and operational discipline.

To go further on this topic, NPM’s broader What If Analysis Services UAE page covers this in more depth.

Our References

NPM’s portfolio demonstrates how structured, scenario‑based thinking translates into safer, more reliable operations. Across refineries, offshore platforms, petrochemical complexes, high‑rise construction programs, manufacturing plants, logistics terminals, and power stations, our teams have helped clients embed prompt‑driven reviews into the fabric of their EHS and process safety management. The thread running through these assignments is continuity: using a consistent core of questions across design, pre‑start‑up checks, and Management of Change so that what is learned in one project informs the next. This continuity, coupled with rigorous action tracking and evidence‑based verification, has supported clients during regulator engagements, insurer due diligence, and internal audits.

Our references also reflect deep integration with complementary methods — from HAZID and HAZOP to LOPA, Bowtie, and QRA — allowing organizations to move seamlessly from qualitative discovery to quantitative justification. Whether aligning to IEC 61511 for SIS lifecycle tasks, ensuring API RP 14C expectations are met offshore, or demonstrating conformance with OSHAD Framework requirements, the focus is always on tangible risk reduction and practical operability. We have seen the benefits of modular prompt sets first‑hand: core corporate backbones augmented with annexes for specialized hazards such as marine SIMOPS, temporary operations during shutdowns, combustible dust handling, or cryogenics. This approach provides consistency where it matters and flexibility where it counts.

These case histories span multiple geographies and regulatory environments, underscoring NPM’s worldwide experience in translating standards and good practice into action on the ground. Readers seeking a deeper view of the types of facilities, scenarios, and outcomes involved are invited to browse selected highlights and summaries. For more information about our references, visit Our References.

Speak With NPM

If you have questions about tailoring a prompt set to your facility, or how to integrate What‑If reviews with HAZOP, LOPA, and MoC workflows, we are happy to share perspectives. A brief conversation can help clarify practical next steps and common pitfalls to avoid. For any further questions or to speak with our team, Contact Us.