A HAZOP study is a structured way of asking one question over and over across a whole process: what happens if this stops working exactly as designed.
It does not rely on a team simply remembering past incidents. It walks every section of the process with a fixed set of guide words, so nothing gets skipped by accident.
That discipline is why HAZOP remains the most widely used process hazard analysis method in chemical, oil and gas, and process industries worldwide.
This guide covers the guide words, how a deviation is built, the full study procedure, and who needs to sit in the room for it to work.
A HAZOP study is a systematic, team based technique that applies standardized guide words to process parameters at defined points in a system to identify deviations that could cause a hazard or an operability problem.
Every process is designed to run within a certain window of flow, pressure, temperature, level, and composition. A HAZOP study exists to find every realistic way that window gets breached.
Rather than leaving that search to memory or intuition, the method forces a team through every process section using the same fixed vocabulary each time.
This article walks through how that vocabulary works, how a HAZOP study is actually run from start to finish, and what the output looks like once the study is complete.
What a HAZOP Study Actually Is
The HAZOP method breaks a process into small sections called nodes, usually a single pipe run or a single vessel, and studies each one on its own.
For every node, the team lists the relevant parameters, things like flow, pressure, temperature, level, and composition, and then challenges each parameter with a fixed guide word.
A HAZOP study follows the international standard IEC 61882, which defines the guide word method along with the expected worksheet structure and study deliverables.
The Seven Guide Words That Drive Every HAZOP
Each guide word represents one way a parameter can drift away from what the design intended, and combining a guide word with a parameter produces a deviation.
| Guide Word | Meaning | Example Deviation |
|---|---|---|
| No | Complete absence of the intended function | No Flow |
| More | A quantitative increase in the parameter | More Pressure |
| Less | A quantitative decrease in the parameter | Less Temperature |
| As Well As | Something extra occurs alongside the intended result | As Well As Contaminant Present |
| Part Of | Only part of the intended result is achieved | Part Of Composition Missing |
| Reverse | The opposite of the intended action or direction | Reverse Flow |
| Other Than | Something entirely different happens instead | Other Than Design Fluid Present |
Applying these seven words to every parameter in every node is what makes the method systematic rather than a loose brainstorming session.
How a Node Turns Into a Deviation
A node is a defined boundary within the process, commonly a pipe segment between two pieces of equipment or a single vessel with its own design intent.
Inside that boundary, the team lists parameters worth challenging, then works through the guide words one at a time, recording anything that looks like a genuine possibility.
Every deviation found this way still needs its own cause, consequence, and safeguard before it becomes a useful finding, which is exactly what the worksheet columns exist to capture.
HAZOP Study Deviation Builder
Pick any guide word and parameter combination below to see the deviation statement it produces, along with a typical cause and consequence for two common combinations.
Two Deviations Analyzed End to End
Case one applies the No guide word to Flow on a feed line into a reactor.
Guide word = No
Parameter = Flow
Deviation = No Flow
Cause = Pump failure, blocked line, or valve left shut
Consequence = Downstream equipment starves, reaction can stall
Safeguard = Low flow alarm with pump interlock
Case two applies the More guide word to Pressure on a storage vessel.
Guide word = More
Parameter = Pressure
Deviation = More Pressure
Cause = Downstream valve fails closed while feed continues
Consequence = Vessel stressed past design limit, relief device may lift
Safeguard = Pressure relief valve and high pressure alarm
Both examples follow the same pattern. A deviation on its own is only half the finding, the cause, consequence, and safeguard columns are what actually make it actionable.
The HAZOP Study Procedure Step by Step
- Define the process scope and record the original design intent for each section under review.
- Split the process into nodes, typically along pipe runs and vessel boundaries.
- List the relevant parameters for each node in turn.
- Apply every guide word to every parameter systematically, generating deviations.
- Discuss and record realistic causes for each deviation the team accepts as worth studying.
- Trace the consequence of each cause through to its worst credible outcome.
- Note existing safeguards, then raise recommendations wherever protection looks insufficient.
- Document everything in the node register, deviation worksheets, action item register, and assumptions register.
Who Sits on a HAZOP Team
Facilitator
Leads the session and keeps the guide word method applied consistently across every node.
Scribe
Records deviations, causes, consequences, safeguards, and recommendations in real time.
Process Engineer
Explains the intended chemistry and process behavior for each node under review.
Operations Staff
Brings first hand knowledge of how the process actually behaves during real operation.
Maintenance Staff
Adds insight into equipment reliability and how failures actually show up in the field.
Control Systems Specialist
Addresses instrumentation, alarms, and interlock design relevant to each deviation.
A mixed team of three to eight people, drawn from different disciplines, is what keeps a HAZOP study from missing scenarios that a single specialist working alone would overlook.
Comparing HAZOP with Other Hazard Analysis Methods
| Method | Core Approach | Best Suited For | Limitation |
|---|---|---|---|
| HAZOP Study | Guide word deviations applied node by node | Continuous processes with defined P&IDs | Time intensive for large, complex plants |
| What If Analysis | Open ended questioning by an experienced team | Simpler processes or early design review | Depends heavily on team experience, less structured |
| FMEA | Failure modes traced at the component level | Equipment and instrument reliability studies | Does not naturally capture process level interactions |
| LOPA | Quantifies protection layers against a specific scenario | Following up on HAZOP findings needing risk ranking | Needs a defined scenario as a starting point, usually from HAZOP |
Why HAZOP Findings Actually Change Designs
A HAZOP recommendation is not just paperwork. It routinely results in an added interlock, a resized relief valve, a revised operating procedure, or a new alarm setpoint before a plant is ever commissioned.
Skipping or rushing the study tends to push those same fixes later into the project, when they cost far more to implement and sometimes require shutting down an operating unit to install.
Treating the study as a genuine design review, not a compliance checkbox, is what determines whether its findings actually make it into the final plant.
HAZOP Study Do's and Don'ts
✓ Do
- Work through every guide word on every parameter, even ones that seem unlikely at first glance
- Include operations and maintenance staff, not only design engineers
- Record assumptions explicitly rather than leaving them undocumented
- Track every recommendation to closure with a named owner and a deadline
✗ Don't
- Skip nodes that seem simple just to save session time
- Let one dominant voice decide consequences without team discussion
- Treat an existing safeguard as adequate without actually checking it
- Close out the study before every recommendation has an owner
More on IEC 61882 and HAZOP Practice
HAZOP Questions Teams Often Ask
External References
- Primatech: HAZOP, Hazard and Operability Study
- iFluids: What Is HAZOP Study, IEC 61882 Method, Steps and Deliverables
What We Learn Today
- A HAZOP study applies seven fixed guide words to process parameters at each node to systematically generate deviations.
- Every deviation needs a documented cause, consequence, and safeguard before it becomes a useful finding.
- The study follows IEC 61882 and produces a node register, deviation worksheets, an action item register, and an assumptions register.
- A mixed team of engineers, operators, and maintenance staff, led by a trained facilitator, is what makes the method work in practice.