The EHS Director's Guide to Running a VBS at a Seveso Site

If you've stepped into an EHS Director role at a Seveso or BRZO-classified site - or you're evaluating whether to - the job description probably reads a lot like any other EHS leadership role: safety culture, training, incident response, compliance oversight. What it doesn't tell you is how different the job actually is once your site sits above the Seveso thresholds.

This isn't a general "how to run a safety program" guide. There are plenty of those, and most of what they cover still applies to you. This is about the parts of the job that are specific to major-hazard sites: the system you own, the regulator you answer to, and the exposure that comes with both.

Why "EHS Director" means something different here

At a non-Seveso site, an EHS Director is largely internally accountable. You report to plant leadership, you're measured against internal KPIs and injury/incident rates, and your worst-case regulatory exposure is typically an inspection citation or a fine.

At a Seveso-classified (upper-tier or lower-tier) site, you carry an additional layer that doesn't exist elsewhere: you are the person who owns and can be asked to defend the veiligheidsbeheersysteem (VBS) - the safety management system mandated by the Seveso III Directive and implemented in the Netherlands through the Brzo 2015 decree. If you're upper-tier, you also own the Safety Report (veiligheidsrapport) and the Major Accident Prevention Policy (MAPP/PBZO) that sits underneath it.

That ownership isn't symbolic. When DCMR (or the relevant regional environmental service) and the Nederlandse Arbeidsinspectie conduct a Brzo inspection, they're not just checking whether you have a safety program - they're checking whether your VBS actually functions as a system: whether the elements connect to each other, whether what's written down matches what happens on the floor, and whether you can produce evidence of that on request. You are typically the person in the room answering for it.

That's the core difference. A general HSE manager builds and runs safety programs. An EHS Director at a Seveso site owns a legally mandated management system that regulators can - and do - formally audit, and that failure to maintain can trigger administrative enforcement, is tied to major-accident liability, and in the Netherlands can escalate to a shutdown order.

The role spans all seven Annex III elements, not just "safety culture"

Generic EHS guidance tends to collapse the job into training, emergency response, and "building a safety culture." Those matter, but at a Seveso site they're only part of what the VBS requires you to own. Annex III of the Seveso III Directive sets out seven elements your management system has to cover:

1. Organisation and personnel - roles, responsibilities, competence, and training relevant to major-hazard prevention at all levels, including contractors.
2. Identification and evaluation of major hazards - systematic identification of major-accident hazards from normal and abnormal operation, and assessment of their likelihood and severity.
3. Operational control - procedures and instructions for safe operation, including maintenance of plant, processes, equipment, and temporary stoppages.
4. Management of change - procedures for planning modifications to, or the design of, new installations, processes, or storage facilities.
5. Planning for emergencies - procedures to identify foreseeable emergencies through systematic analysis, and to prepare, test, and review emergency plans.
6. Monitoring performance - procedures for ongoing assessment of compliance with objectives, investigation and correction of major accidents and near misses, and audit and review of the VBS itself.
7. Audit and review - periodic, systematic assessment of the policy and the effectiveness and suitability of the management system, with documented follow-through.

If you're coming from a role where "safety" meant PPE compliance, incident rates, and toolbox talks, the breadth here is the first adjustment. You're not just responsible for whether people work safely day to day - you're responsible for a documented system that ties hazard identification, engineering change, emergency planning, and internal audit together, with paper trails a regulator can pull on any of the seven threads independently.

In practice, this means your job touches process safety engineering, change management, contractor management, emergency response planning, and internal audit - not as adjacent functions you coordinate with, but as elements you're accountable for integrating.

How this differs from a general HSE manager role

A few concrete differences worth naming, especially if you're moving into this role from a non-Seveso background:

• Regulatory relationship. A general HSE manager deals with labor inspectorate visits on an as-needed basis. At a Seveso site, Brzo inspections are a recurring, structured part of the job, and DCMR/Arbeidsinspectie inspectors will test whether your VBS functions as an integrated system - not just whether individual procedures exist.
• Document ownership with legal weight. The Safety Report and MAPP aren't internal policy documents - they're regulatory submissions with legal standing. Errors, gaps, or drift between what's documented and what's actually practiced are the kind of thing that surfaces in enforcement action, not just an internal audit finding.
• Process safety, not just occupational safety. General HSE work is heavily weighted toward occupational safety - slips, falls, ergonomics, PPE. Seveso work is centered on process safety: the mechanisms by which a loss of containment or process upset could lead to a major accident. That's a different risk model and often a different technical skill set (or a different set of people you need on your team).
• Personal and organizational exposure. Major-accident liability at a Brzo site is a different category of consequence than a typical HSE incident. That doesn't mean you should feel personally exposed day to day - the VBS exists specifically to distribute and systematize that responsibility - but it does mean the standard for "good enough" documentation and follow-through is higher than most EHS roles.
• Site-wide integration. A general HSE manager can often own their function fairly independently. A VBS, by design, has to integrate with engineering (management of change), operations (operational control), and emergency services (external emergency planning) - you're less the owner of a department and more the person who keeps a cross-functional system coherent.

Practical priorities if you're new to this role

If you've just taken on an EHS Director role at a Seveso-classified site, a few starting points tend to matter more than others:

Read the existing Safety Report and MAPP before you touch anything else. These documents define what your predecessor committed to, on paper, to the regulator. Whatever gaps exist between what's written and what's actually happening on site are the first things an inspector will find - better you find them first.

Map your VBS against the seven Annex III elements explicitly. Most sites have documentation for each element somewhere, but it's rarely organized as "here are our seven elements and the evidence for each." Doing that mapping yourself, early, tells you where the real gaps are versus where the paperwork just isn't organized clearly.

Find out when your last Brzo inspection was and what came out of it. Prior inspection findings are the closest thing you'll get to a preview of what regulators will look at next. Unresolved findings from a previous inspection are a priority list, not background reading.

Identify who actually owns each Annex III element on the ground. The VBS names you as accountable, but the seven elements touch engineering, operations, HR, and contractor management. Know who your counterpart is for each one before you need them in an emergency or an audit.

Understand your MoC (management of change) process specifically. A disproportionate number of major accidents trace back to a change - process, equipment, or organizational - that wasn't properly assessed before it was made. If your MoC procedure is weak or inconsistently followed, it's worth fixing early rather than discovering it during an incident investigation.

Build the relationship with DCMR and the Arbeidsinspectie before you need it. Inspectors are more useful as a resource than as an adversary if the relationship is established outside of enforcement moments. Knowing your inspector, and having them know your site, tends to make routine inspections more straightforward.

None of this replaces the fundamentals of good EHS leadership - competent people, clear procedures, a workforce that trusts you enough to report problems before they become incidents. But at a Seveso site, those fundamentals sit inside a legal and regulatory structure that a generic EHS role doesn't have. Understanding that structure, and where you fit inside it, is what the first few months in this role are really about.