The Gemba Walk on a Seveso Site: What It Means for Your VBS

What does "Gemba" mean?

Gemba is a Japanese term meaning "the real place." In lean manufacturing, it refers to the shop floor - the actual location where the work happens, as opposed to the office where it gets reported on. The related principle genchi genbutsu - "go and see for yourself" - captures the same idea: don't manage a process purely from the numbers or the paperwork it generates. Go look at it.

A Gemba walk is the practice built on that principle: a manager or specialist physically walks the work area, observes the process as it's actually running, and talks to the people doing it, instead of relying only on reports.

For a Seveso or BRZO-classified site, that distinction - the real place versus the paper record - is not just a lean-manufacturing nicety. It's the gap where major-accident risk hides.

Why the floor and the VBS drift apart

Your veiligheidsbeheersysteem (VBS) is the documented version of how the site is supposed to run: risk assessments, safe work permits, inspection and maintenance schedules, barrier management records. It's what you'd show a regulator, and it's what most audits check against.

But documentation is a snapshot, and the floor keeps moving. A temporary bypass gets left in place after the job that needed it is done. A permit-to-work gets extended verbally instead of on paper. A safety barrier gets flagged as inspected on the schedule, but the inspection was rushed or the follow-up repair never happened. None of this shows up if you only ever look at the VBS itself - the documentation says everything is under control, because it hasn't caught up with reality yet.

A Gemba walk is one of the few tools that directly targets this gap. It doesn't replace the VBS. It checks whether the VBS still describes what's actually happening.

What a Gemba walk looks like for major-hazard verification

Applied to a Seveso site, a Gemba walk isn't a generic safety stroll - it's a structured comparison between the floor and specific parts of the VBS:

Barriers. Walk to the safety-critical barriers listed in your risk assessment - relief valves, interlocks, fire and gas detection, containment - and check their physical state against what the maintenance record says. Is the barrier actually in the position or condition the documentation claims?
Permits-to-work. Pick a few active permits and go find the work they authorize. Is it being carried out within the conditions on the permit - isolation points, PPE, gas testing, time limits? Permits that have drifted from what's actually happening on-site are one of the most common precursors to major incidents.
Equipment condition. Compare visible wear, corrosion, or damage against the last inspection date and result. A piece of equipment "due for inspection in six months" that already shows signs of failure is exactly what a walk is meant to surface before the schedule does.
Housekeeping and access. Blocked emergency routes, missing signage, or unauthorized storage of flammable materials near process equipment are often invisible in a document review but obvious in five minutes on-site.

The goal isn't to catch individual workers doing something wrong. It's to find out where the documented safety system and the operational reality have quietly stopped matching - and fix that before an auditor, or an incident, does it for you.

How to run one properly

Set the scope before you walk. Pick a unit, a set of barriers, or a batch of open permits - not "the whole site." A focused walk produces findings you can actually act on.
Bring the relevant VBS documents with you. The point is comparison, not just observation. Have the permit, the risk assessment, or the inspection log in hand.
Talk to the people on the floor. Operators and technicians know where procedures have drifted long before it appears in any record.
Log what you find immediately. A gap noticed and not documented is a gap that gets forgotten by the next shift change.
Close the loop. Findings need an owner and a follow-up date, or the walk becomes a one-off exercise instead of part of how the site runs.

A Gemba walk is not an audit

It's worth being clear about what a Gemba walk isn't. A formal Seveso audit - internal or regulatory - is systematic, scheduled, and evaluates the management system as a whole against its requirements. A Gemba walk is faster, less formal, and narrower: a spot-check of whether specific parts of the VBS still hold up against what's physically true on the floor right now.

The two complement each other. Audits tell you whether your VBS is complete and compliant on paper. Gemba walks tell you whether that paper still describes your site. A site that only audits will eventually be surprised by drift that built up quietly between audit cycles. A site that only walks the floor, without ever checking findings against the formal system, loses the paper trail regulators require. Used together, they close the loop from both directions - one from the documentation down, one from the floor up.