From chaos to control: one government overview for bereaved partners.
This repository hosts the challenge brief, supporting documents, synthetic datasets, and data-generation tooling for the second OneGov hackathon, hosted by GovTech NL and challenge owner ICTU.
- Theme: Inwoner Centraal (Citizen-centric)
- Date: 4–5 June 2026
- Location: The Hague Tech, Den Haag
- Challenge owners: Natalie Moreno Robles & Ingrid Verhage (ICTU)
- Contact: hack@govtechnl.nl
When someone loses a partner, they enter one of the hardest periods of their life - and an administrative storm. Bereaved partners receive correspondence from up to twelve different government organisations (Gemeente, SVB, CAK, RDW, Waterschap, Belastingdienst, Toeslagen, RVO, CJIB, UWV, DUO, KVK), each operating from its own silo. The same data is requested over and over while the doenvermogen (capacity to act under emotional pressure) is at its lowest.
How can we help bereaved partners get a complete, proactive, personalised view of their rights and obligations across the entire government - without making them chase it themselves?
The full brief is in CHALLENGE.md. The original PDF brief from ICTU is at the repo root: OneGov#2_Challenge_Brief_Inwoner_Centraal_Nabestaanden_ICTU.docx.pdf.
New teams can begin with START_HERE.md.
The challenge is one integrated scenario: a bundled first message from the whole government, plus a digital place where the bereaved partner can keep track. Within that scenario the brief distinguishes three actions a good solution should cover:
- Informeren. Tell the bereaved partner, in plain language and at the right moment, what is coming and what is being arranged.
- Toegang geven. Give the bereaved partner access to the deceased's relevant records (for example via a nabestaandenmachtiging) and to a single loket for questions.
- Handelen namens. Let the government pre-arrange what can be pre-arranged (e.g. stopping toeslagen, deferring obligations) instead of pushing that work onto the bereaved partner.
As a working form, ICTU has split the ambition into two concrete steps. Teams pick one as their main focus or show how both connect. Whichever step you pick, the three actions above should be recognisable in your prototype.
- Stap 1: De gebundelde eerste brief. A single, empathic letter on behalf of the whole government, sent shortly after the death.
- Stap 2: Het gepersonaliseerde totaaloverzicht. A digital "loket" where the bereaved sees every running obligation and right at a glance.
| Path | Purpose |
|---|---|
| CHALLENGE.md | Full challenge brief (English translation of the Dutch original) |
| docs/ | Personas, the Truus & Cees case, legal context, judging criteria, architecture notes |
| resources/ | Original source materials (PDF, PPTX, XLSX) provided by ICTU and partners — see resources/README.md. Includes the KvK inventarisatie verplichtingen (snapshot 2024, ondernemer-bias). |
| data/schemas/ | JSON Schemas for every data layer |
| data/synthetic/ | Generated synthetic datasets (output of the generator) |
| data/fixtures/ | Hand-curated golden cases matching each persona |
| data-generation/ | Python tooling that generates the synthetic data |
cd data-generation
uv venv # or: python -m venv .venv
uv pip install -e .
python -m generate --seed 42 --n 500 --out ../data/syntheticThe generator produces six data layers (BRP-style death registration, outstanding obligations, partner rights, correspondence stream, expected timeline, and optional KVK/RVO business data) plus four hand-curated fixtures that mirror the personas.
See data/README.md for the data dictionary and provenance.
All data in this repository is fully synthetic and contains no personal
data of real citizens. BSN-like identifiers are generated for testing and are
explicitly tagged with a "synthetic": true marker. Prototypes built during
the hackathon are not policy commitments and require further review before
any production use.
- Code is released under the Apache License 2.0.
- Data, documentation, and challenge text are released under CC BY 4.0.
Teams submit through Alkemio, the central submission and review point for the OneGov #2 jury.
- Alkemio submission link: Inwoner Centraal: Nabestaanden.
- A team submits: a repository link (GitHub, GitLab or similar; this does not have to be a pull request against this repo, teams build their own prototype repository), a working prototype or demo, a pitch deck (max. 10 slides), and a short description of back-end choices.
- The Alkemio submission is what the jury scores during the hackathon. Pull requests against this repository are welcome for high-quality reusable artefacts (schemas, fixtures, generator improvements, documentation), and they remain leading for the post-hackathon review and merge of those contributions into this central repository.
Issues and pull requests are welcome, see CONTRIBUTING.md.