Website handover checklist

Download as Excel (.xlsx)

A clean handover protects both sides: the client owns and controls what they paid for, and the agency is not called months later about a password nobody has. Go through it together at the end of the project and sign it off. Download it as a spreadsheet.

Ownership and access

  • The domain is registered in the client's name and account — registrar login handed over
  • Hosting is in the client's account, or the arrangement is written down — who pays, who has access
  • DNS access is shared or transferred — and records are documented
  • Admin accounts for the CMS are created for the client — agency accounts removed or limited
  • Analytics, tag manager, Search Console and Bing Webmaster Tools are owned by the client — agency as user, not owner
  • Third-party services are in the client's accounts — e-mail sending, forms, maps, payment, CDN
  • Licences for paid themes, plugins and fonts are in the client's name — with renewal dates
  • Passwords are handed over through a password manager, not e-mail — and changed after handover

Documentation

  • How to edit pages, menus and common content — short guide or video
  • A list of plugins, integrations and custom code, and what each does — with reasons
  • Where backups are, how often they run and how to restore — tested once
  • The source code repository is transferred or shared — if custom code exists
  • Known limitations and open issues are written down — nothing left verbal

Quality

  • A final QA report is shared — functional tests, mobile layout, forms, speed
  • Open bugs are listed with priority and owner — in a bug tracker the client can read
  • SEO basics are in place — indexable, sitemap submitted, titles and descriptions
  • Accessibility basics are checked — keyboard, contrast, alt text, labels
  • Legal pages are published and reviewed by the client — privacy, cookies, terms

Support

  • Support or warranty period and what it covers are agreed — in writing
  • How to report a problem and expected response times — contact and channel
  • Who updates the CMS, plugins and server after handover — and how often
  • Sign-off by both sides — date and names