Multiple regulators, one visit The summary is made public Findings end up everywhere

Custom software for Seveso inspections and findings

A Seveso inspection is not a visit from a single regulator. A team arrives from the Labour Inspectorate, the safety region and the environmental agency, sometimes joined by others, having drawn up a joint programme. The findings that come out of it land with different departments, and the summary is made public.

How supervision is organised

Supervision runs through a cooperation programme in which the Dutch Labour Inspectorate, the safety regions and the environmental agencies work together, supplemented by parties such as Rijkswaterstaat, the water boards, the Human Environment and Transport Inspectorate, the Public Prosecution Service and the State Supervision of Mines. They inspect jointly, to avoid three regulators visiting three times with three different verdicts.

For each establishment, the inspectors draw up an inspection programme. That programme is not static: it is revised on the basis of national themes, the results of earlier inspections, policy changes, violations found, complaints, near misses and incidents. What happened at your site last year therefore helps determine what they look at this year.

And then the point that is often underestimated: a public summary is published of every routine inspection. That practice has existed since 2014. It means your follow-up is not an internal matter but something a neighbour, a journalist or a customer can read. A finding that is still open is then a different kind of problem from one that has been resolved.

How we build this

Here the finding is the unit, not the visit. An inspection produces points that still need to be closed months later, often by someone other than the person who was there.

1
Findings as their own register

Every finding with its origin, the inspector who identified it and the article it rests on. As long as this is a row in a report, it disappears.

2
Attaching an owner and a deadline

A finding without a name and a date is an intention. We link every finding to a person and a deadline, and make visible what is overdue.

3
Making the follow-up demonstrable

Not just that something was done, but what, by whom and what shows it. That is what gets checked at the next visit.

4
Looking ahead to the next programme

The inspection programme is adjusted based on earlier results and incidents. If you keep track of your own near misses, you know sooner where the attention is heading.

What the software actually does

The findings register carries the whole. What else you need depends on your size and on how many inspectors visit you.

Findings with their origin

Which inspector, which part of the programme, which legal basis. In a joint inspection that distinction is needed to know who should receive the response.

Follow-up with cause and evidence

A measure without substantiation does not count at the next visit. We record what was done and what shows it.

Deadlines monitored per finding

A finding whose deadline passes makes for a tougher conversation than the finding itself. That should not depend on someone's calendar.

Patterns across inspections

The same cause recurring is what regulators look for. You only see that if findings from multiple years are in a single register.

Preparing for the programme

The programme is adjusted based on themes and on your own history. We make visible which areas have not been covered for a while.

Integration with your management system

Findings touch your substance inventory, your scenarios and your maintenance. We pull these in through integrations with what you already have, including the inventory register and management system.

Who we build for

The scale of the inspection process varies widely. Four situations.

Chemicals and process industry

Upper-tier establishments with a safety report and an extensive programme. This is where most findings and most inspectors come together. See also software for the chemical industry.

Storage and transshipment of hazardous substances

Less complex processes but more movements. Findings here more often concern orderliness, segregation and record-keeping than installation safety.

Companies just below the threshold

Not a Seveso establishment, but still visited by the environmental agency and the Labour Inspectorate. The same follow-up question, a lighter framework. If there is an explosion hazard, there is ATEX software.

Safety professionals and advisory firms

You guide several establishments through the same process. One environment per client saves you reconstructing a file at every visit.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

Supervisory themes and legal bases change; since 2024 the obligations are also set out in different legislation. Everything related to this should be configurable and stored with its history.

Node.js / Python / .NET PostgreSQL Findings register with origin Owner and deadline per finding Follow-up with justification and evidence Pattern analysis across multiple inspections Configurable legal bases and themes Integration with the management system Documents attached to the finding History without overwriting Roles per department and per external adviser Export for regulators Audit logging EU hosting

Why Appfront

One visit, multiple regulators

For each finding, we record who identified it and on what legal basis. Without that, you don't know who should receive the response.

The deadline is the real risk

We track deadlines per finding. A missed date weighs more heavily at the next visit than the original finding did.

The summary becomes public

We build the follow-up so that you can show what happened, because that story ends up in the public domain.

Repetition is the pattern they look for

We keep findings together across the years, so the same root cause stands out before an inspector spots it.

Security and privacy

A findings register describes where things were not in order at your organisation. That is information you want to keep strictly confidential and want to be able to separate by department. We set access per role and per location, give an external adviser only their own scope, and log every time the register is viewed.

For this topic, history carries great weight. At a later visit or after an incident, the question is about the situation at a specific point in time: which finding was open then, who was responsible and what had been done. We therefore keep every change to a finding or its follow-up with a timestamp and the person responsible, and show an amendment alongside the old value instead of overwriting it. How we handle security ourselves is set out in our information security policy; reports from outside go through our coordinated vulnerability disclosure policy.

Frequently asked questions about the Seveso inspection

A joint team. The permanent core consists of the Netherlands Labour Authority, the safety region and the environmental agency; depending on your situation, Rijkswaterstaat, a water authority, the Human Environment and Transport Inspectorate or the State Supervision of Mines may join. They work together in a single programme rather than visiting separately.

A public summary is published for every routine inspection; this practice has existed since 1 May 2014. That means your follow-up counts not only towards the regulator but also towards local residents, customers and the press.

For each site, the inspectors draw up a programme together and review it periodically. National themes, the results of earlier inspections, policy changes, violations, complaints, near misses and incidents all play a part. Your own history is therefore one of the ingredients.

The BRZO software deals with your own substance inventory, the threshold assessment and the safety management system. This page deals with the process with the regulators: the programme, the findings and the follow-up. In practice, you build them on a single register.

Not in the legislation. The Major Accidents (Risks) Decree 2015 was repealed on 1 January 2024 when the Environment and Planning Act came into force, and the obligations are now set out in the regulations beneath it. The term is Seveso establishment. In practice, many companies and advisers still use both terms interchangeably.

Then it comes back at the next visit, and the conversation is no longer about the original shortcoming but about why nothing has been done. Regulators have enforcement instruments at their disposal, and repetition weighs heavily in them. The deadline is therefore more important than the finding itself.

Yes. We give an external safety expert or advisory firm access to the scope they are working on, with a role of their own. That is usually more practical than emailing findings back and forth until nobody knows which version applies.

That depends on the number of sites, your structure and how much has already been recorded. The findings register with deadline tracking is usually quick to get into use and removes the biggest risk; integrations with the management system cost more. We give a well-founded estimate after the discovery phase.

Know what is still open?

Take the report from your last inspection and, for each finding, look up who owns it and when it has to be closed. If that takes more than a few minutes, that is the gap. We build this as a standalone application and as part of a broader custom software programme.

Edit content