HAZOP quality is influenced long before the first guideword is applied. Node selection, drawing preparation, workshop scope and participant readiness all affect whether the team can identify hazards efficiently. A poorly prepared study often becomes repetitive, spends too much time clarifying basic design information and leaves important interfaces unresolved. For related engineering support, see our HAZOP preparation and facilitation.
This guide explains how to select useful HAZOP nodes, define design intent, prepare workshop documents and manage the practical issues that make a HAZOP either productive or frustrating.
What is a HAZOP node?
In a HAZOP study, a node is a defined part of the process reviewed against its intended operation. The node may be a section of piping, a vessel and its associated connections, a compressor system, a utility subsystem or another logical process segment.
The node should be small enough that one design intent can be described clearly, but large enough that the study does not become fragmented into dozens of nearly identical sections. There is no universal node size because process complexity varies widely.
Start with the design intent
A useful node has a concise design intent. This normally describes what the section is meant to do, the material being handled and relevant normal operating conditions. If the team cannot explain the intended operation of the node, it will be difficult to identify meaningful deviations from that intent.
The facilitator should review flow direction, pressure and temperature conditions, phase, composition, major equipment, control functions and interfaces before the workshop. This preparation helps distinguish genuine deviations from misunderstandings about how the system is meant to operate.
How to choose node boundaries
Node boundaries are often placed where process conditions, equipment function or operating intent changes. Typical boundaries may occur at equipment nozzles, pressure let-down points, phase changes, mixing points, battery limits, control valves or interfaces between systems.
For example, a high-pressure separator inlet may be treated separately from its gas outlet and liquid outlet because the relevant deviations, causes and consequences differ. A long transfer line with consistent conditions may be one node unless intermediate equipment or interfaces justify subdivision.
Avoid nodes that are too large
Very large nodes can hide important scenarios. If a node contains several pieces of equipment with different functions and operating conditions, a guideword such as “No Flow” may have multiple meanings and the worksheet becomes difficult to follow.
Large nodes can also encourage the team to discuss only the most obvious hazard while overlooking localised causes and consequences. Splitting at meaningful design changes usually improves traceability.
Avoid nodes that are too small
Overly small nodes create the opposite problem. The workshop repeats the same causes, consequences and safeguards across many short piping sections. This consumes time without necessarily improving hazard identification.
A practical facilitator looks for a balance: enough detail to preserve distinct scenarios, but not so much that the study becomes an exercise in reproducing the P&ID line by line.
Prepare marked-up P&IDs before the workshop
Node boundaries should be shown clearly on the working drawings. Numbered or colour-coded nodes help participants follow the study and make the final report easier to review. The node list should align with the worksheet so that each discussion can be traced back to the correct part of the drawing.
Where possible, drawing revisions should be frozen for the workshop period. If design changes continue during the study, the team needs a controlled method for recording what revision was reviewed and whether later changes require revalidation.
What documents should be available?
The P&IDs are central, but they are rarely enough on their own. Depending on project maturity, useful references include process flow diagrams, heat and material balances, process descriptions, equipment datasheets, relief and blowdown information, control narratives, cause-and-effect charts, shutdown philosophies, layout drawings and previous hazard studies.
For brownfield work, current operating procedures, trip history, incident information and existing HAZOP or LOPA records can provide important context. The team should know which assumptions come from existing plant information and which relate to the proposed modification.
Select the right workshop team
HAZOP is a multidisciplinary activity. Typical participants include process engineering, operations, mechanical, instrumentation and control, project engineering and the facilitator/scribe. Electrical, rotating equipment, inspection, maintenance, safety, vendor and specialist disciplines may be required depending on the scope.
The goal is not to maximise attendance. It is to have the knowledge needed to answer the questions raised by the study. A smaller team with the right expertise is often more effective than a large meeting where key technical knowledge is missing.
Prepare the guideword strategy
The facilitator should decide which parameters and guidewords are likely to be relevant to each type of node. Common deviations include no flow, high flow, low flow, reverse flow, high pressure, low pressure, high temperature, low temperature, high level, low level and other-than composition.
Our detailed guide to HAZOP guidewords and deviations explains how to apply these prompts without mechanically testing combinations that have no physical meaning.
Define study assumptions and boundaries
Before starting the first node, the workshop should agree on scope, operating modes, risk matrix use, action categories and important assumptions. It should be clear whether the study covers start-up, shutdown, commissioning, maintenance and temporary operations as well as normal running.
Interfaces with packages or systems outside the current scope should be recorded. An out-of-scope interface can still create a cause or consequence within the node, so it cannot simply be ignored.
Managing recommendations
Recommendations should address a defined issue rather than become vague design suggestions. A good action explains what needs to be resolved and preserves the reason the team raised it. Where practical, actions should avoid prescribing an unnecessary solution before engineering has evaluated the options.
For example, “Confirm whether the relief system is adequate for blocked outlet from the compressor discharge and document the design basis” is more useful than “Install bigger PSV.”
When to refer scenarios to LOPA or SIL assessment
HAZOP identifies scenarios, but it is not always the right tool for detailed risk quantification. High-consequence scenarios may be referred to LOPA to test the adequacy of independent protection layers.
Where instrumented protection is required, the scenario can feed into SIL assessment and classification and the wider IEC 61511 functional safety lifecycle.
Allow realistic workshop time
Workshop duration should be based on complexity and number of nodes rather than a fixed number of drawings per day. A simple utility system can move quickly; a compressor station or complex process unit may require significantly more discussion.
Rushing the final nodes because the schedule was optimistic creates uneven study quality. It is better to establish a realistic pace and adjust the session plan early if the team is progressing more slowly than expected.
Quality checks after the workshop
After the sessions, the facilitator should review the worksheet for incomplete entries, duplicate actions, unclear wording, missing tag references and inconsistent risk rankings. The final report should preserve the study basis, participant list, drawing revisions, assumptions and node definitions.
HAZOP actions should then be tracked through closure, with significant design changes assessed for their impact on the original study.
HAZOP facilitation and engineering support
Pro Engineers supports HAZOP preparation, facilitation, reporting and follow-up alongside HAZID, LOPA, functional safety and process engineering activities.
For projects moving from early definition into detailed engineering, XGEN also discusses why early engineering definition reduces project rework. Strong definition and strong hazard studies reinforce each other.
To discuss a planned HAZOP, revalidation or brownfield modification review, contact Pro Engineers.