Service · Software development

Custom Omgevingswet software development.

Custom software that moves seamlessly with the Omgevingswet (Environment and Planning Act). We don't replace your VTH system; we build the portals, integrations and mobile tools that complete your Centric, Pink Roccade or Decos environment, from DSO connection to an enforcement app for BOAs (enforcement officers).

DSO-LV integrationVTH integrationSTAM & STOPBAG/Kadaster

The Omgevingswet works, but never 100% out of the box.

Since the Omgevingswet (Environment and Planning Act) came into force on 1 January 2024, every permit process in the Netherlands runs through the Digitaal Stelsel Omgevingswet (DSO-LV). Municipalities, regional environmental agencies, provinces and water boards work with standard packages such as Centric Suite4 Omgeving, Pink Roccade DJOIN, Open Wave, Squit XO, JoinUp or Decos JOIN-VTH. Those packages cover most of the work, but they always get stuck on the specific points where your organisation differs: a pre-application consultation flow that runs slightly differently, a contractor portal that wants to submit draft applications, an inspector who has to be able to work in the field without a network.

We don't build replacement VTH (permitting, supervision and enforcement) systems. We build the layer around them: the citizen portal that validates applications up front, the inspection app for the enforcement officer in the field, the dashboard that consolidates data from three environmental agencies. Custom software that connects to DSO, IMOW and your case management system, written for your reality, not for the average municipality.

In recent years we have worked for municipalities, regional environmental agencies and construction companies on exactly this type of layer software. That experience lies both in the technology (DSO APIs, IMOW mappings, offline sync patterns) and in the regulations, and in knowing how Centric, Pink Roccade and Decos behave under the hood. It's not a domain you understand in a week, so we only come up with an approach once we've properly questioned you about your situation.

Who we build Omgevingswet software for.

Municipalities: permitting, environmental consultation and enforcement. Often with Centric or Pink Roccade as the backbone and custom software for specific flows, such as contractor portals, environmental plan viewing for residents, or integrations with the local GIS platform.

Environmental services and RUDs — these work for several municipalities at once and need to consolidate data from different permitting, supervision and enforcement (VTH) packages. A dedicated workspace with normalised IMOW activities, STAM flows and task planning makes that manageable.

Provinces and water boards — these deal with complex permit types (Water Act, provincial environmental plan, environment) and often have unique policy frameworks that don't fit a standard package. Custom modules alongside the main package are then the practical route.

Construction companies and property developers — these regularly submit environmental plan applications and need their own application library, templates and an integration with their CAD and BIM environment. Here we build the other side: not the government tools, but the applicant tools.

Three types of Omgevingswet software we build.

Most projects fall into one of these three patterns. Which one fits depends on where your VTH package stops and where your own work process begins.

Citizens & applicants · fixed sprint budget

Applicant and citizen portal

A dedicated frontend for your citizens, construction companies and initiators. Pre-check with BAG/Kadaster, intake based on IMOW activities, a status tracking system and direct submission to the DSO-LV. Prevents incomplete applications and relieves your VTH team.

DSO integrationApplication wizardBAG validationDigiD & eHerkenning
Supervision & enforcement · fixed sprint budget

VTH application and supervision app

A mobile application for enforcement officers (BOAs) and inspectors that works offline, records photos and GPS data, and syncs with your VTH case management system as soon as there is a connection again. Plus dashboards for enforcement coordination and planning. Works alongside Squit XO, Centric or Decos JOIN-VTH.

Offline-firstGPS & photoCase integrationiOS & Android
Policy & integration · fixed sprint budget

Environmental plan viewer and multi-RUD consolidation

3D and GIS integrations that make the environmental plan visually accessible, linked to BAG, Kadaster and your own registry. For environmental services, also consolidation of data from multiple municipalities and RUDs in a single workspace, with IMOW and STAM translation.

3D & GISIMRO/IMOWMulti-tenantSTOP publication

What you get at the end of the project.

A production-ready application that fits your existing VTH stack, plus everything around it so you can manage and extend it yourself.

  • The application itselfProduction and acceptance environments, hosted in your own cloud (Azure, GCP, AWS) or with us. Fully tested against the DSO pre-production environment.
  • DSO connection documentationA complete connection document for the Kadaster / Geonovum, with a technical description of the integration, the API versions used and test scenarios.
  • Architecture and codeSource code, architecture diagrams, ADRs and deployment instructions — written so that another team or supplier can take it over.
  • Administration manual for functional managementA practical document for your application administrator: roles, permissions, exports, audit log, and how to configure new IMOW activities.
  • End-user trainingSessions for key users (VTH staff, enforcement officers, policy officers) plus short videos for the applicant side.
  • Support contract (optional)Ongoing maintenance, monitoring, security patches and keeping pace with DSO releases. Fixed monthly price, clear response times.

When custom work around your VTH package pays off.

Four patterns in which municipalities, environmental services and construction companies bring us in. If you recognise yourself in one of these situations, we'd be happy to talk further.

DSO connection

The standard package covers 80%

Centric, Pink Roccade or Decos JOIN-VTH covers the bulk of your permitting, but specific flows — for example environmental consultation or a construction company portal — need their own screens and rules that the package doesn't have.

Field inspection

Enforcement officers still work on paper

Your inspectors record their findings on paper or in a standalone photo app, then retype everything into the case management system in the evening. An offline-first mobile app that writes directly into the VTH system (permitting, supervision and enforcement), combined with workflow automation, saves each inspector hours every week.

Multi-organisation

Consolidating data from multiple sources

As a regional environmental agency, you work for multiple municipalities, each with its own VTH package and its own case management system. What's missing is a consolidation layer that translates everything into a single working environment for your permit officers and inspectors.

Applicant experience

Citizens and businesses drop out in the DSO

The national platform is functional, but it lacks context for your specific municipality or region: local policy rules, cost insight, or a pre-consultation route. A dedicated applicant portal in front of the DSO covers this.

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, integrations and tooling we work with.

Environment and Planning Act software runs on a collection of standards and registers. We build every integration explicitly and with version awareness, because they change several times a year with DSO releases.

DSO & application flow

DSO-LV APIs

Submission, Permits, Applicable Rules and Environmental Documents. We work with the official pre-production environment for the build and test phases and go through the standard connection test ahead of production.

Content & structure

IMOW, IMRO and STAM

IMOW for spatial planning data under the Environment and Planning Act, IMRO for older spatial planning data, and STAM for the standard activity description. We build mappings that support both receiving and publishing.

Architecture & publication

TAM and STOP

TAM (technical architecture model) is the reference for our connection architecture, and STOP for standard official publications. Both determine how we validate documents before they go to the national Announcement and Availability platform.

Geo, location and object

BAG, Kadaster and PDOK

The BAG API for address and building information, Kadaster BRK and KLIC for ownership and cable data, and PDOK for open geodata. For visualisation and 3D environmental plans, we work with Cesium, MapLibre, Esri or QGIS, depending on your existing GIS stack.

How an Environment and Planning Act project works.

1

Introduction and scope

An initial conversation in which we learn which VTH package you run, which processes are painful, and where your DSO-LV connection currently stands. We check whether custom development is really needed, or whether a configuration in your existing package would be cheaper.

2

Architecture and connection plan

Workshops with your functional management, IT architect and VTH staff. We map the IMOW activities, STAM flows and STOP publications that are affected. At the end you have an architecture document, a DSO connection timeline and an initial screen flow.

3

Building in sprints with user testing

Every sprint delivers a working build that your key users and a sample of citizens or inspectors use themselves. We connect early to the DSO pre-production environment and to your VTH package, so integration risks don't only surface at the end.

4

Connection, rollout and maintenance

The formal DSO connection test, production deployment and a phased rollout to users. After that, ongoing maintenance: keeping pace with DSO releases, IMOW updates and new STAM versions. We document thoroughly so you're never locked in to us.

Security, GDPR and archiving under the Environment and Planning Act.

Permitting and enforcement involve personal data, ownership data and land registry information. Our projects take this into account from the very first sprint, not as an afterthought.

  • DPIA and privacy by designFor every major project, we carry out a Data Protection Impact Assessment together with your data protection officer before we start building. Data minimisation and purpose limitation are built into the architecture.
  • BIO and NEN 7510We work in line with the Baseline Information Security Government (BIO) and, where relevant, NEN 7510. Pen tests and security reviews are part of every release cycle.
  • Audit log and archivingLegally required logging of decisions and actions, with exports to your e-depot or case management system. Includes metadata mapping towards TMLO or MDTO.
  • Government-grade authenticationDigiD and eHerkenning for applicants, ADFS / Microsoft Entra ID or Keycloak for your staff. Role management is fine-grained and linked to your HR source.

Frequently asked questions.

The questions we get asked most often by municipalities, regional environmental services and construction companies before we start.

Will you replace our permitting, supervision and enforcement (VTH) package, such as Centric or Pink Roccade?
No. Packages such as Centric Suite4 Omgeving, Pink Roccade DJOIN, Open Wave, Squit XO, JoinUp and Decos JOIN-VTH represent hundreds of person-years of rules and logic, and for standard processes they are almost always the best choice. Replacing one is also a multi-year programme handled by specialist implementation firms. We build the custom layer around it: portals, mobile apps, integrations and dashboards, connecting via the official APIs or case repository integrations of your existing package.
How do you handle the DSO-LV connection?
We follow the standard DSO connection process with the Kadaster and Geonovum. The application is first built against the pre-production environment (the practice environment) and systematically tested there against all application scenarios, after which it goes through the formal connection test for production. We have experience with the DSO APIs for Submissions, Permits, Applicable Rules and Environmental Documents, and with how error scenarios, retry logic and idempotency work in these integrations.
What about IMOW, IMRO, STAM, TAM and STOP?
For every custom application, we look at which standards apply: IMOW and IMRO for spatial planning data, STAM for activity descriptions, TAM for the technical architecture model and STOP for official publications. We build the mappings explicitly and with version awareness, because these standards change every year. Your application therefore keeps pace with DSO releases, and we build a test set so that the next version update is no surprise.
Can you integrate with BAG, the Land Registry (Kadaster) and our GIS environment?
Yes. We regularly work with the BAG API, Kadaster APIs (BRK, KLIC), PDOK services and GIS platforms such as Esri, QGIS and open MapServer. For 3D visualisations of environmental plans we use Cesium or MapLibre, depending on what fits your stack. We build integrations so that your applicants and supervisors never need to have three tabs open. See also our page on smart API integrations for the more general approach.
Do you also work offline for BOAs (enforcement officers) and inspectors?
Yes, this is a common question. We build enforcement apps for BOAs and building inspectors offline-first as standard: a local database, a sync queue, photo and GPS capture without a connection, and conflict resolution when two inspectors work on the same file at once. Only when the tablet or phone has a network connection again does everything sync to your VTH case management system or the separate enforcement module.
What determines the cost of a project like this?
The biggest cost factors are the number of IMOW activities and flows you want to support, the depth of the VTH package integration, whether a mobile app is part of it, and whether multi-tenant consolidation is needed for several municipalities or regional environmental services. We work with fixed sprint budgets and deliver a working product every sprint, so scope and cost move together and you can adjust course yourself.
Do you work with our internal IT department and current suppliers?
Yes, almost always. We fit in with your deployment pipeline, ITIL processes and information security policy. With the suppliers of your VTH package, we explicitly agree who is responsible for what and which API versions we use. At the end of the project we do a full knowledge transfer (code documentation, runbooks, an architecture walkthrough) so that your team can manage it itself or another agency can take it over without rework.
How long will it take before we can go live?
That depends on the scope and how many integrations are affected. A citizen portal with a DSO connection for a single municipality can be up and running in a few sprints. A multi-RUD consolidation (several regional environmental services) with multiple VTH packages and a supervision app is a project of several sprints. We always work in working increments, so you have something to test from the start rather than only at the end.

Talk to us about your Omgevingswet (Environment and Planning Act) project.

A no-obligation half-hour conversation in which we listen to your VTH stack, your DSO connection and the places where custom software would help. We'll give you direction you can actually use, even if the conclusion is that you're better off staying within your existing package.

Edit content