Blog · Delivery
Software Project Handover Checklist (So You Actually Own It)
Repos, cloud, credentials, docs, and runbooks — what to demand before the final invoice.
Last updated: November 2026
Many teams “go live” and still cannot deploy a hotfix without the vendor. That is not ownership. A proper handover is a deliberate phase with artefacts, access, and a short period where the builder supports your team while knowledge transfers. Use this checklist whether you work with Martvill or any other partner.
1. Source code and history
- Full Git repository access (not a ZIP on email as the only copy)
- Main branch protected; release tags for production builds
- README with how to run locally and required env vars (without secret values in Git)
- Licence notes for third-party packages
2. Environments and cloud
- Accounts under your organisation (AWS, GCP, Azure, Hostinger, etc.)
- Separate staging and production where the budget allows
- Domains, DNS, and SSL under your control
- Documented deploy steps (GitHub Actions, scripts, or panel steps)
3. Secrets and access
- Password manager or secrets store owned by you
- API keys rotated at handover; vendor personal keys removed
- List of admin users for app, DB, email, SMS, payment dashboards
- MFA enabled on critical accounts
4. Data and backups
- Backup schedule and restore test date (at least one successful restore drill)
- Where backups live and who gets alerts on failure
- Basic data dictionary: main tables/collections and what “customer” means in the system
5. Quality artefacts
- Known issues list (bugs deferred with reasons)
- Test accounts and UAT notes
- Critical path test checklist your team can re-run after changes
6. Operations
- Error monitoring or log access (even if basic)
- Uptime or health check URL
- Who gets production alerts on day one after handover
- Support window for hypercare (e.g. 2 weeks) written in the contract
7. Business continuity
- Admin manual for common tasks (refund, user disable, config flags)
- Contact tree: vendor escalation during hypercare, then internal owner
- Commercial closure: final milestone tied to checklist completion, not only “site is up”
What “good enough” looks like for an SMB
You do not need enterprise IT bureaucracy. You need the ability to ship a small fix, restore data, and understand who has the keys. If any of those three are missing, the project is not finished — regardless of the marketing launch date.
How we handle handover at Martvill
Handover items are part of the delivery plan, not an afterthought. We aim for your accounts, your repos, and written run steps. Optional retainers exist for teams that want ongoing help; they should be a choice, not a trap because access was never transferred.