At unmanned sites Report within 24 hours Works without a connection

Custom app development for on-site resilience

Under the Wwke (Critical Entities Resilience Act), you must report a disruption to the competent authority within twenty-four hours. That clock starts not at the office but at the site where something goes wrong, often an unmanned location with no signal. What is recorded there at the moment itself determines whether the report is accurate. What is reconstructed afterwards costs time you don't have.

Why resilience starts on site

The Critical Entities Resilience Act has applied since 15 August 2026 and concerns physical resilience: sabotage, terrorism, natural disasters and other major disruptions. Critical entities are designated by their ministry and must then take and test technical, organisational and physical measures.

The word physical is decisive here. The measures the law has in mind are outdoors: fences, access doors, camera installations, emergency power, pumps, switching stations. They are checked by people who drive past, not by a system that receives an alert. And those people work in places where the connection drops out.

That shifts the problem from the file to the recording. A resilience plan is worth little under supervision without evidence that checks and drills have actually been carried out. And in a disruption, what was recorded at that moment is what counts, because the report within twenty-four hours has to rest on something.

How we build this

The round is the unit here. If it is on record which object was seen, when and by whom, both the accountability and the report follow from it.

1
Riding along on the round

We go along to the sites, see how someone records things now and where the signal drops. That shapes the design more than the legal framework does.

2
Recording objects and points

Which objects belong to which critical process and what has to be checked per object. A round without that link is a walk, not evidence.

3
Offline as the starting point

The app works without a connection and syncs later, with a visible status per round. At unmanned sites that is a requirement, not an edge case.

4
Rehearsing the 24-hour report

We simulate a disruption and check whether everything the notification needs has been recorded on site. What is missing then will be missing later too.

What the app actually does

The app does little, and that little must always work, even at night, in the rain and without signal. Which components you need depends on the number of sites and on who visits them.

Inspection rounds along critical assets

For each round, which assets are due and what needs checking. The app guides the round and records what was seen, so it is clear afterwards which asset was inspected and when.

Provable presence at the asset

A scan or tag at the asset proves that someone was actually there. Without it, a ticked-off round is merely a claim, and under supervision that is the difference between evidence and paperwork.

Reporting a disruption from the site

When someone spots something, the recording starts right there: what, where, at what time and with what consequences. That information forms the basis for the notification within twenty-four hours.

Photo with time and location

A damaged fence, an open door, flooding in a basement. In a disruption, an image with time and location is the most convincing piece of evidence and the quickest to capture.

Working fully offline

Rounds, reports and photos carry on without a connection and are synchronised later, with each round showing whether that succeeded. Switching stations and pumping stations rarely have signal.

Site access and visitors

Who was there, for what reason and who let them in. In a disruption, the first question is who was on the site in the hours beforehand, and you won't answer that from a logbook in a site cabin.

Who we build for

The nature of the sites determines what the app looks like. Four situations.

Drinking water and water boards

Scattered, unmanned assets that are rarely visited. Here the round is the main means of control, and there is usually no connection.

Energy, grid operators and installations

Switching stations, transformer houses and sites with restricted access. Besides inspection, what matters here is being able to prove who was allowed where and when that access was used.

Government and public sites

Many buildings with varied functions and security levels. The challenge is knowing, for each building, which critical process depends on it, so that a round is tailored accordingly.

Healthcare and on-site utilities

Emergency power, medical gases, cooling and access to wards. The checks often already exist, but they are on paper and therefore hard to trace under supervision. Similar to the work in an inspection app, with a different purpose.

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

The app is the field side of the resilience file, not a separate administration. What it records ends up in the same register that holds the risk assessment and the measures.

React Native or native iOS and Android Offline storage with synchronisation Rounds with assets and checkpoints Scan or tag at the asset Photo with time and location Report with timeline from the moment of detection Access and visitor registration Roles per site Integration with the resilience file Integration with access or maintenance systems Works at night and with gloves on Remote device management Audit logging per action Hosting in the EU

Why Appfront

The 24-hour clock starts on site

What is recorded there at the moment itself underpins the notification. We build the recording at the point of detection, not at the point of drafting the notification.

No signal is the normal situation here

Unmanned sites and technical rooms rarely have a connection. Offline is therefore the starting point; an app that stalls there won't be used.

A round without evidence is a claim

We link every check to an asset and to proof of presence, because under supervision that is the difference between demonstrating and merely stating.

One file, no second reality

The app writes to the same register as the office side, via integrations. See the Wwke software for that side.

Security and privacy

This app holds the map of your vulnerabilities: which assets are critical, where they are, when they are checked and where the fence is broken. On a device that goes out on site, that is a real risk. We therefore limit what is stored offline on the device to the rounds of the moment, tie permissions to both the user and the location, and make sure a lost device can be disconnected remotely without stopping anyone else's work.

Recording people calls for its own assessment. Access and visitor data are personal data and should not be kept longer than is needed for the purpose for which you record them. We set a retention period on them rather than keeping everything, and keep the resilience records separate from personnel files. The evidence the app captures, photo, timestamp and employee, must on the other hand be immutable. 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 the resilience app

A paper logbook in a site hut does not show that someone actually visited the asset, and it cannot be searched quickly enough after an incident. The law requires you to test measures and to be able to demonstrate it; that requires records with time, place and person captured at the moment itself. That is exactly what a paper round does not provide.

It is not mandatory, but it is sensible. After designation you generally have nine months for the risk assessment and ten for the measures, and testing them is part of that. If you only start recording your inspection rounds then, you have no history when the time comes to account for yourself. Waiting here costs you evidence, not money.

Yes, that is the starting point. The app stores rounds, reports and photos locally and syncs as soon as there is a connection again, with each round showing whether that succeeded. Without this, the app gets bypassed on unmanned sites, and then the records still do not exist.

The report must describe what happened and what the consequences are. If the finding was recorded on the spot with a timestamp, location and image, you do not have to reconstruct it and the report starts from facts. Drafting and submitting it remains human work; the app supplies the material.

Usually, yes. Rounds are often walked by an external party, who can work in the same app under their own roles and with access only to the locations they visit. What you want to avoid is the evidence of your resilience sitting in your security provider's system rather than your own.

The actions look alike, the purpose does not. An inspection app tests against a standards framework and produces an inspection report. This app demonstrates that critical assets are monitored and that measures are tested, and it is tied to your critical processes rather than to a standard.

The Cbw (Cybersecurity Act) covers digital resilience and has its own reporting chain with different deadlines. The Wwke covers the physical side. If you fall under both, it is wise to maintain one overview of dependencies and feed two accountability processes from it.

That depends on the number of locations and assets, whether access registration is needed and how demanding the offline functionality is. Rounds with recording are usually quick to get running; access registration and integrations cost more. We give a well-founded estimate after the discovery phase.

Want to record rounds and incidents verifiably?

Ride along for one round and count how much of what is observed ends up recorded anywhere. That gap is what you will miss in supervision later. We build this as a standalone app and as part of a broader project: custom app or custom software.

Edit content