Software for the public sector that has to hold up under scrutiny
A case moves between three departments, two intake forms, and a mailbox nobody owns, and a citizen waits while it does. We build the digital services that carry that process end to end: accessible, traceable, and explainable to whoever asks.
What we see in the public sector
Case handling spread across systems that do not talk
Intake happens in one place, assessment in another, and the decision lands in a mailbox. Answering “where is my case?” costs a person half an hour.
Accessibility treated as a final test
Accessibility problems surface after the build, when each one is expensive to fix and the service still has to work for every citizen entitled to use it.
Questions the system cannot answer
Procurement and privacy officers ask who accessed a record, on what basis, and how long it is kept. Too often that answer has to be assembled by hand.
What we build for it
Case and intake platforms with visible status
One flow from intake to decision, with the current state visible to the handler and to the citizen, and every step recorded for whoever reviews it later.
Accessible by construction
Everyone entitled to the service can finish it on a screen reader, on a keyboard alone, on an old phone in bad light. Built in from the first screen, because retrofitting it costs several times more.
AI that assists a civil servant, never replaces the decision
Retrieval and summarising over your own documents, with the decision and the reasoning staying with a named person who can explain it.
What you have to be able to show
A public body answers to a citizen, a journalist and an auditor, and each of them can ask a question the system itself has to answer. These three shape the build rather than the paperwork around it.
- The BIO security baseline
The mandatory baseline for government information security, with controls that have to be demonstrable rather than asserted.
Access control, logging and separation are designed against the baseline, so we can point at the measure that implements a given control instead of at a policy document.
- WCAG 2.1 AA
Accessibility is legally required for public services, alongside a published statement that has to be accurate.
Structure, keyboard paths and contrast are checked as the interface is written. Treated as an audit at the end, every finding is expensive; treated as a build requirement, most never occur.
- The Woo and the Archiefwet
Records can be requested and increasingly have to be published, and separately have to be kept or destroyed on a set schedule.
A record carries its classification and its retention from the moment it is created, so answering a request is a query against the system rather than a search through it.
This is how we design against these obligations. It is not legal advice: your compliance officer owns the interpretation, and we make sure the software can answer them.
Compliance and data
A public body has to be able to explain, on request, who had access to a record, on what basis, and how long it is kept. Here is how we arrange that.
Related case
A private client, but the shape a public body will recognise: qualifications, availability and conflicts of interest enforced without exception, while the final decision stays with a named person who can explain it.
Let’s build your next solution
Bring your industry challenges and we’ll pair them with the right mix of AI, engineering, and design to launch fast without sacrificing quality.