Website Handover Checklist: Domain Ownership, Access, Backups and Maintenance
When a business website goes live, its design may be finished while ownership and operational responsibilities remain surprisingly unclear. Who can renew the domain? Who controls DNS and company email? Where are backups stored, and who can restore them if the agency is unavailable? A launch is...
When a business website goes live, its design may be finished while ownership and operational responsibilities remain surprisingly unclear. Who can renew the domain? Who controls DNS and company email? Where are backups stored, and who can restore them if the agency is unavailable? A launch is not complete until the people who depend on the website can answer those questions. This guide is for company directors, marketing teams and agencies handing over a corporate website or a small online shop. It focuses on a practical, testable handover rather than a folder of passwords.
Start with an ownership and dependency map
Record the website domain, registrar, DNS provider, hosting or cloud account, content-management system, email provider, analytics, forms, integrations and paid plugins. For each, write down the legal or contractual account holder, the person authorised to make changes, the billing contact, renewal date and escalation route. A domain registered to an employee's private email is a different risk from a domain in a company-controlled account. Confirm who can prove ownership and regain access, not merely who knows the login today.
The UK National Cyber Security Centre advises small organisations to manage their public domain through an account controlled by the organisation and to protect privileged accounts: NCSC domain protection guidance. That is sound operational practice, not a substitute for checking registration contracts or a legal determination about intellectual property.
Separate registrar, DNS, hosting and website access
These are four related but distinct controls. The registrar manages registration and transfers; authoritative DNS directs traffic to web and mail services; hosting runs the application; and the CMS manages content and users. Putting them all under the label “website access” makes future incidents harder. A technician who needs to edit a page should not automatically receive the ability to transfer a domain or change mail routing.
Prepare a simple dependency diagram and preserve the current DNS records: A, AAAA, CNAME, MX, TXT and any relevant security or validation records. Check the real records against the intended configuration; a screenshot alone may become stale. Record where SSL/TLS certificates are issued and how renewal happens. If the website uses a CDN or reverse proxy, distinguish the public DNS target from the origin server and document the safe route for emergency changes.
Protect critical accounts without circulating shared passwords
Create named accounts where the provider supports them, use the smallest permissions that allow each job, and enable multi-factor authentication for the registrar, hosting and important administration systems. Keep recovery methods under company control and maintain an emergency owner account with a documented access procedure. The NCSC's website and email domain protection guidance describes the value of strong authentication and delegated access rather than routine password sharing.
Do not put passwords, API secrets or recovery codes into the handover PDF or an ordinary email thread. Use an approved password manager or the provider's invite system and verify that the new owner can sign in. Then revoke redundant temporary accounts and rotate shared secrets where necessary. Check agency access separately: ongoing support may require a maintained technical account, whereas project-only access should be removed once acceptance is complete.
Check billing and renewal before a disruption occurs
Make a schedule for domain renewal, hosting invoices, premium themes, plugins, backups, external APIs and email services. Confirm the payment method and who actually receives failure notices. The person who signed the development contract may not be the person who controls the credit card or accounts payable. Avoid making promises that a domain will be available indefinitely; renewals and provider rules still apply.
Registrar transfers deserve special care. For generic top-level domains, ICANN explains the role of an authorisation code in transfers: About Auth-Code. Transfer processes differ by top-level domain and registrar, so do not assume the same code or transfer timing applies to every UK domain. A change of hosting does not necessarily require a change of registrar. If no transfer is needed, a carefully documented DNS update may be the less disruptive route.
Deliver the website as a maintainable system
Handover material should include the production URL, CMS version, active theme, significant customisations, important plugins, environments and deployment procedure. Identify which components are licensed, which source files the client can access under the agreement, and whether the next developer will have the necessary build instructions. Do not say the client owns every third-party asset simply because it appears on the published website.
For a Webasyst or Shop-Script project, describe where the website theme and custom plugin changes live, how configuration differs between staging and production, how scheduled jobs are run and what should not be overwritten during an update. Document any connection to a payment provider, shipping calculation, stock feed or marketplace without exposing credentials. A small diagram showing which system is the authoritative source for each data field is often more useful than a large screenshot gallery.
Test backup and restoration, not just the existence of a ZIP
A backup checklist should cover application files, database, uploaded media, configuration and the version of the software needed to restore them. Record the retention schedule, storage location, access controls and restore owner. Keep copies in a location that is not lost if the production hosting account is unavailable. A successful automated-backup email only confirms a job reported completion; it does not prove that a usable site can be recovered.
Run a controlled restore test in an isolated environment. Check key pages, navigation, media, contact forms and login. If the handover includes an online store, confirm catalogue data, orders, stock states and checkout configuration using safe test procedures. Never route a staging environment to real customer payments or send transactional email to actual buyers accidentally. Log what worked, what failed and who will resolve the gaps.
Perform a realistic launch-acceptance walk-through
Ask the business owner to complete ordinary tasks without the original developer taking control: update a phone number, edit a service description, add a new page, view a form submission and confirm a renewal notice can be reached. A company should also test the website on a phone with slower network conditions, keyboard navigation, links from search results and a direct bookmark to an important service page.
Review search and measurement handover separately. Who controls Search Console and analytics properties? Is the business the owner or merely a viewer? Are consent settings and privacy notices documented for the actual setup rather than copied from a template? Check canonical URLs and any sitemap or redirects that were agreed. An analytics account is not proof that tracking correctly measures every enquiry; validate a small event sample and state what was not tested.
Define maintenance boundaries and incident responsibilities
After launch, someone must apply security updates, monitor uptime, investigate failed forms, renew services and respond to incidents. Agree which tasks are included in a support agreement and which are separately estimated. Specify contact methods, severity levels, responsibility for approving changes and an exit process. A vague “maintenance included” line is not enough to predict what happens after a critical plugin breaks.
Build a simple incident card: affected service, business impact, first contact, fallback contact, location of backup instructions and the person authorised to approve rollback or a DNS change. Do not publish sensitive incident details on the public website. Review the list when personnel, providers or systems change. A written plan is valuable only if the named people know it exists and can follow it.
Choose the handover depth that matches the project
A three-page brochure website does not require an enterprise operations manual. It still needs domain control, reliable access, backup instructions, billing ownership and basic editing guidance. A multi-language corporate site adds translation responsibilities and publishing checks. A complex store requires inventory, payment, customer-data and integration runbooks. Evaluate risk and complexity rather than copying every item from a generic template.
Use an acceptance table with an owner and result for each critical item: verified, awaiting action or not applicable. Include evidence dates and clear outstanding issues, then agree who signs off. Conclusion: a professional website handover is a transfer of operational capability, not simply delivery of a design. If your company is commissioning or rebuilding a website, Quadro Design's corporate website development service and project process provide relevant starting points for discussing a clear scope, launch checks and continuing responsibilities.