Fire Safety Inspection on Seveso Sites: A VBS Element

At a standard commercial building, a fire safety inspection asks a narrow question: if a fire starts, can people get out, and does the extinguisher work. At a Seveso or BRZO-classified site, that question is the wrong scope. Fire and explosion are major-hazard scenarios tied to specific installations - a tank farm, a loading bay, a process unit handling flammable or reactive substances - and the inspection has to verify that the barriers preventing and controlling those scenarios are actually in place and functioning, not just that a corridor is clear.

This distinction matters because fire-related risk at a major-hazard establishment isn't generic. It's scenario-specific, tied to the substances on site, and it's supposed to trace directly back to the risk assessment underpinning your veiligheidsbeheersysteem (VBS). An inspection regime that doesn't reflect that link is checking boxes without checking safety.

Fire and Explosion as a Major-Hazard Scenario, Not a Building Risk

In a Seveso risk assessment, fire and explosion scenarios are derived from the specific hazardous substances present and how they're stored, processed, and handled - not from generic occupancy risk. A warehouse fire and a vapor cloud explosion at a tank farm are different scenarios with different causes, different escalation paths, and different barriers.

That means the starting point for any fire-related inspection isn't a generic checklist - it's the scenario library from your risk assessment (QRA, HAZOP outputs, or equivalent). Each identified fire or explosion scenario should have a defined set of prevention and mitigation barriers attached to it: containment, ignition source control, detection, suppression, isolation, and emergency response. The inspection's job is to verify those specific barriers, installation by installation, not to walk a generic route checking exit signage.

If your inspection checklist can't be traced back to a scenario in the risk assessment, it's not doing the job a Seveso VBS requires.

Fire Detection and Suppression Tied to Specific Installations

Generic fire safety inspection treats detection and suppression as building-wide systems: smoke alarms in the ceiling, sprinklers throughout. At a major-hazard site, these systems are engineered around specific installations and specific failure modes, and they need to be inspected that way.

Points that matter at installation level:

Detection technology matched to the hazard. Flammable gas detection, heat detection, or flame detection - the right technology depends on what could actually ignite or leak at that specific installation, not a one-size-fits-all smoke detector.
Suppression systems designed for the substance. Water-based suppression is not appropriate for every process fire; foam, inert gas, or dry chemical systems may be required depending on what's stored or processed at that point. The inspection needs to confirm the system installed matches the hazard it protects.
Coverage and deployment area. Detection and suppression coverage should map to the installation's hazard footprint, not just to occupied space. A tank farm's fixed foam system needs functional testing and coverage verification distinct from an office sprinkler check.
Response time and activation logic. For process-critical fire scenarios, the inspection should confirm activation thresholds and response times are set correctly for the escalation speed of that specific scenario - a slow-developing storage fire and a fast-developing process leak fire need different detection response profiles.

This is inspection at the level of the installation and the scenario, not the building.

Fire-Related Elements of the Risk Assessment: What the Inspection Should Actually Check

A fire safety inspection at a Seveso site should be structured around the fire and explosion scenarios already identified in the site's risk assessment, checking whether the barriers assumed in that assessment are present and functioning. That includes:

Ignition source control. Are hot work permits, electrical classification (ATEX/zoning), and static control measures being followed at installations where flammable atmospheres are credible?
Containment and segregation. Are flammable and reactive materials stored and segregated according to the assumptions in the risk assessment - separation distances, compatible storage groups, bunding?
Detection system function. Are gas, heat, or flame detectors at each installation calibrated and tested on the schedule the risk assessment or equipment manufacturer specifies?
Suppression system readiness. Are fixed and mobile suppression systems (foam systems, deluge systems, fire water pumps) tested at the intervals required, with results documented and deficiencies tracked to closure?
Isolation and shutdown capability. Can the installation be isolated (emergency shutdown valves, deluge activation, power isolation) fast enough to match the escalation timeline assumed in the scenario analysis?
Escalation barriers. Are passive fire protection measures (fireproofing, fire walls, blast walls) intact and undamaged at installations where escalation to a domino event is a credible scenario?

Each of these should have a documented inspection frequency, a responsible role, and a record trail - because that's what regulators and your own VBS audits will ask to see.

Inspection Regimes for Fire-Critical Safety Equipment

Generic fire safety guidance treats "check the extinguisher" as roughly equivalent across an entire building. At a major-hazard site, fire-critical equipment has different criticality levels depending on which scenario it's a barrier for, and the inspection regime should reflect that.

Practical structuring:

Risk-based frequency, not uniform frequency. Equipment protecting high-consequence scenarios (a fixed suppression system on a flammable storage tank) warrants more frequent functional testing than a general-purpose extinguisher in a low-hazard administrative area. Frequency should be justified by the scenario's consequence and likelihood, not applied uniformly across the site.
Functional testing, not just visual checks. A visual check confirms an extinguisher is present and in date. It does not confirm a deluge valve will actually open, or that a gas detector will trip at the correct concentration. Fire-critical safety equipment at major-hazard installations needs functional or performance testing on a defined schedule, not just presence checks.
Independent verification of safety-critical elements. Where a fire or explosion barrier is classified as safety-critical in the risk assessment, inspection results should be independently reviewed, not just self-certified by the operating team.
Closure tracking, not just findings. A deficiency found during inspection (a suppression system that failed functional test, a detector reading out of calibration) needs a tracked corrective action with a deadline and a re-verification step - an open finding on safety-critical fire equipment is itself an unmanaged risk.

Connecting Fire Inspection to the VBS: Operational Control and Performance Monitoring

Under the Seveso Directive (and BRZO in the Dutch context), fire and explosion inspection isn't a standalone activity - it's one of the mechanisms that feeds two specific elements of the VBS: operational control and performance monitoring.

Operational control is where the procedures governing fire-critical equipment and activities live - permit-to-work systems for hot work, maintenance procedures for suppression systems, change management for anything that alters fire or explosion risk at an installation. The inspection regime is how you verify these procedures are actually being followed in practice, not just documented.

Performance monitoring is where inspection results become evidence. A VBS is expected to include indicators that show whether safety-critical systems are performing as intended - and fire detection/suppression testing results, ignition control audit findings, and equipment inspection closure rates are exactly the kind of leading and lagging indicators performance monitoring is meant to track. If your fire inspection program produces findings that never surface in your VBS performance review, the loop between "we inspected it" and "we know our fire risk is under control" is broken.

In practice, this means fire and explosion inspection data shouldn't sit in a separate maintenance log disconnected from your broader VBS documentation. It should be structured so that:

Inspection frequency and scope are traceable to the risk assessment scenarios they verify.
Results feed into the performance indicators reviewed at the frequency your VBS defines (often annually, or following any significant change or incident).
Deficiencies and their closure status are visible to whoever owns operational control for that installation, not just to whoever performed the inspection.

Building an Inspection Regime That Reflects Actual Risk

A fire safety inspection at a Seveso or BRZO site is only as good as its connection to the risk assessment it's meant to verify. Before finalizing or auditing your inspection program, it's worth checking:

Does every fire and explosion scenario in the risk assessment have a corresponding set of inspected barriers?
Is inspection frequency justified by scenario consequence and likelihood, rather than copied from a generic schedule?
Are functional tests - not just visual checks - being performed on safety-critical detection and suppression equipment?
Do inspection results and open findings feed into your VBS's operational control procedures and performance monitoring indicators?

Getting these connections right is what separates a fire safety inspection that satisfies a checklist from one that actually reduces the likelihood and consequence of a major accident.