Custom BAG mutation management software
Appfront builds software for municipalities that, as source registry holders, maintain the Basic Registry of Addresses and Buildings. Signals from permits, notifications and inspections become mutations; each mutation runs from signal to delivery to the national facility, deadlines are monitored, and feedback from recipients is followed up. So the BAG stays accurate, and the caseworker sees what needs doing today.
What is software for BAG mutation management?
The Basic Registry of Addresses and Buildings (BAG) contains all addresses, residential 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. Every new home, renovation, merger or demolition leads to one or more mutations, which must appear in the BAG within the deadlines set by the rules.
In many municipalities, signals come in from several directions: an issued environmental permit, a notice of completion, an on-site inspection, a report from a customer who has spotted an error. These signals sit in emails, spreadsheets and the permit system. The BAG officer keeps track of what is still open, but a deadline is easily missed, and during an audit it is hard to show how a change was made.
We build custom software because change management has to fit your municipality: which permit system you use, which BAG software feeds the national facility, how you receive signals and how your work is divided. The rules and deadlines for the BAG are set out in law and the regulations that follow from it; what that means 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 through to delivery to the national facility.
Deadlines monitored
A deadline for each mutation, with an overview of what is due today and this week.
Reports of errors followed up
Reports of errors from users of the data about the object, with investigation, decision and resolution.
How we build your BAG mutation management software
We start with your maintenance process: where signals come from, how a mutation progresses, and where things currently go wrong.
Your signals, division of work, deadlines, BAG software and permit system.
Signals from permits and notifications as mutations with a status and a deadline.
Checks before delivery, and the handover to the BAG software or the national facility.
Handling of reports of errors, reporting on backlog and quality, and ongoing management afterwards.
What BAG mutation management software actually does
The components below come up in almost every municipality. Which ones you need depends on how your setup is organised.
Alerts
Signals from permits, notifications and checks in one place.
Mutations
Mutations per building, residential unit and address, with status.
Deadlines
Deadline monitoring with an overview of what is due today.
Source documents
Permit, drawing and photographs attached to the mutation.
Feedback
Reports of errors from users, with investigation and decision.
Reporting
Backlogs, processing times and quality for the audit.
Who we build BAG mutation management software for
The software is intended for municipalities that maintain the BAG as the data holder.
Large municipalities
A high volume of mutations each week. Division of work and deadlines are central.
Small municipalities
One or two staff members. An overview of what is still open matters most.
Regional cooperation
BAG for multiple municipalities. Separation by municipality is what's needed.
Geo-information departments
BAG alongside other registers. Audit reporting is central.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.
Explore OneDayBuild →Technology and integrations
This page is about maintaining the BAG as a municipality. To read BAG data in your own software, see our page on a BAG API integration; for permit processing, our page on VTH software; and for municipalities in general, our page on software for municipalities. You can read about our way of working at getting software built.
If you want the BGT current in your management system, with only the changes, see our page on a BGT integration.
Why Appfront for your BAG mutation management software?
A mutation that appears in the BAG too late affects everyone who uses it, from property valuation to the emergency services. We build around that: every signal becomes a mutation, deadlines are visible, and reports of errors do not get left sitting.
No missed deadlines
What is due today is at the top.
Traceable
For each mutation, the signal, the documents and who did what.
Ready for the audit
Backlog and quality can be shown at any time.
Security and privacy in BAG mutation management software
The software holds data about buildings, addresses and permits, and sometimes about owners or residents. Access is set up by 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 back-ups and two-factor sign-in.
Frequently asked questions about BAG mutation management software
Questions municipalities ask before starting.
It gathers signals from permits, notifications and checks, turns them into mutations with a status and a deadline, monitors those deadlines, checks before delivery, and follows up reports of errors from users.
No. The BAG software delivers the changes to the national facility. This software handles the work around it: signals, work allocation, deadlines and reports from customers. It integrates with your BAG software, so nobody has to retype anything.
The rules for the BAG set out deadlines for processing changes. The software monitors the deadlines you record and shows which mutations are at risk of being late. What applies to your way of working is something you decide together with your quality officer.
Yes, provided that system has an interface or export. An issued permit or a notice of completion becomes a signal against the correct object.
A return from a customer is attached to the object, along with the report, the investigation, the decision and the resolution. This makes it clear which returns are still open, how long they have been open, and who is handling 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 processing times can be viewed in an overview at any time.
Check this first. Some BAG software includes a work queue and deadline tracking, and that is enough if your way of working fits within it. Custom software makes sense when signals come from several systems, or when you serve several municipalities.
Every mutation on time, from signal to delivery?
Tell us how many mutations you process, where the signals come from and which systems you work with. We will show you what the work queue, the deadlines and the returns look like.