SAFETY OPERATIONSSTANDARD

Evidence for safer work and accountable operations.

Coverage desk

Incident Reporting Governance

Source-backed reporting and analysis connected to the companies, capabilities, authorities, and operating domains it affects.

SOII, CFOI, and OSHA ITA answer different injury-data questions

BLS survey estimates, the fatal-injury census, and establishment-submitted OSHA records describe different populations and measures. Safety teams should choose the source from the question, then preserve its population, denominator, year, geography, coverage, and limitations.

REACH downstream-user duties need a role-and-measure record

ECHA identifies responsibilities shared by all downstream users and additional duties for formulators and article producers. A defensible operating record should connect the organization's actual role, the safety-data and exposure-scenario measures it received, implementation evidence, supplier communications, and chemicals-of-concern actions without claiming that the overview proves a particular use is covered.

ISO 31000 risk register does not replace a site hazard assessment

ISO identifies ISO 31000:2018 as risk-management guidelines rather than a certifiable management-system requirement. EHS teams can connect enterprise risk and site hazards, but they should preserve the work, location, exposure, legal duty, control, verification, and worker-participation evidence that a corporate risk row cannot carry.

GRI 403 rates need worker-scope denominator records

GRI 403 requires injury counts, rates, and hours for employees and separately for non-employees whose work or workplace the organization controls. A published rate stays comparable only when the worker population, hours, exclusions, event definitions, multiplier, reporting period, and later corrections remain attached to it.

A RIDDOR report does not close the incident investigation or control record

The UK Health and Safety Executive explains who reports under RIDDOR, which incidents are reportable, how notifications are submitted, and how a report can be amended. Regulatory notification is one governed outcome; immediate response, investigation, causal analysis, corrective action, effectiveness review, and workforce communication remain separate operating records.

A VelocityEHS trend should trigger investigation, not declare incident cause

VelocityEHS says Accelerate can capture EHS data across programs while AI analyzes patterns, recommends next steps, and dashboards reveal trends. Cross-module signals can prioritize investigation, but they do not establish why an incident occurred or which control will prevent recurrence.

Intelex links incident cases and corrective actions—but case closure is not a recordability decision

Intelex lists incident management, case management, action plans, corrective-action reporting, inspections, and compliance tracking across its EHS environment. A completed case can organize response while regulatory recordability still depends on the applicable rule, worker and event facts, medical evidence, and accountable review.

EPA TRI releases are not exposure estimates

EPA describes TRI as facility-reported chemical-release, waste-management, and pollution-prevention information; the agency points to a separate screening model for potential impacts.