ISO 31000 risk register does not replace a site hazard assessment

Connect the records without collapsing their purpose

The direct answer is to use ISO 31000 as an enterprise risk-governance reference while keeping the site hazard assessment as its own controlled operating record. The ISO page identifies the document as guidelines and describes principles, a framework, and a process that organizations can customize. That supports a common language for ownership, context, assessment, treatment, monitoring, and communication. It does not turn one high-level risk-register row into evidence that work-specific hazards were identified and controlled. ^[1]

Create an explicit relationship between the enterprise risk and every affected facility, process, task, change, contractor activity, chemical, machine, energy source, environment, and worker population. Preserve the enterprise owner and tolerance separately from the site assessor, worker or representative input, applicable duty, assessment method, hazard, exposure pathway, existing controls, risk basis, selected action, verification, residual uncertainty, approval, review date, and trigger.

Do not convert the guideline into a certification claim

ISO states that ISO 31000 is not for certification. A provider badge, template, dashboard, or internal statement that a process is ISO 31000 aligned may describe an approach, but it does not establish certified conformity or effective hazard control. Record the exact edition, the parts of the guidance adopted, the organization's approved method, scope, owner, exceptions, and evidence rather than using a single aligned flag. ^[1]

The same boundary applies to scoring. Enterprise likelihood and impact categories may help prioritize attention, yet a site hazard assessment may need different exposure measures, control hierarchy, legal thresholds, competent-person judgment, and emergency assumptions. Preserve both calculations and their units. If scores differ, document why; do not normalize them until the distinction between strategic consequence and work-level exposure disappears.

Test one enterprise risk through a local change

Choose a material change such as a new process line, chemical substitution, contractor task, production rate, ventilation change, or energy-isolation method. Trace the enterprise risk to affected sites and then to the change request, hazard assessment, worker consultation, engineering review, selected controls, procedure, permit, training, pre-start check, exposure or performance verification, exception, and authorization to operate. The enterprise register should show the consequence of unresolved site findings without pretending to contain every local artifact.

Also test the reverse path. A serious near miss, exposure result, failed safeguard, recurring observation, or regulatory change at one site should be evaluated for enterprise significance and for applicability elsewhere. Record the initiating evidence, affected population, immediate protection, investigation, cross-site review, risk-owner decision, transferred learning, action status, and closure proof. A closed corporate action is not enough when local corrective work remains open.

Keep legal and technical judgments in their proper lanes

The official ISO record establishes the publication identity and guidance boundary. It does not decide which occupational safety, environmental, chemical, process-safety, public-safety, or reporting requirements apply in a jurisdiction. It also does not validate a risk appetite, site assessment method, control selection, exposure conclusion, or management review. Those decisions need the applicable authority, competent expertise, operating facts, and retained evidence. ^[1]

A useful review output therefore names both records and the handoff between them: the enterprise risk and accountable executive, the site hazard and competent owner, the triggering facts, controls and evidence, unresolved uncertainty, escalation threshold, effective date, and reassessment event. That structure lets leaders see aggregate exposure without allowing aggregation to erase the people, work, and controls behind the number.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Safety Operations Standard will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.