Software Handover Checklist: Access, Runbooks and Ownership

Identify the receiving team.

Ask who will operate, maintain and approve changes to the application after delivery. These may be different people. Confirm the information each person needs, from everyday user instructions to deployment procedures. Avoid assuming a developer’s knowledge will transfer automatically through a demonstration.

Walk through real operating tasks.

Use a controlled environment to rehearse routine support tasks, access changes and a release. Record dependencies and the route for escalation. Documentation should help the receiving team repeat an action, including how to check that it worked and what to do when an expected step fails.

Close the ownership gaps.

Confirm where source code, configuration instructions and support records are stored. Transfer access through approved channels rather than embedding credentials in documents. Finish with an agreed list of outstanding issues and responsible owners so that the end of delivery does not leave essential decisions unresolved.

Test the handover with the receiving team

List the tasks the receiving team must perform after delivery: deploy a change, configure the application, investigate a failure and find the right escalation owner. Prepare instructions for those tasks, then ask someone who did not write them to follow the steps in a suitable environment.

Record missing prerequisites, unclear commands and undocumented decisions. Check that repositories, environments and third-party services have appropriate organizational ownership. Transfer access through approved processes and confirm that obsolete project access is reviewed. Finish by agreeing acceptance evidence and the boundaries of any post-delivery support. A document being sent is not the same as a team being ready to operate the software.

A handover pack people can use

Organize the pack around tasks rather than a large unstructured folder. Keep links current and name the owner who maintains each part.

• Application overview: main workflows, components, dependencies and important design decisions.
• Setup and deployment: prerequisites, configuration names, environment differences and verification steps.
• Operational runbook: health checks, common failures, recovery guidance and escalation contacts.
• Data responsibilities: storage locations, access ownership and agreed backup or restoration procedures.
• Delivery evidence: test results, known issues, accepted limitations and outstanding work.
• Ownership record: repositories, third-party accounts, documentation updates and support boundaries.

Keep secrets out of the handover document

Document where configuration is supplied and who manages it, rather than embedding live passwords or tokens in a shared guide. A readable runbook should still be usable when a credential is rotated.

Avoid assigning support to “the development team” without naming the receiving role and the arrangement. Clarify response expectations, covered systems and exclusions. Keep known issues visible; hiding them in an old conversation creates uncertainty for the people taking responsibility.

When should handover preparation begin?

Start while the system is being built, especially for deployment and operational decisions. Update the pack as the implementation changes. Schedule a receiving-team walkthrough before final acceptance so missing information can be corrected while the delivery team is still available.

ILLUSTRATIVE PLANNING EXAMPLE

Example: handing over a web application

Ask the receiving team to deploy the application in a suitable test environment using the handover instructions. Check that they can locate configuration guidance, run agreed checks and identify the person responsible for an incident. Transfer credentials through an approved secure channel rather than placing them in a document or email.

Record missing instructions and resolve them before sign-off. Agree which support tasks are included after handover and which need a separate arrangement.

FURTHER READING

Official resources to explore

Explore the related official guidance below. The templates and examples are practical starting points to adapt to your own project.

• Microsoft: safe deployment practices