Web development · Permits & government

Custom permit registration software.

One coherent system for the entire permitting process: application, assessment, issuance, publication and objection. It includes an application portal for citizens and businesses, an assessment flow for case officers, integrations with the Digitaal Stelsel Omgevingswet (DSO, the national Environment Act platform) and the national base registries, and publication on DROP and Bekendmakingen.nl. It is built on an open architecture that keeps pace with the Environment Act, the General Administrative Law Act (Awb) and the Building Quality Assurance Act (Wkb).

Target groupMunicipalities · provinces · water boards · environmental agencies
TypeApplication · assessment · issuance · publication
StandardsDSO · STAM · STTR · NLX
ComplianceEnvironment Act · Awb · GDPR · BIO · WCAG 2.1 AA
IntegrationsDigiD · eHerkenning · BAG · BRP · DROP
OwnershipCode owned by your organisation

What is a permit register?

A permit register is the system in which a government organisation records and supports every step of a permit: from the application by a citizen or business, through the substantive assessment by one or more disciplines, to the decision and issuance of the permit, the publication of the decision and, where the decisions call for it, the handling of views, objections and appeals. It is not an accounting afterthought, but the working heart of permitting.

We design and build these systems to your requirements. Not as a closed package where every new type of permit becomes an extra project, and not as a standalone form builder that leads nowhere. We build a platform in which the application portal for citizens and businesses, the assessment flow for case officers, the integration with the Digitaal Stelsel Omgevingswet and publication to DROP and Bekendmakingen.nl work together as one coherent whole. Each type of permit has its own process variant, but all within the same foundation.

Our background is in custom software for municipalities and in broad permitting software. For us, a permit register is not a separate module, but the web layer on top of a serious process architecture. The system suits the full spectrum: Environment Act permits (environmental permit, BOPA, overlap with Wkb), municipal APV permits (events, alcohol and hospitality, taxis, tree felling, market pitches, terraces, exemptions, parking), and sector-specific domains at enforcement bodies such as NVWA, ProRail, safety regions and environmental agencies. One foundation, with different process variants on top.

DSO-connected
The Digitaal Stelsel Omgevingswet as an integral part, compliant with STAM/STTR and suitable for applicable rules
Awb & GDPR
The General Administrative Law Act and privacy as design requirements: deadline monitoring, reasoning and data subject rights are built into the system
WCAG 2.1 AA
An accessible application portal in line with the Digital Accessibility Decree for government, independently tested
Code ownership
Repository and documentation held by your organisation: no package lock-in, no renegotiation for every new type of permit

When does a new permit register make sense?

01
Environment Act

Your current Wabo system won't survive the Environment Act

The Environment Act coming into force has pushed many old Wabo flows to their limits. Applicable rules in STTR, permit checks via the DSO, BOPA procedures, overlap with Wkb notifications: the existing system manages the bare minimum, but never comfortably. A newly built register lets all the new paths run in parallel with the remaining Wabo decisions. We work from the same principles as our broader permitting software practice.

02
Package lock-in

The suite vendor turns every change into extra work

A large part of the public sector is locked into a suite where every new permit type, field or integration means a separate quote. If the licence is about to expire or the annual indexation is getting out of hand, this is the natural moment to move to an open architecture in which your organisation keeps control of maintenance.

03
Lead times

Assessment stalls on manual handovers and email

Applications arrive through a form, but the substantive assessment takes place in email, shared folders and standalone Excel trackers. In practice, multidisciplinary coordination runs on copies of documents. Awb deadlines are met because someone remembers them, not because the system drives them. A well-configured workflow layer takes that manual work away.

04
Publication

Public notices are out of sync with decisions

Publication on DROP and Bekendmakingen.nl happens in a separate application or as a manual step. Deadlines for consultation, views and objections are tracked in a third tool. The result: decisions whose official publication can no longer be neatly reconstructed afterwards. An integrated register publishes directly from the decision and keeps the legal audit trail in a single system.

What sets our permit register apart.

Difference 01

One system, multiple permit types

The foundation is generic: application, admissibility check, assessment, decision, issuing, publication, objection. Process variants — environmental permit, event, alcohol, taxi, tree felling, exemption, parking — are configured on top of that foundation. One system to manage, one set of audit logs, and new permit types become a configuration project rather than a new procurement process.

Difference 02

Open on DSO, NLX and base registries

We connect directly to the Digital System for the Environment and Planning Act (STAM for applications, STTR for applicable rules), to NLX for inter-organisation integrations, and to Haalcentraal APIs for BAG, BRP, BRO and BGT. No shadow architecture — just the standards the sector itself has agreed on.

Difference 03

Ownership stays with the government

The code lives in a repository belonging to your organisation, documentation is in Dutch, and data flows are transparent. If you change supplier, someone else can take over without data or logic being held hostage. For a permit register this is not a marketing argument but a basic requirement: permits are decisions with legal effect, and their continuity should rest with you.

The components of the system.

In practice, a permit register is a collection of connected modules. We build them as a single platform, with a dedicated UX for each user group — citizens, businesses, case handlers, permit officers, lawyers, objection committees. Components can be replaced individually without rebuilding the whole.

Citizen application portal

A guided journey with DigiD authentication, fields pre-filled from BRP and BAG, conditional logic, saving in progress and attachment uploads. With a live permit check via DSO where applicable.

Business application portal

eHerkenning with an authorisation structure, pre-filled from the KvK, support for advisers and authorised representatives, and a dedicated dashboard with ongoing cases per organisation.

Admissibility check

Automatic checks for completeness, mandatory attachments and consistency with other pending applications — with a simple route for the applicant to supply missing documents.

Multi-discipline assessment flow

Parallel routing to building physics, fire safety, spatial planning, environment, heritage and external advisers such as the environmental agency and the Safety Region. Each discipline returns a reasoned opinion into the case file.

Awb deadline monitoring

The statutory deadlines for the regular and extended procedures are built into the system. Extensions, suspensions and the deemed-approval period are actively displayed.

Decision-making and issuing

Template-driven decisions, reasoning that evolves with the assessment, a mandate and signature route, and delivery via MijnOverheid Berichtenbox or post.

DROP & Bekendmakingen.nl publication

Immediate publication of decisions and draft decisions with the correct metadata, a map layer for environmental decisions and the statutory public inspection period, all derived from the decision itself rather than handled as an afterthought.

Views, objections & appeals

A consultation portal for views, an objection route linked to the case file, and a referral route to the administrative court, including a full export of the case file.

Which organisations do we build for?

Permitting is broad: municipal service desks, provincial exemptions, sector-specific implementing bodies and joint ventures, each with its own processes, all within the same framework of fundamental rights.

Municipalities

Municipalities

The full breadth of the municipal permit desk on one platform: environmental permits, events, alcohol/hospitality, tree felling, terraces, street trading, parking and exemptions under local bylaws (APV). Processes differ per type, with shared auditing and publication.

Provinces

Provinces

Permits for large-scale projects, exemptions, infrastructure, decisions by the provincial executive. Connection to the Provinciaal Blad (provincial gazette) and specific integrations for provincial supervisory actions.

Water boards

Water boards

Water permits, discharge decisions and exemptions under the Keur (water board bylaws). Its own General Administrative Law Act (Awb) deadlines, its own publication channel (Waterschapsblad) and a specific enforcement route.

Regional environmental agencies

Environmental services / RUDs

Assessment on behalf of multiple competent authorities. Multi-tenant integration via NLX, separation of authority and execution, and handover points that keep legal responsibility intact.

Safety regions

Safety regions & NVWA

Advice and own permits for fire and event safety, food safety and operating licences. Often combined with a municipal permit that carries conditions.

Sector-specific

ProRail, environment, taxi

Sector-specific permitting domains with their own regulations (Railways Act, Environmental Management Act, Passenger Transport Act). Our foundation fits these domains, provided the specialised process is configured on top.

Compliance: the framework we work within.

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.

Our guiding principles.

Principle 01

Accessible application portal

WCAG 2.1 AA built into every component of the portal, not added as a testing round afterwards. Keyboard navigation, screen reader support, contrast, reading level and read-aloud friendliness are part of the delivery — independently tested before the portal goes live. Applying for a permit is a legal act; everyone must be able to do it.

Principle 02

Process-driven assessment

The assessment flow is neither a free-form workspace nor a rigid form, but a process that guides the case officer through the right steps without limiting their room for professional judgement. Mandatory checkboxes only where the General Administrative Law Act (Awb) or the administrative-law framework requires them — otherwise support, not coercion.

Principle 03

Explainability and audit trail

Every change to a case file can be reconstructed: who, when, on what basis. For an objections committee and ultimately the administrative court, that is not a luxury but a requirement. The full case-file export is ready as a single consolidated PDF bundle.

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 →

How a project works in practice.

We start with an intake. Around the table you will typically find the head of Permits, a representative from the administrative-law or legal quality department, a delegate from the CIO office or Information Services, and — depending on the scope — the Data Protection Officer and the CISO. For projects that connect directly to the DSO, a DSO coordinator is often there too. The aim: which problem is most urgent right now, and what constraints apply to architecture, hosting, maintenance and integrations.

A discovery phase follows. Externally: which permit types dominate in volume, where applicants get stuck, which rounds of additional information come up often. Internally: which registries, which discipline desks, which integrations already exist, how legal quality is currently handled, which publication steps are manual work. End result: a functional and architectural design that we discuss with you — and with your legal audit role — before we start building in earnest.

The build phase runs iteratively in sprints. Each sprint delivers something concrete: a working application flow for one permit type, a complete assessment flow, a DSO integration, a publication route to DROP. The code sits in a repository owned by your organisation, with an acceptance environment for the department and lawyers, and a production environment that we only open once the accessibility and security audits have been approved.

Before go-live we have an independent WCAG audit carried out and — depending on scope and BIO impact — a pentest and/or DPIA update. The report is delivered to you and serves as the basis for the accessibility statement and the in-control statement. For projects with greater security impact, see our approach to ISO 27001-compliant software. After go-live we either handle maintenance or hand over to your IT department. On handover we deliver full documentation, a runbook and a repeatable deployment pipeline. The code is yours, and stays yours.

Integrations we build as standard.

Integration 01

DigiD & eHerkenning

Authentication for citizens and businesses, with authorisations for representatives and advisers. We also guide the Logius connection process, including the associated security assessments.

Integration 02

Digital System for the Environment and Planning Act (DSO)

Full DSO integration: STAM for incoming applications, STTR for publishing applicable rules, and OZON options where relevant. Suitable for receiving DSO applications and passing decisions on to the system.

Integration 03

Basic registrations via Haalcentraal

BAG, BRP, BRK, BGT, BRO. Pre-filled address and cadastral data in the application, automatic validation, and consistent data across the application portal, assessment file and case management system.

Integration 04

NLX for inter-organisation exchange

NLX as the routing standard for exchanges between the municipality, environmental agency, province, safety region and other chain partners. An auditable, logged route for advice and co-decisions.

Integration 05

Case management system & DMS

Routing of applications to the right case type, status feedback, and document archiving in line with Archive Act requirements. We integrate via standard APIs and respect the separation between the primary process and the archive.

Integration 06

DROP & Bekendmakingen.nl

Immediate publication of draft and final decisions, with the right metadata, a map layer for environmental decisions, inspection periods and archiving, all derived from the decision itself.

Per permit type: how it works out in practice.

The base platform is generic, but each permit type has its own process questions that shape the UX and the integrations.

Environmental permit & BOPA — The regular route under the Environment Act, with DSO integration, applicable rules, and overlap with the Wkb (Building Quality Assurance Act) for building activities in consequence class 1. The BOPA route for out-of-plan activities has its own procedure; the registration runs both side by side and ensures that the right advice from the right discipline arrives on time.

Events, alcohol & operating licences — Event permits are almost always multidisciplinary (municipality, police, fire brigade/safety region, public health service); our flow supports issuing advice requests in parallel and template routes for recurring events. Alcohol Act and operating licences involve a BIBOB screening with its own document set and retention periods.

Taxi, hairdresser, terrace, market pitch, local bylaw exemptions — The typical local bylaw (APV) categories that are high in volume and visible in turnaround time. There are gains to be made here with a good application portal, automatic admissibility checks and template decisions, without designing away the legal room for custom handling.

Parking permits — Often a front end of their own, linked to the parking rights register and the permit-zone layer. Real-time checks by enforcement officers (BOAs) through a separate enforcement app on the same register. This is where our workflow layer comes in handy, in a variant of its own.

Water permits (water authority) — Their own General Administrative Law Act (Awb) deadlines, their own publication channel (Waterschapsblad), and their own bylaw (Keur) powers. Often combined with an environmental permit from the municipality, which makes coordination at file level crucial.

Anti-lock-in: how we prevent vendor dependency.

In the permits market, vendor lock-in is a particular pain point: a suite vendor raising the licence fee every year without a realistic way to migrate. A package from which files can only be retrieved through paid exports. A DSO connector that only works with other components from the same vendor. It is not malice; it is simply how things work commercially when the architecture is not open.

Our counter-strategy is deliberate and simple: no pre-selected vendor stack. We build on an open architecture with code ownership on your side, using proven open-source building blocks as the foundation and domain-specific logic on top. For every integration with a commercial package we use standard APIs rather than vendor-specific interfaces, so replacing such a package does not mean rebuilding your registration system. The code lives in your repository, and documentation is in Dutch. For the broader context, see also our municipal website practice and our wider permit software offering.

Frequently asked questions.

Do you work on top of an existing permit package, or entirely from scratch?
Neither as dogma. We work on an open architecture built on proven open-source components — a process engine for the workflow, a forms engine for the application flow, a DSO integration layer — and build domain-specific logic around them. We don't pre-select a single commercial suite, and we don't indulge in "everything from scratch" romanticism where public funds are spent unnecessarily. We choose the building blocks based on your existing landscape and what your functional management team can comfortably maintain.
Can you integrate with the DSO?
Yes, that is a central part of what we deliver. STAM for receiving applications via the DSO, STTR for publishing applicable rules, and OZON choices where relevant. For a competent authority that wants to receive DSO applications and also handle its own applications through a municipal counter, we support both routes — with one shared case-file layer behind them.
Does this work for an environmental service that assesses applications on behalf of several municipalities?
Yes. We build multi-tenant where it makes sense — a single platform serving several competent authorities, with a clear separation of authority and execution, mandate arrangements and handover moments that keep legal responsibility intact. NLX provides the standardised inter-organisation routing.
How does the system support the overlap with the Wkb?
For building activities in consequence class 1, the technical assessment under the Quality Assurance for Construction Act (Wkb) is carried out by an independent quality assurer, while the spatial part remains with the competent authority. The registration lets those tracks run in parallel: spatial assessment in your flow, and Wkb notifications (start notification, completion notification, competent authority file) as a separate intake linked to the case file.
Can we bring our current case files and history with us?
Migration runs as a separate track alongside the build: inventory, clean-up, automated conversion where possible and manual curation where necessary. We pay attention to archiving requirements under the Archive Act, to the legal continuity of open case files and to continuous deadline monitoring. Ongoing objection and appeal files get extra attention.
How does this fit our GEMMA architecture?
For us, GEMMA is a guiding principle, not decoration. We build on the building blocks your organisation already recognises: case-oriented working, NORA principles, VNG standards. NLX for integrations between organisations, Haalcentraal APIs for base registrations. No shadow architecture — just the standards the sector itself has agreed on.
What if we want to use AI — a chatbot, a classifier, preliminary assessments?
Then we treat it as a separate decision chain. For every AI function, first the risk classification under the AI Act, then assessment against the Algorithm Register, then a DPIA update, and only then implementation. Many applications around permitting fall into the high-risk category — a classifier on incoming applications that determines the handling route is a decision with legal effect. For exploratory AI on preliminary assessments a smaller scope is possible, provided the final judgement stays with the civil servant. See also our AI development practice.
Do you guarantee the accessibility statement for the application portal?
We deliver a portal whose building blocks have been tested against WCAG 2.1 AA by an independent audit at handover. The accessibility statement itself is your organisation's responsibility; we provide the supporting evidence. Editorial content (form help texts, objection explanations) remains the bottleneck your own people have to manage — we provide instructions and checklist components for that.
What about the archiving obligation?
Permits are decisions of archival value with long retention periods, and the Archiefwet (Dutch Archives Act) sets requirements for durability, findability and authenticity. Our register supports e-Depot integrations, archive statuses and metadata requirements, and archived case files remain fully reconstructable, including process history and audit log. For archive transfers to a regional historical centre or the Nationaal Archief, we handle the transformation to the correct ingest format.
Can our own developers get involved?
Gladly. For organisations with their own development team or an ICT partnership, that is a healthy way to safeguard knowledge. We work openly, with code reviews your developers can take part in, and with guided handover so your people are comfortable with the platform. For smaller organisations without their own team, we handle maintenance ourselves or hand over to a third party.
What if we want to switch to another supplier later?
It should be possible, and that is what we work towards. The code sits in your repository, documentation is complete, the architecture follows open standards, and case data can be exported in common formats. If you switch, we provide a clean handover: no withholding of case files, no artificial barriers, no migration fee. For a permit register this is a matter of principle: permits are decisions with legal effect, and their continued availability should remain under your own control.
What is the difference with your broader permit software practice?
The permit software practice is broader: back-office systems, integration platforms for supervision and enforcement, and policy applications. The register this page is about is the central operational layer within it, the system the entire process runs through.

Talk to us about your permit register.

A half-hour introduction in which we go through where you stand now: an outdated Wabo system that won't make it through the Omgevingswet (Environment and Planning Act), a suite vendor where every change becomes extra work, review lead times that put the Awb (General Administrative Law Act) deadlines under pressure, or the wish to finally get objections and publication into a single system. Afterwards we send a concrete proposal with scope, architecture and sprint planning.

Reply within 1 working day
No-obligation conversation
Westerdoksdijk 599, Amsterdam
FV
Fabian van Dijk · Business developer
Share LinkedIn Email

Edit content