ISO 31000 vs IEC 31010 vs HAZID: Which One Fits 5 Risk Decisions in a Process Plant?

A process plant rarely suffers from a complete absence of risk tools. The harder problem appears when a team uses the right tool at the wrong level. A project manager may ask for a HAZID when the organization has not defined its risk criteria. An engineer may cite IEC 31010 when the real dispute concerns who can accept residual exposure. A corporate leader may require alignment with ISO 31000 while receiving a report that does not explain what happens in the field.

ISO 31000, IEC 31010, and HAZID are therefore not three interchangeable competitors. They answer different questions. ISO 31000:2018 describes how an organization governs risk. IEC 31010:2019 helps practitioners select and apply risk assessment techniques. HAZID gives a team a structured way to identify hazards and scenarios, usually before the organization knows every detail of the final design.

The decision that matters is not which label sounds most rigorous. It is which evidence a responsible leader needs before approving a design, accepting a temporary condition, funding a control, authorizing a restart, or reviewing whether a previous risk decision still holds.

Evaluation criteria for a defensible choice

A comparison becomes useful only when the criteria reflect the decision being made. A process plant should assess each option against five dimensions, because the same technique can be valuable for one question and weak for another.

Purpose. Does the option set management direction, select a technical technique, identify scenarios, test controls, or support a decision already under review?

Lifecycle timing. Does the plant need the tool during concept selection, detailed design, commissioning, routine operation, management of change, or incident follow-up? Timing changes the information available and the consequences of an incomplete answer.

Evidence produced. A useful output must be specific enough for someone to act. A list of hazards, a risk matrix, a set of safeguards, and an accountable decision record are not the same output, even when they all use the word risk.

Decision owner. Technical analysis can inform a decision, but it does not automatically transfer authority. The accountable owner must know what the analysis proves, what it leaves uncertain, and which conditions make the decision invalid.

Review trigger. A risk decision has a useful life. Process changes, equipment degradation, new information, altered production demand, and a failed control can all require a review before the next scheduled study.

This distinction reflects a practical principle in Andreza Araujo's work on safety culture and risk perception. A system becomes more reliable when declared processes and operating decisions remain connected. The document is not the control. The control exists when a competent person can use the evidence to make, verify, and revisit a decision.

ISO 31000: best for governing the risk process

ISO 31000 is the strongest option when the question is how the organization should make risk decisions consistently. It gives leaders a common architecture for principles, framework, process, communication, monitoring, and improvement. It can connect enterprise risk language with operational safety, but it should not be mistaken for a substitute for hazard identification or engineering analysis.

In a process plant, ISO 31000 is useful before the team chooses a technique. Leaders can define what counts as material risk, which consequences require escalation, who owns the decision, what evidence is mandatory, and when the result must be reviewed. Those choices prevent a technical workshop from becoming an isolated event whose conclusions disappear into a project folder.

ISO 31000 also clarifies that context matters. A risk assessment for a new solvent unit does not have the same purpose as a decision about running an existing compressor beyond its planned inspection interval. The plant may use different techniques, yet both decisions should follow a consistent governance logic.

Its limitation is equally important. ISO 31000 does not tell a team whether a relief scenario is credible, whether an isolation is effective, or whether a degraded detector can be relied upon. It establishes the decision environment. Technical methods and field evidence must fill it.

Choose ISO 31000 when the plant needs to decide how risk is owned, escalated, recorded, monitored, and reviewed across functions. If the immediate need is to identify process hazards in a new design, ISO 31000 should frame the work, not replace the hazard study.

IEC 31010: best for selecting the assessment technique

IEC 31010 is the strongest option when the team knows a risk decision is required but has not yet chosen the right analytical lens. Its value lies in helping practitioners understand what different techniques are suited to reveal, what inputs they require, and what limitations should be considered.

That matters because method selection is often treated as a matter of habit. One department always uses a risk matrix. Another prefers a workshop. A third asks for a failure analysis because the template already exists. IEC 31010 helps move the conversation from preference to fit. The team can ask whether the decision concerns deviation, failure mode, human interaction, uncertainty, consequence escalation, or barrier performance.

For example, a structured hazard study may be suitable for a process design review, while a failure-mode analysis may fit equipment reliability questions. A scenario-based technique may help a team examine how an initiating event can pass through safeguards, while a consequence analysis may be more important when release behavior or escalation distance is uncertain.

IEC 31010 does not remove professional judgment. It makes that judgment visible. The team should record why the selected technique matches the decision, what alternatives were rejected, which assumptions limit the result, and what additional evidence is required before approval.

Choose IEC 31010 when the main risk is analytical mismatch. It is especially useful for a corporate engineering standard that tells sites how to select techniques without forcing every problem into one familiar workshop format.

HAZID: best for early hazard and scenario discovery

HAZID is the strongest option when a multidisciplinary team needs to identify hazards, credible scenarios, exposed people or assets, and broad control needs before the design or operating change is fully settled. It is often valuable at concept stage, during project definition, before a major change, or when a new activity creates unfamiliar interfaces.

The method gives the team a practical structure for asking what could go wrong, how the event could start, who or what could be exposed, and which safeguards should be considered. Its strength is breadth. It can bring process, operations, maintenance, engineering, emergency response, and management perspectives into the same early conversation.

Its output should not be confused with proof that controls work. A HAZID can identify the need for isolation, detection, containment, access control, emergency response, or operating limits. It cannot, by itself, demonstrate that a valve closes within the required time, that a detector is positioned correctly, or that a field team follows the intended sequence under production pressure.

The quality of a HAZID depends on the boundaries set before the workshop and the follow-through afterward. If the team does not define the node, change, operating state, or credible deviation under review, the discussion becomes broad but difficult to close. If actions have no owner and verification date, the hazard register becomes a memory aid rather than a control decision.

Choose HAZID when the plant needs structured discovery at the front end of a decision. Pair it with a governance framework and a later control-verification process when the decision affects continued operation or high-consequence exposure.

Decision matrix: match the option to the question

The following matrix is not a scorecard that declares one universal winner. It shows the level at which each option contributes the most value.

The matrix exposes a common failure pattern. A plant may perform a detailed workshop and still lack a clear acceptance authority. It may have a polished risk framework and still lack evidence about a specific scenario. It may select a technique carefully and still fail to verify whether the resulting controls survive commissioning, maintenance, or production change.

That is why the strongest process links the three levels. ISO 31000 defines how the decision is governed. IEC 31010 informs which technique can produce useful evidence. HAZID supplies early scenario discovery when that is the immediate question. The levels support one another without becoming interchangeable.

Which option fits five common plant decisions?

1. Selecting a concept for a new process unit. Start with ISO 31000 to define decision criteria and authority, use IEC 31010 to choose the assessment approach, and use HAZID to identify the broad hazard and scenario picture. The concept decision should preserve the assumptions that shaped the choice.

2. Reviewing a management-of-change proposal. Use the ISO 31000 logic to define what changed and who can accept the resulting exposure. Use IEC 31010 to select a method that fits the change. Use HAZID when the change introduces new interfaces, energy sources, materials, or operating states that the existing analysis does not cover.

3. Deciding whether a temporary operating condition can continue. ISO 31000 is the governance anchor because the question concerns authority, criteria, duration, and review. A technique selected with IEC 31010 can examine the uncertainty, while HAZID may help identify scenarios created by the temporary condition. The decision should have an expiry or review trigger rather than becoming permanent by neglect.

4. Prioritizing a capital request for risk reduction. ISO 31000 helps define the decision and compare the request with other exposures. IEC 31010 can guide a proportionate analysis when the evidence is incomplete. HAZID is useful if the investment concerns a proposed design or a new hazard, but a current control-performance review may be more appropriate when the existing barrier is already known to be weak.

5. Accepting residual risk before restart. ISO 31000 should define the acceptance authority and escalation path. IEC 31010 can help select a method to address unresolved uncertainty. HAZID may identify remaining scenarios, yet restart should also require direct evidence that critical controls are installed, available, tested, and owned. A workshop conclusion alone is not restart assurance.

Recommendation by plant context

New process design. Use ISO 31000 as the governance frame, IEC 31010 as the technique-selection reference, and HAZID as an early discovery step. Preserve the assumptions and actions so later studies can test whether the original design logic remains valid.

Operating plant with recurring control drift. Start with the decision that is failing. If ownership and escalation are unclear, repair the ISO 31000 layer. If the assessment method is producing weak evidence, use IEC 31010 to change the analytical choice. If the plant has not mapped the changed scenario, use HAZID, then move into field verification.

Multinational organization. Create a common corporate language for decision ownership, evidence, review, and records, while allowing sites to apply local legal and technical requirements. A common framework should improve comparability without forcing every facility to use the same technique for every hazard.

Andreza Araujo's book Safety Culture: From Theory to Practice emphasizes the distance that can exist between declared expectations and operating reality. That distinction is central here. A plant does not demonstrate mature risk management by owning three methodologies. It demonstrates maturity when leaders can explain why a method was selected, what evidence it produced, who acted on it, and how the organization will know when the decision must be revisited.

What leaders should ask before signing the decision

Before accepting the result, ask whether the team defined the decision in plain language, selected a technique that fits the question, recorded assumptions, separated known facts from judgment, assigned control owners, and established a review trigger. Ask which evidence would change the decision and who has authority to stop the work if that evidence appears.

Those questions keep the comparison practical. ISO 31000 is not a badge of maturity, IEC 31010 is not a menu to complete, and HAZID is not a permanent substitute for control verification. Each option earns its place when it produces the evidence needed at the level where the plant is making the decision.

For a process plant, the safest choice is rarely one framework alone. It is a connected decision chain in which governance sets the rules, technique selection matches the uncertainty, hazard identification makes scenarios visible, and field evidence confirms whether the controls can still carry the risk assigned to them.

For more practical guidance on safety culture, risk ownership, and leadership decisions, visit Andreza Araujo.