Website handover checklist for agencies and freelancers
The site is live and the client is happy. What happens in the next week decides whether they can run it without you, and whether you get a panicked call in eight months when the domain expires. This website handover checklist covers everything to hand over, grouped so you can tick it off on the page, plus a handover email you can copy and the checks to run before the final invoice goes out.
What a good handover gives the client
A handover is the moment the site stops being your project and becomes the client's asset. Done well, they own every account that matters, know what renews when, and can make simple changes without calling you. Done badly, the domain sits in your registrar account, the font licence is in your name, and nobody knows where the contact form sends its messages.
It also protects you. A clear handover marks the end of the project, starts a support period with known limits, and leaves a written record of what was agreed and approved. That record is what you point to when a request comes in six months later that sounds like a bug and is really new work.
The checklist below is tickable. Your progress is saved in your browser, and Copy as text gives you the whole list to paste into a project doc or ticket.
1. Final sign-off and project records
2. Domain and DNS
3. Hosting, CMS and admin accounts
4. Analytics and Search Console
5. Backups, security and SSL
6. Forms, email and integrations
7. Subscriptions, renewals and licences
8. Training and documentation
9. Support and warranty
10. Design files and source
Ownership is the part that goes wrong most
Most handover trouble traces back to one habit: setting things up in your own accounts to save time during the build. The domain goes in your registrar account because you had a card handy. The premium plugin uses your agency licence. The map key sits in your cloud account. All of it works on launch day, and all of it becomes a problem the day the client moves to another agency, or your card expires.
The fix is to set up accounts in the client's name from the start and invite yourself as a user. Where that wasn't possible, move each one before handover, and check that the client has logged in to it themselves. For Google Analytics, that means the client holds the Administrator role, since that is the role that can add and remove users. For Search Console, the client should be an owner of the property, so they can manage who else has access.
If you agree to keep paying for something and recharge it, such as a font licence or a managed hosting plan, write that down in the renewals table with the price and the notice period for moving it.
Before you send the final invoice
Run these in order. Each one is quick, and each one prevents a common reason a final payment stalls.
- Confirm the final sign-off covers the version that is live now, and that any changes made after it were approved too.
- Ask the client to log in to the registrar, hosting, CMS and analytics, and to reply once each one works. Don't take "I'll check later" as a yes.
- Send a real test through every form and confirm the client received it.
- Check that nothing on the renewals table is still billed to your card without an agreement.
- Share the backup and the editable files, and confirm they open.
- Set the support period dates, so the invoice and the warranty start on the same day.
Once all six are done, send the invoice with the handover email or straight after it. A client who has just logged in to everything and seen the full list of what they own is in a good frame of mind to pay.
A handover email you can copy
Keep it short and put the detail in a linked document. Adjust the names and dates.
Subject: Your website handover: logins, files and support
Hi [Name],
The new site is live and signed off. Here is everything you now own,
and how to reach it.
Accounts (you're the owner on each, please log in and reply to confirm):
- Domain: [registrar], renews [date]
- Hosting: [host], renews [date]
- Website editor: [CMS link]
- Analytics and Search Console: invites sent to [email]
Also in the handover doc: [link]
- Renewals table with every paid service and its date
- Backup from [date] and how to restore it
- Font, plugin and photo licences
- Editable design files
- Walkthrough video ([length] minutes)
Support: we fix any bugs in our work until [date]. New pages,
features and content changes are quoted separately.
To report something, reply to this email with the page link and
what you expected to see.
Thanks for working with us,
[Your name]
Send the passwords separately, through account invites or a password manager, and leave them out of this email.
Keeping a record of what was agreed
The support period only holds if both sides can see what was approved. "That button was always meant to do X" is hard to answer from a pile of emails. It is easy to answer when the feedback and the final approval sit on the page they were about.
This is where HTMLAnnotate fits into the handover. Send the client a review link to the live site for the final check. They click anything to comment, with no account, and press Approve when it's right. Each approval belongs to the version it was given on, the manage page shows who approved and when, and you get an email the moment it happens. If you push a fix after approval, upload or fetch the new version on the same link and ask for approval again. Earlier versions keep their comments, and you can export everything as a CSV to store with the project files. Free links last up to 14 days, so export the CSV before you close the project or use a paid plan where links don't expire (see pricing).
The same history helps earlier in the project. Our guide to getting client approval on a website covers sign-off at each stage, how many revision rounds to include explains how to keep each round in one place, and the website launch checklist covers the checks that come just before this one. You can try the review side on the free live demo first.
Questions
What should be included in a website handover?
A record of the final sign-off, access to and ownership of the domain, hosting, CMS, analytics and Search Console, backups with restore steps, a list of every subscription and renewal date, licences for fonts and images, editable design files, a short training session or video, and a written support period. The checklist on this page groups all of it.
Who should own the domain name, the agency or the client?
The client, in a registrar account in the client's name and paid with the client's card. If you registered it for them during the project, move it into their account before handover. You can be added as a user or given the login for support, but the account itself should belong to them.
How should I send passwords to a client?
Avoid plain email and chat messages. Better options are inviting the client as the owner of each account so they set their own password, or sharing entries through a password manager. Once the client has logged in, ask them to change any password you created.
How long should a website support or warranty period be?
Thirty days is a common starting point for small business sites, and larger projects often use 60 or 90. Whatever the length, write down what it covers (bugs in your work) and what it doesn't (new features, content changes, problems caused by plugin updates or edits made by others).
Should I give the client the design files?
If your contract says the client owns the work once paid, yes, in an editable format they can open, such as a shared Figma file or a copy moved to their workspace. Agree this in the proposal so neither side is surprised at the end.
When should I send the final invoice?
After the client has signed off the final version and confirmed they can log in to the accounts you handed over. Sending it with the handover email works well, as long as the access checks are done first.
How do I prove the client approved the final website?
Keep a dated record of the approval on the exact version that went live. In HTMLAnnotate the client presses Approve on the review link, each approval belongs to the version it was given on, and the manage page shows who approved and when. Export the comments as a CSV and store it with the project files.
Get the final sign-off on the live page. Send a review link, let the client comment and press Approve, and keep the record of who approved which version.
Start a free review