Who Should Attend a HAZOP? Team Coverage and Session Handover Checklist
Plan HAZOP team roles, specialist attendance, substitutions and session handovers. Use a practical coverage sheet to keep knowledge gaps visible.
A HAZOP invitation list can look complete while important knowledge is still missing. An operations manager may not know a particular shift’s workarounds; a package designer may not know the site’s shutdown interfaces. The practical question is not simply “Who should attend?” It is “Who can explain and challenge this part of the process, in the operating modes being reviewed?”
This guide helps project leads plan HAZOP team coverage, substitutions and session handovers. It does not prescribe a universal team size or replace a competent facilitator’s study-specific judgement. For the wider service scope, see HAZOP studies and workshop facilitation.
Start with knowledge coverage, not job titles
Write down the knowledge the study needs before selecting names. Separate understanding of the intended design from experience of the actual plant. For a new development, identify how future operating and maintenance perspectives will be represented. For an existing facility, include people familiar with its configuration and operating history.
As an international reference, the US OSHA process safety management standard, paragraph 1910.119(e)(4), specifies engineering and operations expertise, process-specific experience and knowledge of the analysis method for covered process hazard analyses. This is a US requirement, not a statement of Australian law. It illustrates why a list of senior titles alone is insufficient.
Use the project scope, applicable obligations and company procedures to establish the actual requirements. Confirm the study boundaries first using the node selection and preparation guide; otherwise, you cannot reliably identify which expertise each session needs.
Build a role-coverage sheet
Create one row per knowledge area and record a named contributor, relevant experience, sessions needed and an alternative contact. The following prompts are a starting point, not a mandatory roster:
- Study method: Who leads the structured examination, manages assumptions and identifies when the discussion needs specialist input?
- Process design: Who explains design intent, operating limits, material behaviour and the basis of the current drawings?
- Operations: Who understands routine tasks, transitions, abnormal conditions and the difference between written procedures and observed practice?
- Controls and instrumentation: Who explains relevant control narratives, alarms, interlocks and interfaces without assuming undocumented behaviour?
- Maintenance and inspection: Who can discuss access, isolation arrangements, maintenance modes and known equipment issues?
- Other specialists: Which nodes need electrical, mechanical, materials, human-factors, relief-system, vendor or other expertise?
One person may cover more than one area where their competence and availability support it. Equally, one discipline may need several contributors. Record the basis rather than treating either approach as automatically acceptable. Include a column for information the contributor must bring, such as the current operating procedure or control narrative. This makes the invitation actionable and helps distinguish an availability problem from a missing-document problem.
Separate participation from decision authority
A knowledgeable participant may explain a problem without authority to approve a design change or commit resources. Conversely, a project sponsor may authorise expenditure without supplying the technical evidence needed to assess a scenario.
Record who supplies information, who owns follow-up engineering and who reviews or accepts outcomes under the project’s governance. Do not convert agreement in a workshop into an undocumented approval to modify equipment. The facilitator and recorder also need clear responsibilities: managing the discussion and preserving its meaning are related but different tasks.
The UK HSE’s training and competence guidance links competence to skills, experience and knowledge, and cautions that training alone is insufficient. Applied to attendance planning, this means checking relevant capability rather than relying only on a course certificate, job title or years of general experience.
Plan attendance around nodes and operating modes
Use a session plan showing the proposed nodes and modes alongside required contributors. A vendor specialist may be needed for a defined package discussion, while operations knowledge may need continuity across several sessions. Agree practical availability before issuing a fixed timetable.
Do not schedule solely from drawing numbers. An operating-mode discussion can cross several drawings and require someone who understands start-up, shutdown or maintenance conditions. Identify these dependencies before promising that a specialist can leave after a particular sheet.
Build in a way to adjust the plan when the examination exposes an unexpected interface. Our vendor-package interface checklist helps identify the information needed at boundaries. Its purpose differs from the coverage sheet: the interface checklist organises evidence, while the coverage sheet identifies who can explain and challenge that evidence.
Worked example: a specialist leaves before the relevant discussion
Consider a hypothetical transfer-system study. The controls engineer is booked for the morning, but the team reaches a shutdown-interface question after lunch. Someone recalls how the logic probably works, yet the current cause-and-effect document does not resolve the point.
The useful response is not to record the recollection as a verified safeguard. The team should identify the uncertainty, the affected scenario and the evidence or expertise needed. The facilitator can then determine whether unaffected work can continue or the relevant discussion must be deferred, following the agreed study procedure.
A clear record might state: “Confirm the documented behaviour of the transfer shutdown interface for this scenario; reconvene the relevant contributors before finalising the affected assessment.” This is an example of recording an information gap, not a recommendation for the hypothetical plant’s design or a basis for risk acceptance.
Make substitutions deliberate
When a participant becomes unavailable, ask whether the replacement brings the specific knowledge required, not merely the same department name. Provide the current study basis, relevant drawings, unresolved questions and the session’s starting point before they join.
Record attendance by session, including meaningful arrivals and departures. If a replacement changes or corrects a material assumption, identify which earlier discussions may be affected. Let the facilitator determine the necessary review; do not quietly amend a statement without preserving its consequences elsewhere in the record.
Remote participants need readable drawings, access to the working record and a reliable way to interrupt or challenge. Confirm these arrangements beforehand. A connected microphone is not evidence that the contributor could follow the discussion.
Use a short handover at every session boundary
End a session with a concise handover rather than relying on the next day’s memory. Record:
- The last node or discussion completed and the next planned starting point.
- Open assumptions, unresolved questions and the scenarios they affect.
- Documents or revisions introduced during the session.
- Specialist contributors required for the next discussion.
- Any coverage gaps that prevented an assessment from being completed.
This handover complements, rather than replaces, the formal worksheet. For the broader recording approach, see our HAZOP workshop facilitation and records guide. The official IEC 61882:2016 description identifies preparation, examination, documentation and follow-up as parts of the HAZOP study procedure. The coverage sheet and handover suggested here are practical planning aids, not claimed templates from the standard.
Check the coverage record before issuing the report
Before report issue, reconcile planned attendance with actual participation. Identify deferred discussions, unresolved specialist input and assumptions awaiting verification. Distinguish a completed session from a completed assessment: reaching the end of the diary booking does not resolve the outstanding engineering.
Carry unresolved items into the project’s controlled follow-up process, with responsibility and a review route. The HAZOP action close-out evidence checklist addresses that later stage in more detail.
A useful team plan therefore produces more than an attendance register. It shows which knowledge was available, where limitations remained and how the study preserved those limitations for follow-up. That traceability supports a more useful engineering review without claiming that attendance alone proves safety or compliance.