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 target has been met. That second determination 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 are involved in soil remediation: the execution under BRL SIKB 7000 and the environmental supervision under BRL SIKB 6000, both as separate categories in Annex C of the Soil Quality Decree 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.
Supervision consists of two roles. Process control steers the execution process; verification establishes whether the remediation target has been achieved and forms the basis on which the competent authority forms its judgement. For that reason BRL SIKB 6000 requires functional separation for verification: it may not be carried out by the contractor performing the remediation, nor by the client. That requirement does not apply to process control.
The environmental supervisor does not need to be present continuously, but must be present during critical work: anything in the soil that could affect the result. Which activities and moments these are is fixed in advance in the supervision plan. The contractor's quality officer should likewise be present, and if they are replaced for non-critical work, that should be recorded in the logbook.
If you run several remediation projects at once, an office side is added, with protocols, qualified staff and notification deadlines per project. See the page on software for projects under BRL SIKB 7000.
How we build this
Records must be created where the work takes place. What is reconstructed in the office from photos and memory no longer carries weight as verification.
Who was present, what was excavated, which layer and which section. The report is built from that, not from a weekly timesheet after the fact.
A control sample without a place on the map is of no use at assessment. We link the sample, coordinate and analysis certificate together.
Exceptional circumstances belong in the evaluation report. Whoever writes them down afterwards misses the reason why things were done differently.
Not a writing session at the end, but a file that builds up during the remediation.
What the app does in practice
Daily logging on site carries the whole thing. The rest depends on the approach and the number of projects running.
Daily logging on site
Who was present, which works were underway and whether they were critical. The last point determines whether the supervisor had to be there.
Samples linked to their place on the map
Control sampling of the pit bottom and walls, with coordinates, time and image. The analysis certificate is later attached to that same point.
Deviations from the notification
What went differently from what was notified, when and why. If the notified details change, that goes to the competent authority in advance.
Works without signal
Inside a remediation pit there is no coverage. Everything is recorded locally and synchronised later, with the original time preserved.
Deadlines around the works
The advance notification, the list of executing parties and the report after completion each have their own moment. We place those on the project timeline.
The report builds up as the work proceeds
Records, samples and special circumstances fill the evaluation report while the remediation is still under way.
Who we build for
Who uses the app differs by project. Four situations.
Contractors carrying out remediation themselves
Work carried out under BRL SIKB 7000, with a quality-responsible person on site. You manage the certification 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 fixed record saves building up a file each time. See also the inspection app.
Cables, pipes and temporary removal
Soil that is removed and later returned falls under its own protocol. That work runs alongside infrastructure projects and sewer works.
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 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 receive new versions and the data to be reported differs by approach. Everything relating to protocols and fields should be configurable.
Why Appfront
Critical works determine the day
We record for each day whether critical work took place, because that makes the supervisor's presence mandatory.
Verification should stand apart
We separate the roles within the app. Verification must not be carried out by the contractor performing the remediation, nor by the client.
The report starts on day one
We build the logging so that the evaluation report follows from it. Starting to write only at the end produces a reconstruction.
We do not assess your remediation
Whether the target has been met is established by verification, and the competent authority weighs it. We build the record on which that judgement rests.
Security and privacy
A remediation file contains analysis results, images and notes about someone else's site. That information touches on the value of a plot of land and on your client's position. We set access per role and per project, give a verifying party its own scope, and log every inspection.
For this subject, the reliability of the record is the whole point. A sample whose location or time can be changed afterwards carries no weight as evidence of the final result. We record registrations, samples and images in a tamper-proof way, with time, place and person, even when synchronisation happens later, and any correction appears as 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 CVD policy.
Frequently asked questions about remediation under BRL SIKB 7000
Since 1 January 2026, only those of version 7.0 apply: protocol 7005 for excavation and remediation of soil, 7006 for in situ techniques and groundwater remediation, 7003 for interventions in the bed of surface water, and 7007 for the temporary removal of soil. Work on surface water beds touches on water engineering.
Process control guides the execution of the remediation while it is under way. Verification establishes whether the remediation objective has been achieved, so that the competent authority can assess whether the site has been properly remediated. Both fall under environmental supervision under BRL SIKB 6000, and for both the supervisor is registered by name.
No. BRL SIKB 6000 requires external separation of functions for verification: it may not be carried out by the contractor who performed the remediation or by the client, nor by a party organisationally, financially or legally connected to either. That requirement does not apply to process control; for an in situ remediation, the contractor may perform it itself.
Soil remediation is notified via the Omgevingsloket 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. In addition there is an information duty: the boundary and the expected start date four weeks beforehand, and the name and address of the certified contractor and of the supervision at least one week before the start.
It is prepared by the environmental supervisor and covers both process control and verification. It contains the outcome of the supervision, a list of special circumstances, and the verification of the final result: for removal, the control 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 in advance or afterwards, and the competent authority decides for itself what it checks. If it turns out the remediation was not carried out as notified, it may enforce. The data also enter 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 concurrent projects and whether integrations with a laboratory are needed. Daily logging with samples is usually quick to become useful; integrations cost more. We provide a reasoned estimate after the discovery phase.
Can you find a sample from last year?
Take a completed project and, for a single control sample, find the location, timestamp and certificate together. If they are not in one file, the report was written after the fact. We build this as a standalone app or as part of a broader building an app project.