Public Sector · Digital Projects
Digital projects for public organisations.
A project can cover one or several lots - from a portal to an on-site kiosk.
When public bodies bring us in
- you're preparing a tender and need a supplier
- the project needs several disciplines at once
- an existing system needs extending or connecting
- a procedure needs digitalising from application to decision
- long-term support after handover is required
What this means for the contracting authority
- Traceability for every step of the procedure.
- Documentation that matches the tender requirements.
- One accountable partner even with several vendors.
- Acceptance testing against pre-agreed criteria.
- Support and development after handover.
Problem → solution
What a project can include
- web portals
- mobile applications
- internal applications
- digital records
- GIS and data visualisations
- user portals
- admin systems
- integrations
- APIs
- automation
- AI
- kiosks
- interactive displays
A tendered project is often several projects at once
Tender documents can combine, in one lot, a portal, an integration with a back-office system, on-site equipment and training. These are not related tasks; each has its own deadline, technical requirement and contact on the client side.
So we break the project into parts that can be accepted and tested individually, and set the order in which they can run.
- which part is a precondition for another
- where the project needs a client decision
- what can run in parallel
- what depends on a third party
- what is tested and accepted separately
What we look for in tender documents
Before responding we check the requirements that most often decide whether the deadline is achievable - not just the technical specification.
- whether access to existing systems is guaranteed
- who owns the source code at the end
- what the accessibility requirements are
- where the data may reside and where it is hosted
- what the warranty period covers and what maintenance covers
- what the acceptance criteria are for each lot
What you receive
- the project split into individually acceptable parts
- a schedule showing dependencies between lots
- delivery of the lots we are contractually responsible for
- coordination with the other suppliers on the project
- documentation and handover for each lot
How we run a public project
Requirements
Tender and technical requirements are translated into a delivery plan with milestones and responsibilities.
Project management
One contact, regular progress reporting and subcontractor coordination in one place.
Quality and security
Test scenarios, a security review and compliance with the client's requirements before acceptance.
Documentation
Technical and user documentation, instructions and training material.
Acceptance and SLA
Acceptance testing, handover and support with agreed response times.
Related work
FAQ
Do you help prepare tender documentation?
We can contribute to the technical part and clarifications, within public procurement rules.
Who manages the subcontractors?
We do. The client has one contact and one progress report.
What does post-handover support include?
Agreed response times, defect resolution and enhancements as agreed.
Related solutions
Sounds like your project?
Send us the project description, your existing system, the tender documents or the event date.