Industry
Public sector - digital solutions.
Procedures, records and services for citizens.
When clients usually bring us in
- the existing system no longer keeps up
- the work happens in spreadsheets
- data is duplicated across systems
- you need a new application
- you want to modernise an old system
- you're building a new digital product
What this means for you
- a solution that respects how your sector actually works
- we start with the part that pays off first
- one team for the digital and the physical side
What we can digitalise
- digitalising procedures
- citizen portals
- registers
- AI over documentation
- registry integrations
What we digitalise in a public environment
In a public environment every step of a procedure is defined in a regulation, so digitalisation is not free process design but a precise transfer of the existing procedure into a system - with its deadlines, permissions, exceptions and evidence.
That is exactly why, on such projects, how the requirements are written matters more than which technology is used.
- procedures with deadlines, states and responsible officers
- portals for citizens, companies and external stakeholders
- records and registers with an audit trail
- submission of applications, attachments and amendments
- notifications about status and deadlines
- reporting for management and oversight bodies
- AI over internal documentation for staff
- accessibility and keyboard-only use
How a public project differs from a private one
| What | In a public environment |
|---|---|
| scope | set out in the tender documents; changes go through a formal procedure |
| acceptance | against written criteria, with test scenarios and a formal record |
| documentation | part of the contract, not an extra |
| accessibility | a requirement, not a recommendation |
| personal data | purpose, retention and audit trail defined at design time |
| maintenance | contractual, with issues classified by severity |
A typical case
The example illustrates the type of task, not a specific client.
A public body receives applications by email and on paper and tracks deadlines in a spreadsheet. The system takes over submission with attachments, checks completeness automatically, assigns the case, tracks the deadline, informs the applicant of the status and leaves an audit trail for every step. A report on volumes, deadlines and backlog is available at any time.
How such a project runs
Process mapping
Breaking the regulated procedure into states, deadlines and responsible officers.
Requirements and criteria
Linking every documented requirement to an acceptance criterion.
Design and prototype
A prototype of the application form and the officer's view.
Phased build
Phased build with a working version at the end of each phase.
Rollout and support
Training, acceptance testing with key users and formal handover.
What you receive
- a working system in production, with a separate test environment
- documentation of the process, the rules and the integrations
- user guides and training for your team
- test scenarios and acceptance test results
- access, source code and data under the agreed model
- an audit trail and reports for oversight bodies
- evidence of accessibility and the security review
Signs that it is time for a change
- the procedure is regulated but runs in spreadsheets and email
- deadlines are tracked by hand and occasionally missed
- applicants cannot see what stage their application is at
- an oversight body requires an audit trail
- the existing system cannot be used without a mouse
- a tender is open and the deadline is short
How we work in this sector
Where we start
We look at which processes run manually, where data is duplicated and what would deliver the biggest effect.
First step
We start with a bounded scope that can be rolled out quickly and measured.
Scaling
Once the first part works, we add the next step of the process or the next location.
Support
After rollout we stay available with an agreed response time.
Related work
FAQ
Can you take part as a subcontractor?
Yes. We can take a single workstream within the lead contractor's structure - development, integrations, QA or documentation.
How do you ensure traceability of tender requirements?
Each requirement is linked to the implementation, a test scenario and an acceptance criterion, so it can be verified individually at handover.
Can the system run in our own infrastructure?
Yes. We work in the cloud, in your infrastructure or in a hybrid setup; the data and availability requirements decide.
Related solutions
Sounds like your project?
Send us the project description, your existing system, the tender documents or the event date.