Not every process needs the rigid, line-by-line discipline of a full HAZOP, and What-If analysis is the technique that offers a lighter alternative. It is a structured brainstorming method built around a simple question repeated across a process: what if this went wrong? This guide explains how a What-If study works, the What-If/checklist hybrid that adds a safety net, when operators choose it over HAZOP, and how a record of past upsets can seed the questions that make it effective.
What-If Analysis in one line: A What-If analysis is a process hazard analysis technique in which a team systematically asks a series of what-if questions about deviations, failures, and upsets in a process, then evaluates the consequences and adequacy of safeguards for each. It is less rigidly structured than HAZOP, relying on the experience of the team to generate the questions, which makes it well suited to simpler or well-understood facilities. A common variant, the What-If/checklist, pairs the brainstorming with a standard checklist so that important topics are not missed.
A What-If analysis proceeds through a process, section by section, with a facilitator prompting the team to raise what-if questions: what if a valve is left open, what if a pump loses suction, what if the feed contains water, what if power is lost during start-up. Each question describes a plausible deviation or failure, and for each one the team works through the consequences, identifies the existing safeguards, judges whether they are adequate, and records recommendations where they are not. The questions and their answers are captured on a worksheet so the analysis is documented and its conclusions traceable.
The defining feature of What-If is that it is guided by experience rather than by a fixed grammar. A HAZOP forces the team through a matrix of guidewords and parameters at every node, which guarantees coverage but takes time. What-If instead trusts a knowledgeable team to raise the questions that matter, which makes it faster and more flexible but also more dependent on who is in the room. A team that knows the process well and has seen its failure modes will generate rich, relevant questions; a weak or inexperienced team may leave gaps precisely because nothing forces them to consider a topic they did not think of.
That dependence on the team's imagination is the method's main limitation, and it is the reason facilitation matters. A good facilitator keeps the questioning systematic - moving through the process in order, covering operating modes beyond normal running such as start-up, shutdown, and maintenance, and pushing the team past the obvious failures. Documented worksheets and a defined scope keep a What-If from drifting into an unstructured conversation, which is the failure mode the technique is most prone to.
Because a pure What-If can miss topics that no one happens to raise, many teams use the What-If/checklist hybrid. Here the brainstorming is backed by a standard checklist of hazard categories, equipment types, and known failure modes drawn from experience and codes. The team runs the open-ended what-if questioning to capture the process-specific concerns, then works the checklist to confirm that the common, well-established hazards have all been considered. The two halves complement each other: the what-if half catches the unusual and site-specific, and the checklist half provides the systematic coverage that a free brainstorm can lack.
Choosing What-If over HAZOP is a judgement about the process and the risk. What-If is often selected for simpler processes, for facilities that are well understood and similar to others already studied, for smaller modifications, or for an early-stage screening that decides whether a fuller study is warranted. HAZOP tends to be reserved for complex, novel, or high-hazard processes where the exhaustive, node-by-node discipline is worth the extra effort. The choice is not about one method being better; it is about matching the rigour of the technique to the complexity and consequence of the process being analysed.
It is worth remembering that What-If, like HAZOP, is one of the recognised methods that can satisfy a process hazard analysis requirement. Selecting it does not lower the bar for what the study must cover - the same breadth of hazards, controls, and consequences still applies - it only changes how the team goes about identifying them. A well-run What-If/checklist on an appropriate process can be entirely credible; the danger is using an under-structured What-If on a process complex enough to have deserved a HAZOP.
The quality of a What-If study rises or falls on the quality of the questions, and one of the best sources of good questions is what has actually gone wrong before. A record of past process upsets - the times a level ran high, a compressor tripped, a separator carried over, a line froze in cold weather - is a catalogue of real deviations that the team can turn directly into what-if questions. Rather than relying only on imagination, the team can ask what if the conditions behind a known upset recurred, and whether the safeguards that caught it last time would still be adequate.
This is especially valuable because operating history surfaces the awkward, site-specific failure modes that a generic checklist would never contain. The particular way a given plant tends to lose suction, the ambient conditions that cause its instruments to drift, the operating step where it habitually alarms - these are exactly the details a What-If team wants and exactly what a free brainstorm can overlook. Alarm and trip records, trends showing the process drifting toward its limits, and the sequence of events around previous shutdowns give the team concrete material to interrogate.
Merobix, as cloud SCADA for oil and gas, retains alarm activity, trip events, and process trends from many remote sites in one browser, which makes that upset history straightforward to review before a study. The What-If analysis itself remains the work of a knowledgeable team following the method, but arriving with a factual record of how the process has misbehaved gives the team better prompts than memory alone, and helps ensure the what-if questions reflect the failures the plant has actually shown rather than only the ones people happen to recall.
What-If is generally chosen for simpler or well-understood processes, smaller modifications, or early screening, where its flexibility and speed are an advantage and the process is not complex enough to require an exhaustive study. HAZOP is preferred for complex, novel, or high-hazard processes where its rigid, node-by-node coverage is worth the extra effort. The choice matches the rigour of the method to the complexity and consequence of the process.
It is a hybrid that pairs open-ended what-if brainstorming with a standard checklist of hazard categories and known failure modes. The what-if half captures process-specific and unusual concerns, while the checklist half provides systematic coverage of common, well-established hazards. The combination reduces the main weakness of a pure What-If, which is that it can miss topics no one happens to raise.
Yes, What-If and What-If/checklist are among the methodologies recognised as acceptable ways to perform a process hazard analysis under OSHA PSM. Choosing What-If does not reduce the required scope of the study - the same breadth of hazards, controls, and consequences must still be addressed. It only changes the technique the team uses to identify them, so the method must be appropriate to the process's complexity.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.