Service · Software development

Custom permit software development.

Custom VTH software for municipalities, environmental services, provinces, water boards and private certification bodies. An application portal for citizens and businesses, a practical back office for your case handlers, and an inspection app that keeps working offline, connected to your case management system and national standards.

VTH applicationZGW APIInspection appDSO integration

Permits cover more than the Environment and Planning Act.

VTH stands for Vergunningverlening (permit granting), Toezicht (supervision) and Handhaving (enforcement) — three processes that follow the same pattern in every municipality, province, environmental service and certification body, but play out differently under each legal framework. The Environment and Planning Act (Omgevingswet) governs the environmental plan, the DSO portal and the RO standards, but permit software covers much more: alcohol and hospitality licences, event permits, APV exemptions, parking permits, operating licences, permits under the Weapons and Ammunition Act, BRL and SCIOS certification processes — and all enforcement files arising 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, an environmental service, a province or a private certification body with its own permit scheme.

In practice, every permit process 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 steps in to check whether the permit holder complies with the conditions. What differs per permit type is the legal framework, the number of advisory roles, the processing time, the publication requirement and the enforcement powers. Good permit software accommodates 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 that we see often, frequently in combination and sometimes on their own.

Citizens, businesses and certification clients

Application and citizen portal

The front end where applicants enter. DigiD for citizens, eHerkenning for businesses, an application flow that asks only what is needed, status pages, a my-permits overview, and integration with the BAG, KVK and the BSN interface. For private certification bodies, 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, rather than putting everyone through the same long standard form.

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

VTH application and case workflow

The working environment in which case handlers take on cases, set internal advice requests, monitor deadlines and record decisions. Role-based: permit officer, legal adviser, enforcement officer, team leader. With workload overviews, advisory rounds, delegation and overrun alerts, connected to your existing case management system via the ZGW APIs. Deadline monitoring is critical here: a permit granted by operation of law because a statutory decision period was missed is immediately a political issue, so the software flags early, escalates automatically and keeps an audit trail of every deadline decision for later Public Records Act (WOO) requests.

Case assignmentAdvisory roundsDelegationDecision-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. Offline mode for field checks, photos with GPS coordinates, smart checklists per permit type, and an enforcement flow from observation through warning, penalty payment and administrative enforcement. Everything syncs back to the file in the VTH application. For construction projects, the app works with Building Decree checklists per phase (foundations, structural work, handover); for events, with crowd safety and emergency response checks; for hospitality, with the mandatory control points under the Alcohol and Catering Act. Each is specific to the permit type, not one generic form.

Offline modePhoto & GPSChecklistsEnforcement flow

What you get at the end.

A working permit environment that fits into your IT landscape, plus everything needed to manage it yourself and let it evolve with new laws and regulations.

  • The permit 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 service 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 understand, and an operational runbook for incidents and releases.
  • Functional administration manualWritten for your application administrator: how to add permit types, how to adjust case-handling flows, how to export reports, and how to consult the audit log for Dutch Open Government Act (WOO) requests.
  • Training for key users and supervisorsSessions for your case handlers and legal staff in the office, and separate short training courses for supervisors who go out with the inspection app.
  • Management and further development contract (optional)Security patches, legal amendments, monitoring, backups and further development for a fixed monthly fee, with agreed response times for each type of incident.

When custom is the right choice.

Four situations in which a standard package does not fit and we are more often at the table together. If you recognise yourself in one of these, we would be happy to talk further.

Municipalities

A permit flow outside the package

Your municipality has a specific permit regime (think of a night-time permit, a moorings policy or an events register) that the standard package does not cover. Custom software alongside it, connected via ZGW, avoids endless workarounds.

Environmental services

One platform for multiple competent authorities

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

Provinces & water boards

Other legal frameworks

Provinces work within different frameworks from municipalities (Water Act, Nature Conservation Act, groundwater extraction, indirect discharges). Standard packages are built around the average municipality. Custom software makes statutory deadlines, advisory roles and publication obligations fit.

Private certification bodies

Your own permit or certification scheme

A trade association or certification body (BRL, SCIOS, SC certification) has no ZGW context but does have exactly the same processes: application, assessment, audit, withdrawal. A private licensing-light solution suits better than a municipal package.

Not yet sure about a large project?

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 →

Standards we work with.

Permit software does not 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) to which the Dutch government landscape is aligned. We implement both as a consumer and as a provider, in line with VNG's current Gemma case type catalogue.

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 registries

BAG, KVK, BRP & BSN

Retrieve applicants and objects from the correct base register so data does not need to be re-entered. BSN interface via Logius, KVK via API-Maatschappij, BAG queries via Kadaster.

Publication

GVOP & STOP/TPOD

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

How a permit project runs.

1

Introduction and scope

A conversation in which we understand which permit types you process, which legal frameworks apply, which systems will be replaced or retained, and how your case handlers work today. We also map which packages and integrations you already have (often Centric, Pink Roccade or Decos JOIN-VTH plus an in-house case system) so the new custom layer fits precisely alongside them rather than over them.

2

Process analysis and legal check

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

3

Building in sprints

A working build every sprint that your key users and legal advisers can test. We start with the most-used permit flow, then scale out to the less common ones, and build integrations incrementally. We develop the inspection app and back office in parallel: as soon as a permit type can be both applied for and processed, we immediately add the corresponding inspection checklist so an inspector 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 range of tasks, training for case handlers and inspectors, 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: the three core processes that every municipality, environmental service, province and water board carries out. A VTH application is the back-office system in which your case handlers pick up cases, issue advice requests, track deadlines and record decisions, while your inspectors in the field create findings that end up in the same file. One file per case, with three processes running around it.
How does it differ 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. Permit software is broader: it also covers non-environmental permits such as events, alcohol and catering licences, parking, local bye-law exemptions and private certifications. In practice there is overlap, and we often build a single platform in which both worlds come together.
Do you replace Centric, Pink Roccade or Decos JOIN-VTH?
For enterprise municipalities with a broad remit, we almost never recommend replacing the entire suite. Those packages can do a lot, and migration costs are significant. What we do instead is build a custom layer for flows the package doesn't support, run a specific permitting regime alongside the main package via a ZGW integration, or deliver a fully custom platform for organisations without an existing package (environmental services, 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 through which your case management system, document register, archive and VTH application communicate. We implement 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 integration strategy.
How does the inspection app work offline?
Inspection and enforcement checks take place at locations without coverage — a construction 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 synchronises back to the file in the VTH application once the inspector regains connectivity.
Do you also build for building permits and environmental permits?
Yes, this is an important part of what we do for municipalities and environmental services. Since the Environment and Planning Act (Omgevingswet), building permits fall under the environmental permit for the building activity, with a split between the structural 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 manage the digital collaboration between plan assessors, structural engineers and enforcement officers (BOA's).
How do you handle publication to official announcements?
Permit decisions subject to a publication requirement go through an automated flow to officielebekendmakingen.nl, GVOP and the municipal local announcements environment. We generate the correct XML in IMOW or STOP/TPOD format, attach the relevant map layers, and manage the objection and representation flow, including deadline tracking and automatic publication of amended 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, 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 defined permit type with limited integrations is a different conversation from a full multi-organisation VTH platform. We give a realistic picture of this in the first conversation.
How long does a permitting project take?
A pilot with one permit type and a limited set of integrations can be working within a few sprints. A full VTH platform for an environmental service with multiple competent authorities, an inspection app and integrations with DSO and the case management system is a project spanning several sprints and multiple releases. We always work incrementally: once a permit type runs stably, it goes live while we build the next one.

Talk to us about your permitting software.

A free, no-obligation half-hour introduction. We listen to your permitting regime, your current package and your pain points, and give direction where it helps you, including if the outcome is that a custom project isn't the smartest choice. We can then complement documents and case flows with workflow automation, or embed them in a broader project software for municipalities.

Edit content