Service · Software development

Custom permit software development.

Custom permitting, supervision and enforcement (VTH) software for municipalities, regional environmental agencies, provinces, water boards and private certifiers. An application portal for citizens and businesses, a practical back office for your case handlers, and an inspection app that keeps working even without coverage — integrated with your case management system and the national standards.

VTH applicationZGW APIInspection appDSO integration

Permits go beyond the Environment and Planning Act.

VTH stands for Vergunningverlening, Toezicht en Handhaving (permitting, supervision and enforcement) — three processes that follow the same pattern in every municipality, province, regional environmental agency and certification body, but play out differently under each legal framework. The Environment and Planning Act (Omgevingswet) governs the environment plan, the DSO portal and the spatial planning standards, but permit software covers more: alcohol and hospitality licences, event permits, exemptions under the local bylaws (APV), parking permits, operating licences, permits under the Weapons and Ammunition Act, BRL and SCIOS certification schemes — and all the enforcement cases that arise from these processes.

We build custom software for organisations that can't get by with the standard packages (Centric Suite4 Omgeving, Pink Roccade Djoin, Squit XO, Decos JOIN-VTH, Open Wave), or that need to run alongside them for a specific flow the package doesn't support. We connect to the ZGW APIs, IMOW, STAM, IMRO and the DSO-LV, and we work just as readily for a municipality, a regional environmental agency, a province or a private certifier with its own permit system.

In practice, every permit flow comes down to the same core: an applicant submits something, an organisation assesses it against laws and regulations, a decision follows with deadlines and publication obligations, and then supervision comes into play to check that the permit holder complies with the conditions. What differs per permit type is the legal framework, the number of advisory roles, the lead time, the publication obligation and the enforcement powers. Good permit software absorbs that variation without forcing case handlers to adapt their way of working to a rigid package.

Three types of permit software.

Not every client needs the same thing. We distinguish three patterns we see often — frequently in combination, sometimes on their own.

Citizens, businesses and certification clients

Application and citizen portal

The front end where applicants come in. DigiD for citizens, eHerkenning for businesses, an application flow that asks for what is needed and nothing more, status pages, a my-permits overview and integrations with BAG, KVK and the BSN interface. For private certifiers, a separate login with its own account structure. We build the application flow as a dynamic decision tree: based on what the applicant enters on the first screen, the system determines which follow-up questions, attachments and supporting documents are needed, instead of sending everyone through the same long standard form.

DigiD & eHerkenningMy permitsBAG/KVKDocument upload
Back office for case handlers and legal officers

VTH application and case-handling flow

The working environment where case handlers pick up cases, request internal advice, monitor deadlines and record decisions. Role-based: permit officer, legal officer, enforcement officer (BOA), team leader. With workload overviews, advice rounds, mandating and overrun alerts, integrated with your existing case management system via the ZGW APIs. Deadline monitoring is critical here: a permit granted by operation of law because a decision deadline was missed immediately becomes a political issue, so the software flags problems early, escalates automatically and keeps an audit trail of every deadline decision for later WOO requests.

Case assignmentAdvice roundsMandatingDecision-making
Inspection app for supervision and enforcement

Mobile inspection and enforcement app

An app on the phone or tablet of your supervisors, inspectors and enforcement officers (BOAs). Offline mode for checks in the field, photos with GPS coordinates, smart checklists per permit type, and an enforcement flow from finding to warning, penalty payment and administrative enforcement. Everything syncs back to the file in the VTH application. For construction projects, the app uses Building Decree checklists per phase (foundations, shell construction, completion); for events, crowd-safety and emergency-response checks; for hospitality, the mandatory inspection points from the Alcohol and Hospitality Act. Each one is specific to the permit, not a single generic form.

Offline modePhoto & GPSChecklistsEnforcement flow

What you get at the end.

A working permits environment that fits your IT landscape, plus everything you need to manage it yourself and keep it growing with new legislation and regulations.

  • The permits software itselfApplication portal, VTH back office and/or inspection app, running in your own cloud environment (Azure Government, AWS Sovereign Cloud, GCP) or on a shared regional environmental agency platform.
  • Integrations with national standardsZGW APIs, DSO-LV, STAM messages, IMOW, IMRO, BAG, KVK integration, BSN interface, publication flow to officielebekendmakingen.nl and GVOP, depending on what your type of permit requires.
  • Codebase, architecture and runbookFull source code in your own Git environment, an architecture document your IT department can follow, and an operational runbook for incidents and releases.
  • Functional management guideWritten for your application manager: how to add permit types, how to adjust case-handling flows, how to export reports, and how to consult the audit log for WOO requests.
  • Training for key users and supervisorsSessions for your case handlers and legal officers at your office, and separate short training sessions for supervisors who head out with the inspection app.
  • Management and further development contract (optional)Security patches, legislative changes, monitoring, backups and further development for a fixed monthly price, with agreed response times per type of incident.

When custom is the right choice.

Four situations where an off-the-shelf package doesn't fit and we sit down with clients more often. If you recognise yourself in one of these, we'd be happy to talk further.

Municipalities

A permit flow outside the package

Your municipality has a specific permit system (such as a night permit, a mooring policy or an events register) that the standard package doesn't cover. A custom solution alongside it, integrated via ZGW, avoids endless workarounds.

Regional environmental agencies

One platform for multiple competent authorities

Your environmental agency carries out tasks for multiple municipalities and a province, each with its own mandates, templates and publication rules. A multi-organisation platform keeps the data separate without case handlers having to work in ten systems.

Provinces & water authorities

Other legal frameworks

Provinces work with different frameworks to municipalities (Water Act, Nature Conservation Act, extraction permits, indirect discharges). Standard packages are configured for the average municipality. Custom software adapts the statutory deadlines, advisory roles and publication obligations to fit.

Private certifiers

Your own permit or certification scheme

A trade association or certifying body (BRL, SCIOS, SC certification) has no ZGW context but exactly the same processes: application, assessment, audit, withdrawal. A private lightweight VTH (permitting, supervision and enforcement) system is a better fit than a municipal package.

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 →

Standards we work with.

Permit software doesn't run in isolation. We work with the national standards the government chain relies on, and with the interfaces your existing IT landscape requires.

Case-based working

ZGW APIs

The five standardised APIs (Cases, Documents, Catalogues, Decisions, Notifications) that the Dutch government landscape is converging on. We implement them as both consumer and provider, in line with the current GEMMA case-type catalogue from VNG.

Environment and Planning Act

DSO-LV, IMOW & STAM

Message exchange with the Digital System for the Environment and Planning Act (DSO) for environmental permits. We connect to the STAM interfaces for applicable rules and to IMOW for the environmental plan format.

Base registers

BAG, KVK, BRP & BSN

Applicants and properties are retrieved from the right base register, so data doesn't have to be entered twice. BSN interface via Logius, KVK via API-Maatschappij, BAG queries via the Kadaster.

Publication

GVOP & STOP/TPOD

Statutory announcements to officielebekendmakingen.nl and lokaalbekendmakingen.nl in the correct publication format, with automatic generation of deadlines, objection start dates and attachments.

How a permit project runs.

1

Introduction and scope

A conversation in which we learn which permit types you process, which statutory frameworks apply, which systems are being replaced or kept, and how your case handlers work today. We also map out which packages and integrations you already have (often Centric, Pink Roccade or Decos JOIN-VTH plus a case management system of your own), so the new custom layer slots in exactly where it should rather than being placed on top.

2

Process analysis and legal check

We model the application, handling, supervision and enforcement flow for each permit type, identify the statutory deadlines and advisory roles, and check which standards (ZGW, IMOW, STAM, DSO-LV) apply. For municipalities and environmental agencies this often includes a workshop in which we work with your lawyers and case handlers to clarify the division of powers and mandates, which prevents rework during the build phase.

3

Building in sprints

Every sprint delivers a working build that your key users and lawyers can test. We start with the most-used permit flow, then scale out to the less common ones, adding integrations incrementally. We develop the inspection app and back office in parallel: as soon as a permit type can be both applied for and handled, we add the matching inspection checklist straight away so a supervisor can test the entire chain.

4

Pilot, rollout and management

First a pilot with a clearly defined permit type, then a phased rollout across the full scope of tasks, training for case handlers and supervisors, and ongoing maintenance for legislative changes, security and functional expansion. For government organisations this also means periodic penetration tests, DPIA updates and alignment with the VNG information security policy and BIO standards.

Frequently asked questions.

What clients in permit projects usually want to know first.

What exactly is a VTH application?
VTH stands for Vergunningverlening, Toezicht en Handhaving (permitting, supervision and enforcement) — the three core processes carried out by every municipality, environmental agency, province and water board. A VTH application is the back office where your case handlers pick up cases, request advice, monitor deadlines and record decisions, while your inspectors in the field create findings that end up in the same case file. One file per case, three processes revolving around it.
What is the difference from Omgevingswet software?
Our Omgevingswet software focuses specifically on the environmental plan, the DSO portal and the spatial planning standards such as IMOW and STAM. Permitting software is broader: it also covers permits outside the Environment Act, such as events, alcohol and hospitality, parking, APV exemptions and private certifications. In practice there is some overlap, and we often build a single platform that brings both worlds together.
Do you replace Centric, Pink Roccade or Decos JOIN VTH?
For enterprise municipalities with a broad range of responsibilities, we almost never recommend replacing the entire suite — those packages are capable and the migration costs are substantial. What we do is build a custom layer for flows the package doesn't support, run a specific permit regime separately from the main package via a ZGW integration, or deliver a fully custom platform for organisations without an existing package (environmental agencies, smaller municipalities, certification bodies).
How do you integrate with our existing systems via the ZGW API?
The ZGW APIs (Zaken, Documenten, Catalogi, Besluiten, Notificaties) are the standard that lets your case management system, document register, archive and VTH application talk to each other. We implement them as both consumer and provider: our software registers cases and documents in your existing ZGW stack, or exposes its own endpoints for other applications. We align with the current version of the Gemma case type catalogue and with your interface strategy.
How does the inspection app work offline?
Inspection and enforcement checks take place at locations without coverage — a building site behind an embankment, an event in a building with thick concrete walls, or a check in an industrial area. Our inspection app stores all data locally, supports photos with GPS coordinates, checklists per permit type and standard reports, and automatically syncs back to the case file in the VTH application as soon as the inspector is connected again.
Do you also build for building permits and environmental permits?
Yes, that is an important part of what we do for municipalities and environmental agencies. Since the Omgevingswet, building permits fall under the environmental permit for the building activity, with a split between the technical building assessment (municipality) and the spatial assessment (depending on the environmental plan). We build flows that support this split, integrate with the Building Decree assessment, and handle digital collaboration between plan reviewers, structural engineers and enforcement officers.
How do you handle publication to official notices?
Permit decisions with a publication obligation go through an automated flow to officielebekendmakingen.nl, GVOP and the municipal local notices environment. We generate the correct XML in IMOW or STOP/TPOD format, attach the relevant map layers, and handle the views and objections flow, including deadline monitoring and automatic publication of amending decisions.
What determines the cost of a permitting project?
The biggest cost drivers are the number of different permit types in scope, the number of integrations with external systems (case management system, archive, DSO, BAG, KVK, BSN), the type of publication and enforcement flow, and whether a separate inspection app is needed. A project for a single, well-defined permit type with limited integrations is a different conversation from a full multi-organisation VTH platform. We give you a realistic picture of this in the first conversation.
How long does a permit process take?
A pilot with a single permit type and a limited set of integrations can be up and running within a few sprints. A full permitting, supervision and enforcement (VTH) platform for a regional environmental agency with multiple competent authorities, an inspection app and integrations with DSO and a case management system is a project spanning multiple sprints and multiple releases. We always work incrementally: as soon as a permit type runs stably, it goes live while we build the next one.

Talk to us about your permit software.

A no-obligation introductory call of half an hour. We listen to your permit system, your current package and your pain points, and give you direction you can use, even if the outcome is that a custom project is not the smartest choice. Afterwards, we can complement documents and case flows with workflow automation, or embed them in a broader software for municipalities project.

Edit content