Corporate ESG Reporting: Your Seveso VBS Is Half the Answer

Most corporate ESG reporting guides treat environmental, social, and governance disclosure as three separate tracks that all need their own data collection process. For Seveso-classified companies, that framing misses something important: a large part of the "S" in ESG is already being generated, every day, inside your veiligheidsbeheersysteem (VBS).

If you run a major-hazard site under the Seveso Directive (known in the Netherlands as BRZO), your VBS produces continuous data on incidents, near-misses, safety-critical equipment inspections, and audit findings. That's not a side project you need to build for ESG purposes - it's occupational health and safety performance data, and occupational health and safety is one of the core pillars of ESG-S reporting.

This post looks at what ESG-S actually asks for, why compiling it manually from scattered VBS records is a recurring headache, and why continuous VBS data capture naturally produces ESG-S inputs as a byproduct of the safety work you're already required to do.

What ESG-S Actually Covers

ESG reporting breaks corporate performance into three areas: environmental (emissions, resource use, waste), social (how a company treats its workforce, supply chain, and communities), and governance (board oversight, ethics, transparency).

The Social pillar is broad, but occupational health and safety is consistently one of its most concrete, measurable components - arguably more measurable than most environmental or governance metrics, because safety data is already something regulated industries are required to track. Typical ESG-S safety metrics include:

• Injury and incident rates - recordable injuries, lost-time incidents, and severity, often expressed per hours worked
• Near-miss reporting volume and trends - a leading indicator that regulators and ESG frameworks increasingly want alongside lagging injury statistics
• Safety-critical equipment inspection and maintenance compliance - whether inspections on safety-critical systems happened on schedule and what was found
• Audit and inspection findings - internal audits, regulatory inspections, and how quickly corrective actions were closed out
• Training and competency coverage - whether staff involved in hazardous operations have current, verifiable safety training

For a Seveso-classified company, every one of these already exists as a byproduct of running your VBS. The performance-monitoring obligations under Seveso - tracking safety-critical equipment, logging incidents and near-misses, running internal audits, verifying corrective actions - produce exactly the raw material ESG-S reporting asks for.

Why This Data Rarely Makes It Into ESG Reports Cleanly

In practice, most of this data doesn't move smoothly from the VBS to the ESG report. A few reasons come up repeatedly:

It lives in different places. Incident logs, inspection checklists, audit findings, and corrective action tracking are often split across spreadsheets, paper forms, a maintenance system, and whatever tool the safety team happens to use. Pulling a single year's near-miss trend means reconciling formats and definitions across all of them.

Definitions don't line up. A "near miss" in a plant's internal safety culture program isn't always logged the same way as an "incident" for regulatory purposes, and neither automatically maps to the categories an ESG framework expects. Someone has to manually translate between the two.

It's compiled once a year, under time pressure. Because the VBS data isn't captured with ESG reporting in mind, producing the annual ESG-S section usually means a sustainability or compliance team scrambling to reconstruct a year of safety performance from records that weren't built to be queried that way - right around the same time as annual Seveso audit and reporting obligations.

Nobody owns the handoff. Safety teams own VBS compliance. Sustainability or ESG teams own the disclosure. Without a clear process connecting the two, the same underlying data gets collected twice, in different formats, by different people.

Why This Matters More Under CSRD

The EU's Corporate Sustainability Reporting Directive (CSRD) is expanding sustainability disclosure requirements to a much broader set of companies than were previously in scope, with more detailed and more standardized requirements than earlier EU sustainability reporting rules. Occupational health and safety metrics sit squarely within the social disclosures CSRD asks for.

The exact scope and timeline depend on company size and other criteria set out in the directive, so it's worth checking current guidance for your specific situation rather than assuming a one-size-fits-all deadline. The direction of travel is clear, though: more companies will need to report social metrics in more detail, with more rigor around how the underlying data was collected and verified. For Seveso-classified companies already sitting on relevant safety data, that's a structural advantage - if the data is usable.

Continuous Capture Beats Annual Reconstruction

The fix isn't a separate ESG data collection exercise bolted onto the safety program. It's making sure the VBS data is captured in a structured, consistent way from the start, so that ESG-S metrics can be pulled from it rather than rebuilt from it.

That means:

• Incidents and near-misses logged in one consistent format, with fields that map cleanly to the categories ESG frameworks use - not free-text notes that need to be re-interpreted later
• Safety-critical equipment inspections recorded with clear pass/fail and completion-rate data, so compliance rates can be reported directly rather than estimated
• Audit findings and corrective actions tracked to closure, so "percentage of findings resolved within target" is a query, not a research project
• All of it timestamped and attributable, so a year's worth of performance data can be pulled on demand instead of reconstructed under deadline pressure

When VBS data is captured this way as part of routine safety management, ESG-S reporting stops being a separate annual project. It becomes a report generated from data that was already being collected to run the safety management system properly. The safety work and the reporting work are the same work - the only question is whether the data is structured well enough to serve both purposes without a manual translation step in between.

The Takeaway

For Seveso and BRZO-classified companies, ESG-S reporting isn't a new data requirement - it's a new destination for data your VBS is already generating. Incident rates, near-miss trends, inspection compliance, and audit findings are the substance of occupational health and safety disclosure under ESG frameworks and CSRD alike. The companies that find this easy are the ones whose VBS data was structured for reuse from the start. The companies that find it painful are reconstructing a year of safety performance from scattered records every reporting cycle. The underlying data is the same either way - what differs is whether it was captured once, cleanly, or compiled twice, under pressure.