PLANNING & MAINTENANCE · 3 MIN READ
What Should Be Included in a Website or Application Handover?
Plan a useful software handover covering code, accounts, deployment, data, recovery, and operating responsibilities so the business can maintain the product.
A handover is more than sending a ZIP file and a password. The business needs to know what it owns, where the system runs, and how a responsible person can operate or change it.
Plan those deliverables before launch rather than reconstructing them after a developer becomes unavailable.
01
Identify the assets and owners
List the code repository, domain, hosting, database, storage, email service, analytics if used, and external integration accounts. Record the business owner and the authorized technical contacts for each.
Keep secrets in an appropriate controlled system. Documentation should explain where credentials are managed and how access is granted, not reproduce every secret in an easily forwarded file.
Clarify ownership and licence terms through the project agreement. This technical checklist does not replace that agreement.
02
Make the code usable
Provide instructions for setting up a development environment, required runtime versions, configuration variables, and the build or test commands. Explain any private packages or paid dependencies that another developer will need.
If repository ownership changes, follow the provider's supported process. GitHub's transfer documentation describes consequences and requirements for repository transfers; review them before treating a transfer as a simple name change.
The test is practical: can an authorized developer obtain the code and run the application using the documentation?
03
Explain deployment and recovery
Document where the application runs, how a release is made, what checks follow it, and how a problematic change is handled. Include background workers, scheduled jobs, and external callbacks that are not obvious from the homepage.
For a hypothetical reporting portal, the web server may be healthy while the nightly import has stopped. The handover should identify that job, its owner, and where failures appear.
Record backup responsibilities and the evidence from a restoration test where applicable. Do not assume the hosting provider's general backup feature covers every required component.
04
Preserve data understanding
Describe important records, identifiers, integrations, and export methods. List known limitations and any manual processes still required.
Explain how staff correct mistakes and which operations need technical assistance. A new operator should not have to infer the meaning of a database field from a screenshot.
05
Close with an operating walkthrough
Walk through a routine update, a representative failure, and a common business task. Confirm that the intended owners can access the relevant systems.
Agree what support continues after handover and what requires a new scope. A successful handover reduces dependence on one person's memory while preserving a clear route for future development.
06
Discuss the implementation
Explore custom web applications or discuss an existing system.
KEEP EXPLORING
Sources & further reading
Official documentation for the topics discussed. Check implementation details against the versions and services used by your project.
PUT THE IDEAS TO WORK
Need help with
the implementation?
Explore the approach and scope for custom web applications.
Explore the service