A HAZOP node is a defined part of the system or procedure being examined. Pair a clear boundary with design intent so the team can test meaningful deviations.
Updated: 3 November 2026. This revision replaces fixed node-size, time and parameter rules with a scope-based explanation. A HAZOP node is a defined part of a process, system or procedure that the team examines as one study section. Design intent states what that section should do and the operating conditions relevant to the study. A useful boundary gives the team enough context to identify meaningful deviations without mixing unrelated functions. IEC 61882 describes HAZOP study definition, preparation, examination and follow-up; the exact node boundary should fit the study scope and information available. (IEC 61882:2016)
What should a HAZOP node boundary identify?
For each node, record the boundary and references that let another reader find the same section, such as:
- the equipment, process segment or procedure step included;
- relevant inlets, outlets and interfaces;
- the drawing, document or procedure revision;
- operating mode and assumptions;
- the function the section is intended to perform.
A process HAZOP often uses P&IDs, but a HAZOP can also examine procedures or other system descriptions. Do not define a node only as “the highlighted pipe” if its interactions or operating modes are important to the analysis.
How do you write design intent?
Write one or two sentences that say what the node does and under what relevant conditions. Use site-approved design information for materials, destination, flow, temperature, pressure, sequence or other parameters that matter to the study.
| Less useful | More useful structure |
|---|---|
| “Move liquid from the tank to the reactor.” | “Transfer the specified feed from [source] to [destination] in [operating mode], within the design flow and operating-condition limits recorded in [verified source document].” |
| The bracketed details are placeholders. A study team must replace them with verified site information. Do not copy sample chemicals, tags, setpoints or limits into a real study. |
How large should a node be?
There is no single node size that suits every process. A node may be too broad if several functions or operating conditions make it difficult to keep one clear design intent. It may be too narrow if splitting it removes the interfaces or cause-and-effect relationships the team needs to examine. The team should choose boundaries that keep the discussion coherent and preserve relevant interactions.
During preparation, check whether the boundary changes at an equipment interface, a significant change in function, a different operating mode or a separate procedure step. Those are prompts for discussion, not automatic rules to split a node.
What should the team verify before analysis?
- Scope: Confirm which system, procedure, modes and interfaces are included.
- References: Record the approved drawing or procedure number and revision.
- Intent: Agree what the node should do; note applicable design limits and their source.
- Boundary: Mark the start, end and connections clearly for every participant.
- Missing information: Record open questions and assumptions for resolution; do not treat them as verified facts.
- Review: Revisit boundaries when the team finds that a node contains materially different functions or loses important context.
Good node definition helps the team apply HAZOP guide words consistently. For a hypothetical worked row, see the illustrative HAZOP example; for the wider workflow, see the HAZOP study guide.
Frequently asked questions
Is a HAZOP node always a physical P&ID section?
No. A process HAZOP commonly uses drawings such as P&IDs, while a procedural HAZOP examines defined steps. The study scope and chosen reference documents determine what the team treats as a node.
Must design intent contain exact numerical limits?
Include numerical conditions when they are relevant and supported by approved information. The team should not invent a flow, temperature or pressure value just to make the statement look precise.
Should each pump or valve become its own node?
Not automatically. Decide whether a separate boundary helps the team assess design intent and interactions. Record the rationale in the study preparation material.
Do node definitions make a HAZOP legally compliant?
No. Clear nodes support a systematic study, but they do not establish compliance by themselves. For a South African MHI, Regulation 10 sets the AIA and SANS 1461 risk-assessment requirement. (Major Hazard Installation Regulations, 2022, reg. 10)
Need help planning a workshop? Contact MMRisk with the process, system or procedure and the documents available for review.