IT that stands up to scrutiny
Municipalities, agencies and public bodies work within fixed frameworks and under public accountability. We deliver inside those frameworks, record what we do in a way that survives later questions, and keep systems available for people who have no alternative.
Accountability is part of the work here
What you do has to be right, and it has to be explainable afterwards to somebody who was not there.
In the public sector nearly every IT decision runs past two questions at once. The first is whether it works. The second is whether, a year from now, you can still show why it was done that way, who decided it and what it cost. That second question comes from an auditor, a regulator, a council member or a journalist filing a freedom-of-information request, and it arrives at a moment you were not waiting for.
That changes the work. A change that elsewhere goes ahead after a short conversation needs a request, an approval and a trail here. We are used to that and set up management so the evidence appears by itself: every change traceable, every access recorded, every agreement findable without somebody spending an afternoon on it.
The frameworks you work inside
For government organisations in the Netherlands the BIO is the baseline for information security, with the GDPR over it and, for some bodies, NIS2 alongside. Those standards remain your responsibility; we make sure our setup and way of working line up with them. In practice that means role-based access management, logging that survives an audit, backups that can demonstrably be restored, and agreements written in plain language in an SLA. Our own processes are covered by ISO 9001, ISO/IEC 27001, ISO 14001 and Kiwa NEN 4400-1.
That last mark is more than a logo here. Kiwa NEN 4400-1 covers reliability in supplying personnel and protects a hirer against chain liability. For a public body that brings people in, that is not a detail but a condition.
Tendering and handing over
Work in this sector is tendered, which means it will move again one day. So we build nothing you cannot get out of. Documentation, passwords, licences and the setup we built are yours and come with you if the contract goes to somebody else. That is not a nice promise but a practical choice: we have taken over environments from parties that made it difficult, and we know what that costs an organisation.
What we handle in public sector environments
You choose what you need. It all sits under one contract, one report and one point of contact.
- Support with recorded response timesTickets arrive by phone, email or portal, get a priority that is written into the SLA, and can be traced back individually afterwards.
- Changes that are traceableEvery change has a requester, an approval and a fallback, inside a recorded window so services to the public are not affected by it.
- Role-based access and rightsAccounts and rights follow the role, with multi-factor authentication and immediate closure when permanent or contracted staff leave.
- Logging that survives an auditRecording who could reach what and when, retained and searchable in a way that handles an audit or an information request.
- Backup and recoveryCopies that have demonstrably been restored, with recovery times agreed per system in advance rather than discovered afterwards.
- Built to be handed overDocumentation and access that are complete at the moment the contract moves, so a tender does not cost you your institutional knowledge.
How we take over a public sector environment
In this order, because here a surprise during the transition hits services to the public directly.
Walking the floor
At the counter, in delivery and in the office. An hour walking along shows more than three meetings, especially the workarounds people invented themselves when something did not work.
Mapping the chain and the frameworks
Which systems hang together, which link is fragile, and what BIO, the GDPR and possibly NIS2 require. That decides where we start.
Setting priorities and windows
Which services are critical, what response time belongs to them and when nothing may be touched. That goes into an SLA in plain language, including 24/7 cover where it is needed.
Steering on what we see
The reporting shows volumes, lead times and recurring causes per department or location. Those figures exist to improve your environment, and they can be used in your own accountability.
The services that come up most here
These building blocks come up most often in a public sector environment.
Looking further
Recognise the picture but work in another industry? Have a look at the other sectors.
Tell us which services cannot go down
Name the systems the public or your colleagues are waiting on, and the frameworks you work inside. We build the cover, the record keeping and the maintenance window around those.