HAZOP Action Close-Out: A Practical Evidence Checklist
A practical HAZOP action close-out checklist for project and operations teams, covering scenario traceability, engineering responses, evidence, change control and documented acceptance.
A HAZOP action is ready for close-out when the response addresses the original concern and the supporting evidence has been accepted through the project’s review process. A comment such as “drawing updated” may show progress, but it leaves the reviewer asking which drawing, which revision and whether the change resolves the scenario.
This HAZOP action close-out checklist helps project and operations teams organise that evidence. It is a practical review aid, not a substitute for the facility’s approved procedures, competent engineering assessment or start-up authorisation.
Why HAZOP follow-up needs a clear record
The scope of IEC 61882:2016, the HAZOP application guide, includes documentation and follow-up as well as preparation and examination sessions. The workshop report therefore needs a practical route into engineering work and review.
For Queensland major hazard facilities, WorkSafe Queensland’s adopted guides include safety assessment and safety management systems. Safe Work Australia’s SMS guide provides the wider management context. The applicable facility requirements and current jurisdictional framework still need to be checked for each project.
1. Keep the action linked to its original scenario
Before assessing a response, assemble the action’s context: the study and worksheet reference, node, deviation, cause, consequence, recorded safeguards and original recommendation. Include the drawing revision examined in the workshop.
A useful review question is: “Can someone who missed the workshop understand why this action exists?” If the answer depends on a conversation that was never recorded, clarify the record with the relevant study participants. Preserve the original wording and record the clarification separately so the history remains visible. Our guide to HAZOP node selection and workshop preparation explains the importance of a clear study basis.
2. State the engineering response precisely
Use a short response that explains the work undertaken, the result and its limitations. Distinguish a completed investigation from a completed physical modification. Where the response proposes a different solution, make the alternative visible rather than silently changing the recommendation.
- What question was investigated or what change was made?
- Which operating cases and equipment were included?
- What evidence supports the conclusion?
- What assumptions, exclusions or follow-on work remain?
For example, “assessment complete” is difficult to review. A stronger record names the assessment, its revision, the scenario assessed, the conclusion and the documents affected. This is a documentation example, not a technical acceptance criterion.
3. Match the evidence to the action
Choose evidence that answers the recommendation. Depending on the work, this could include a reviewed calculation, revised P&ID, approved operating procedure, equipment specification or relevant inspection and test record. A link to a folder is less helpful than a document number, revision and the section that supports the response.
Keep design acceptance and implementation evidence distinguishable. An approved design document records an engineering decision; it does not by itself demonstrate that the installed arrangement matches that decision. The UK’s HSE guidance on plant modification describes traceable review and checking intended actions, including hardware and software. It is useful technical guidance, not a statement of Australian legal requirements.
4. Check changes to the original study basis
Close-out can reveal that the design, operating conditions or proposed safeguards have moved on since the workshop. Screen those differences through the facility’s management-of-change process. HSE’s modification guidance highlights that a change can affect plant beyond the immediate equipment being modified.
Ask the responsible engineering team whether the response affects related actions, another node or a linked risk study. Where LOPA or functional safety work is involved, route the relevant changes to those reviewers. Our management-of-change and HAZOP review guide discusses selecting a review appropriate to the change.
5. Record who reviewed and accepted the response
Separate the action owner’s submission from the acceptance decision. Use the project’s defined responsibilities and competence requirements to identify the reviewer and closure authority. Record their decision, date and any conditions. This checklist does not prescribe a universal approval hierarchy.
If evidence is incomplete, make that visible. “Submitted for review”, “returned for clarification” and “awaiting implementation evidence” communicate different situations. Use status names that match the site’s system, and avoid a green status that obscures unresolved work.
A practical HAZOP close-out register checklist
Consider the following fields when checking the completeness of an action record:
- Traceability: action ID, study reference, node and original recommendation.
- Responsibility: action owner, due date and required project milestone.
- Response: work completed, conclusion and remaining limitations.
- Evidence: document references, revisions and relevant records.
- Interfaces: linked actions, change-control references and affected studies.
- Acceptance: reviewer, decision, date, conditions and final status.
At a project milestone, report unresolved actions and their implications explicitly. A percentage-complete figure cannot explain whether a particular unresolved issue prevents the next activity. Any decision to proceed belongs within the operator’s authorised safety and project controls.
An example of a reviewable action response
Consider a fictional workshop action asking the team to clarify which approved operating procedure covers a particular start-up step. A response reading “procedure available” gives the reviewer little to work with. A useful response would identify the procedure and revision, the relevant section and how the action owner checked its relationship to the scenario.
If the review found an ambiguity, the record would also explain what was changed, who reviewed the change and which associated records were affected. Where implementation includes briefing operators, the evidence list would distinguish the approved procedure from the briefing record. A reviewer could then assess the actual response rather than infer completion from a file name.
This example shows a way to structure information. It does not establish that a procedure is an adequate safeguard for any particular hazard, or that training alone resolves a process safety concern.
What if an action cannot be closed?
Record the missing information, the responsible person and the decision it prevents. Distinguish an unresolved technical question from an administrative delay, such as a missing document reference. If the original recommendation is disputed, preserve the reason for that disagreement and refer it to the designated review authority.
Changing a due date or transferring an action to another register does not demonstrate resolution. Keep the original reference linked to any replacement action, and use the facility’s escalation process when a required milestone is at risk. Do not treat this checklist as permission to accept an unresolved hazard or proceed with start-up.
Plan HAZOP follow-up before the workshop ends
Agree early on the register format, evidence location and review responsibilities. That makes it easier for engineers to prepare useful responses and for operations to understand what will change.
For support with study preparation, facilitation or follow-up, explore Pro Engineers’ HAZOP services or contact Pro Engineers to discuss the project scope.