New law from 1 January 2027 Twenty years becomes ten Staying accessible, not just preserved

Custom software for sustainable accessibility and DUTO

Preserving is not the same as keeping accessible. A file that sits on a disk in eight years' time but can no longer be opened, or whose case nobody knows, does not comply. The new Archives Act sharpens that distinction and also halves the period within which you must transfer records.

What changes in 2027

The new Archives Act was passed in May 2026 and comes into force on 1 January 2027. The most concrete change is the transfer period: it goes from twenty to ten years. An important detail for your planning is that the shorter period applies to information created after the Act comes into force; the period for your older records does not change.

In addition, a government body must appoint an archivist. This is not a symbolic role: it gains a position in decisions about what is kept and what is destroyed. In many organisations the role exists on paper, but nobody has the data to carry it out.

The hardest part is sustainable accessibility. For this there is the DUTO framework, which describes what information must meet to remain findable, readable, interpretable and reliable for years to come. It covers metadata, file formats and the context in which something was created. It is not a storage issue but a design issue, and it must be set up at the moment the information is created.

How we build this

Accessibility is created at the point of capture, not at the point of transfer. If you try to fix it afterwards, you lack the context that was there at the time.

1
Setting up the selection list as data

Which category, which retention period, which legal basis. As long as this is a document, nothing can monitor a deadline.

2
Enforcing metadata at creation

Who, when, about what and in which case. These four cannot be reconstructed later, and without them a file is not an archive record but just a file.

3
Monitoring and migrating formats

A format that is perfectly normal today is a problem in ten years. We make visible what is stored in which format and what needs to be converted.

4
Preparing the transfer as a process

Ten years sounds long until it arrives. We build it as an ongoing flow with a check up front, not as a project after the fact.

What the software actually does

The register of categories and their periods underpins everything. What else you need depends on your size and on how many systems produce information.

Selection list as working data

Categories with retention periods and legal bases, applied to what comes in. A selection list in a PDF monitors nothing.

Metadata checked at creation

Missing or incomplete metadata surfaces while it can still be fixed, instead of at the time of transfer.

Formats and their risks in view

What is stored in which format, and which of it can still be opened in ten years. That is the question nobody asks until it can no longer be answered.

Deadlines that run themselves

Retention, destruction and transfer each have their moment. When a period goes from twenty to ten years, your entire planning shifts.

Destruction with justification

What was destroyed, when, on what legal basis and with whose approval. Destruction without that trail is indefensible when you are asked to account for it.

Connecting to your source systems

Information originates in case management systems, document management and email. We pull it in through integrations, because an archive that is filled manually is incomplete by definition.

Who we build for

The challenge differs greatly from one organisation to the next. Four situations.

Municipalities and provinces

Many different processes, many systems and an archivist who has to keep an overview. See also software for municipalities.

Implementing organisations

Large numbers of files with long retention periods. The gain here is mostly automated: periods that expire on their own instead of an annual clear-out.

Organisations with a public task

Depending on the task, you sometimes fall under the Act and sometimes you do not. You want that boundary recorded rather than discussed case by case.

Advisers and archive services

You guide several organisations through the same process. One environment per client saves you from mapping everything out again each time.

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

Selection lists, formats and the accessibility framework are being revised. All of this should be configurable and kept with its history.

If your documents come from Corsa, read more about our Corsa integration.

To deliver metadata in line with MDTO, there is our MDTO integration.

If you want to turn documents from your systems into an open standard, there is our ODF integration.

Node.js / Python / .NET PostgreSQL Selection list with retention periods and legal bases Metadata schema configurable per category Metadata validation on receipt Format inventory with risk indication Migration that preserves the original Period monitoring for retention, destruction and transfer Destruction with approval and justification Integration with case management and document management Transfer file for the archive repository Roles including the archivist Audit logging Hosting in the EU

Why Appfront

Accessibility starts at the point of capture

We validate metadata at the moment information arrives. Afterwards the context is gone, and repairing it becomes guesswork.

Twenty years becomes ten

We build retention periods as data, so a change in the law is a setting rather than a migration project.

A format becomes obsolete silently

We make visible what is stored in which format. It is the only way to plan a migration before it becomes urgent.

The archivist needs data

We build the role with the information that goes with it, rather than a function with no view of what comes in.

Security and privacy

An archive almost by definition contains personal data and often decisions about individuals. Access to it is itself something you have to be able to account for. We set access per category and per role, distinguish viewing from editing, and log every access.

On this subject, the immutability of the archival record is the whole point. A document that can still be changed after archiving is not an archival record but a working file. We therefore store archival records with their original content and metadata, keep a migration to another format alongside the original rather than over it, and record destruction with its legal basis and approval. 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

The new Archives Act was passed on 12 May 2026 and comes into force on 1 January 2027. The most important practical change is the transfer period, which goes from twenty to ten years. Check the precise transitional provisions for your situation, as they determine what applies to your existing records.

No. The ten-year period applies to information created after the Act comes into force. For what is already in the archive, the old period continues to apply. This means you will have two regimes side by side for a while, and that is exactly what you want to record in the system rather than in a work instruction.

A framework for the long-term accessibility of government information. It describes what information must meet to remain findable, readable, interpretable and reliable years later. In practice, that means requirements for metadata, file formats and capturing the context in which the information was created.

No, for two reasons. Keeping records without metadata gives you a mountain of files that nobody can find or make sense of, and that is not accessible. And keeping records for too long is a problem in itself: what should have been destroyed under the selection list should no longer exist. So keeping everything is not a safe choice.

The app is about information created outside the office, by an inspector or a field worker, and about capturing it properly on the spot. This page is about what happens next: selection, accessibility, formats and transfer.

The law requires government bodies to designate an archivist. Whether that is one of your own employees or a shared role, and which powers come with it, depends on your organisation. What is needed in any case is that this person has the data to carry out the role.

Usually yes, and it is the only workable route. Information is created in case systems, document management and email; an archive that is filled manually is by definition incomplete. See also custom document management.

That depends on the number of source systems, the size of your archive and whether a selection list is ready. The selection list with retention-period monitoring is usually quick to put to use and immediately shows where the gaps are; format migration and integrations cost more. We give a well-founded estimate after the discovery phase.

Want to know whether your archive will still be readable in ten years?

Take a file from eight years ago and try to establish which case it belonged to, who created it and whether you can still open it. What you are missing there, you will also be missing at transfer. We build this as a standalone application and as part of a broader custom software project.

Edit content