EMPHASOFT / WORKING TEMPLATE

Software project handover checklist

Verify ownership, access, deployment, recovery and support before accepting a handover.

Download blank HTML template

How to use: click in a bordered answer area and type. These pages do not submit or save your entries. Keep completed answers using your browser's Print → Save as PDF. Download the blank HTML to work in a local copy. Review the print preview before saving. An unanswered requirement remains open; do not treat it as a pass.

Product, release and receiving owner

Record evidence for each item

Use status Open, Accepted or Not applicable with a reason. Link to a safe evidence location; never paste passwords, API keys or private customer data into this sheet.

Item to verifyOwnerStatus and evidenceOpen action / due date
Repository, branches and build instructions
Code and design ownership; third-party licences
Cloud, domains, billing and account control
Access inventory and secret transfer via secure channel
Environment configuration and deployment runbook
Database schema and migration procedure
Backup and demonstrated restore procedure
Monitoring, alerts and incident contact
Critical journey tests and acceptance results
External integrations and renewal responsibilities
Known issues and accepted limitations
Support boundaries and response expectations
Independent deployment by the receiving team
Departing supplier access removed when agreed

Acceptance decision