5 Ways Seveso-Classified Sites Are Using EHS Software
July 11, 2026
Seveso and BRZO-classified sites carry a different kind of operational weight than a typical industrial facility. A missed inspection isn't just a maintenance gap - it can be a gap in your veiligheidsbeheersysteem (VBS), the safety management system that Seveso III and the BRZO 2015 require you to run across all seven Annex III elements. When that system depends on spreadsheets, shared drives, and someone's memory of which valve was due for inspection, the risk isn't abstract.
Below are five concrete ways EHS software gets used on major-hazard sites specifically - not generic workplace safety scenarios, but the kind of operational problems that show up when you're running a Seveso VBS across multiple installations, shifts, and inspection regimes.
1. Tracking Safety-Critical Equipment Inspections Across Multiple Installations
A Seveso upper-tier site typically has dozens to hundreds of safety-critical elements: pressure relief valves, gas detection systems, emergency shutdown valves, bunding and containment, fire suppression systems - each with its own inspection interval defined by risk assessment, manufacturer guidance, or regulatory requirement. Multiply that across several installations on one site, or across several sites in a group, and the tracking problem stops being a spreadsheet problem.
The use case here is a single register that ties each safety-critical element to its inspection frequency, its last and next due date, and the person or contractor responsible - with automatic flags when an inspection is overdue or when an inspection result indicates the element has drifted out of tolerance. Instead of an EHS manager manually cross-checking maintenance logs against a compliance calendar, the schedule itself surfaces what's due, what's overdue, and what failed its last check. For a VBS, this is direct evidence supporting Annex III element (e) - planning and procedures for identifying foreseeable hazards.
2. Running Management-of-Change Workflows With Risk-Assessment Sign-Off
Any modification on a Seveso site - a process change, a new chemical, a temporary bypass of a safety system, even a change in shift coverage for a hazardous operation - needs to go through a formal management-of-change (MOC) process before it happens. That process has to produce a documented risk assessment, route it to the right technical and safety authorities for review, and capture their sign-off before the change is implemented. Skipping a step, or implementing before approval lands, is exactly the kind of gap that turns up in incident investigations.
The use case is a structured MOC workflow: someone raises a proposed change, the system routes it to the reviewers defined for that type of change (process engineer, HSE manager, site director, depending on scope), each reviewer records their assessment and either approves, rejects, or requests revisions, and the whole trail - original proposal, risk assessment, revisions, approvals - stays attached to that change record permanently. When an inspector or auditor asks "show me how this modification was assessed and approved," the answer is a record, not a reconstruction.
3. Consolidating Multi-Site Incident and Near-Miss Data for Trend Monitoring
A single incident report tells you what happened once. Seveso's requirement to monitor and review performance - Annex III element (g) - is really asking a different question: across all your near-misses, minor incidents, and safety observations over the past year, what pattern is emerging? Is one installation generating more gas-detection alarms than the others? Are near-misses clustering around a particular shift or a particular task? On a multi-site operation, that pattern is invisible if each site logs incidents in its own local system or its own spreadsheet.
The use case is a shared incident and near-miss log across all sites and installations, tagged consistently by location, hazard type, and root cause, so that trend analysis is a query instead of a manual data-consolidation exercise ahead of the annual management review. An EHS director can see, for example, that near-miss reports involving loading/unloading operations have doubled in six months across two sites - a signal that would otherwise stay buried in separate local records until something more serious forces the comparison.
4. Preparing Evidence Packages Ahead of DCMR or Arbeidsinspectie Inspections
Seveso inspections from DCMR (in Rijnmond) or the Nederlandse Arbeidsinspectie are not a formality. Inspectors will ask for specific evidence: inspection records for named safety-critical equipment, proof that a particular MOC went through its full approval chain, training records for personnel working with hazardous substances, drill records and the corrective actions that followed. Pulling that evidence together the week before an inspection, from scattered files and inboxes, is where a lot of avoidable stress in the EHS function comes from.
The use case is having that evidence already structured for retrieval - inspection logs, MOC records, training completions, and drill follow-ups organized so that "show us the last three years of pressure vessel inspections for this installation" is a filtered export, not a scramble through archived emails. The same structure that supports day-to-day operations doubles as the site's standing inspection-readiness file, which also happens to be what most VBS audits are checking for in the first place: can you demonstrate the system actually runs, not just that it exists on paper.
5. Coordinating Emergency Plan Drills and Follow-Up Actions Across Shifts
Seveso's internal emergency plan requirements (Annex III element (f) and the site's own noodplan) only mean something if they're tested regularly and the lessons from testing actually change something. A drill run on the day shift doesn't validate that the night shift knows the same evacuation route or the same role assignments. And a drill that surfaces a gap - a blocked emergency exit, a radio that didn't reach the control room, a muster point that's too close to the release scenario being simulated - is only useful if that gap gets tracked to a fix, not just noted in a report that gets filed away.
The use case is scheduling drills across all shifts and installations on a defined cycle, recording what was tested and who participated, capturing the observations and gaps from each drill, and assigning corrective actions with owners and due dates that get tracked to closure the same way any other safety action would be. Over time, this also produces the drill history that regulators and internal auditors expect to see: not just "we ran a drill," but "we ran a drill, found three gaps, and closed all three within the following quarter."
These five use cases share a common thread: a Seveso VBS isn't a document, it's an operating rhythm across inspections, changes, incidents, audits, and drills. EHS software matters here not because it replaces the judgment of your safety team, but because it keeps that rhythm from depending on any one person's memory or any one spreadsheet staying up to date.