HAZOP Action Closure: How to Track and Verify Recommendations

A HAZOP meeting identifies hazards, but risk reduction happens only when recommendations are implemented and verified. Actions can remain open because ownership is unclear, the wording is vague, engineering interfaces are missed or documentary closure is accepted without checking the safeguard in the field.

A disciplined HAZOP action closure process converts each recommendation into a controlled task with a risk priority, accountable owner, deadline, technical review and evidence of effectiveness.

1. Write actions that can be verified

Capture the node, deviation, cause, consequence, existing safeguards and recommendation. Replace vague wording such as “review alarm” with a clear deliverable, required decision and acceptance criteria. Retain the link to the original HAZOP worksheet.

2. Prioritise using the assessed risk

Use the organisation's approved risk matrix and escalation rules. High-risk actions may need interim controls, management visibility and shorter deadlines. Priority should reflect the risk scenario, not the cost or convenience of implementation.

3. Assign one accountable owner

Several departments may contribute, but every action needs one accountable owner. Define support functions, budget approval and the person authorised to accept technical closure. Review ownership when roles or project teams change.

4. Route plant changes through MOC

Recommendations that change equipment, control logic, operating limits, layout or procedures should follow management of change. The MOC should review new hazards, drawing updates, training, pre-startup checks and interactions with other safeguards.

5. Match evidence to the recommendation

Examples include approved calculations, revised P&IDs, instrument set-point records, proof-test results, photographs, updated procedures and training attendance. The evidence must demonstrate the specific action, not simply show that related work occurred.

6. Verify effectiveness in the field

Confirm installation and function at the plant. Check that operators understand the change and that inspection or proof-test tasks exist. Where an action is rejected or replaced by an alternative, document the risk review and approval at the required authority level.

Minimum action-tracker fields

• HAZOP node, deviation and recommendation reference.
• Risk rank and any interim risk-control requirement.
• Action owner, support team and target date.
• MOC or project reference where applicable.
• Closure evidence, verifier, verification date and comments.
• Overdue status, escalation and formal risk acceptance.

For facilitation and follow-up support, see our HAZOP study services. If plant conditions have changed, review the HAZOP and QRA revalidation triggers.

Frequently Asked Questions

Can the action owner approve their own closure?

Independent technical verification is preferable for material risk-reduction actions. Follow the organisation's governance and approval levels.

What should happen to overdue high-risk actions?

Escalate them promptly, verify interim controls and obtain documented management decisions. A changed target date alone does not control the underlying risk.

Can a HAZOP recommendation be rejected?

Yes, when a competent risk review shows that another measure or the existing safeguards meet the risk criteria. Record the technical basis and approval; do not silently delete the action.