EHS Compliance at Seveso Sites: What Safe Work Requires

For most companies, "EHS compliance" is a loose bucket term - training records, PPE policies, the occasional audit. For a Seveso-classified site, it means something much narrower and much less forgiving. Compliance isn't a general standard of good practice you're roughly meeting. It's a defined legal state, with specific documents, specific system requirements, and a specific authority that checks whether you're actually in it.

If you run a lower-tier or upper-tier Seveso establishment - a chemical plant, a tank terminal, a storage site handling hazardous substances above the Annex I thresholds - your EHS compliance question isn't "are we being safe." It's "can we currently prove, on demand, that we meet Seveso III." Those are different questions, and conflating them is where a lot of sites get into trouble.

Compliant Doesn't Mean Safe. It Means Provable.

A site can run for years without an incident and still not be compliant. Compliance under Seveso III isn't measured by outcomes, it's measured by documentation and system state at the moment someone checks. Three things have to hold at the same time:

• A veiligheidsbeheersysteem (VBS) that actually satisfies the Annex III requirements - not a binder that describes what the system should do, but a system that is demonstrably operating: organization and personnel, hazard identification, operational control, management of change, emergency planning, performance monitoring, and audit/review, all with evidence behind them.
• A safety report that reflects the current installation, not the one from the last permit application. Process changes, new substances, modified storage volumes, altered emergency procedures - if the report doesn't reflect reality, it's not compliant regardless of how good it looked when it was written.
• A current MAPP (major accident prevention policy) that is genuinely in force and genuinely reflected in how the site operates, not a signed document sitting in a shared drive.

Miss any one of these and the site is non-compliant, even if nothing has gone wrong operationally. That's the part generic EHS advice skips: compliance is a state you either hold or don't, not a score you're trending toward.

Who Checks, and What They're Actually Looking For

In the Netherlands, upper-tier Seveso sites are inspected under the joint BRZO regime, with DCMR (for the Rijnmond region) and the Nederlandse Arbeidsinspectie among the competent authorities involved, alongside the safety region and, where relevant, the water authority. Inspections aren't a paperwork review from a distance - they test whether the VBS is real.

That means inspectors will ask to see:

• Evidence that hazard identification and risk assessment are current, not archived from years ago
• Records showing management-of-change procedures were actually followed for recent modifications
• Training and competence records tied to the roles that matter for major-accident prevention
• Audit findings and what was done with them - a closed loop, not a list of open items nobody touched
• Emergency plan testing and the corrective actions that came out of it

If the answer to "can you show us" is "give us a few weeks to pull that together," that's already a finding. The expectation is that this evidence exists in usable form before the inspector arrives, not after.

What Non-Compliance Actually Costs

Non-compliance under Seveso III doesn't sit at the level of a fine and a stern letter. The enforcement ladder for BRZO sites runs from formal warnings and improvement orders through operational restrictions to, in serious or repeated cases, suspension of activities. For an upper-tier site, an enforcement order that halts part of operations is a materially different event than a compliance gap on a checklist - it affects production, contracts, and in some cases the conditions attached to the environmental permit itself.

That permit link is worth being explicit about: the omgevingsvergunning for a Seveso site is not independent of BRZO compliance. Sustained or serious non-compliance is a factor competent authorities weigh when permits come up for review or amendment. Treating compliance as a box to check before a permit renewal, rather than a continuous condition of holding the permit, misreads how the two are connected.

Compliance Is Continuous, Not Periodic

The most common gap isn't ignorance of the rules - it's treating compliance as an event tied to the permit cycle instead of an ongoing operating condition. A VBS that was accurate at the last renewal degrades the moment something changes on site and the documentation doesn't follow:

• A process modification goes through management of change on paper but the safety report update lags behind
• A new hazardous substance is introduced and the MAPP's scope technically no longer covers it
• Staff turnover erodes the competence records tied to major-accident-prevention roles
• An internal audit finds a gap, it gets logged, and six months later it's still open

None of these show up as a single dramatic failure. They accumulate as a set of small mismatches between what the documentation says and what's actually true on site - and that gap is exactly what an inspection is designed to find.

Staying compliant continuously means the VBS's own audit and review function is actually being used: hazard identification gets revisited when conditions change, management-of-change triggers a real update to the safety report and MAPP where relevant, and audit findings get tracked to closure rather than parked. None of that is exotic - it's what Annex III already asks for. The difference between sites that pass inspection comfortably and sites that scramble is almost always whether that loop runs continuously in the background or gets reconstructed under pressure right before an inspection.

The Practical Takeaway

For a Seveso-classified site, "EHS compliance" isn't a training topic or a values statement. It's a specific, checkable condition: a functioning VBS aligned with Annex III, a safety report that matches the current installation, a MAPP that's actually in force, and the ability to put evidence in front of DCMR or the Nederlandse Arbeidsinspectie without a scramble. Get those four things right, keep them current as the site changes, and compliance stops being a periodic project and becomes a normal, unremarkable part of how the site runs.