Quick answer
A website handoff gives its owner the access, documentation, and recovery information needed to operate it. Domain ownership, hosting, software licenses, and content rights are separate items that should be identified explicitly.
Before you begin
List responsibility for domains, hosting, website administration, email, analytics, payments, and integrations. Use business-owned accounts where practical.
What to do
- Confirm business control of the domain and current renewal contacts. Record where DNS is managed without putting passwords in the handoff document.
- Create individual user access with appropriate permissions. Remove temporary project access no longer required after the agreed handoff.
- Record platform, theme, important plugins or apps, license ownership, renewals, custom code, and external services. Note dependencies on supplier-owned licenses.
- Request editing instructions and a release record. Identify the source repository or deliverable package when included in the agreement.
- Confirm backup coverage, recovery procedures, support channels, and maintenance arrangements. Assign monitoring for forms, renewals, and connected services.
How to check the result
Someone outside the build team should be able to locate the correct account and request help. Confirm that the owner can sign in and perform a routine edit using the intended role.
If you need help
For an account owned by a former supplier, request documented transfer or access review before creating duplicate services. Store recovery codes and private keys securely, not in a public file or general AI conversation.
Related help
- Review who has access to your website and connected services
- Track plugin, theme, and app licenses for your website
- Check that a WordPress backup includes files and database
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
