Service · Web development

Custom case management system development.

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

ZGW APICommon GroundCase registrationBIO-compliant

A case management system is more than case management.

A case management system registers, routes and archives every case your organisation handles, from a permit application to a Wmo report, 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 take a decision, which documents must be recorded at which stage, and which deadline applies to completion.

In the public sector, the case management system is at 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 notaries; there without ZGW, but with the same attention to audit trails, status control and integrations.

Target groups we know well: municipalities and provinces (obliged 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 notaries or law firms with case administration. However different the domains, the building blocks overlap strongly: case registration, status control, document binding, role-based authorisation, audit log and a portal for stakeholders.

Three scenarios in which we build custom solutions.

For broad municipal processes, a standard package such as Centric Suite4, Pink Roccade DJOIN, Decos JOIN or eSuite is usually the right choice. We give that advice honestly. Custom software comes into play when the standard package does not move with your specific workflow.

Compact project · sector-specific workflow

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 workflowSLA monitoringDocument bindingAudit log
Medium-sized project · portal integration

Case management system with citizen and business portal

A case management system at the back end, combined with a portal where citizens can log in via DigiD or businesses via eHerkenning to track the status of their cases, upload documents and submit applications. Fully branded in your corporate identity, 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 (complaints and compliance cases), HR organisations (absence, integrity reports) and notary and legal practices. Multi-site, with deep integrations into policy administration systems and 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 needed 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 implementationCase, Document, Notification, Decision and Catalogue APIs in line with the VNG reference components, with OpenAPI specifications and test suites.
  • Codebase and architecture documentationComplete source code in your own repository, build instructions, ADRs (architecture decision records) and a component overview.
  • Administration manual and runbookHow to assign roles, how to configure case types, how to consult audit logs, how to set retention periods in line with the Dutch Archives Act.
  • BIO assessment and DPIAA completed Baseline Informatiebeveiliging Overheid (BIO) assessment, a DPIA prepared together with the architect, and a penetration test in the final sprint.
  • Training and handoverSessions for key users and administrators, a short video tutorial for case handlers, and a written knowledge transfer to your IT department.
  • Ongoing maintenance (optional)Monitoring, backups, security patches and further development under an SLA with fixed response time categories.

When custom development delivers a case management system that fits.

Four signals we often see in organisations that ultimately choose custom development, either alongside or instead of a standard package.

Sector-specific

The standard package doesn't bend to fit

Your case types (youth care, permits on complex BAG objects, grants with multiple assessment points) call for workflows that, in eSuite or Suite4, only run with a great deal of custom integration work.

Integrations

Deep BRP/BAG/Kadaster integration

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

Collaboration

Joint arrangement

Several municipalities, a safety region or a collaborative partnership working in one environment on shared files, with separate role management boundaries and separate retention periods per party.

Smart case handling

AI classification and triage

You want incoming cases to be classified automatically, routed to the right team, or predicted to be at risk of breaching an SLA. These are capabilities that standard packages offer only in a basic form.

Portal layer

Citizens and businesses expect transparency

You want applicants to track their case status themselves, upload documents, and receive a notification via MijnOverheid when something changes, all in your own house style and to WCAG 2.1 AA level, rather than a generic portal look from a vendor.

Open government and archiving

Open government publication and retention periods

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

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 →

How a case management project runs.

1

Introduction and architecture discussion

A conversation in which we map out the case types, the stakeholders and your 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 caseworkers, interviews with the citizens or businesses who use the portal side and, if there is a tender, support in drafting the requirements specification. At the end: a concrete scope, a reference architecture and a first screen flow.

3

Building in sprints

We build in sprints, delivering a working build every two weeks. You test along the way, as do your key users, and the ZGW API integrations are tackled from sprint one, so there is no big bang at the end. A first case type can go live within a handful of sprints.

4

BIO assessment, DPIA and penetration test

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

5

Rollout and management

A phased rollout per case type or per part of the organisation, training sessions for caseworkers and administrators, and then ongoing management with security patches, ZGW version upgrades and further development.

The modules a case management system is built from.

Which modules you need depends on your case types and stakeholders. For government clients the ZGW components are mandatory; for private organisations we assemble the building blocks more freely. In both cases we work API-first, so that smart API integrations with existing systems remain straightforward.

Case registration

Consistent intake

Every case receives a unique ID, a case type, an applicant and an initial status. Intake via form, email, telephone or an API call, always with the same structured registration. This is the top query intent where we currently perform well.

Case flow and status

From intake to archive

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

Documents

DMS integration

Documents are linked to the case, with version control and metadata. Integrating with an existing document management system or building your own DMS layer are both possible.

Audit trail

Who did what, and when

Every status change, document access and authorisation change is logged. This is a requirement under BIO, GDPR and the Wpg, and in practice it is indispensable for Wob requests and internal audits. Note: WOO (Wet open overheid) is the Dutch transparency act; keeping the acronym as is.

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 Basic Registers: BRP for persons, BAG for addresses and buildings, Kadaster for real estate, KvK for businesses, and the MijnOverheid Berichtenbox for formal communication.

Frequently asked questions.

What clients usually want to know before we start.

Do you replace Centric Suite4 or Pink Roccade DJOIN?
Not for the entire municipal process. Suite4, DJOIN, Decos JOIN, JoinUp, GeoMatch, Caesar, NoCare and eSuite cover broad case handling well, and the migration impact is too great to replace them lightly. For most municipalities, doing so would mean a multi-year procurement process with significant risk of disruption to ongoing processes. We build custom software alongside the standard package: for example, a domain-specific case management 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 post before it lands in Suite4 or DJOIN. For private organisations, we 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 specifications, authorisation via JWT, and connection to NLX if your organisation works via the federated data ecosystem. We can build the components as a whole, replace a single component, or extend an existing implementation with functionality that is not in the reference. API integrations are a core activity for us.
What does the implementation phase of a case management system actually involve?
Implementing a case management system involves far more than technical installation. It means configuring case types (with SLAs, statuses, involved roles 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 periods in line with your selection list (Archiefwet). In our projects, we carry out this configuration together with your application managers, so that 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 comes in for handling: a unique identification number, the case type, the applicant, the handler, the status, the processing-time SLA and the documents attached 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 other applications can consult the case without making a copy (Common Ground principle: data at the source).
How do you connect to Common Ground and the DSO?
Common Ground is about federated querying via open standards. We align with the Haven Compliancy for cloud hosting, use NLX where transport-layer federation is needed, and build our components so they run as reference-implementation-compatible. For the Digital Environment Act system (DSO), we integrate via STAM and STTR for applicable rules, which is relevant if your case system handles environmental plan applications.
How do you handle BIO, GDPR and the Archiefwet?
BIO is the baseline for government information security. We work through its building blocks in a demonstrable way: classification, access control (BIO building block 5.4 on access rights), logging, hardening and penetration testing. We embed GDPR in the architecture through data minimisation, the right to erasure at case level, and a DPIA. We translate the Dutch Archives Act into destruction periods per case type, based on your selection list (selectielijst): automated, logged destruction once each period has expired.
What does a custom case management system cost?
An honest answer: it depends on scope. A single domain-specific case type with a portal layer is a very 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 scope along the way. For tenders, we provide a well-grounded submission based on the programme of requirements. Arrange an introductory call, and we can give you a realistic order of magnitude based on your specific workflow.
Do you work alongside our ICT department or current supplier?
Almost always. Municipalities usually already run a combination of Centric, Pink Roccade or Decos plus separate line-of-business applications, and we connect carefully to these, with clear agreements on responsibilities, support hours and escalation routes. We handle knowledge transfer in the final sprints and deliver a runbook for incidents. For private organisations we work the same way: 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 workflow, ask questions about the tender or business case, and give direction where it is useful to you. Even if the outcome is that a standard package is the better choice, we will say so 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 to automatically send documents from your case management system to iBabs, take a look at our page on iBabs integration.

Edit content