- Handover is the day the agency stops being the default owner of your site. Plan it like a launch.
- Every account should be in your company's name, with two admins from your team. The agency stays as a guest you can remove.
- Editors need training on real tasks, plus written CMS rules for slugs, images and publishing.
- Get a written map of every form, where its leads go and who is told, and test each one.
- Keep a who-to-call list with the support window, what it covers and what happens after it ends.
The short answer
A website handover is the day the agency stops being the default owner of your site. On that day, your team should own every account in the company's name, have editors trained on real tasks, have written CMS rules, know where every form sends leads, be able to test tracking, hold the redirect list, know how to roll back a bad change, and have a list of who to call for what.
This is not the same as a launch. Our launch checklist makes sure the site works. Our post on what breaks after launch covers the routine that keeps it working. This checklist sits between them: it makes sure your team can run it.
1. Accounts and ownership
The rule: every account is owned by the company, with at least two admins from your team. The agency gets a role you can remove later.
| Account | Check |
|---|---|
| Domain registrar | Company login, auto-renew on, billing card current |
| DNS | You can log in and see the records; export a copy |
| Site platform | Webflow Workspace and site plan, or the code repository and host, owned by the company |
| CMS | For a headless CMS such as Sanity, your team holds admin on the project |
| Analytics, Tag Manager, Search Console | Your team is admin; the agency is a user |
| Forms, CRM, email tool, automations | Company login; note any API keys and who created them |
| Design files | Figma files moved to your team's space |
| Fonts, stock images, paid plugins | Licences in the company's name |
Watch for keys and automations created under an agency person's own login. They stop when that person's access is removed. Check renewal dates for the domain, the site plan and any paid tools too, and put them in a shared calendar, so nothing lapses because the reminder went to someone who left.
2. Editor training on real tasks
A tour of the CMS is not training. Ask the agency to watch each editor do these tasks themselves:
- Change a line of copy and a button link.
- Swap an image, with alt text.
- Publish a blog post, then unpublish it.
- Build a new page from existing sections.
- Send a preview or staging link to a colleague.
- Undo a change.
Record the session. A short recording of a real task is easier to come back to than a long manual.
3. Written CMS rules
Most damage after handover comes from small edits nobody agreed on. Write these down in one page:
- Who can publish, and who only drafts.
- Never change a published URL without adding a 301 redirect.
- Image sizes and formats for each slot.
- Which fields are required for SEO: title, description, social image.
- How to retire a page: redirect it, do not just delete it.
- What not to touch: global styles, components, custom code, without asking first.
4. Forms and where leads go
Ask for a form map, and test every row on handover day:
| Form | Page | Goes to | Who is told |
|---|---|---|---|
| Contact | /contact | CRM, with source | Sales inbox |
| Demo request | Pricing, product pages | CRM and calendar tool | Account owner |
| Newsletter | Footer, blog | Email tool | Nobody |
Change the "who is told" column from agency people to your own before they leave. A form that thanks the visitor but tells nobody is the most common quiet failure.
5. Tracking you can test
Get a list of every conversion the site tracks, where it is set up (in the site code, in Tag Manager or in the analytics tool) and how to test it. Then complete each one yourself and watch it arrive. Ask how consent affects what is recorded. Our tracking setup guide lists what a sound setup includes.
6. Redirects, SEO and backups
- Redirect list. Get the full list as a file, and know where it lives on your platform.
- Sitemap and robots. Know the sitemap URL and confirm it is submitted in Search Console.
- Rolling back. On Webflow, someone on your team should know how to save and restore a backup. On a code site, someone should know how to roll back a deploy, or who to ask.
- Content export. Know how to export CMS content, so a copy exists outside the platform.
The handover pack
Ask for these in one shared folder, owned by your company:
- Systems map. One page listing every tool the site touches and what it does.
- Access list. Every account, its owner and its admins. Logins shared through a password manager, never in email or chat.
- Form map and tracking list, from the sections above.
- Redirect file and the sitemap URL.
- CMS rules and the training recordings.
- Known issues. Anything left open, with a plan for each.
- Code notes, for a code site: how to run it, how to deploy, where secrets are set.
7. Who to call
| Problem | First call |
|---|---|
| Site down or showing errors | Host or platform status page, then your developer |
| Domain or email not working | Whoever manages DNS |
| Leads not arriving | Marketing ops, then the form or CRM owner |
| A page looks broken | Your developer or agency |
| Copy or pricing out of date | Content lead |
Write down the support window too: how long it lasts, what it covers and what happens after. At Kookies, every project includes 30 days of support after launch for safe changes: copy, image, colour and link updates, and fixes to what we built. New sections and redesigns are quoted separately. After that, teams move to hourly work or a care plan, or run the site themselves.
A handover day agenda
- Walk the accounts table. Move ownership live, while everyone is on the call.
- Each editor does the training tasks, recorded.
- Read the CMS rules together and agree them.
- Send a test through every form and check it arrived.
- Fire each tracked conversion and watch it arrive.
- Confirm the redirect list and the sitemap.
- Save a backup or confirm the last deploy, as a known good point.
- Fill in the who-to-call table and share it with the team.
What to do next
Copy the accounts table into a shared doc and fill it in before your agency's last week, not after. If you are partway through a project with us, ask and we will run this agenda with your team. If not, tell us where your site is today.
Terms used: Core Web Vitals, AEO



