ChecklistLab

Client Ops

Website Handover Checklist

A website handover turns a finished build into an owned, maintainable asset. This checklist helps you transfer access, documentation, training, support expectations, and final acceptance without leaving the client dependent on scattered messages.

Use when: A website project is approved and ready to move from build mode to client ownership.

Best for: Freelancers, agencies, and small teams handing a website to a client, owner, or internal operator.

Start with: Access inventory. The client cannot own the site if the accounts and responsibilities are unclear.

Then review: Client Onboarding Checklist for the opposite end of the project lifecycle.

Copy workflow

Access transfer

Handover starts with account control. Make sure the right person owns every critical account.

  • Transfer or document access for hosting, domain registrar, CMS, analytics, tag manager, forms, CDN, and email tools.
  • Remove temporary developer accounts or reduce them to the agreed support role.
  • Confirm two-factor authentication and recovery email ownership.
  • Store credentials in the client's password manager, not in email threads.
  • List which accounts are owned by the client versus managed by the vendor.

Documentation pack

Documentation should explain how the site works without turning into a 60-page manual no one reads.

  • Create a concise site overview: platform, hosting, theme/framework, plugins, integrations, and key dependencies.
  • Document how to edit common content types: pages, posts, menus, images, forms, and metadata.
  • List recurring tasks: updates, backups, analytics review, content refresh, and broken-link checks.
  • Include support contacts for hosting, domain, email, and any paid tools.
  • Add a change log for launch decisions that may matter later.

Training and walkthrough

Training prevents basic update requests from becoming ongoing support debt.

  • Record a walkthrough covering login, dashboard orientation, page editing, form checks, and publishing workflow.
  • Show the client how to avoid common mistakes: oversized images, broken layouts, deleting required blocks, or changing slugs.
  • Explain what should require professional support rather than DIY edits.
  • Provide one practice task so the client can confirm they understand the workflow.
  • Save the recording and notes in a shared handover folder.

Ownership and maintenance

A handover should define who maintains the site after the project ends.

  • Clarify who owns updates, backups, plugin renewals, SSL, domain renewals, and monitoring.
  • Document recurring subscription costs and renewal dates.
  • Confirm backup schedule and restore procedure.
  • List known risks, deferred improvements, and non-critical issues accepted at launch.
  • Create a simple maintenance log template for future work.

Acceptance and support

Close the project cleanly so there is no ambiguity about what is included after launch.

  • Send a final acceptance checklist covering pages, forms, tracking, responsive layout, and key integrations.
  • Define the support window and what counts as a bug versus a new request.
  • Document outstanding exclusions or future-phase work.
  • Collect written signoff before archiving the project board.
  • Schedule a post-handover check-in if support is part of the agreement.
WEBSITE HANDOVER CHECKLIST

ACCESS
[ ] Transfer domain, hosting, CMS, analytics, and forms access
[ ] Remove temporary accounts
[ ] Confirm 2FA and recovery ownership
[ ] Store credentials in password manager

DOCUMENTATION
[ ] Create platform and integration overview
[ ] Document editing workflows
[ ] List recurring maintenance tasks
[ ] Add support contacts

TRAINING
[ ] Record walkthrough
[ ] Show common edit risks
[ ] Define DIY vs professional changes
[ ] Save notes in shared folder

OWNERSHIP
[ ] Clarify updates and backups owner
[ ] Document renewal dates
[ ] List accepted launch risks
[ ] Create maintenance log

SIGNOFF
[ ] Send final acceptance checklist
[ ] Define support window
[ ] Document exclusions
[ ] Collect written signoff

Next step

Use this next

Once the handover is complete, set up the recurring maintenance rhythm that keeps the website stable.

For scope boundaries, use the Scope of Work Template.

Website Handover Checklist FAQ

What should a website handover include?

At minimum: account access, documentation, training, backup and maintenance responsibilities, known limitations, support terms, and final acceptance signoff.

Should agencies keep admin access after handover?

Only if the support agreement requires it. Otherwise, reduce access or remove temporary accounts after the client confirms ownership. Lingering admin access creates security and responsibility confusion.

How do you prevent endless post-launch requests?

Define a support window, classify bugs versus new requests, and get written acceptance. Without that boundary, handover can turn into unpaid maintenance.