New law from 1 January 2027 Accessible from the moment of creation Including what is created outside

Custom app development for archive records from the field

The new Archives Act requires digital information to be managed in an accessible way from the moment it is created. That phrase, the moment of creation, is the difficult part. A photo of a sunken kerb, a message about an enforcement decision, a note on a tablet: that is government information, and it is created out on the street, on a phone that belongs to no one.

What changes in 2027

The new Archives Act was passed by the Senate in May 2026 and comes into force on 1 January 2027. The transfer period is reduced from twenty to ten years, so government bodies will hand over the information they must retain permanently to an archive service sooner. That shorter period applies to records created or received after the Act comes into force; anything already held remains subject to the old period.

More important for day-to-day practice is the requirement that digital material is managed in an accessible way from the moment of creation, so that it is not lost through a system change or outdated technology. The framework for this is DUTO, which describes what sustainably accessible government information means. The Act also requires an archivist to be appointed.

The unspoken challenge lies in the phrase "moment of creation". For a decision in a case management system, this is taken care of. For the photo an inspector takes, the meeting notes he types up in the car and the message he receives from a resident, it is not, even though it is just as much government information.

What happens to that information afterwards is a separate challenge: selection, metadata, formats and the transfer, which from 2027 moves from twenty to ten years. See software for sustainable accessibility and DUTO.

How we build this

Here, the observation in the field is the unit. If it is created straight away with the context that makes it findable, sustainable accessibility is not a clean-up project after the fact.

1
Establishing what is created outside

Photos, reports, measurements, messages from residents. At most organisations this is more than expected and is scattered across personal devices.

2
Adding context at the moment of creation

Which case, object or decision does this belong to? Without that link, a photo is a meaningless file in five years' time.

3
Recording in an open, durable format

What needs to be readable in ten years' time must not depend on the app it was made with. That is exactly what the Act means by sustainable accessibility.

4
Passing on to your case or archive system

The app is the point of creation, not the place of storage. What has been recorded moves on to the system where it belongs.

What the app actually does

The app records with the context that will be needed later. Which components you need depends on the work your people do outside.

Images with time, place and case

A photo with only a timestamp is unusable after a few years. When it is taken, we link it to the case, object or location it concerns.

Recording observations in the field

An observation, meeting note or measurement, with fixed fields wherever possible. That keeps it searchable later instead of leaving it as free text.

Metadata required by law

Who recorded it, when, about what and in what capacity. That is what lasting accessibility means in practice, and it cannot be added afterwards.

Working fully offline

In the street, in a basement or on an industrial estate. Recording carries on with the actual timestamp and synchronises afterwards.

Retention period from the start

When a record is created, it is already determined how long it must be kept and whether it needs permanent retention. Assigning a period to ten thousand files after the fact is exactly the project you want to avoid.

Passing it on to your case management system

The app does not store anything itself; what is recorded goes via integrations to your case or archive system, for example through the ZGW APIs.

Who we build for

The work your people do in the field determines what gets created. Four situations.

Supervision and enforcement

Observations, photos and conversations that later support a decision. If these are not attached to the case, the decision can no longer be justified in a few years' time.

Public space management

Reports, inspections and repair work on objects. It is about volume and about whether something can still be found, linked to the right object, in ten years' time.

Social domain and neighbourhood teams

Meeting notes that are both case files and archive records, with a sensitivity that limits retention rather than extending it.

Projects with external parties

Contractors and consultants who supply information that becomes archive-worthy for you. The question is when that information becomes yours and who then manages it.

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 point of origin, not a storage facility. What it records is passed on to the system that manages it, in a format that does not depend on the app.

React Native or native iOS and Android Offline storage with the actual timestamp Images with time, location and case link Fixed fields for observations Metadata according to your own framework Retention period set at creation Open, durable file formats Integration with case management system or e-depot Roles per team and per case Limited offline storage Immutable recording of time and person Remote device management Audit logging Hosting in the EU

Why Appfront

Accessibility from the moment of creation is a design question

We add context at the moment of recording. Adding metadata afterwards to a folder of photos is the clean-up project the law is precisely meant to prevent.

The retention period belongs at the start, not the end

At the moment of creation, we determine what has to happen to a record. That pays off later at transfer, which comes ten years sooner than you are used to.

Keeping things longer is not always better

What must be kept permanently and what must be destroyed are two sides of the same selection. We build both, not just the first.

The app does not store anything itself

What the app records is passed on to your case management system or e-depot. An app acting as an archive is exactly the system dependency the law wants to avoid.

Security and privacy

Information created in the field sits temporarily on a device that goes out on the street with your staff, and in supervision and enforcement it often concerns identifiable people and their homes. We limit offline storage to that day's cases, tie permissions to the user rather than the device, and make sure a lost device can be disconnected remotely.

There is also a tension that grows with the new act. Government information that must be kept permanently will in time become public, and transfer comes ten years earlier than before. What an enforcement officer records about a resident today can therefore end up in an archive service faster than anyone is used to. That means selection at the front end carries more weight: what is worth archiving, what is working material and what should never have been captured at all. We build that choice in at the point of creation instead of postponing it for ten years. How we handle security ourselves is set out in our information security policy; reports from outside go through our coordinated vulnerability disclosure policy.

Frequently asked questions about the Archives Act in the field

On 1 January 2027; the Senate passed the act in May 2026. The shortened transfer period of ten years applies to records created or received after it comes into force. Anything that already exists remains subject to the old twenty-year period, so you will have to deal with both.

If it was taken in the course of your duties, generally yes. That is exactly where organisations are caught out: the material sits on personal devices and in chat groups, even though it falls under the act. Where the line lies is for your archivist to decide; what we build is the place where it does end up correctly.

That information remains findable, readable and interpretable, even after a system change. In the field, it mainly comes down to context: which case does this belong to, who recorded it and when. Without that data, a file can no longer be understood in ten years' time, however well it has been preserved.

No. The app is the point of creation and does not store anything itself; see e-depot software for the preservation facility. Using an app as an archive is precisely the system dependency the act aims to avoid.

The new act requires you to designate an archivist to oversee information management. How you arrange that depends on your size and whether you work with an archive service. It is an organisational question; as far as we are concerned, that person decides what needs to be captured in the field and we build it.

That is the trickiest category, because it arrives through channels that nobody sees as an archive. What works is offering a single entry point that is properly integrated and easier for the employee than a WhatsApp message. Anything that takes more effort than the existing channel will be bypassed.

Yes, that is the starting point. Capture happens locally with the actual timestamp and syncs as soon as there is a connection. On the street, in basements and on industrial estates, that is the normal situation.

That depends on the type of work, how much metadata you want to capture and which case management system it needs to be integrated with. Capture with case linking and context is usually usable quickly; the integration and the selection rules cost more. We give a well-founded estimate after the discovery phase.

Want to know what is being created out in the field right now?

Ask an enforcement officer how many photos from last week are on their own phone and how many of those are linked to a case. That gap is what needs to be sorted out by 2027. We build this as a standalone app and as part of a broader custom app or custom software project.

Edit content