What You Should Receive When Your Business Website Is Handed Over

A useful website handover gives you enough information to run the site, keep essential services renewed and get help when something stops working. You should leave knowing which accounts matter, what your team can change and who is responsible for the work you will continue to need.

Ask for a short demonstration as well as documentation. Finding the renewal contact, making a safe draft edit and tracing a test enquiry will reveal gaps that a folder of files can leave hidden. The aim is to accept a website your business can operate within the arrangement you agreed with its delivery team.

Get a record of the systems behind the site

Start with the website address and work through the services that support it. Domain registration, hosting, content editing, business email and booking or enquiry tools may involve different providers. Record which ones are actually in use; do not assume that the company sending the website invoice supplies every service.

For each system, ask the delivery team to document:

• The service name, its purpose and the correct account or sign-in address
• The business account holder and the person responsible for administration
• Who receives renewal notices and who approves or pays the bill
• The renewal date or billing cycle, verified in the relevant account or agreement
• Who provides support and where the operating instructions are kept

Add important dependencies in plain language. For example, the website's contact form may use a separate delivery service, or a booking button may lead to a separately billed platform. Knowing about that dependency helps the next person investigate a problem without assuming that everything lives in the website editor.

Keep this record in a business-controlled location where the people responsible can find it. A handover document that only a departing contractor can access does not help the owner handle the next renewal.

Be precise about the domain relationship

Identify the domain registrar and the account used to manage the registration. ICANN's registrant guidance explains that a registrant registers a domain through a registrar and manages its settings through that relationship. Ask the delivery team to show where your registration and renewal information are recorded without changing them during the review.

For a .CA domain, CIRA distinguishes its role as registry operator from the registrars that sell domain registrations. CIRA's presence in the domain system does not tell you which company your business pays or which account receives renewal notices.

The practical handover question is simple: if a renewal notice arrived today, would the right person see it and know what to do? Verify the answer from the account or billing record rather than relying on a remembered provider name.

Separate access, agreed rights and operating responsibility

Being able to sign in answers an access question. It does not, on its own, answer which files, licences, content or deliverables your agreement allows you to use elsewhere. Ask the supplier to point you to the relevant terms and explain what has been delivered. Unresolved contractual questions may need appropriate professional advice.

The technical record should also say what can be exported, in which format and who would help with a move. Ask for an accurate account of the platform in use. A content export and a complete, independently deployable website may be different deliverables; do not assume every hosted platform supplies the latter.

Operating responsibility needs its own answer. Who updates the software where updates are required? Who changes business hours? Who investigates a failed form? A provider may supply some of those services under a separate arrangement. Put the confirmed scope and exclusions in the handover record instead of treating the word “support” as a complete description.

Keep credentials out of the handover document

Use the document to record where access is managed and who is responsible, not to collect passwords, recovery codes or payment details. Ask the provider to use the platform's supported account invitation or approved access-transfer process where available. The business should complete sensitive account steps through its established secure process.

ICANN's account-protection guidance advises protecting domain-account login details and keeping the associated contact addresses current. Although that article is older, those are the limited points relevant here; use your current provider's instructions for any account changes.

Do not cancel an old service or remove someone's access simply to make the handover look finished. First establish the dependencies, the replacement arrangement and who has authority to make the change. The acceptance review can identify those actions without carrying them out on the spot.

Rehearse five everyday tasks

Arrange these demonstrations with the delivery team. Use an agreed preview or test environment where available and stop before an action would publish unwanted content, charge money or disrupt a live service. Write down what you actually observed. “Not demonstrated” is more useful than an assumed pass.

The recovery demonstration is deliberately limited. Seeing a backup label does not establish that every necessary component is included or that a restore would work. If a recovery test is part of the delivery agreement, ask for its evidence and limitations. Do not restore over the live website during a general handover call.

Likewise, one successful draft edit does not prove that the owner can change every page. Record which areas are editable and which require the delivery team. Training is most useful when it follows the work the business expects to do, such as changing hours or updating a service description.

Turn unfinished items into named follow-ups

Consider a fictional handover where the manager can edit page text but nobody can identify who receives the domain renewal emails. The design may be accepted while the renewal responsibility remains unresolved. Record the missing information, the person investigating it and when the business expects an answer. Do not hide it in a general “handover complete” note.

For every unresolved item, distinguish the missing document, access problem or untested behaviour. Attach the relevant evidence without including secrets. The delivery team can then respond to a concrete request rather than a broad complaint that something feels incomplete.

Before the final handover meeting ends, confirm where the latest record will live and who will keep it current when staff, suppliers or billing arrangements change. Include the agreed support terms and any known limits. A future colleague should be able to understand the arrangement without reconstructing the project from an email chain.

If you are planning a new site, raise these requirements while discussing ZXP's website services. Naming the owner tasks and handover evidence early gives the project a clearer finish line.