For a US agency using a remote developer, receiving files is one milestone. The next team also needs a repeatable way to run them.
List the source repository, domain, hosting and third-party accounts.
Confirm the intended owner can administer each one.
Keep source, history and open issues together.
With GitHub, review access after a transfer: existing collaborators can remain.
Document runtime versions, installation and configuration names.
Share secret values through secure access, not a public README.
Record payment, email and API integrations, licence owners and renewals.
Note who receives alerts when one fails.
Have the receiving team build staging, change a test page and practise rollback.
Record any steps that still depend on memory.
Before accepting a website handover, check ownership, build instructions, integrations, deployment and the team's ability to make a small release.
Editorial review by Mesh Creation ยท 2026-10-03
The cover illustration was generated with AI.
More storiesFinish with verified access, a working release guide and named support owners. The handover should survive a developer's absence.