Custom app for soil remediation under BRL SIKB 7000
On a remediation site, two accredited parties work side by side. The contractor excavates, and the environmental supervision establishes what has been removed and whether the objective has been met. That second finding becomes the evaluation report, and that report can only be built from what was recorded on site that day.
What is recorded on site
Two accreditations come into play when remediating soil: execution under BRL SIKB 7000 and environmental supervision under BRL SIKB 6000, each a separate category in Annex C of the Soil Quality Regulation 2022 (Regeling bodemkwaliteit 2022). Since 1 January 2026, only version 7.0 of BRL SIKB 7000 applies, with protocol 7005 for excavation and remediation, 7006 for in situ techniques and groundwater, 7003 for sediment and 7007 for temporary removal.
The supervision consists of two roles. Process control steers the execution process; verification establishes whether the remediation objective has been achieved and forms the basis on which the competent authority forms its opinion. That is precisely why BRL SIKB 6000 requires external separation of functions for verification: it may not be carried out by the contractor performing the remediation, nor by the client. This requirement does not apply to process control.
The environmental supervisor does not need to be present continuously, but must be present during critical activities: anything in the soil that can affect the outcome. Which activities and moments these are is set out in advance in the supervision plan. The contractor's quality officer is also present, and if they are replaced during non-critical work, this belongs in the log.
If you run several remediations at the same time, there is also an office side to deal with, with protocols, qualified staff and notification deadlines for each project. See the page on software for projects under BRL SIKB 7000.
How we build this
The recording must originate where the work takes place. What is reconstructed at the office from photos and memories no longer supports verification.
Who was there, what was excavated, which layer and which section. The report is built from this, not from a weekly summary written afterwards.
A control sample with no position on the map is of no use in the assessment. We link the sample, coordinates and analysis certificate together.
Special circumstances belong in the evaluation report. Anyone who writes them down afterwards misses the reason why a different course of action was taken.
No writing round at the end, but a file that grows during the remediation.
What the app actually does
The daily record on site carries the whole. The rest depends on your approach and the number of projects running.
Daily record on site
Who was present, which activities were running and whether they were critical. The latter determines whether the supervisor needed to be there.
Samples with their position on the map
Control sampling of the excavation floor and walls with coordinates, time and images. The analysis certificate is attached later to that same point.
Deviations from the notification
What went differently from what was notified, when and why. If the notified details change, this goes to the competent authority beforehand.
Works without signal
In a remediation excavation, the signal drops out. Everything is recorded locally and synchronised later, keeping the original timestamp.
The deadlines around execution
The advance notification, the declaration of the executing parties and the report afterwards each have their own moment. We put these on the project card.
The report grows during the work
Records, samples and special circumstances fill in the evaluation report while the remediation is still under way.
Who we build for
Who holds the app differs per project. Four situations.
Contractors who carry out remediation themselves
Work carried out under BRL SIKB 7000, with a person responsible for quality on site. You manage the accreditation in the Kwalibo software. For demolition there is software for demolition companies.
Environmental supervisors
You work for several clients and deliver a report per project. A single permanent registration saves you building up a file from scratch each time. See also the inspection app.
Cables, pipes and temporary excavation
Soil that is removed and later returned falls under its own protocol. That work is part of infrastructure projects and sewer work.
Removal, storage and processing
Excavated soil goes to a destination according to its quality class. You want to be able to trace that flow back to the section it came from, together with waste registration.
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 get new versions, and the data to be reported differs per approach. Everything to do with protocols and fields should be configurable.
Why Appfront
Critical work determines the day
We record for each day whether it involved critical work, because that makes the supervisor's presence mandatory.
Verification should be independent
We separate the roles in the app. Verification may not be carried out by the contractor performing the remediation, nor by the client.
The report starts on day one
We build the registration so that the evaluation report follows from it. Only starting to write at the end means reconstructing it after the fact.
We do not assess your remediation
Whether the objective has been achieved is determined by verification and weighed by the competent authority. We build the records on which that judgement rests.
Security and privacy
A remediation file contains analysis results, images and notes about someone else's site. That information affects the value of a site and your client's position. We set access per role and per project, give a verifying party its own scope, and log every access.
For this subject, the reliability of the registration is the whole point. A sample whose location or time can be changed afterwards cannot support a conclusion about the end result. We record registrations, samples and images immutably with time, location and person, even when synchronisation happens later, and turn a correction into a visible correction alongside the original value. How we handle security ourselves is described in our information security policy; external reports go through our CVD policy.
Frequently asked questions about remediation under BRL SIKB 7000
Since 1 January 2026, only those of version 7.0: protocol 7005 for excavating and remediating soil, 7006 for in situ techniques and groundwater remediation, 7003 for work on water beds, and 7007 for temporary excavation of soil. Water bed work touches on water engineering.
Process control adjusts the execution process during the remediation. Verification establishes whether the remediation objective has been achieved, so that the competent authority can judge whether the remediation was done properly. Both are part of environmental supervision under BRL SIKB 6000, and for both the supervisor is registered by name.
No. For verification, BRL SIKB 6000 requires external separation of duties: it must not be carried out by the contractor who performed the remediation or by the client, nor by any party organisationally, financially or legally affiliated with either. This requirement does not apply to process management; for in situ remediation, the contractor may do that themselves.
Soil remediation is notified through the Omgevingsloket (the Dutch Environment Portal) at least four weeks before the start; if the remediation is carried out differently from what was notified, this must be known at least one week in advance. There is also a duty to provide information: the boundaries and the expected start date four weeks beforehand, and the name and address of the certified contractor and of the supervision no later than one week before the start.
It is drawn up by the environmental supervision and covers both process management and verification. It contains the outcome of the supervision, a list of special circumstances and the verification of the end result: for removal, the verification sampling with analysis certificates and the sampling locations on a map; for capping, the check on the layer and its thickness. It goes to the competent authority within four weeks of completion.
It is not obliged to. For an activity under general rules, there is no approval beforehand or afterwards, and the competent authority decides for itself what it checks. If it turns out the remediation was not carried out in accordance with the notification, it can take enforcement action. The data is also entered into the soil information system.
The Kwalibo software is the office system: which certification you hold, who is listed for what, and how you demonstrate that during an assessment. This app is about the site: the day, the samples and the deviations. The project file refers to the certification that applied at the time.
That depends on the remediation approaches you encounter, the number of simultaneous projects and whether integrations with a laboratory are needed. Daily recording with samples is usually usable quickly; integrations cost more. We give a well-founded estimate after the discovery phase.
Can you find a sample from last year?
Take a completed project and, for one verification sample, try to bring together the location, the time and the certificate. If that is not in a single file, the report was written after the fact. We build this as a standalone app and as part of a broader app development project.