Service · Web development

Custom case management system development.

A case management system that fits the way your organisation handles cases — with ZGW API support, integrations with BRP, BAG and MijnOverheid, and a citizen portal that makes the entire case file transparent. For municipalities, implementing bodies and private organisations that work with file and case management.

ZGW APICommon GroundCase registrationBIO-compliant

A case management system is more than case handling.

A case management system registers, routes and archives every case your organisation handles — from a permit application to a Wmo (Social Support Act) notification, from an insurance claim to a complaint file. It is the central backbone where intake, handling, decision-making and archiving come together, linked to documents, statuses and stakeholders. Unlike a general document management system or a CRM, a case management system explicitly models the course of a case: which status may follow which, who may make a decision, which documents must be recorded at which stage, and which deadline applies to handling.

In the public sector, the case management system is the heart of Common Ground: the architecture in which data and processes are consulted at the source via open standards. We build custom software for municipalities and related organisations, with the ZGW API as the starting point. In the private sector we build comparable case management environments for insurers, banks, HR organisations and notary firms — there without ZGW, but with the same attention to audit trails, status monitoring and integrations.

Target groups we know well: municipalities and provinces (required to connect to Common Ground and ZGW), water boards and safety regions, implementing bodies such as UWV, RDW, SVB and RVO, independent administrative bodies, and on the private side insurers with claim cases, banks with complaint files, HR organisations with integrity reports, and notary firms or law firms with case administration. However different the domains are, the building blocks overlap strongly: case registration, status monitoring, document binding, role-based authorisation, audit log and a portal for stakeholders.

Three scenarios in which we build custom.

An off-the-shelf package such as Centric Suite4, Pink Roccade DJOIN, Decos JOIN or eSuite is usually the right choice for broad municipal processes. We will tell you so honestly. Custom comes into play when the off-the-shelf package doesn't adapt to your specific flow.

Compact project · sector-specific flow

Domain-specific case management system

For processes where the standard package becomes too generic: permit issuing with deep BAG integration, youth care files with multidisciplinary consultation, Wmo allocations with budget monitoring, or grant awarding with automated assessment criteria. A custom case management system that respects the Common Ground standards but follows your handling flow exactly.

Case type flowSLA monitoringDocument bindingAudit log
Mid-sized project · portal integration

Case management system with citizen and business portal

A case management system on the back end, combined with a portal where citizens can follow the status of their cases via DigiD, and businesses via eHerkenning, upload documents and submit applications. Fully branded in your house style, WCAG 2.1 AA accessible, and integrated with MijnOverheid for messaging.

DigiDeHerkenningMijnOverheidWCAG 2.1 AA
Larger project · multi-organisation

Collaborative case management system for the private sector

Case management for insurers (claims, assessments), banks (complaint and compliance cases), HR organisations (absence, integrity reports) and notary and law firms. Multi-branch, with deep integrations to policy administration systems, core systems, or document workflow automation for the document flows around them.

Multi-tenantSSORBACAPI-first

What you get at the end.

A production-ready case management system, plus all the technical and organisational support to manage it yourself or have your own IT supplier manage it.

  • The case management environment itselfProduction and acceptance, in your own cloud (Azure/GCP/AWS) or with a Dutch hosting provider that is BIO-compliant.
  • ZGW API implementationCases, Documents, Notifications, Decisions and Catalogues APIs in line with the VNG reference components, with OpenAPI specs and test suites.
  • Codebase and architecture documentationComplete source code in your own repository, build instructions, ADRs (architecture decision records) and a component overview.
  • Admin guide and runbookHow to assign roles, configure case types, consult audit logs and set retention periods in line with the Dutch Archives Act.
  • BIO assessment and DPIAA completed Baseline Informatiebeveiliging Overheid (BIO) assessment, a DPIA carried out with the architect, and a pen test in the final sprint.
  • Training and handoverSessions for key users and administrators, a short video tutorial for case handlers, and written knowledge transfer to your IT department.
  • Ongoing management (optional)Monitoring, backups, security patches and further development under an SLA with fixed response-time classes.

When a custom case management system is the right fit.

Four signals we often see in organisations that ultimately opt for a custom solution, alongside or instead of an off-the-shelf package.

Sector-specific

The off-the-shelf package doesn't bend with you

Your case types (youth care, permits on complex BAG objects, subsidies with multiple assessment points) need flows that only run in eSuite or Suite4 with a great deal of custom integrations.

Integrations

Deep BRP/BAG/Kadaster integration

The integrations you need go beyond the standard adapters: real-time BRP queries, historical Kadaster mutations, or your own federated data landscape with other government bodies.

Collaboration

Joint arrangement between public bodies

Multiple municipalities, a safety region or a partnership work in a single environment on shared files, with separate role management boundaries and separate retention periods per party.

Smart case handling

AI classification and triage

You want to automatically classify incoming cases, route them to the right team, or predict which cases risk breaching an SLA: capabilities that off-the-shelf packages only offer in a rudimentary form.

Portal layer

Citizens and businesses expect transparency

You want applicants to be able to follow their case status themselves, upload documents, and receive a notification via MijnOverheid when something changes, in your house style and at WCAG 2.1 AA level, not in a generic supplier-branded portal look.

Woo and archive

Woo publication and retention periods

You must comply with the Open Government Act (Woo) for proactive disclosure and with the Archives Act for retention periods per case type. Standard packages cover this, but often not at the level of granularity your selection list requires.

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 →

How a case management project runs.

1

Introduction and architecture discussion

A conversation in which we map out your case types, stakeholders and existing IT environment. For government clients: which ZGW components are already running, and which interfaces with DSO, NLX or the Berichtenbox are in place.

2

Scope, user research and tender documentation

A workshop with policy staff and case handlers, interviews with the citizens or businesses who use the portal side, and, for a tender, support in drawing up the programme of requirements. At the end: a concrete scope, a reference architecture and a first screen flow.

3

Building in sprints

We build in sprints, with a working build every two weeks. You test along, key users test along, and the ZGW API integrations are exercised from sprint one, with no big bang at the end. A first case type can be in production within a handful of sprints.

4

BIO assessment, DPIA and pen test

In the final sprint block we carry out the Baseline Informatiebeveiliging (BIO) assessment, a DPIA with your data protection officer, and an external pen test. Findings are resolved before go-live.

5

Rollout and maintenance

A phased rollout per case type or per organisational unit, training sessions for case handlers and administrators, and then ongoing maintenance with security patches, ZGW version upgrades and further development.

The modules a case management system is made up of.

Which modules you need depends on your case types and stakeholders. For government clients the ZGW components are mandatory; for private organisations we are freer in how we put the building blocks together. In both cases we work API-first, so smart API integrations with existing systems remain possible as a matter of course.

Case registration

Consistent intake

Every case gets a unique ID, a case type, a submitter and an initial status. Intake via a form, email, phone or an API call, always resulting in the same structured registration. This is the top query intent for which we currently rank well.

Case flow and status

From intake to archive

We model the flow of a case (intake, in progress, decided, completed, archived) per case type, with SLAs, escalations and automatic routing to the right case handler.

Documents

DMS integration

Documents are tied to the case, with version control and metadata. Integration with an existing document management system or with a dedicated DMS layer are both possible.

Audit trail

Who did what and when

Every status change, every document access and every authorisation change is logged. This is a requirement under BIO, GDPR and the Wpg (Police Data Act), and in practice indispensable for Woo requests and internal audits.

Portal layer

Citizens, businesses and partners

A citizen portal with DigiD, a business portal with eHerkenning, and collaboration portals for chain partners, all as separate layers on top of the same case registration source.

Integrations

BRP, BAG, Kadaster, KvK

The base registries: BRP for persons, BAG for addresses and buildings, Kadaster for real estate, KvK for businesses, and MijnOverheid's Berichtenbox for formal communication.

Frequently asked questions.

What clients usually want to know before we start.

Are you replacing Centric Suite4 or Pink Roccade DJOIN?
Not for the complete municipal process. Suite4, DJOIN, Decos JOIN, JoinUp, GeoMatch, Caesar, NoCare and eSuite handle broad case handling well, and the migration impact is too great to replace them lightly — for most municipalities it would mean a multi-year procurement process, with a serious risk of disrupting running processes. We build custom software alongside the standard package: for example, a domain-specific case system for a single department, a branded citizen portal that talks to the standard package via the ZGW API, or an AI classification layer that routes incoming mail before it lands in Suite4 or DJOIN. For private organisations, we do build the full case management stack.
What does a ZGW API implementation look like in practice?
The ZGW standard consists of five components: Zaken API, Documenten API, Notificaties API, Besluiten API and Catalogi API. We implement them in line with the VNG reference components, with OpenAPI 3 specs, JWT-based authorisation and a connection to NLX if your organisation works via the federated data system. We can build the components as a whole, replace a single component, or extend an existing implementation with functionality that isn't in the reference. API integrations are a core activity for us.
What exactly does the implementation phase of a case management system involve?
Implementing a case management system involves far more than technical installation. It covers configuring case types (with SLAs, statuses, roles involved and documents per case type), setting up role-based authorisations at department level, integrating with BRP, BAG, KvK and Kadaster, configuring Berichtenbox routing to MijnOverheid, and defining retention and destruction periods according to your selection list (Archiefwet, the Dutch Archives Act). In our projects we do this configuration together with your application administrators, so the knowledge stays within your organisation.
What is case registration and why is it the core of the system?
Case registration means recording every case that is being handled: a unique identification number, the case type, the applicant, the case handler, the status, the turnaround SLA and the documents belonging to the case. It is the core because all subsequent steps — status changes, decision, archiving, audit log — refer to that case registration object. For government clients, registration takes place via the ZGW Zaken API, so that other applications can consult the case without making a copy (the Common Ground principle: data at the source).
How do you connect to Common Ground and the DSO?
Common Ground is all about federated data retrieval via open standards. We align with Haven Compliancy for cloud hosting, use NLX where transport-layer federation is needed, and build our components so that they run as reference-implementation-compatible. For the Digitaal Stelsel Omgevingswet (DSO, the Dutch Digital System for the Environment and Planning Act), we integrate via STAM and STTR for applicable rules — relevant if your case management system handles environmental plan applications.
How do you handle BIO, GDPR and the Archiefwet?
BIO is the baseline for government information security. We demonstrably work through its building blocks: classification, access security (BIO building block 5.4 on access rights), logging, hardening and penetration testing. We embed GDPR in the architecture with data minimisation, the right to erasure at case level, and a DPIA. We translate the Archiefwet (the Dutch Archives Act) into destruction periods per case type based on your selection list — automatic, logged destruction once the period has expired.
What does a custom case management system cost?
An honest answer: it depends on the scope. A single domain-specific case type with a portal layer is a different project from a full ZGW stack with multi-organisation collaboration. We work in sprints at a fixed rate per sprint, so you can adjust the scope along the way. For tenders, we submit a well-founded bid based on your statement of requirements. Book an introductory call, and we can give you a realistic order of magnitude based on your specific flow.
Do you work with our IT department or current supplier?
Almost always. Municipalities usually already run a combination of Centric, Pink Roccade or Decos plus separate specialist applications. We connect with these carefully, with clear agreements on responsibilities, support hours and escalation lines. We hand over knowledge in the final sprints and deliver a runbook for incidents. We work the same way for private organisations: integrations with your existing enterprise software are a standard part of the project.

Talk to us about your case management system.

A no-obligation introductory call of half an hour. We listen to your case flow, ask follow-up questions about the tender or the business case, and give you direction you can actually use. Even if the outcome is that an off-the-shelf package is the better choice, we will tell you honestly.

Would you like to look at this issue from the custom software side? On applatenmaken.com you'll find a write-up of Custom software by sector.

If you want documents from your case management system to flow automatically into iBabs, see our page on an iBabs integration.

If you work with the e-Suite and want to connect line-of-business applications, take a look at our e-Suite integration.

If your organisation uses Corsa as its case and document management system, take a look at our Corsa integration.

Already working with iZaaksuite and want to connect other systems? Read more about our iZaaksuite integration.

Edit content