Website handover checklist: what to give a client
A handover document lists every service behind the site, who owns each account, who pays, when each renews, and what the client must change, such as the card on file. Give it to the client before you remove your access, and keep a copy.
What goes in the document
Start from the client book, because it already holds most of this. For each client, list every service behind the site. For each service, write down:
- What it is and which site it belongs to: the domain, the hosting plan, the email, the certificate, the licences and any third-party service.
- The provider, and the account it sits in. Write the account identifier, which is the login email or username, and never the password.
- Who manages it, and who pays: you, the client, or a third party.
- The renewal date, and what it costs.
- Where the login is kept. A pointer to your password manager is enough for your own notes. The client needs their own access, set up in their own accounts.
Add the things that are not services: where the code and the backups live, who gets the contact form emails, and any scheduled jobs or integrations that someone has to keep running. Those are the items that surprise the next person.
In Yven, the services list is already this table. The export gives you a CSV with one row per service, which you can open in a spreadsheet, delete the columns the client does not need from, and send. Check the columns before you send it: your cost and any markup are private to you, and the client should not see them.
The order that avoids a lapse
Most handovers go wrong in the middle, when one account has moved and another has not. Do it in this order.
- Move the services you pay for first. If you rebilled a domain or hosting plan, the card on file is probably yours. Ask the client to add their own card, or transfer the account to them, before you remove anything. A service that renews on your card after you have left is a charge you carry.
- Check the renewal dates. If something renews in the next 30 days, settle who pays for that renewal in writing before the handover date, not after it.
- Give the client the document and walk through it once, by call or by email. They do not need to understand every line. They need to know it exists and where to find it.
- Bill the open work. Log anything still unbilled and send a final invoice. It is easier to settle this while you still have access and the client still remembers what you did.
- Revoke your own access last. Remove yourself from the registrar, the host and the other accounts only after the client has confirmed they can sign in to each one.
- Keep a copy of the document, with the date, in case a question comes up later.
Who should own what at the end
My default is that the client owns the domain registrar account and anything else that has their name on it. They keep the domain whatever happens to you, and there is nothing to untangle. The rebilling guide covers when it makes sense for you to hold an account, and what to write in the agreement if you do.
Services that were part of your own tooling, such as your hosting reseller account or your agency licence for a plugin, stay with you. The client needs an equivalent of their own, not a copy of yours. That means a new hosting account, or a licence bought in their name, and the site has to move across. Plan for that move, and price it, before you say yes to the handover.
What the client has to change
The document should end with a short list of what the client must do, because they are the only ones who can. The usual items:
- Put their own card on file at each provider, and keep it current.
- Add a second contact email at the registrar, so renewal notices do not depend on one person.
- Change the passwords you knew, and turn on two-factor sign-in where the provider offers it.
- Decide who handles small changes from now on, and tell you whether they want a care plan with someone else.
Be plain about the domain especially. A domain that lapses after a handover is the client’s problem, and also the first thing they will tell people about you. A line in the document that says “this renews on 14 March; the registrar emails the address above” costs nothing.
A short example
An invented client, a bakery, with one site. The document lists four rows. The domain is registered at the client’s own account, managed by you and paid by the client, renewing on 14 March. Hosting is on a plan you resell, managed by you and rebilled, renewing on 2 June. Email is on a separate provider, managed by the client and paid by the client. The booking plugin has a yearly licence in your agency account, paid by you and absorbed.
Reading that, the problems are plain. The hosting and the plugin licence are in your name, so both need to move before you leave, and the client needs to know the licence costs money each year. The domain is already safe. None of that is visible without the list, and it takes ten minutes to write.
Common mistakes
- Sending the document last. If the client first sees it on your final day, they have no time to ask questions. Send it a week ahead when you can.
- Assuming the client knows where the domain is. Many do not. Check that they can sign in to the registrar before you let go of your own access.
- Forgetting the small services. A forgotten email plan or a stray subdomain is what lapses a year later. Walk through the site’s DNS records and make sure each service there has a row.
- Leaving a service on your card. It will renew quietly, and the charge will be yours until someone notices.
Mark the services in your own records
When the handover is done, the services are no longer yours to track. Set each one’s status to Transferred if it moved to the client’s own account, or Cancelled if it was shut down. The help page on services lists the four statuses. Services marked transferred or cancelled stop appearing in your renewals, which is what you want: a reminder for something that is no longer yours is noise that hides the real ones.
Keep the client itself, and its work history, for as long as you need the records for your accounts. If you later part ways with the whole tool, not only one client, the export takes your whole book with you.
A handover that goes the other way
If you are the one receiving a site, the same list is your first-day checklist. Ask the previous person for it before you accept the job, and treat a missing answer as a risk to price. The client book you build on day one is this document, turned around.
How long it takes
For a client with a handful of services and a current client book, the document takes about ten minutes to produce and another half hour for the call. Without a client book it takes much longer, because you first have to find out what exists. That is the strongest argument for keeping the record as you go. Every service you log at setup is a row you never have to hunt for at handover, and the client gets a document that is accurate on the day they need it.
Where another tool is the better choice
If the handover includes a long technical migration, with servers, code deployments and database moves, a project plan from your hosting provider or an agency checklist will cover those steps better than a client book can. Yven records what exists and who pays for it. It does not move the site.
Where to go next
- The client book, for what to record about each client and site.
- Who pays for the domain? The money side of renewals and rebilled services.
- How to bill small website changes.
- All guides.