Website Handover Checklist for Small Businesses

A website handover checklist helps you confirm that your business can use, manage, and support its finished website. Before accepting delivery, collect the agreed accounts, files, instructions, and recurring costs. Then verify them yourself. A folder of documents is useful only if your team can complete the tasks it describes.

Website handover checklist: confirm account access

Ask your provider to list every service involved in running the site. For each one, record the account holder, the person responsible, your permission level, and the recovery contact.

Start with these categories:

• Domain registration and renewal.
• Hosting or the website platform.
• The content editor used for page updates.
• Analytics and search performance tools.
• Connected forms, booking systems, or payment services, where applicable.

Some services may sit inside a provider’s shared account. Ask what access your business receives and how a future transfer would work. Do not assume every account can simply be handed over.

Accept invitations using an account your business controls, and sign in independently. Seeing a dashboard does not necessarily mean you can manage users. For example, Google Analytics requires an Administrator role to add or modify users at the relevant account or property level.

Collect files your team can actually use

Request the deliverables included in your agreement: final copy, approved images, editable design files, and any agreed code or exports. Record where they live and open a sample from each group.

Ask which assets depend on subscriptions or licenses. A delivered image file does not, by itself, explain how you may reuse it. Keep the relevant usage information alongside the asset.

For a hosted website platform, ask what can be exported and what would need rebuilding elsewhere. Record the answer instead of assuming an export recreates the complete website.

Keep passwords and recovery codes in an appropriate password manager, separate from the general handover document.

Rehearse everyday tasks during the meeting

Use the handover meeting for your team to practice. The provider can guide you, but the person who will manage the website should perform the actions.

Try three exercises:

1. Prepare a content change. Update opening hours or a service description in a draft or preview, then explain how publication works.
2. Locate a customer inquiry. Send a clearly labeled test inquiry and find where it arrives, who receives it, and who should respond.
3. Find help. Show where to report a broken page, which details to include, and who handles the request.

For example, a studio manager might discover that they can edit class descriptions but cannot change the booking destination. Record who handles that change and how to request it.

If inquiries continue into a sales process, document that handoff too. Nexlab Business includes contacts, notes, stages, and commercial follow-up tools.

Agree on costs and continuing responsibilities

Create a short record of recurring services, renewal dates, billing contacts, and who approves changes. Separate included support from work that needs a new quote.

Name the person responsible for updates, backups, recovery, and urgent faults. Ask for written instructions or a short recording for tasks your team will handle.

When a previous provider’s access should end, review each service separately after replacement access works. Google’s Search Console guidance explains that removing a verified owner does not remove their verification tokens; remaining tokens can allow ownership to be verified again.

Finish with an unresolved-items list. Give each item a responsible person, a deadline, and evidence needed to close it.

Frequently asked questions

What should a website handover include?

Working access, agreed files, editing instructions, recurring costs, support contacts, and clear responsibility for ongoing tasks.

Is a website login enough for a handover?

No. Confirm what that login permits and whether your business can recover access, manage relevant services, and obtain support.

Can my agency keep access after handover?

Yes, when it remains responsible for agreed work. Record the access it needs and review it when responsibilities change.

Do I need the website source code?

That depends on the platform and agreed deliverables. Ask what you receive, what you can move, and what depends on the provider.

Accept delivery with clear responsibilities

Use your website handover checklist to verify access, practice essential tasks, and resolve missing deliverables. Explore Nexlab’s website options for businesses, then discuss access, support, and ongoing responsibilities as part of your project scope.