The Business Case for a Digital VBS at a Seveso Site
July 9, 2026
If you manage safety at a Seveso or BRZO-classified site, you already know your veiligheidsbeheersysteem (VBS) works. The question you're facing now isn't whether it's compliant - it's whether it can survive another year of being run out of shared drives, inspection binders, and someone's personal task list. Making that case to the people who control budget is a different skill than running the VBS itself, and it's the one this article is about.
Getting sign-off for a digital VBS platform means translating operational pain into a decision your management team can act on. That means naming what the current approach actually costs, being honest about where the risk sits, and presenting the investment as a structural fix rather than a tooling preference. Below is a framework for building that case.
Start with what the status quo actually costs
Most VBS budget requests fail at the first step because they open with the solution instead of the problem. Before you talk about a platform, you need a clear-eyed account of what running the VBS manually is costing today. Three areas are worth quantifying, even roughly:
Time spent on administration versus time spent on safety. Track how many hours your EHS team and site supervisors spend each month compiling inspection records, chasing overdue actions, consolidating data ahead of audits, and reformatting reports for different stakeholders. This is time not spent walking the floor, coaching operators, or closing out actual risk. If nobody has measured this, that's worth doing before you draft the business case - even a rough log over a few weeks gives you a defensible number.
The risk of gaps that go unnoticed until an audit or incident. Manual systems - spreadsheets, shared folders, paper checklists - depend on people remembering to update them. Corrective actions get logged but not tracked to closure. Inspection frequencies slip during busy periods. Versions of procedures diverge between sites or departments. None of this shows up as a cost on a P&L, but it's exactly the kind of gap that a Seveso inspector, or worse, an incident investigation, will find. Frame this not as "we might get fined" but as "we don't currently have a reliable way to prove our VBS is being executed as designed, in real time."
The pre-audit scramble. Ask your team what happens in the weeks before a regulatory inspection or internal audit. If the honest answer involves late nights pulling together evidence, reconciling conflicting versions of documents, and hoping nothing was missed, that's a cost - in hours, in stress, and in the risk of the audit itself surfacing something you didn't know about. This scramble is also a signal: if producing evidence of compliance takes weeks of manual work, the underlying system isn't actually giving you real-time assurance, it's giving you a periodic reconstruction.
Put a number or a range on each of these where you can. Where you can't, describe them in terms your management team already tracks - audit findings, incident recurrence, staff turnover in EHS roles, time-to-close on corrective actions. The goal isn't a precise figure; it's making an invisible, distributed cost visible in one place.
Frame the investment case, not just the price tag
Once the cost of the status quo is on the table, the investment in a digital VBS platform needs to be framed against it - not against "doing nothing costs nothing."
What changes structurally. A digital VBS platform doesn't just digitize existing paperwork - it changes where the burden sits. Inspections, corrective actions, and audit evidence move from being manually assembled to being captured as a byproduct of doing the work. That shift is what should anchor your business case: less time spent proving compliance after the fact, more time spent managing risk before it becomes an incident.
What to quantify, not what to guess. Resist the temptation to promise specific percentage improvements or time savings before you've tested them in your own environment - those numbers vary enormously by site size, current process maturity, and how disciplined the rollout is. Instead, structure your model around the categories that will actually move:
- Administrative hours reclaimed from your EHS and operations teams, based on your own time-tracking from the previous step
- Reduction in audit preparation effort, measured by comparing your current pre-audit timeline to what real-time evidence capture would replace
- Faster closure of corrective actions, because a system that tracks and escalates automatically closes gaps that manual follow-up misses
- Reduced exposure to findings, fines, or escalation from regulators, framed as risk avoided rather than a guaranteed saving
What it costs, honestly. Include the full picture: software cost, implementation and configuration time, training across sites, and the internal time required to migrate existing procedures and historical data. A three-year view is usually more honest than a first-year view, since the heaviest lift is upfront (setup, data migration, change management) while the return compounds as adoption spreads across the site and across inspection cycles.
Build the model your finance team will accept
Decision-makers outside EHS will want to see this in a format they already use to evaluate other investments: cost against risk-adjusted return, over a defined period.
A simple structure that holds up under scrutiny:
- Column 1 - Current state cost. Administrative hours (valued at loaded labor cost), audit preparation cost, and a conservative estimate of exposure from delayed corrective actions or missed inspections.
- Column 2 - Platform cost. License or subscription fees, implementation, training, and internal project time, spread across the same period.
- Column 3 - Expected shift. Where you expect hours and risk to move, stated as ranges rather than single numbers, and sourced from your own baseline data rather than vendor claims or industry benchmarks you can't verify.
Presenting a range, and showing your working, will do more for your credibility than a single confident number that can't be defended if someone on the finance committee asks how it was calculated.
Present it as a risk decision, not a software purchase
The framing that tends to land with leadership at a Seveso site is to lead with risk and follow with cost. Start the conversation with what could go wrong under the current system - a missed inspection, a corrective action that never closed, an audit that takes weeks to prepare because the evidence lives in ten different places - and only then move to what it costs to fix it.
This ordering matters because it's how Seveso obligations are actually assessed: the question regulators and your own board care about first is whether the VBS is functioning as intended, not whether it's efficient. Efficiency is what gets a budget approved quickly. Risk is what gets it approved at all.
Close with a clear ask: what you're requesting, over what timeframe, and what specifically it changes about how the site manages VBS obligations day to day. A vague request for "a digitization tool" is easy to defer. A specific request tied to named gaps in your current inspection, corrective action, and audit-readiness process is much harder to postpone.