EHS Inspectors: What Do They Check at a Seveso Site?

If you run a Seveso or BRZO-classified site, at some point an inspector from DCMR or the Nederlandse Arbeidsinspectie is going to walk through your gate. Not a generic "safety inspector" - a regulator with a specific mandate under the Seveso III Directive, a specific set of things they're required to verify, and a specific way they go about verifying it.

Most explanations of "what an EHS inspector does" describe a job role: qualifications, training, career path. That's not useful if you're the one who has to host the visit. What matters is what happens when the inspector arrives, what they ask to see first, and what they're actually evaluating while they're there. This is a walkthrough of that process, from the regulator's side.

Who actually shows up

In the Netherlands, Seveso/BRZO oversight is split between two bodies that usually inspect together:

• DCMR Milieudienst Rijnmond (or the relevant regional environmental service if you're outside Rijnmond) - checks environmental permits, process safety, and the technical integrity of installations.
• Nederlandse Arbeidsinspectie (the former Inspectie SZW) - checks occupational safety, working conditions, and how the VBS translates into what actually happens on the shop floor.

A BRZO inspection team is typically a joint team, sometimes including the fire brigade (Veiligheidsregio) depending on the site's risk profile. You're rarely dealing with one inspector - you're dealing with a small team, each with a different angle on the same site.

Announced vs. unannounced

Most Seveso inspections are announced in advance, with a scope and date agreed with the site. This isn't a courtesy - it's practical: the inspection team needs specific people available (the VBS coordinator, process safety engineer, site manager) and specific documentation prepared in advance.

That said, unannounced inspections happen, particularly:

• Following an incident or near-miss report
• After a complaint (from an employee, neighbor, or another authority)
• As a spot-check when a site's compliance history raises questions
• As part of a broader sweep of an industrial area

An unannounced visit tests something an announced one can't: whether your VBS is actually operating day-to-day, or whether it only gets assembled when a visit is scheduled. Inspectors know the difference between a system that's lived-in and one that's staged, and it shows in small things - whether the permit binder is current on the shelf or has to be printed that morning, whether the person doing a hot-work job can explain the permit process unprompted.

How the inspection day itself unfolds

A typical BRZO inspection runs in three phases, usually in this order:

1. Document review. Before or at the start of the visit, the team works through the paperwork: the safety report (veiligheidsrapport), the VBS documentation, permits, risk assessments, maintenance and inspection records for safety-critical equipment, training records, and the log of past incidents and near-misses. They're checking not just that documents exist, but that they're current, internally consistent, and actually match what's on site.

2. Site walk. The team walks the installation, comparing what they saw on paper to what's physically there. This is where mismatches surface fast: a bund wall that's supposed to hold a certain volume but has a drain valve left open, a gas detector due for calibration three months ago, safety-critical valves without visible tagging, escape routes partially blocked. Inspectors are trained to notice the gap between "documented" and "true."

3. Interviews. Inspectors talk to people, not just management. An operator might be asked to explain what they'd do in a specific upset condition, or to demonstrate they know where the nearest eyewash station is and why. A shift supervisor might be asked how a recent process change was assessed and approved. This is where a paper VBS that no one below management level actually knows about gets exposed.

The order and mix vary by site and by inspector, but all three phases happen in some form, even on a short visit.

What inspectors are actually checking, beyond the checklist

Beyond ticking off specific documents and equipment, an inspector is forming a judgment on a few underlying questions:

• Does the VBS function as a live system, or as a compliance artifact? Is it something staff refer to and update, or something that was written once for the permit application and never touched again?
• Is there traceability? Can the site show a clear line from a hazard identified, to a control measure implemented, to that measure being checked and maintained over time - with dates and names attached?
• Does management of change actually happen? When something on site changes (a new chemical, a modified process, a temporary bypass), is there evidence it went through a documented risk assessment before it happened, not after?
• How does the site handle its own incidents? Are near-misses reported and investigated, or does the incident log only contain things that were impossible to hide?

These questions don't appear as line items on a checklist, but they shape how an inspector reads everything else they see.

What sites can do to be ready

Being ready for an inspector isn't the same as having a good VBS on paper - it's being able to produce evidence of that VBS working, on demand, for anyone who asks.

• Keep documentation current, not reconstructed. If records only get updated in the run-up to a scheduled inspection, that gap is visible to an inspector who has seen dozens of sites do the same thing.
• Make sure records and reality match. Inspection dates on paper should match the tags and stickers on the actual equipment. A mismatch is one of the fastest ways to lose credibility in a visit.
• Prepare people, not just paperwork. Operators and supervisors should be able to speak to their own role in the VBS - permits, escalation procedures, what to do in an upset condition - without needing a manager to answer for them.
• Have your incident and near-miss history available and honest. A thin or suspiciously clean log tends to invite more scrutiny, not less.
• Know your own management-of-change trail. Be able to show, for recent changes on site, that the risk assessment came before the change, not after.

None of this replaces having a genuinely functioning VBS. But a site that can retrieve the right document, point to the right tag, and put the right person in front of an inspector within minutes is having a very different conversation than one that's still searching for the file when the team arrives.