HAZOP Review: How to Lead a Plant Modification in 30 Days
A practical 8-step HAZOP guide for plant modifications, showing how to set the boundary, test safeguards, assign decisions, and verify startup readiness.

Key takeaways
- 01Define the modification boundary, including temporary states and interfaces, before the first HAZOP session.
- 02Build a 4 to 8 person team that combines design knowledge, operating experience, maintenance insight, and EHS judgment.
- 03Test safeguards by detection, response, ownership, verification method, and failure condition rather than by paperwork count.
- 04Convert every recommendation into a decision with an owner, due date, closure evidence, and startup consequence.
- 05Use the HAZOP to make risk visible before work starts, then keep the conversation alive through field verification and leadership review.
A HAZOP review can produce a polished worksheet while leaving the plant exposed to the change it was meant to control. This guide shows a supervisor, process engineer, or EHS manager how to lead a plant-modification HAZOP in 30 days, connect the study to field controls, and stop the review from becoming a filing exercise.
Step 1: Define the modification boundary
Start by writing one sentence that states what is changing, where it changes, and what remains outside the review. A boundary such as “new solvent transfer pump in Area 4, including suction, discharge, controls, and startup” gives the team a workable object, while “review the project risks” does not.
The boundary must include temporary states, because commissioning, bypasses, flushing, testing, and first production often carry a different exposure from normal operation. OSHA’s Process Safety Management rules require covered facilities to manage process changes through a written procedure, and its standard describes the management-of-change elements that keep technical, safety, and operating information aligned.
Record three exclusions beside the boundary. If an excluded interface can change the hazard path, bring it back into scope before the first workshop.
Step 2: Assemble the right review team
A HAZOP team works when its members can explain the design, the operating reality, and the safeguards that will be tested. For a plant modification, appoint one facilitator, one process or design engineer, one experienced operator, one maintenance or reliability representative, and one EHS or process-safety representative.
Do not treat attendance as proof of competence. Ask each person to bring one artifact and one concern. The operator should bring the current operating sequence, maintenance should bring failure history, and engineering should bring the latest drawings and control narrative. Andreza Araujo’s Safety Culture: From Theory to Practice makes a related point about the distance between a declared system and the conditions that make it real. The team has to close that distance with evidence, not seniority.
Keep the group between 4 and 8 active voices. Larger groups can attend as observers, but the facilitator should prevent silent consensus from replacing technical disagreement.
Step 3: Freeze the evidence set
Before the first session, issue one controlled evidence pack with the P&IDs, cause-and-effect diagrams, operating procedures, equipment data, alarm list, relief basis, layout, emergency response assumptions, and the proposed startup sequence. Put a revision and date on every item.
Evidence quality matters because a HAZOP can only challenge the design that the team can see. OSHA’s process-safety guidance explains why process information, operating procedures, training, and pre-startup review must connect rather than sit in separate files.
Use a two-column check before the meeting. The first column lists the document the design requires. The second records who verified that the field condition, software logic, or operating instruction matches it. Missing evidence becomes an action before it becomes an assumption.
Step 4: Select nodes that expose the change
Divide the modification into nodes that have one clear purpose and a manageable flow path. A transfer system may need separate nodes for storage outlet, pump suction, pump discharge, blending entry, and return line. If a node contains an entire process area, the discussion will become general and the deviations will lose their connection to equipment.
Choose nodes around changed energy, changed chemistry, changed control logic, changed access, or changed staffing. ISO 31000 sets out principles for risk management that support this boundary discipline. That approach is more useful than copying the old study and changing a few equipment numbers.
For each node, write the intended design intent in one sentence and list the normal operating limits. Then compare the new node with the operating envelope and decision record used by the plant, because the HAZOP should not create a second version of the risk boundary.
Step 5: Run deviations in a fixed sequence
Apply guide words consistently so the team tests more than the obvious loss of flow. For each node, work through no, more, less, reverse, as well as, part of, and other, then record causes, consequences, existing safeguards, recommendations, and the person who owns the next decision.
The facilitator should ask the operator what would be seen first, the engineer what would fail first, and the maintenance representative what would make the failure persist. Those three views expose different parts of the same deviation, which is why a fast verbal review cannot replace a structured study.
Limit each deviation discussion to a defined timebox, such as 10 to 15 minutes, unless the team identifies a credible high-consequence pathway. When discussion expands, split the deviation into separate causes or consequences instead of allowing the worksheet to become a paragraph of unresolved concerns.
Step 6: Test safeguards at the point of need
Every safeguard needs a clear failure response. Ask what detects the deviation, what action follows, who receives the signal, how long the action can take, and what happens if the safeguard is unavailable during startup or maintenance.
Separate independent protection from duplicated paperwork. A procedure, a warning label, and a supervisor reminder may all depend on the same person noticing the same condition. The team should therefore identify which barriers are engineered, which are administrative, and which rely on human recovery under pressure.
Use the plant’s existing hazard-review and control-verification logic to test whether each safeguard has an owner, a verification method, and an expiry condition. A safeguard that nobody verifies is an assumption with a name.
Step 7: Convert recommendations into decisions
A recommendation is not complete when the worksheet says “consider installing an alarm.” It is complete when the action states the required performance, the accountable role, the due date, the evidence of closure, and the condition that blocks startup if the action remains open.
Rank actions by consequence and dependency, not by the order in which the team wrote them. A missing interlock may control the path for three lower-level actions, while a procedure edit may be useful only after the design is stable.
At the close of the review, classify every item as accepted, assigned, rejected with rationale, or requiring a separate study. Link the final action list to the plant’s management-of-change decisions so the HAZOP does not disappear when the workshop ends.
Step 8: Verify readiness before startup
Close the loop with a field walk, a document check, and a controlled challenge of the changed system. Confirm that equipment labels match the drawings, alarms and trips respond as designed, operators can explain the new sequence, and emergency arrangements cover the temporary states that were reviewed.
OSHA’s pre-startup review requirements make the same operational point: the facility should verify that construction and equipment match design, procedures are in place, and affected workers have been trained before introducing hazardous chemicals.
Use a four-part readiness record. It should show the open recommendation count, the blocked-startup items, the person who authorized residual risk, and the date for the first post-startup review. If the operating conditions change again, stop treating the old HAZOP as current and trigger a new change review.
Comparison: a HAZOP worksheet versus a field-ready change review
| Dimension | Worksheet-only review | Field-ready review |
|---|---|---|
| Boundary | Broad project description | Defined equipment, states, interfaces, and exclusions |
| Evidence | Mixed revisions and verbal updates | Controlled drawings, procedures, logic, and field checks |
| Safeguards | Listed without failure response | Assigned owner, test method, response time, and expiry condition |
| Actions | Open recommendations | Decisions with evidence, due date, and startup consequence |
| Readiness | Meeting minutes approved | Field verification, worker understanding, and documented authorization |
Conclusion: make the HAZOP change the work
A HAZOP earns its place in a plant modification when it changes the design, the safeguards, or the startup decision before exposure begins. The practical test is simple: can the team show which risk boundary changed, which barrier must work, who verified it, and what stops the job if the proof is missing?
If you are building a leadership routine around those decisions, the Headline Podcast brings together real conversations on safety, risk, and the choices that shape better workplaces.
Frequently asked questions
How long does a plant-modification HAZOP take?
Who should participate in a HAZOP review?
What is the difference between a HAZOP and a management-of-change review?
Can a HAZOP be completed without updated drawings?
What should happen to open HAZOP actions before startup?
About the author
Andreza Araújo
Safety Culture Expert | Senior EHS Executive
Andreza Araújo is a safety culture expert and senior EHS executive with more than 25 years of experience in environment, health and safety. She is a Civil Engineer and Occupational Safety Engineer from Unicamp, holds a Master's degree in Environmental Diplomacy from the University of Geneva, and completed sustainability studies at IMD Switzerland. Andreza has served in Global Head of EHS roles in Fortune 500 environments, leading cultural transformation programs across multinational operations. She has represented Brazil as a speaker at the United Nations in Paris and has spoken at the International Labour Organization in Turin. She is the author of more than 16 books on safety culture in Portuguese, Spanish, English and German. Her work has earned more than 10 EHS awards, including two recognitions from Indra Nooyi, former PepsiCo CEO.
- Civil & Safety Engineer (Unicamp)
- M.A. Environmental Diplomacy (University of Geneva)
- Sustainability Cert (IMD Switzerland)
- People Management & Coaching (Ohio University)
- UN Paris speaker representative for Brazil
- ILO Turin speaker
- LinkedIn Top Voice
- Indra Nooyi PepsiCo CEO recognition (2x)
Documentaries
Watch Andreza's documentaries
Three productions on safety culture, organizational failure and the human lessons behind major disasters.
Podcasts
Listen to Andreza's podcasts
She hosts three shows on safety leadership, EHS and organizational culture, in English and Portuguese.