How to use it
Work through it with the outgoing supplier and the team taking over, well before the end date. Give every item an owner and confirm it by doing it, not by being told it is done: deploy a change, restore a backup, rotate a credential.
The tone matters. Most gaps come from undocumented habits, not bad faith.
Access and accounts
- Cloud accounts: administrative and emergency (break-glass) access held by the organisation, not by named supplier staff.
- Identity provider and single sign-on administration.
- Domain registrar, DNS and TLS certificate management.
- Source code repositories, including organisation ownership and admin rights.
- Build and deployment systems (CI/CD), including stored credentials and runners.
- Monitoring, logging, alerting and ticketing tools.
- A plan to remove supplier access on an agreed date, and evidence that it happened.
Code and deployment
- Every repository needed to build the service is held by the organisation.
- The service can be built from source by the receiving team, from a clean environment.
- The receiving team has deployed a change to production, and rolled one back.
- Secrets and keys known to the supplier are rotated after transfer.
- Infrastructure is defined as code, or the gaps are listed.
Operations
- Runbooks for common incidents, releases and recovery, tested by the receiving team.
- Alerts route to the new owners, and someone is on the escalation path.
- A backup has been restored by the receiving team.
- Scheduled jobs, certificate renewals and other recurring tasks are listed with owners.
Knowledge
- Architecture decisions and the reasons behind them.
- Known issues, workarounds and fragile areas.
- Undocumented dependencies: other systems, people or manual steps the service relies on.
- Contacts at third parties the supplier dealt with.
Commercial and data
- Licences and third-party contracts held in the supplier’s name, and how they transfer.
- Data held by the supplier, and its return or deletion.
- Contractual exit obligations, such as handover support or document delivery.
Timing
- An overlap period in which both teams can work on the service.
- A clear date when responsibility transfers, agreed by the service owner.
- A final check of access and ownership after the transfer.