Notification valid for twenty working days Risk analysis per location Deviations reported to the Kadaster

Custom software for excavation notifications and the careful excavation process

Since CROW 500 came into effect, preventing excavation damage is no longer solely the machine operator's responsibility. The guideline places the duty of care on the entire chain: client, designer, excavator and network operator each have their own share. That means that for every excavation location, something must be demonstrable, not just agreed.

Appfront
Live

What the guideline asks of the chain

CROW 500 is the elaboration of the careful excavation process and succeeds the earlier publications 250 and 308. Where attention used to focus mainly on the excavator, this guideline explicitly names the role of the client and the network operator. The Dutch Supreme Court has ruled that, in cases of excavation damage, the guideline serves as a standard of care and that its wording carries great weight.

Then there is the legal side: under the WIBON, the excavator investigates cables and pipelines in the area where digging will take place. That investigation starts with an excavation notification, in practice the KLIC notification. It must be submitted at least three working days before work begins and is valid for a maximum of twenty working days. If the work overruns, a new notification should be in place.

Where the exact position is unclear, locating is required, for example with trial trenches. If the actual situation turns out to differ from what was supplied, this should be reported to the Kadaster. These are not isolated actions; they are steps in a single process that you need to be able to account for afterwards.

And that is where the gap lies. Notifications are made, drawings are downloaded and trial trenches are dug, but the evidence is scattered across mailboxes, phones and a folder on a server. When damage occurs, the question is not whether someone intended to be careful, but what was recorded.

How we build this

The core is the excavation site, not the project and not the notification. A single site can involve several notifications, several crews and several weeks, and everything that happens there should be tied to that site.

1
The site as a file

Each excavation site gets its own file with the area, the client and the work involved. Notifications, drawings and observations are attached to it rather than to a person.

2
Notifications and their clock

Every notification has a validity period. The system monitors that period and warns you before anyone digs without a valid notification.

3
Recording the investigation

The risk assessment, the choices made and the locating work belong in the site file, including who did it and when. That is the part that counts when damage occurs.

4
Passing on deviations

If the actual position differs from the data supplied, this is recorded with an image and position and prepared for reporting to the Kadaster.

What the software actually does

The file per excavation site carries the whole. What else you need depends on your role in the chain and on the number of sites running at the same time.

Notifications with validity

Every excavation notification has a start date and a validity of twenty working days. The system shows which sites are approaching that limit.

Risk assessment per site

The assessment belongs to the area and to the work. We record which risks were identified and which measure followed from them.

Recording locating work

Where a trial trench was dug, what was found and at what position. With an image and timestamp, so it can be traced afterwards.

Reporting deviating positions

A confirmed deviation is recorded and prepared for reporting to the Kadaster, instead of getting lost in a group chat.

Roles in the chain

Client, designer, excavator and supervisor each see their own part. Who took which step remains visible.

A file for later

In the event of damage or a dispute, you can provide the complete history of the site: notifications, assessments, observations and images, in order.

Who we build for

Your role in the excavation chain determines what you need from the software. Four situations.

Contractors and excavators

They submit the notifications and do the locating. What matters most to them is that nobody digs on an expired notification.

Clients and municipalities

Since the guideline, they have their own share in the preparation. They want to be able to demonstrate what was supplied and agreed.

Network operators

They supply the data and have an interest in feedback about deviating positions, preferably with position and images.

Engineering and consultancy firms

If you do the preparation for several clients, you want one way of working rather than a different folder for every project.

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

Guidelines are revised, notification formats change and the requirements for what must be available on site have been tightened in recent years. Periods, roles and risk categories should be configurable rather than hard-coded.

Configurable periods per notification type Map view of the excavation area Storage of supplied area information Alerts for expiring validity Photo with timestamp and position Roles for client, execution and supervision History per excavation site Export of the site file Audit trail on every change API for integration with your project administration

Why Appfront

The site is the file, not the notification

A single excavation site often involves several notifications and crews. If you keep records per notification, you lose the history of the site itself.

A deadline you have to remember doesn't work

The validity of a notification is the most predictable cause of mistakes. The system should be monitoring it.

Recording in the moment

A trial trench entered at the office in the evening is a recollection. We build the recording where the work happens.

We don't determine your duty of care

What counts as careful in a specific case is a professional and legal question. We make sure that what you do remains demonstrable.

Security and privacy

An excavation file contains data on the location of cables and pipelines, which is information that should not circulate widely. We set access per role and per location, give a subcontractor only the locations they work on, and log who views what. Integrations with your existing software run through secure integrations.

For this topic, what matters is that the record is reliable at the moment it is made. A risk analysis added after an incident is no longer preparation. We record notifications, analyses and observations immutably, with time, position and person, and turn a correction into a visible correction alongside the original entry. How we handle security ourselves is set out in our information security policy.

Frequently asked questions about the careful excavation process

A notification must be made at least three working days before work starts and is valid for a maximum of twenty working days. If the work continues, a new notification must be in place. That is exactly the kind of deadline you do not want to monitor by hand.

Yes. The guideline defines the roles of client, designer, excavator and network operator. Preventing excavation damage is a responsibility shared across the chain, not just for whoever operates the machine.

A discrepancy between the data supplied and the actual situation should be reported to the Kadaster (the Dutch Land Registry). Software helps mainly by recording the finding, with position and image, at the moment it happens.

The guideline assumes you investigate what lies in the area and take measures that fit. How extensive that needs to be depends on the location and the work. Whatever you choose, it must be possible to reconstruct it later.

Usually not. Many companies submit notifications through an existing channel. We build the layer around it: the file, deadline monitoring and on-site recording, integrated with what you already use.

Yes. The digital map at the excavation site is covered on our page about the CROW 500 app.

Do you know today where the notification stands?

Take a project that is under way and look up when the excavation notification was made. If you have to dig through a mailbox to find it, that is the gap through which an incident slips. We build this as a standalone solution and as part of a broader custom software development project.

Edit content