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).
Since the Environment and Planning Act came into force on 1 January 2024, every permit process in the Netherlands runs through the Digital Environment and Planning System (DSO-LV). Municipalities, environmental services, 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. These packages cover most of the work, but always get stuck on the specific points where your organisation differs: a pre-application consultation flow that runs slightly differently, a construction company portal that needs to submit draft applications, or an inspector who must be able to work in the field without a network connection.
We don't build replacement VTH systems. We build the layer around them: the citizen portal that validates applications upfront, the inspection app for the enforcement officer in the field, the dashboard that consolidates data from three environmental services. Custom software that connects to DSO, IMOW and your case management system, written for your reality, not for the average municipality.
Over the past few years we have worked for municipalities, environmental services and construction companies on exactly this type of layer software. That experience covers both the technology, such as DSO APIs, IMOW mappings and offline sync patterns, and the regulations and the knowledge of how Centric, Pink Roccade and Decos behave under the bonnet. It's not a domain you understand in a week, so we only come up with an approach once we have thoroughly questioned you about your situation.
Municipalities for permit issuing, pre-application consultation and enforcement. Often with Centric or Pink Roccade as the backbone and custom development for specific flows such as construction company portals, public access to the environmental plan for residents, or integrations with the local GIS platform.
Environmental services and RUDs that work for several municipalities at once and need to consolidate data from different VTH packages. A dedicated working environment with normalised IMOW activities, STAM flows and task planning keeps this manageable.
Provinces and water boards — these handle complex permit types (Water Act, provincial environmental plan, environmental permits) and often have unique policy frameworks that don't fit a standard package. Custom modules alongside the core system are then the practical route.
Construction companies and property developers who regularly submit environmental plan applications and need their own application library, templates and integration with their CAD and BIM environment. Here we build the other side: not the government tools, but the applicant tools.
Most projects fall into one of these three patterns. Which one fits depends on where your VTH system ends and where your own working process begins.
A dedicated front end for your citizens, construction companies and initiators. Pre-checks against BAG/Kadaster, intake by IMOW activity, a status tracking system and direct submission to the DSO-LV. It prevents incomplete applications and relieves pressure on your VTH team.
A mobile application for enforcement officers and inspectors that works offline, records photos and GPS data, and syncs with your VTH case management system as soon as connectivity returns. Plus dashboards for enforcement management and planning. It works alongside Squit XO, Centric or Decos JOIN-VTH.
3D and GIS integrations that make the environmental plan visually accessible, linked to BAG, Kadaster and your own records. For environmental services, also consolidation of data from multiple municipalities and RUDs in a single working environment, with IMOW and STAM translation.
A production-ready application that fits your existing VTH stack, plus everything around it so you can manage and extend it yourself.
Four patterns in which municipalities, environmental services and construction companies engage us. If you recognise yourself in one of these situations, we would be happy to talk further.
Centric, Pink Roccade of Decos JOIN-VTH covers most of your permit processing, but specific flows, such as environmental consultation or a construction company portal, call for their own screens and rules that the package does not support.
Your inspectors record findings on paper or in a loose photo app, then retype everything into the case system in the evening. An offline-first mobile app that writes directly into your VTH system, connected to workflow automation, saves hours per inspector each week.
As an environmental service, you work for several municipalities, each with its own VTH package and case system. There is no consolidation layer that translates everything into one working environment for your permit officers and inspectors.
The national facility is functional, but it lacks context for your specific municipality or region: local policy rules, cost visibility, or a pre-consultation route. A dedicated applicant portal ahead of the DSO catches this.
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 →Environment Act software runs on a set of standards and registers. We build all integrations explicitly and with version awareness, because they change several times a year with DSO releases.
Submissions, Permits, Applicable Rules and Environmental Documents. We work with the official pre-production environment for the build and test phase, and go through the standard connection test towards production.
IMOW for spatial planning data under the Environment Act, IMRO for older spatial planning data, STAM for the standard activity description. We build mappings that support both receiving and publishing.
TAM (technical architecture model) as the reference for our connection architecture, STOP for the standard official publications. Both determine how we validate documents before they go to the National Facility for Publication and Availability.
BAG API for address and building information, Kadaster BRK and KLIC for ownership and cable data, PDOK for open geodata. For visualisation and 3D environmental plans we work with Cesium, MapLibre, Esri or QGIS, depending on your existing GIS stack.
A first conversation in which we understand which VTH package you run, which processes are painful, and where the DSO-LV integration currently stands. We check whether custom development is really needed, or whether a configuration in your existing package is cheaper.
Workshops with your functional management, ICT architect and VTH staff. We map the IMOW activities, STAM flows and STOP publications affected. At the end you have an architecture document, a DSO integration calendar and a first screen flow.
Every sprint, 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 surface only at the end.
The formal DSO connection test, production deployment and a phased rollout to users. Then ongoing maintenance: keeping pace with DSO releases, IMOW updates and new STAM versions. We document thoroughly so you are never tied to us.
Permit processing and enforcement involve personal data, ownership data and cadastral information. Our projects take this into account from the first sprint onwards, not as an afterthought.
The questions we most often get from municipalities, environmental services and construction companies before we start.
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 give direction you can act on, even if the conclusion is that you are better off staying within your existing package.
Appfront uses cookies and similar technologies to keep the website working properly, for analytics and for marketing. You choose what you allow. Read more in our privacy policy.
