Admin access, content ownership, and maintenance plans that prevent post-launch confusion for internal teams.
Key facts - Topic: Handing a finished website to the client team - Must include: Account ownership, documentation, training, backups - Biggest risk: Credentials and knowledge held only by the agency - Related service: Web Development | /services/web-development
A website handover is the process of transferring full control and understanding of a finished website to the team that will run it. A good handover means the business can update, maintain and, if needed, move the site without depending on any one person.
What a complete handover includes
- Ownership: domain, hosting, repositories, analytics and third-party accounts registered to the business.
- Access: named admin accounts with strong authentication, and agency access removed or limited.
- Documentation: architecture overview, environment setup, deployment steps and integrations.
- CMS training: recorded sessions and short guides for common editing tasks.
- Backups: automated backups with a tested restore procedure.
- Maintenance plan: who updates dependencies, monitors uptime and fixes issues.
Check it before sign-off
Ask the team to publish a page, replace an image, restore a backup to a test environment and find the deployment instructions without help. If they cannot, the handover is not finished.
Frequently asked questions
Who should own the domain and hosting?
The business should always own its domain, hosting and code repositories, even when an agency manages them day to day.
What happens after handover?
Agree a support or maintenance arrangement so security updates, backups and small changes continue to happen.

