Service · Web development

Custom waterboard software.

Custom software for the 21 Dutch water authorities: permit flows, dyke management, emergency apps, geo platforms on PostGIS, and Common Ground components. Built in line with BIO, GDPR and the architecture guidelines that water authorities set jointly, not on a rigid enterprise package.

Common GroundBGT & PostGISBIO-compliantMulti-water authority collaboration

A water authority is not a municipality with wet feet.

The Netherlands has 21 water authorities (waterschappen), from Hollands Noorderkwartier and Rijnland to Hunze en Aa's and Scheldestromen. They are independent, democratically elected regional government bodies with four core tasks: flood protection, water quality, sufficient water and wastewater treatment. These tasks call for software you won't find in any standard case management system or generic municipal package.

Dike inspection, water level management, discharge permits, emergency on-call duty, wastewater treatment plant asset management and integrations with BGT, AHN and BAG via PostGIS: these are all flows designed specifically for water authorities. We build these components to your specification, whether it's a citizen portal, a mobile inspection app or a shared service that several water authorities use together via the case management architecture you already follow.

We work alongside existing packages such as Centric, Pink Roccade DJOIN and Decos. We don't replace them, but fill the gaps where they no longer fit. Our code remains the property of the water authority, runs wherever you want and connects to the rest of your IT landscape through open integrations.

The water authority context also calls for attention to what does not belong in software: dike watch procedures, emergency coordination with safety regions, and accountability to the General Board and the Dijkgraaf (dike reeve). Good software supports these processes without dominating them: operation stays simple, the audit trail stays complete, and the people out in the field stay in charge.

Three types of water authority software we build.

From a well-defined citizen portal to a multi-year platform shared by several water authorities. We'll decide which form fits in the first conversations.

Defined project · fixed sprint budget

Citizen and application portal

A portal for residents and businesses to apply for discharge permits, report damage, declare water use or view permits. Login via DigiD and eHerkenning, an integration with your existing case management system and enforcement workflow, and an audit trail that meets the requirements of the Archiefwet (Dutch Archives Act).

DigiD / eHerkenningCase management integrationPDF decisionGDPR-compliant
Mid-sized project · operational

Dike, emergency and inspection apps

Mobile-first applications for field staff: dike inspection, flood barrier inspection, emergency reporting to the on-call team. Usable offline, with photo, GPS location and an integration with asset registers or CMMS. Results land directly in the GIS and in the management reporting dashboard.

Offline-firstGPS & photoDrone dataCMMS integration
Larger project · multiple water boards

Geo and collaboration platforms

Shared services between water boards: a geo platform on PostGIS that combines BGT, BAG and AHN, a joint permit workflow for multiple management areas, or a Common Ground component used as an open-source service by several water boards. We help you think through architecture, governance and further development.

PostGISCommon GroundMulti-tenantOpen source

What you end up with.

A working application, tested and accepted by the users within your water board, plus everything IT and operations need to carry on with it themselves.

  • The application itselfProduction and acceptance environments, running in your own cloud or with a Dutch host with a BIO baseline. No vendor lock-in on a SaaS package.
  • Full codebase and documentationSource code in the water board's own Git repo, build instructions, architecture overview and API documentation. No black box.
  • Integrations with your existing stackIntegrations with Centric, Pink Roccade DJOIN, Decos, the GIS platform, asset management and the regional tax administration via clear API contracts and smart API integrations.
  • Operations manual for ITWhat to do in case of incidents, how to add roles, how to export for archiving, how to follow up on pen-test findings. Written for the people who will carry on without us.
  • Training for key usersTwo live sessions for the end users within your organisation and short instruction videos for partners or residents who will use the portal.
  • Optional: ongoing maintenanceMonitoring, backups, security patches and further development for an agreed monthly fee, with clear response times for emergencies via the on-call service.

When custom software for a water authority is the right choice.

Four situations in which we typically help water boards. Sound familiar? Then an exploratory conversation is worth your time.

Common Ground

Components instead of a package

You don't want one large SaaS package but shared services within the Common Ground architecture that VNG and the water boards are developing together. We build those components as open-source services that other water boards can reuse too.

Geo & PostGIS

A BGT integration that needs to do more

The BGT, BAG and AHN are already in your map layer, but no standard package combines that data the way you need it for watercourses, water level areas or dike rings. A custom PostGIS backend with a clean tile API gives you that control back.

Collaboration

Collaborating digitally with other water boards

Several water boards want to run a single service together, for example a joint permit workflow, a shared emergency app or a central monitoring dashboard. We build it multi-tenant, with governance agreements that work across water board boundaries.

Operational apps

Field staff still work on paper

Inspection reports, flood defence inspections or sampling that are still processed via clipboard and Excel. A mobile app with offline mode, GPS location and direct sync with the GIS saves field staff daily frustration and data loss, and at the same time produces usable time series for trend analysis and board accountability.

Climate adaptation

Stress tests and heat/drought monitoring

The climate stress test is by now established in every water board, but the results often end up in separate reports or static maps. We build interactive dashboards that link your stress test data and KNMI scenarios to your own water level and quality measurements, so that management, the board and partners can see what is happening in one place.

How a water board project with us works.

1

Introduction and scope kick-off

An initial conversation with the process owner and someone from IT architecture. We learn which core task is affected, which software packages are already in use and which compliance requirements apply — BIO, GDPR, the Archives Act and, for environment-related topics, the DSO-LV integration requirements.

2

Architecture and user research

A workshop with your team plus interviews with the people who will use the software every day — a dyke manager, a permit officer or a colleague on the on-call rota. At the end you have a concrete scope, a first screen flow and a well-supported architecture that fits the Common Ground guidelines.

3

Building in two-week sprints

Every sprint delivers a working build that your team can test. We work with a fixed team of two to three developers and a product designer; your product owner attends every review. Adjusting course along the way is the norm, not the exception.

4

Pen test, acceptance and rollout

Before go-live, an independent pen test is carried out in line with the BIO guidelines. This is followed by a phased rollout: first a pilot team, then the whole organisation and, for multi-water-authority platforms, a controlled rollout per participant.

5

Ongoing maintenance and further development

After delivery, the application moves into maintenance — monitoring, backups, security updates and small-scale further development based on user feedback. For shared services, we help think through governance between the participating water authorities.

Frequently asked questions.

What colleagues at water authorities usually want to know before we start.

What is Common Ground, and do you build for it?
Common Ground is the shared information architecture that the VNG (the Association of Dutch Municipalities) and the water authorities are developing together. Instead of one big software package, information is decoupled from applications through reusable services. We actively build components within this architecture: API-first, open source where it makes sense, and set up so that another water authority can easily reuse the same service. We don't force everything into a Common Ground mould — for well-defined portals or inspection apps, classic patterns are often the wiser choice.
How do you handle BGT, BAG, AHN and PostGIS?
Our geo stack runs on PostGIS as standard. We load the BGT periodically from the official PDOK sources, and the same goes for BAG and AHN. On top of that we deliver tile services, vector tiles or OGC APIs, so that your front-end application or GIS viewer talks to them through one clear API. For analysis work — such as water-level area calculations or dyke ring overlays — we write the SQL and CTEs in the PostGIS layer rather than fiddling around in a front-end package.
Can several water authorities collaborate digitally in a single application?
Yes, that is one of the main reasons water authorities approach us. We build multi-tenant: one codebase, one hosting environment, but with each participant having their own roles, their own reports and their own control over the content. For shared services, we help think through governance up front — who pays, who decides on further development, who maintains the roadmap. You can't solve that with technology alone, but you can't solve it without technology either.
Do you replace Centric, Pink Roccade or Decos?
No. For the core case management system or the basic registers, those enterprise packages usually stay in place. We build alongside them: the application flow that is too specific, the citizen portal that the standard look can't handle, the inspection app that isn't included, or the shared geo platform that works across package boundaries. Integrations run through clear API contracts or an ESB if one is central to your landscape.
What about BIO, GDPR and the Archives Act?
For us, BIO is the baseline, not an after-the-fact check. We work with IBI-compliant logging, separation of environments and a pen test in the final sprint. GDPR requirements — purpose limitation, data minimisation, data subject rights — are built into the design from the start. For the Archives Act, we make sure decisions and relevant case documents can be exported to your e-Depot. For environment-related topics, the DSO-LV integration obligation also applies; for that, we also refer you to our Environment Act page.
How does water authority software differ from water engineering software?
Water engineering software runs close to the installations: PLCs, SCADA environments and control of pumps, pumping stations and wastewater treatment processes. We go into more depth on that on the water engineering page. Water authority software in this context is the administrative and operational layer above it: permits, dyke management, emergency coordination, user portals and collaboration platforms between water authorities.
And how does it differ from software for municipalities?
Many components overlap (DigiD, eHerkenning, GDPR, a case-oriented architecture) and we like working at the intersection. But water authorities have specific tasks you won't find in any municipal package: dyke ring monitoring, water level decision administration, wastewater treatment plant asset management and coordination with Rijkswaterstaat. Our approach to municipal projects is on the municipality page; for water authorities the process is similar, but the domain model is different.
Can you work with our consultancies and partners?
Almost always, yes. Consultancies such as Witteveen+Bos, Royal HaskoningDHV or Sweco regularly supply the technical models or the functional design; we build the software around them. We also work with Deltares or HKV models by exposing them as services in dashboards. That kind of collaboration calls for clear agreements on IP and further development up front, and we help you put those in writing.
Which models and datasets do you integrate in terms of content?
On the flood safety side, we often integrate with dyke strength models and Flood Protection Programme (HWBP) data. For water quantity and quality, we bring results from Sobek, D-Flow or MIKE into a dashboard, and for asset management we connect to GeoIT or BeheerIT. PDOK is a regular supplier for BGT, BAG, AHN and aerial photographs, and for climate adaptation we integrate KNMI stress test data. We don't build new hydrological models; we make your existing models usable for decision-makers and field staff through software.
How does it work with the water authority tax and SVHW or BSGR?
The levy administration of most water authorities runs through SVHW, BSGR or a comparable regional tax service. We don't replace that. What we do build is the application and objection portal, a specific direct debit integration, or your own reporting layer on top of the supplied data. The integrations run via standardised messages or via API contracts that we agree with the tax service.

Talk to us about your water authority software.

A no-obligation introductory call of half an hour. We listen to which core task or collaboration challenge is at stake, ask questions about the existing landscape, and give you direction you can use internally straight away, even if you decide to continue without us afterwards.

Is this topic also relevant within your own organisation? On applatenmaken.com you can read more about custom software per sector.

On the discharger's side, with registration per job and the evidence for the supervisory authority, there is our app for cleaning water discharge accountability.

For administering soil and dredged material per batch, with notifications and an application file, there is our app for soil flow administration under the Bbk.

Edit content