Website Ownership and Handover: What Your Business Should Receive

A website handover should give your business the access, files, documentation and agreed rights needed to operate its website and arrange future support. Confirm control of the domain, hosting, editing tools and connected services; collect the agreed source and content deliverables; and verify billing, recovery and maintenance responsibilities. A homepage that loads successfully is only one part of delivery.

Agree these items before work starts, then check them with the provider at handover. Access, ownership and permission to use an asset are separate questions. Ask the provider to document each clearly rather than assuming that one administrator login answers all three.

Start with an account and asset register

Create a list of the services and materials the website depends on. For each one, record the account holder, business administrator, billing contact, renewal date, support contact and recovery route. Store credentials through an agreed secure process, separately from the register.

Some services may sit within a provider’s managed account. Ask what your business can access, what the service includes and how an exit or transfer would work. Record any transfer limitations before accepting the arrangement.

Item	What to collect	How to verify it
Domain and DNS	Registrar, registered holder details, DNS provider and responsible contacts	An authorised business representative can reach the relevant account and confirm details
Hosting or website platform	Account details, plan, billing and support arrangement	Confirm the site, subscription and appropriate administrative access
Content editing	Named accounts, roles and editing instructions	Your editor can update a test page and preview the result
Code and build files	Agreed repository or archive, dependencies and deployment instructions	A developer can identify the source corresponding to the delivered version
Design and media	Agreed editable files, final assets and usage information	Check that the files open and the usage terms are documented
Connected services	Form delivery, booking, analytics and other relevant accounts	Trace the normal journey and confirm the responsible administrator
Recovery and support	Backup arrangements, recovery instructions and support contacts	Complete an agreed recovery check and document unresolved gaps

This register describes operational control. The project agreement should separately state what is assigned, licensed, retained by a provider or supplied by a third party.

Confirm the domain, DNS and business email dependencies

Know where the domain is registered, who is recorded as its holder and who receives renewal notices. ICANN’s domain registration overview explains the roles of the registrant, registrar and registry. Use your registrar’s own account information and procedures for the domain you actually hold.

DNS directs services associated with your domain, potentially including the website and business email. Record who manages it and which services depend on it. A handover does not automatically require moving the domain or changing DNS. Arrange any genuine change with the responsible provider and verify the affected services afterwards.

Use business-controlled recovery contacts where supported. If one departing employee or supplier is the only person who can recover a critical account, resolve that dependency as part of the handover.

Ask what the delivered files allow you to do

For a custom implementation, agree which source files, repository access, configuration instructions and build steps are included. A folder of generated website pages may be deployable but insufficient to recreate the original editing or build workflow. Ask which version matches the delivered site and who can maintain it.

For a hosted website builder, confirm what can be exported, what remains dependent on the subscription and what would need rebuilding on another platform. The correct deliverables depend on the platform and agreement; do not assume every website has a portable source-code package.

Include approved copy, original media supplied by the business and any editable design files agreed in scope. Ask for an asset and licence list identifying third-party fonts, photographs, themes, plugins and other dependencies. Record restrictions, recurring charges and any licences that need replacement if the provider changes.

For disputed ownership or assignment language, ask an appropriately qualified adviser to review the actual agreement. This checklist helps you identify the questions; it does not establish legal ownership of a particular asset.

Prove that your team can manage everyday tasks

Schedule a practical walkthrough with the people who will update the website. Ask them to complete normal tasks themselves: revise opening hours, change a service description, replace an image and preview a page before publishing.

Give each person the access appropriate to their responsibilities. Include instructions for inviting and removing users, handling account recovery and requesting help. Confirm which changes need developer support so that an editor does not discover those limits during an urgent update.

If the project is still being scoped, include these editing and training requirements in your website brief. That article covers the wider planning document; this checklist verifies the deliverables and operational control at handover.

Verify forms, integrations and measurement

Use agreed test data to check that an inquiry reaches its destination, confirmations are understandable and the right team receives notifications. For booking or other third-party services, document where the website’s responsibility ends and the provider’s begins.

Confirm access to the business’s existing analytics and search tools where these are included. Record what has been configured and what remains unverified. Google’s SEO starter guide provides a foundation for discussing search setup; receiving an account or sitemap is not a guarantee of indexing or rankings.

Keep private keys and credentials out of public repositories and ordinary handover notes. Arrange their transfer and any necessary rotation through the agreed access process, while checking that connected services continue to work.

Document recovery, recurring costs and support

Record what is backed up, where copies are kept, who can access them and how restoration would happen. A backup status message is different from a demonstrated recovery procedure. Agree an appropriate restore check with the technical provider in a suitable test environment.

List subscriptions and renewals separately from the original project fee. Include hosting, domain registration, paid extensions, booking services and any ongoing support arrangement that applies. Identify the payer, renewal date and consequence of cancellation.

Ask what the support agreement covers, how to report an issue, when support is available and how additional work is approved. Record known issues and the people responsible for them. Avoid leaving “maintenance included” undefined.

Use a short acceptance record

At the handover meeting, record each item as verified, outstanding or not applicable. Add the evidence, owner and due date for outstanding work. An unresolved item should remain visible rather than disappearing into a general “website complete” statement.

• The business can access the agreed accounts and recovery routes.
• Delivered files match the scope and can be opened or used as intended.
• Content and third-party usage information have been supplied.
• An editor has completed the agreed everyday tasks.
• Forms, external handoffs and notification delivery have been checked.
• Backup and recovery responsibilities are documented.
• Recurring costs, support boundaries and known issues are recorded.
• Provider access to retain or remove has been agreed and reviewed.

Do not remove a supplier’s access until the necessary operational responsibilities and replacement access are confirmed. Agree the transition so there is a clear person to contact if a service stops working.

Make handover part of the development scope

Handover is easier to verify when deliverables and responsibilities are agreed at the beginning. Our web development service connects implementation, testing, documentation and delivery. The wider digital experience approach connects those delivery decisions with the website’s purpose and visitor journeys.

Discuss your website delivery and handover requirements with OctalFox. Share your platform, the stage of the project and the access or documentation you need clarified. We can help define a practical handover scope without assuming that every site needs rebuilding.