Public Sector · Documentation
Technical documentation, training and handover.
Technical documentation, user manuals, training and a clean handover including access.
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 it covers
- technical documentation and architecture
- interface specifications
- user manuals
- administrator guides
- deployment instructions
- source code and access
- a handover record
Documentation is insurance against vendor lock-in
A system only its builder can maintain is a risk for the client - even when it works perfectly. The next tender can only be run if another supplier can understand what they are taking on.
- a description of the architecture and its dependencies
- a specification of the interfaces the system uses
- instructions for installing into an empty environment
- a list of environment settings and keys
- separate administrator and user guides
- a list of known limitations and open items
What must be handed over besides the code
A handover often consists of source code and nothing else. But without access, domains and keys, the system is not really in the client's hands.
- access to the repository, environments and databases
- ownership of domains and certificates
- third-party service accounts in the client's name
- backups and a demonstrated restore procedure
- a handover record listing what was transferred
- training for the system administrators
When clients come to us
- the system was handed over without documentation
- you are preparing a new tender and need the current state described
- the system administrator left and the knowledge went with them
- an audit requires handover evidence
What you receive
- technical documentation and an architecture description
- user and administrator guides
- deployment instructions and an access inventory
- training for administrators
- a handover record
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.