Every mutation from signal to delivery Deadlines monitored Feedback reports followed up

Custom BAG mutation management software

Appfront builds software for municipalities that maintain the Basic Registration of Addresses and Buildings (BAG) as source holders. Signals from permits, notifications and inspections become mutations, every mutation runs from signal to delivery to the national facility, deadlines are monitored, and feedback reports from data users are followed up. So the BAG is correct, and the case officer sees what needs doing today.

What is BAG mutation management software?

The Basic Registration of Addresses and Buildings, BAG, contains all addresses, accommodation units and buildings in the Netherlands. Municipalities are source holders: they record changes and deliver them to the national facility, which is managed by the Kadaster (the Dutch land registry). Every new home, renovation, merger or demolition leads to one or more mutations, and these must be in the BAG within the deadlines set by the rules.

In many municipalities, signals come from different directions: a granted environmental permit, a notification of completion, an on-site inspection, a feedback report from a user who spots an error. Those signals end up in emails, spreadsheets and the permit system. The BAG officer keeps track of what is outstanding, but a deadline is easily missed, and during an audit it is hard to show how a mutation came about.

We build custom software because mutation management has to fit your municipality: which permit system you use, which BAG software supplies the national facility, how you receive signals and how work is allocated. The rules and deadlines for the BAG are set out in the law and the accompanying regulations; what follows from them for your way of working is for you and your quality officer to decide.

From signal to delivery

Every signal becomes a mutation with a status, from receipt to delivery to the national facility.

Deadlines monitored

The deadline for each mutation, with an overview of what is due today and this week.

Feedback reports followed up

Feedback reports from users, linked to the object, with investigation, decision and resolution.

How we build your BAG mutation management software

We start with how you maintain the BAG: where signals come from, how a mutation progresses, and where things currently go wrong.

1
Mapping your maintenance process

Your signals, work allocation, deadlines, BAG software and permit system.

2
Signals and mutations

Signals from permits and notifications as mutations with a status and deadline.

3
Checks and delivery

Checks before delivery, and the handover to the BAG software or the national facility.

4
Feedback and maintenance

Handling of feedback reports, reporting on backlog and quality, and ongoing maintenance afterwards.

What BAG mutation management software actually does

The components below appear at almost every municipality. Which ones you need depends on your set-up.

Alerts

Signals from permits, notifications and inspections in one place.

Mutations

Mutations per building, address object and address, with status.

Deadlines

Deadline monitoring with an overview of what is due today.

Source documents

Permit, drawing and photos attached to the mutation.

Feedback reports

Feedback reports from users with investigation and decision.

Reporting

Backlogs, turnaround time and quality for the audit.

Who we build BAG mutation management software for

The software is intended for municipalities that maintain the BAG as a source holder.

Large municipalities

Many mutations per week. Work allocation and deadlines are at the core.

Small municipalities

One or two staff members. An overview of what is outstanding matters most.

Regional collaboration

BAG for multiple municipalities. Separation per municipality is what is needed.

Geo-information departments

BAG alongside other registers. Reporting for the audit is the core.

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

This page is about municipalities maintaining the BAG. For reading BAG data in your own software, see our page on a BAG API integration; for permitting, our page on VTH software; and for municipalities in general, our page on software for municipalities. You can read about our approach on building software.

If you want the BGT kept up to date in your management system, with only the changes, see our page on a BGT integration.

Signals Mutations per object Workflow and status Deadline monitoring Source documents Checks before delivery Feedback reports Integration with the permit system Integration with BAG software Reporting for the audit

Why choose Appfront for your BAG mutation management software?

A mutation that reaches the BAG too late affects everyone who uses the BAG, from property valuation to the emergency services. That is what we build on: every signal becomes a mutation, deadlines are visible, and feedback reports don't get left lying around.

No missed deadlines

What is due today is at the top.

Traceable

For each mutation: the signal, the documents and who did what.

Audit-ready

Backlog and quality can be shown at any moment.

Security and privacy in BAG mutation management software

The software holds data on buildings, addresses and permits, and sometimes on owners or residents. Access is set up per role, and every change to a mutation is logged.

The software runs in a European data centre or in your own environment, with encrypted storage, daily backups and two-factor login.

Frequently asked questions about BAG mutation management software

Questions municipalities ask before getting started.

It collects signals from permits, notifications and inspections, turns them into mutations with a status and a deadline, monitors those deadlines, runs checks before delivery, and follows up on feedback reports from data users.

No. The BAG software delivers the mutations to the national facility. This software handles the work beforehand: signals, work allocation, deadlines and feedback reports. It integrates with your BAG software, so nobody has to retype anything.

The BAG rules set deadlines for processing changes. The software monitors the deadlines you define and shows which mutations are at risk of being late. What applies to your way of working is something you determine with your quality officer.

Yes, provided that system has an interface or an export. A granted permit or a notification of completion becomes a signal on the right object.

A feedback report from a data user is attached to the object, along with the report, the investigation, the decision and the resolution. This makes it clear which feedback reports are still open, how long they have been open, and who is working on them.

Yes. For each mutation you can see which signal it came from, which documents belong to it, who did what and when. Backlogs and turnaround times are visible in an overview at any moment.

Check that first. Some BAG software has a work queue and deadline monitoring, and that is enough if your way of working fits it. Custom software makes sense if signals come from multiple systems, or if you serve multiple municipalities.

Every mutation on time, from signal to delivery?

Tell us how many mutations you process, where your signals come from and which systems you work with. We will show you what the work queue, the deadlines and the feedback reports look like.

Edit content