# Software handover checklist

Prepared by Yarify — https://yarify.cz
Contact: sales@yarify.tech

Project:
Version / release:
Delivering team:
Receiving team:
Review date:

For each item, record its location, responsible person, evidence checked, and any open action. Mark items that do not apply. Keep credentials and customer records out of this document.

| Item | Location | Owner | Verification / open action |
| --- | --- | --- | --- |
| Source repository and release version | | | |
| Agreed code rights and dependency licenses | | | |
| Architecture decisions and known limitations | | | |
| Service accounts, billing, and recovery contacts | | | |
| Configuration template and secure secret transfer | | | |
| Setup instructions checked in a test environment | | | |
| Release steps and post-release checks | | | |
| Recovery approach and limitations | | | |
| Data ownership and migration records | | | |
| API access, mappings, and failure recovery | | | |
| Backup owner and restoration verification | | | |
| Automated and manual test instructions | | | |
| Acceptance criteria and results | | | |
| Monitoring and incident contact | | | |
| Support scope and change request process | | | |
| Client communication owner, if white-label | | | |

## Handover rehearsal

- Who set up the application and in which test environment?
- Which checks did they run?
- Which release and recovery steps were verified?
- Which gaps prevent acceptance?
- Which follow-up actions were accepted, by whom, and for when?

This checklist is a planning aid. Project rights, acceptance, and support obligations depend on the agreed engagement.