Resources  /  November 18, 2026

Client handoff checklist for agency website projects

A website launch is not the end of the job. A poor handoff leaves the client confused and your team answering the same questions for months. A good one leaves them confident, protects your agency and makes it easy to sell ongoing care. Use this checklist on every project.

Before launch day

  • Test everything one last time. Forms send, links work, the site looks right on phones, tablets and desktops, and pages load at a reasonable speed.
  • Check the basics for search. Page titles and descriptions, a sitemap, and that nothing is accidentally hidden from search engines.
  • Plan the move. If the site replaces an old one, match old pages to new ones and set up redirects, so visitors and search visibility are not lost.
  • Back up the old site before anything changes.
  • Confirm tracking. Analytics and any conversion tracking are installed and recording.

Access the client should own

  • Admin login for the website (with their own user, not a shared one)
  • Hosting account
  • Domain registration and DNS
  • Email accounts connected to the site
  • Analytics and Search Console
  • Any paid plugins, themes or licences, in the client’s name
  • Social, booking and payment accounts linked to the site

Put them in a password manager and share them securely. Never send logins by email or chat.

Files and documents

  • The final design files and brand assets
  • A copy of the site’s backup
  • A list of the plugins used, with what each one does
  • Any custom code or notes someone else might need later
  • The signed scope and what was delivered

Training and a short guide

A long manual goes unread. A two-page guide does not. Include:

  • How to log in and where to find things
  • How to edit text and images on the pages they will change
  • How to add a blog post or a product, if relevant
  • What not to touch, and who to ask
  • How to see form enquiries and where they go

A short video of the main tasks helps even more than a document.

Confirm the ongoing basics

  • Backups. How often, where they are kept and how to restore one.
  • Updates. Who updates WordPress, the theme and the plugins, and how often. Updates should be tested first.
  • Security. Who monitors the site and what happens if it is hacked.
  • Support after launch. Is there a period of free fixes? How are small changes requested and priced? Our website projects include 30 days of free fixes for anything in the original scope.
  • Care plan. Offer a clear plan so the site stays healthy. See what a care plan normally covers, or our white label maintenance service if you want to offer it under your own brand.

Agree what happens next

Before you close the project, book a short check-in a few weeks after launch. Ask what is working, what confuses people and what they would like next. It is often where the next project comes from, and it shows the client you did not disappear.

Extra care for sites with forms and email

Many handoff problems are about email. Before you finish, send a test through every contact form and confirm the message reaches the right inbox and not the spam folder. Make sure forms send through the client’s real mailbox using proper authentication, because mail that is sent from a website without it is often filtered as junk. Confirm who receives each form, and set up an automatic reply so visitors know their message arrived.

Extra care for online stores

If the site sells products, test a real order from start to finish: add to basket, pay, receive the confirmation email, and see the order in the admin. Check tax and shipping settings with an accountant if you are unsure, and show the client how to process, refund and fulfil orders. A store should never go live without a test order.

Common handoff mistakes

  • Handing over logins in an email thread
  • Leaving hosting or the domain in your own account with no plan to move it
  • Forgetting to remove staging copies and test accounts
  • Skipping redirects, so old pages disappear from search
  • Giving the client a manual so long they never read it
  • Never offering a care plan, so the site quietly falls out of date

A closing checklist you can copy

  1. Site tested on phone and desktop
  2. Redirects and search basics checked
  3. Analytics recording
  4. Client owns hosting, domain and licences
  5. Login details shared securely
  6. Short guide and video delivered
  7. Backups confirmed
  8. Update and support plan agreed
  9. Care plan offered
  10. Check-in booked

Related reading

Starting a relationship with a new developer? See our onboarding checklist. Wondering how a handoff fits into the whole process? Our how it works page walks through the steps from brief to launch.