A website handover is complete when the business can recover access and keep operating without relying on one person. Ask for an ownership record and test each important account before the project closes.
Separate ownership from day-to-day access
Record the owner, recovery contact and delegated administrator for the domain, DNS, hosting, CMS and analytics. The agency can retain scoped access for maintenance while the business controls the account and its recovery methods.
Collect the materials needed for a change
Ask for the source location, deployment steps, design assets and a list of paid licences. Note which renewals transfer and which have to be purchased independently. Keep credentials in an approved password manager rather than in the handover document.
Ask someone to demonstrate recovery
Have an authorized person sign in, identify the latest backup and explain how to restore into staging. Verify the website can still receive an enquiry after a restore. Save a short record of what worked and who to contact if something fails.
Use a handover acceptance test
Pick a harmless change such as editing a staging page. Ask the business owner to grant access to a colleague, make the change and then revoke access. If any step requires an old employee’s account, resolve it while the project team is available.
Use one register for access decisions
For each service, write the account name, business owner, backup contact, renewal date, recovery method and whether vendor access should continue. Do not copy secret values into the register. Review it with the owner and verify the recovery contact is still someone the business can reach.
The website maintenance checklist covers what happens after handover. Our website development services can include documented ownership and operating steps in the build scope.
