HAZID (Hazard Identification Study)

What Is HAZID?

A Hazard Identification Study (HAZID) is a structured, team-based, workshop-driven technique for systematically identifying potential hazards, risks, and opportunities for risk reduction during the early phases of project development. HAZID is conducted during concept development, preliminary design, or detailed design-before major capital expenditure, procurement, or construction begins. The primary purpose is to identify significant hazards early enough that they can be eliminated or designed out at low cost, rather than managed operationally at high cost and risk.

HAZID is widely used in:

• Oil & Gas Sector: Identifying hazards in offshore platforms, pipelines, processing facilities, and export terminals during design concept.
• Dredging & Maritime: Identifying hazards in new vessel designs, port infrastructure projects, and coastal development.
• Construction & Infrastructure: Identifying major hazards in complex projects (tunnels, bridges, power stations, data centres) during conceptual and detailed design.
• Energy: Identifying hazards in renewable energy projects (offshore wind, solar farms), power plants, and electrical distribution networks.

HAZID typically involves a 2-3 day facilitated workshop where a multidisciplinary team (engineers, designers, operations staff, HSSE specialists, contractors) reviews the project scope, design, and proposed operations to identify "what could go wrong?" and "how could we design it better to reduce risk?"

Also Known As / Abbreviations: Hazard Identification, HAZID Workshop, Preliminary Hazard Analysis (PHA), Hazard Brainstorm.

Regulatory Standard / Framework: HAZID aligns with IEC 61882 (Failure modes and effects analysis (FMEA) and failure modes, effects and criticality analysis (FMECA)) and ISO 45001:2018 (Occupational Health and Safety Management Systems). In construction, HAZID supports CDM 2015 requirements for early hazard identification and design for safety. In offshore/oil & gas, HAZID is often mandated by regulators (NORSOK standards, API guidelines, IMO regulations) as a prerequisite for project approval.

How HAZID Works

A typical HAZID follows this structured workshop process:

Step 1: Preparation & Scoping (2-4 weeks before workshop)

• Define the study scope: Which project? Which lifecycle phase? Which systems/areas to examine?
• Gather background information: concept drawings, process flow diagrams, preliminary design documents, regulatory requirements, lessons learned from similar projects.
• Identify and brief the facilitator (external, experienced HAZID facilitator preferred) on project context, objectives, and constraints.
• Assemble the multidisciplinary team (see Step 2).

Step 2: Team Assembly

• Bring together diverse expertise: project design engineers, operations representatives (who understand how the facility will be run), process specialists, HSSE professionals, external contractors (if planned), regulatory/compliance advisors, and finance/project management.
• Typical team size: 8-15 people. Smaller teams risk missing hazard perspectives; larger teams become unwieldy.
• Ideally, include at least one person who is unfamiliar with the project (brings fresh perspective) and someone from a similar previous project (brings experience).
• Ensure psychological safety: participants should feel comfortable challenging design and raising concerns without career risk.

Step 3: Workshop Day 1 - Project Overview & Familiarisation

• Facilitator leads detailed walkthrough of project scope, design, and operations.
• Project engineer(s) present:
• Concept drawings, 3D models, process flow diagrams
• Planned operations, staffing, maintenance procedures
• Regulatory framework and compliance targets
• Constraints (budget, timeline, site limitations)
• Known challenges and previous design iterations
• Q&A: workshop participants clarify understanding, identify information gaps, and ask clarifying questions.
• Goal: ensure all participants have sufficient shared understanding to contribute meaningfully to hazard identification.

Step 4: Workshop Day 1-2 - Structured Hazard Identification

• Facilitator guides systematic examination of the project across key topic areas:

Topic-Based Approach:

• Design & Layout: Are there congestion points? Poor visibility? Pedestrian/vehicle conflicts? Isolation hazards?
• Operations: How will the facility be started up, run, and shut down? What are normal and abnormal operating scenarios? How are alarms/emergencies detected and responded to?
• Maintenance: How will equipment be accessed for maintenance? Are there isolation/lockout requirements? Space constraints?
• Major Accident Hazards: Large inventories of hazardous materials, high temperatures/pressures, electrical hazards, crane/lifting operations, working at height, confined spaces, etc.
• Environmental: Discharge points, chemical storage, waste handling, spill control, noise, vibration.
• Staffing & Human Factors: Are roles clear? Can staffing be achieved? What training is needed? Are there fatigue, complacency, or cultural issues?
• External Hazards: Extreme weather, flooding, seismic activity, external third-party interference, supply chain risks.
• Integration & Interfaces: Are there gaps where hazards "fall between" responsible parties? Are handovers clear (design to construction to operations)?
• Brainstorming Approach: Facilitator may pose open-ended questions:
• "What could go wrong during startup?"
• "If we lost power, what would happen?"
• "What is the most dangerous task to perform in this facility?"
• "What could cause unplanned shutdown?"
• Participants brainstorm freely; all ideas are captured without immediate filtering.
• For Each Identified Hazard:
• Describe the Hazard: What is the specific risk?
• Identify Potential Consequences: What could happen? Who could be affected? What is the severity (injury, fatality, environmental impact)?
• Consider Root Causes: Why might this happen? Is it a design gap, operational procedure gap, or human factors issue?
• Propose Risk Reduction: What design change, procedure, or control could eliminate or reduce the hazard? Who should own this?
• Facilitator and scribe document all identified hazards and proposed risk reductions on a master list.

Step 5: Workshop Day 2-3 - Risk Assessment & Prioritisation

• For each identified hazard, the team estimates risk (likelihood × consequence) and assigns priority.
• High-Priority Hazards: Design should be changed to eliminate or significantly reduce (e.g., relocate hazardous material storage away from personnel areas; redesign crane path to avoid pedestrians).
• Medium-Priority Hazards: Design change preferred but operational controls acceptable (e.g., implement alarm system, automated shutdown, training/procedures).
• Low-Priority Hazards: Standard operational controls acceptable; monitor during operations.
• For high-priority hazards, the team identifies specific design actions and owners. These become design input for the next design phase.

Step 6: Workshop Closure & Action Assignment

• Facilitator summarises findings, high-priority actions, and ownership.
• Each action is assigned an owner with defined timeline (e.g., "Design Engineer A to evaluate relocation of fuel storage by 15 March").
• Commitment to follow-up meeting (typically 4-8 weeks later) to review progress on actions.

Step 7: Documentation & Follow-Up

• HAZID report is produced documenting:
• Project scope, team members, facilitator
• All identified hazards, potential consequences, and risk assessment
• Proposed risk reduction measures and assigned actions
• Timeline for follow-up
• Follow-up meetings are scheduled to confirm that high-priority actions have been addressed in subsequent design phases.
• HAZID findings inform:
• Detailed design input and design specifications
• Operational procedures and training requirements
• HAZOP study (the next, more detailed hazard analysis step)
• Regulatory applications and project approvals

Why HAZID Matters: Operational impact

For HSSE Teams

HAZID is the primary mechanism for embedding safety into design and project planning from the outset. By identifying major hazards early, HSSE teams can influence design choices to eliminate hazards rather than managing them operationally later. HAZID provides a strategic input into project safety cases and regulatory compliance documentation, demonstrating that hazards have been systematically considered during development.

For IT & CIOs

HAZID generates large volumes of hazard data, risk assessments, and action items that must be documented, tracked, and integrated into subsequent design and operational planning phases. Digital systems support HAZID workshop management (collaborative documentation, real-time hazard recording), action tracking (assigning owners, monitoring progress), and integration with design and risk management systems. This data must be maintained for the life of the project and asset.

Industry context

According to the offshore and oil & gas regulatory bodies (HSE UK, DNV, ABS) and project case studies, hazards identified and eliminated during HAZID typically cost 5-10 times less to address than the same hazards discovered during construction or operation. A 2021 study by the Process Safety Management Centre (UK) found that projects conducting early HAZID studies experienced 60% fewer design-related safety incidents during construction and commissioning than projects without early hazard identification. In the UK construction sector, projects conducted HAZID for complex work.

Implementing & Monitoring HAZID: From Manual to Digital

Traditionally, HAZID has been a labour-intensive, workshop-driven process: a facilitator leads discussions, a scribe manually documents findings, hazards are recorded in notebooks and whiteboards, and information is consolidated into a Word or Excel report post-workshop. This approach creates several challenges:

• Information Loss: Nuanced discussions and context are lost in transcription; the final report may not capture all discussions.
• Inconsistent Follow-Up: Actions are assigned verbally; lack of formal tracking means some actions are forgotten or delayed.
• Poor Integration: HAZID findings are often documented separately from design systems; subsequent design teams may not reference or incorporate HAZID recommendations.
• Knowledge Loss: HAZID reports are filed; institutional knowledge is not retained as team members change.

Forward-thinking organisations are transitioning to digital HAZID management systems that:

• Real-Time Collaborative Documentation - HAZID facilitators and participants use shared digital platforms (collaborative worksheets, live brainstorming tools) to capture hazards in real time, reducing transcription loss.
• Structured Data Capture - Digital forms ensure consistent data entry: hazard description, consequence, likelihood, severity, risk level, proposed control, owner, deadline.
• Automated Action Tracking - Systems automatically assign action items, send reminders to owners, and track progress. Follow-up metrics are automatically generated.
• Integration with Design Systems - HAZID findings can be directly linked to design documents, CAD models, and design change processes, ensuring design teams reference HAZID when making decisions.
• Regulatory Documentation - Digital systems support automatic generation of regulatory documentation (design safety cases, hazard reports) directly from HAZID findings.

For large projects or portfolios, digital HAZID management ensures systematic hazard identification, disciplined follow-up on design changes, and traceable evidence of design for safety.

Best Practices for HAZID

• Conduct HAZID Early, in Concept or Preliminary Design Phase: The value of HAZID is identifying hazards early enough that design changes are low-cost. HAZID conducted after detailed design or during construction is less effective because design is locked in. Schedule HAZID during concept or early design phase, with sufficient time for design teams to incorporate findings.
• Assemble a Truly Multidisciplinary Team: Effective HAZID requires perspectives from designers, operations, contractors, HSSE, and regulators. A team of only designers will miss operational and human factors hazards. Including someone unfamiliar with the project (external expert) often identifies issues that project-familiar team members overlook due to familiarity bias.
• Use an Experienced, External Facilitator: HAZID effectiveness depends significantly on facilitator skill. An experienced, external facilitator (not the project manager or design lead) can maintain neutrality, ensure all voices are heard, and guide systematic exploration of hazards without being influenced by project politics or design constraints. Internal facilitators are often influenced to minimise hazards ("that's too expensive to fix") or skip difficult topics.
• Follow Up Diligently: HAZID is only effective if actions are tracked and design teams actually incorporate recommendations. Assign specific owners to high-priority actions, set realistic timelines, and conduct formal follow-up meetings (4-8 weeks post-HAZID) to confirm that design changes have been made. HAZID findings should feed into the next phase of hazard analysis (typically HAZOP).