A permit register operates within a denser regulatory framework than almost any other government application. A permit is a decision with legal effect, and the process leading to it is regulated in detail. That determines how the system looks on the inside.
The Environment and Planning Act (Omgevingswet) underpins the vast majority of physical living environment permits. It brings its own procedural and technical obligations: connection to the Digital System of the Environment and Planning Act, use of applicable rules in STTR, submission via STAM, alignment with the environmental plan, and the out-of-plan environmental plan activity (BOPA) as a specific route. On top of that sits the Building Quality Assurance Act (Wkb): for building activities in consequence class 1, the technical assessment runs through an independent quality assurer, while the spatial part remains with the competent authority. Our register runs those two paths in parallel.
The General Administrative Law Act (Awb) governs the entire process: admissibility, the duty to give reasons, the duty to hear, regular and extended procedures, decision deadlines, grounds for suspension and extension, and permits by operation of law where not excluded. Deadline monitoring is built into the system itself. The GDPR and UAVG (the Dutch GDPR Implementation Act) set requirements for purpose limitation, data minimisation and data subject rights. We actively document which data is held where, on what legal basis, and how access or correction requests are handled technically.
The Baseline Information Security Government (BIO) sets requirements for logging, authorisation management and incident handling. In a permit register, the audit log is literally part of the legal process: who gave which advice, signed which decision or granted which extension, and when. The Digital Government Act (Wet digitale overheid) and the Digital Accessibility Decree for Government (Besluit digitale toegankelijkheid overheid) require WCAG 2.1 AA compliance, a design requirement that touches every component and is independently audited before go-live.
The AI Act applies to the system as soon as you deploy AI components — a classifier on incoming applications, a preliminary-review AI on building plans. AI that supports decisions about people's rights almost always falls under high risk. We treat every AI function as a separate decision chain with its own DPIA, its own entry in the Algorithm Register and its own evaluation round. See also our broader AI development practice. Finally, we work with the standards of VNG, Geonovum and Logius: GEMMA, Common Ground, NLX for inter-organisation integrations, and Haalcentraal for querying base registries.