Skip to content

Handover completion checklist

Align technical handover with Handover deliverables by defining what “done” means for an engineering team inheriting the repository. Legal sign-off may use separate Word/PDF packages; this checklist is for developers and operators.

#CriterionEvidence
1main branch builds and tests run per project policyCI logs or local bench run-tests output archived
2App installs on a clean Bench site following Deployment & operationsScreenshot or runbook entry
3docs/ site builds (pnpm / npm per docs/package.json)CI or local build log
#CriterionEvidence
4Root .env.example and docs/.env.example list names onlyFile review
5Environment & integration matrix reviewed for your tenantSigned row for each integration in use
6No secrets in git history for inherited default branchSecret scan report
#CriterionEvidence
7New developers can follow Start guide for day-one orientationWalkthrough with timestamps
8Critical integrations understood: Xero, Stripe, SingpassQ&A or short internal quiz
9Architecture decisions accepted or updatedPR or meeting notes
10DocType reference + Domain documentation strategy agreed for ongoing maintenanceTeam decision
#CriterionEvidence
11Whitelisted API inventory matches production exposureDiff review after deploy
12Guest endpoints hardened or network-restricted per policySecurity review ticket
13Security checklist items assigned ownersTicketing system
#CriterionEvidence
14Operational runbook exercised for migrate + rollback drillDated log entry
15Backups for DB + sites/*/private/files verified restoreRestore test record
#CriterionEvidence
16Test evidence & CI linked from your pipelineURL to workflow
17ERD / diagram package attached to formal archiveSame as commercial handover
RoleNameDate
Engineering lead
Operations
Security (if applicable)