Veiligheidskundige: What the Role Really Involves

What a veiligheidskundige actually is

A veiligheidskundige is the safety professional inside a Dutch organisation who is responsible for identifying risks, advising on controls, and being able to show that both happened. The word does not translate cleanly. "Safety officer" is too narrow, "HSE manager" is too corporate. So we keep the Dutch term, because the job is defined by Dutch law and Dutch practice.

Under the Arbowet, an employer has to be supported by qualified experts. The veiligheidskundige is one of them, alongside the bedrijfsarts, the arbeidshygiënist, and the arbeids- en organisatiedeskundige. Not every company employs one directly. Plenty buy the hours in from an arbodienst or a consultancy. On larger industrial sites, and certainly on Seveso sites, the role is usually internal and full time.

MVK and HVK: the two levels people ask about

Two abbreviations come up in almost every vacancy text:

• MVK, middelbaar veiligheidskundige. The operational level. Present on the werkvloer, running inspections and toolbox sessions, handling incident reports, checking work permits, keeping the RI&E current in practice.
• HVK, hoger veiligheidskundige. The advisory and system level. Designs the safety management system, does the heavier risk analyses, advises the board, signs off on the things that require an expert judgement rather than an observation.

The split is not a hierarchy of competence so much as a split of altitude. An MVK who has walked a plant for fifteen years knows things an HVK will never see from a document. An HVK is the one who has to explain, in writing, why the system is arranged the way it is.

The part of the job that is not in the vacancy text

Ask a veiligheidskundige where the week goes and you rarely hear "risk analysis". You hear documentation.

The pattern repeats itself everywhere. There is a procedure that says what should happen. There is a practice that has drifted since it was written. And there is a document set that has to prove the two are still the same thing. We put it in one line internally: you have to write what you do, and you have to do what you write. That is the entire compliance problem, compressed.

Some concrete versions of that gap:

1. The checklist that is too long for the slot. Four pages of inspection points and two hours in the agenda. Nobody says out loud that it does not fit, so it gets ticked on paper afterwards and the tick means nothing.
2. The change that was never fed back. An installation is modified, the modification is approved, and the underlying document is not updated. Two years later that becomes a finding, and the technician who could have explained it has retired.
3. The over-written document. You fill a paragraph by referring to an internal procedure, then discover that the procedure now travels with the report to the bevoegd gezag. So you are shipping a stack of instructions you never intended to share.
4. The knowledge that walks out. Experienced people leave. New people on both sides of the table, yours and the inspectorate's, then talk past each other, and the result is a finding that is really a translation error.

None of that is a failure of expertise. It is a failure of retrieval. The knowledge exists, it is just not findable at the moment somebody needs it.

Where it gets heavier: high hazard and Seveso sites

On a Seveso site the job changes shape. You are no longer only advising on safe work, you are maintaining a veiligheidsbeheerssysteem with formal elements, a PBZO-document, and for hoge drempel sites a veiligheidsrapport that has to stay actual. Inspections come from the Nederlandse Arbeidsinspectie and, in the Rijnmond region, from DCMR. They arrive with the documents in hand.

Worth saying plainly: inspectors are not always right. A written overtreding is an interpretation, and interpretations can be discussed. Our view is that safety professionals hold that discussion too rarely. Not out of conflict, but because a discussion over facts is shorter and cleaner than a discussion over readings. To do that, you need your own documentation to be tighter than theirs. That is the real argument for keeping the paperwork in order, not the audit itself.

If you want the longer version of why standard EHS tooling struggles here, we wrote it up separately: why generic safety management software falls short for Seveso III companies.

What actually helps

Not more policy. Three things, in this order.

Make the inspection fit the walk. Split the long checklist by installation or by route, so the person doing it is answering questions about what is in front of them. Mixed-up points on a large installation is where it goes wrong.

Close the loop on changes. Every modification needs a defined path back to the documents it touches. If your MOC process ends at approval, it is not finished. Somebody has to be told which paragraph is now stale.

Get the evidence captured where the work happens. A photo, a timestamp, a location, an action with an owner. Captured once, on a phone, at the point of observation. If it has to be re-typed later, it will be re-typed badly or not at all.

That last one is the part we build. Capptions does mobile inspections and audits, custom forms and workflows, corrective action tracking, Clara as an AI assistant for the document side, and Capptions Seveso Control for the VBS work. It is a tool. It does not make you compliant, and it does not make a site risk free. It makes the evidence easier to produce and the gaps easier to see. The judgement stays with the veiligheidskundige, and the system stays yours, not ours.

A short, honest next step

If you are in this role and the documentation half is eating the advisory half, start by picking one document you know is out of date and tracing why. Usually the answer is not laziness. It is that nothing told anyone it had changed.

If you want to see how we handle that specific loop, we can walk through it on a call and show you the unfinished parts too. There are plenty. We are not going to pretend the platform is done.