Custom software for projects under BRL SIKB 7000
A certified contractor rarely has just one job on the go. Excavation works above the intervention value run alongside remediations, each with its own protocol, notification moment and staffing. The office needs to know where all those projects stand at the same time, which is a different question from what is happening in the pit that day.
Two regimes under one certification
The certification for BRL SIKB 7000 covers two environmentally relevant activities that in practice get mixed up. Excavating soil above the intervention value is set out in section 4.120 of the Environment Activities Decree (Besluit activiteiten leefomgeving); remediating soil in section 4.121. Both are carried out by a company holding that certification, and in Annex C of the Soil Quality Regulation 2022 they fall together under category 11. What must happen around them differs, however, and that should be visible as soon as an assignment comes in.
For remediation, the activity is always supervised by a company holding a certification for BRL SIKB 6000. For excavation, that applies in three cases: when contaminated soil is removed rather than returned, when a soil cover layer or other durable capping already lies where the excavation passes through, or when batches must be kept separate. That belongs in the costing and not on the morning the work starts.
Since 1 January 2026, only version 7.0 of BRL SIKB 7000 applies, adopted on 7 March 2022, together 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, along with versions 1.0 of 7005 and 7006. A project that ran across the turn of the year was carried out under two document versions.
How we build this
A records system rebuilt in a folder for each job does not keep the comparison between projects intact. We record the regime, protocols and deadlines against the project itself.
Excavation above the intervention value or remediation of soil. These trigger different notifications and a different supervision requirement.
Which protocol applies to this approach and which version was in force at the time. The version belongs to the project, not to the company.
Who is responsible for quality on which project and when they must be on site. For critical activities this is not a preference but a requirement.
The prior notification, the declaration of the parties involved and the data after completion each have their own deadline.
What the software actually does
The project register with protocols and deadlines holds it all together. The rest depends on the number of concurrent projects and branches.
All ongoing projects side by side
Which regime, which phase, which protocol and who is assigned to it. That is precisely what a folder per project does not provide.
Protocol and version against the project
Which standard document was in force while the work ran, up to the adoption date. If the work is reviewed afterwards, the discussion starts there.
Qualified personnel and their deployment
Who is qualified for what, which job they are assigned to and where they are expected to be afterwards, alongside your Kwalibo software.
Notifications with their own deadline
Notification four weeks in advance, the names of the executing and supervising parties no later than one week in advance, and a fresh notification whenever the work changes course.
Compiling the evaluation report
Daily logs, samples and special circumstances come from the field and are combined here into a single report.
Connecting to field and laboratory
Analysis certificates and field records usually sit elsewhere. We retrieve what is there via integrations.
Who we build for
Where the emphasis lies depends on your role in the work. Four situations.
Contractors with several jobs running at once
Your question is capacity: which job needs someone on site this week and where is that person now. If other construction work is involved, see software for construction companies; you record the day at the well in the SIKB app.
Consultancies providing supervision and investigation
You deliver process control and verification to clients who do not know one another. A single register keeps the roles for each job separate and supports your audit preparation.
Cables, pipes and temporary removal
Many small jobs with a short lead time and their own protocol. This is covered within infrastructure projects and for sewerage work.
Clients with several sites
You are not certified yourself but keep the records for your sites and want to see which report belongs to which location. If the work is demolition involving soil remediation, see software for demolition companies.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.
Explore OneDayBuild →Technology and integrations
Protocols are revised, and different remediation approaches require different notification fields. What relates to protocols, notification fields and roles should therefore be configurable.
If you want to exchange soil data with laboratories and authorities without retyping, see our page on an SIKB0101 integration.
If the matter is not soil investigation but archaeological data, there is our page on an SIKB0102 integration.
Why Appfront
The deadline depends on the regime
We set notification moments per activity. Excavation and remediation do not require the same data, nor at the same point in time.
The protocol version belongs to the work
We record which document applied at the time. A reference to the current protocol says nothing about a project from last year.
The notification requires figures
Soil volume, quantities to be removed per quality class, and the location on a map and cross-section. We build fields for this rather than a loose spreadsheet.
We do not assess your work
Whether the approach is sound and whether the objective has been achieved are questions for the supervising party and the competent authority. We build the administration on which those judgements rest.
Security and privacy
A project administration contains analysis results, quantities and notes about client sites that may be competitors of one another. We set access by role and by project, give a supervising or verifying party access only to its own works, and log every access.
Here it also matters that a record cannot quietly change after the fact. A notification that turns out to have been updated after an inspection is exactly the document that becomes the subject of dispute. We store notifications, data and report versions as unalterable, with time and person recorded, and treat any correction as a visible correction alongside the original value. Our approach to security is set out in our information security policy; reports from outside reach us through our CVD policy.
Frequently asked questions about working under BRL SIKB 7000
Annex C of the Soil Quality Decree 2022 (Regeling bodemkwaliteit 2022) lists in category 11 the excavation of soil above the intervention value and the remediation of soil, as well as remediations and groundwater remediations under transitional law or governed by an environmental plan, environmental regulation 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 excavation and remediation of soil, 7006 for in situ techniques and groundwater remediation, 7003 for sediment and 7007 for temporary removal. Protocols 7001, 7002 and 7004, and version 1.0 of 7005 and 7006, were withdrawn with effect from 1 January 2026.
For remediation always: the activity is supervised by a company certified under BRL SIKB 6000. For excavation above the intervention value only where contaminated soil is removed rather than returned, where the excavation passes through an existing barrier layer or other durable capping layer, or where separate batches must be kept apart.
Both activities must be notified at least four weeks before commencement. Four weeks in advance, the boundary and the expected start date also go to the competent authority; for excavation, the expected duration and the reason are added. No later than one week in advance, the name and address of the executing party and of the supervising party follow. If the work will proceed differently, a new notification is required at least one week in advance.
When remediating, you submit an evaluation report under BRL SIKB 6000 no later than four weeks after completion, including the results of process control and verification. For excavation it is lighter: no later than one week after completion, the end date and, if supervision took place, its results together with the excavation on map and cross-section, the destination of removed soil, and any special circumstances.
The Kwalibo software is about the certification itself: which categories you hold, who is named on it, and how you demonstrate that. This page is about the work you carry out under that certification; a project carries the certification 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 jobs are running, which protocol applies to them, which deadlines are open and how the report is compiled from that. If you only build the office side, you are left with manual data entry.
That depends on the number of concurrent jobs, how many protocols you run and whether integrations are needed with a laboratory or your project administration. The register of protocols and deadlines is usually quick to become useful; integrations cost more. We give a reasoned estimate after the discovery phase.
Do you know which protocol applied last year?
Take a job that ran over the New Year and look up which protocol and version applied, and who was deployed on the critical days. If that isn't recorded 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.