BRÈCHE
Software handover acceptance record
Guide: /guides/software-handover-checklist
Updated: 2026-09-25

Record evidence that another developer can run and operate the product. Use pass, fail or unverified for each check.
Fill this in locally. Nothing is sent to BRÈCHE.
Do not include passwords, API keys, wallet recovery phrases or private customer data.

1. Release identity
Record repository, branch, deployed revision, environment and verification date. Can the deployed version be matched to the source?
Your notes:


2. Clean setup
Record tool versions and setup instructions. Name the person who followed them from a fresh environment and the result of the agreed checks.
Your notes:


3. Accounts and billing
For domain, hosting, data, email and integrations, record account owner, billing owner, access role and transfer status. No passwords.
Your notes:


4. Deploy and rollback
Record the staging deployment and rollback checks, their outcome and any limitations involving data or external systems.
Your notes:


5. Backup and restore
Name the backup owner, restore instructions and a restore test into an isolated environment. Do not treat backup existence as a passed restore.
Your notes:


6. Rights and dependencies
Link to the agreed rights for custom work and the inventory of libraries, fonts, media and hosted services with their terms.
Your notes:


7. Operations and recovery
Identify alerts, scheduled jobs, exports and important recovery procedures. Name the person responsible for each.
Your notes:


8. Open items and sign-off
List failed or unverified checks, known limitations, remaining work and its owner. Record exactly what is accepted and what is still open.
Your notes: