Excavating is not the same as remediating The protocols changed in January Staffing is a requirement, not a schedule

Custom software for projects under BRL SIKB 7000

An accredited contractor rarely has just one job under way. Excavation work above the intervention value runs alongside remediation projects, each with its own protocol, notification point and staffing. The office needs to know where all those projects stand at the same time, and that is a different question from what is happening in the pit that day.

Two regimes under one accreditation

The accreditation for BRL SIKB 7000 covers two environmentally burdensome activities that overlap in practice. Excavating soil above the intervention value is covered by section 4.120 of the Environment and Planning Activities Decree (Besluit activiteiten leefomgeving); remediating soil by section 4.121. Both are carried out by a company with that accreditation, and in Annex C of the Soil Quality Regulation 2022 (Regeling bodemkwaliteit 2022) they fall together under category 11. What has to happen around them does differ, and that should be visible as soon as an assignment comes in.

For remediation, the activity is always supervised by a company accredited for BRL SIKB 6000. For excavation, this applies in three cases: when contaminated soil is removed rather than returned, when there is already a living layer or other permanent cover layer that the excavation passes through, or when batches have to be kept separate. That belongs in the costing, not on the morning the work starts.

Since 1 January 2026, only version 7.0 of BRL SIKB 7000, established on 7 March 2022, applies, with protocol 7005 for excavating and remediating soil, 7006 for in situ techniques and groundwater remediation, 7003 for sediment and 7007 for temporary removal. Version 6.0 and protocols 7001, 7002 and 7004 were withdrawn at that point, together with versions 1.0 of 7005 and 7006. A job that ran across the turn of the year was carried out under two document versions.

How we build this

Records rebuilt in a folder for every assignment can't sustain comparison between jobs. We record the regime, protocols and deadlines on the project itself.

1
Establish the regime at assignment

Excavating above the intervention value or remediating soil. Different notifications and a different supervision requirement come with each.

2
Record protocols with their version

Which protocol belongs to this approach and which version applied at the time. The version belongs to the job, not to the company.

3
Link people to jobs

Who is responsible for quality on which project and when they have to be on site. For critical work, that is not a preference but a requirement.

4
Put the notification points on the project card

The advance notification, the declaration of the parties and the data after completion each have their own deadline.

What the software actually does

The project register with the protocols and deadlines holds it all together. The rest depends on the number of simultaneous projects and sites.

All current projects side by side

Which regime, which phase, which protocol and who is assigned. That is exactly what a project folder per job does not give you.

Protocol and version per project

Which standard document applied while the work was under way, up to and including the date of determination. In a review after the fact, the conversation starts there.

Qualified persons and their deployment

Who is qualified for what, which project they are on and where they are expected next, alongside your Kwalibo software.

Notifications with their own deadlines

Notification four weeks in advance, the names of the executing and supervising parties at the latest one week in advance, and a new notification as soon as the work changes course.

Compiling the evaluation report

Daily records, samples and special circumstances come in from the field and are combined here into a single report.

Connecting to the field and the laboratory

Analysis certificates and field records usually live elsewhere. We pull in what is available through integrations.

Who we build for

Where the emphasis lies depends on your role in the work. Four situations.

Contractors with several projects at once

Your question is staffing: which project needs someone on site this week and where they are now. If other construction work runs alongside, see software for construction companies; you record the day in the pit in the SIKB app.

Consultancies providing supervision and investigation

You provide process management and verification for clients who do not know each other. One register keeps the roles per project separate and supports your audit preparation.

Cables, pipes and temporary excavation

Many small jobs with a short turnaround and their own protocol. That fits in with infrastructure projects and sewer work.

Clients with multiple sites

You are not accredited yourself but you maintain the file for your sites, and you want to see which report belongs to which site. If it involves demolition with soil work, see software for demolition companies.

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

Protocols are revised and each remediation approach calls for different notification fields. Anything tied to protocols, notification fields and roles should therefore be configurable.

If you want to exchange soil data with laboratories and authorities without retyping it, see our page on a SIKB0101 integration.

If it concerns archaeological data rather than soil investigation, there is our page on a SIKB0102 integration.

Node.js / Python / .NET PostgreSQL Project register with regime and phase Configurable protocols with version date Qualifications and availability per person Notifications with deadline and status Data and documents per notification point Quantities per quality class Samples and analysis certificates linked to the work Evaluation report structure Roles for execution, process management and verification Integration with field recording and the laboratory Audit logging Hosting in the EU

Why Appfront

The deadline depends on the regime

We set the notification points per activity. Excavating and remediating do not require the same data, nor at the same moment.

The protocol version belongs to the project

We record which document applied at the time. A reference to the current protocol says nothing about a project from last year.

The notification needs figures

Soil volume, quantities to be removed per quality class, and the location on the map and cross-section. We build fields for these instead of a loose spreadsheet.

We do not assess your work

Whether the approach is sound and whether the objective has been met is a question for the supervising party and the competent authority. We build the administration that those judgements rely on.

Security and privacy

A project administration holds analysis results, quantities and notes about sites belonging to clients who may be competitors. We set access per role and per project, give a supervising or verifying party only its own works, and log every access.

What also matters here is that data cannot shift unnoticed after the fact. A notification that turns out to have been updated after an inspection is exactly the document that ends up in dispute. We record notifications, data and report versions immutably, with a timestamp and the person responsible, and make a correction a visible correction alongside the original value. 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 working under BRL SIKB 7000

In category 11, Annex C of the Regeling bodemkwaliteit 2022 (Soil Quality Regulation) lists excavation of soil above the intervention value and soil remediation, as well as remediations and groundwater remediations under transitional law or governed by an environmental plan, environmental ordinance or environmental permit. The standard document is BRL SIKB 7000 version 7.0.

Only those of version 7.0, adopted on 7 March 2022: 7005 for excavating and remediating soil, 7006 for in situ techniques and groundwater remediation, 7003 for the water bed and 7007 for temporary storage. Protocols 7001, 7002 and 7004 and versions 1.0 of 7005 and 7006 were withdrawn as of 1 January 2026.

For remediation, always: the activity is supervised by a company accredited under BRL SIKB 6000. For excavation above the intervention value, only if contaminated soil is removed rather than returned, if the excavation goes through an existing habitable layer or other durable covering layer, or if batches have to be kept separate.

Both activities are notified at least four weeks before the start. The delineation and the expected start date also go to the competent authority four weeks in advance, supplemented for excavation by the expected duration and the reason. At the latest one week before, the name and address of the executing party and of the supervisor follow. If the work changes course, a new notification is required one week beforehand.

For remediation, an evaluation report in accordance with BRL SIKB 6000, no later than four weeks after completion, with the results of process control and verification. For excavation it is lighter: no later than one week after completion, the end date and, if there was supervision, its results with the excavation shown on a map and cross-section, the destination of removed soil and any special circumstances.

The Kwalibo software is about the accreditation itself: which categories you work in, who is named on it and how you demonstrate that. This page is about the work you carry out under that accreditation; a project carries the accreditation that applied at the time. You manage third-party certificates in a certificate file.

The SIKB app is the site: the day, attendance, samples and deviations. This software is the office: which projects are running, which protocol applies to each, which deadlines are open and how the report is compiled from them. If you build only the office side, you are left with data entry.

That depends on the number of simultaneous projects, how many protocols you work with and whether integrations are needed with a laboratory or your project administration. The register of protocols and deadlines is usually usable quickly; integrations cost more. We give a substantiated estimate after the discovery phase.

Do you know which protocol applied last year?

Take a job that ran across the turn of the year and look up which protocol and which version applied, and who was deployed on the critical days. If that isn't all in one place, the answer is buried in mailboxes. We build this as a standalone application and as part of a broader custom software project.

Edit content