GuideSoftware
Software handover checklist
By Inara Crest Engineering 1 min read
Source code, credentials, documentation, environments and support arrangements — what you should receive when a system is delivered.
When a custom system is delivered, make sure your organisation can run, support and change it — whoever built it.
1. Code and ownership
- Access to the source code repository, in your organisation's name.
- Confirmation of who owns the code and any licences for third-party components.
2. Environments and credentials
- Hosting accounts, domains and databases in your organisation's name.
- Administrator credentials stored in your password manager.
3. Documentation
- How to deploy, back up and restore.
- Architecture overview and integrations.
- User guides for each role.
4. Testing evidence
Acceptance test results and known issues.
5. Support arrangements
Response times, how to report issues, and the cost of changes.
See our software delivery approach.
About the author
Inara Crest Engineering
Engineering team
Written by the Inara Crest Technologies engineering team, who design, install and support software, network, security, power and data centre systems for organisations in Kenya and East Africa.