# Handover checklist

SIT Consultancy — editable sample

Illustrative template, not a client deliverable. Adapt it to your project.

## Ownership

Name the business owner, technical owner, support contact and escalation route. Confirm who can approve releases, access changes and supplier costs.

## Code and environments

Transfer repository access, build instructions, environment inventory and deployment documentation. Verify the receiving team can build and deploy. Share credentials only through an approved secret-management process.

## Runbook

Document routine checks, monitoring, alerts, backup restoration, incident triage and rollback. Rehearse critical recovery steps and record results.

## Data and suppliers

Record approved data flows, storage, retention, integrations and supplier dependencies. Confirm account ownership, licences, renewal responsibilities and access removal.

## Knowledge transfer

Run a walkthrough of architecture and key workflows. Capture known limitations, unresolved risks and prioritised improvements. Record questions and owners.

## Acceptance

List deliverables received, evidence reviewed and exceptions agreed. Record the handover decision, named owners and the start/end of any agreed support period.