What a website handover should include
Scroll DownA launched website still needs people to look after it. A clear handover tells your team what they own, how to make ordinary changes and where to go when something needs attention.
Record ownership and access
Identify the owner of the domain, hosting, source repository and third-party services. Give people access appropriate to their responsibilities and agree on how access will be removed when someone leaves.
Document ordinary changes
Explain how to edit pages, replace images and publish content. Include any limits or review steps so the team can make routine updates confidently.
Explain releases and recovery
Document how code reaches production and how to return to an earlier version. Record backup responsibilities and how a restore will be checked rather than assuming that a backup setting alone is enough.
Check forms and integrations
List destinations for enquiries, payment events and other automated messages. Agree who watches for failures and how to test a connection after an important change.
Agree on continuing support
Separate fixes, content work, platform updates and new features in the support scope. Name the contact and escalation route so the business knows what happens after launch.
Put the plan into practice
Explore our cloud deployment & ai workflows service or discuss your project.