Handing a website to a client: a checklist for training, access and editing rights
Short answer: A website handover is the moment an agency gives a finished site to the client: the accounts, the login details, the right to edit, and the know-how to use it. Do five things: put every account in the client's name, give each person the lowest role that lets them do their job, run one 60 minute training session on four tasks, hand over a one-page document, and get a written sign-off. Then offer a care plan for what happens next, such as updates, backups and small fixes, so nobody is left guessing.
You are about to hand a finished website to a client, and you want a checklist that covers accounts, training and editing rights so nothing is left unclear afterwards.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
A good handover answers three questions in writing: who owns what, who can change what, and who to call when something breaks. If the client cannot answer those after your session, the handover is not finished. The rest of this page is a checklist you can copy, a training plan, a document template, video ideas and a sign-off form.
It is written for an agency or freelancer handing over a business website, whatever platform it runs on. It is not legal advice. Put ownership and warranty terms into your contract and have a lawyer check them. For contract wording about AI-assisted work, see contracts between agencies and clients.
Step 1: put accounts in the client's name
This is the part clients most often regret. The rule is simple: the client owns the accounts that represent their business, and you hold a role in them.
| Account | Who should own it | What you keep |
|---|---|---|
| Domain name (the web address) | The client, at a registrar (the company that sells domain names) account in their name | Delegate or technical contact access, if the client agrees |
| Website platform or hosting | The client, or a transferable workspace you can move to them | An admin or editor role while you support the site |
| Google Analytics and Search Console | The client's Google account | An invited user role |
| Google Tag Manager and ad accounts | The client | An invited user role |
| Email sending (newsletters, form notifications) | The client | Access only if you manage the mail |
| Google Business Profile | The client | Manager role |
| Payment and booking tools | The client | As needed |
| Design files, images and fonts you licensed | Depends on your contract and each licence | Your own tools and templates |
Check the domain first. ICANN (the Internet Corporation for Assigned Names and Numbers, the body that oversees domain names) says a registrant (the person or company that registers a name) assumes sole responsibility for the registration and use of the domain, must give accurate WHOIS details (the public record of who holds a domain) and must respond to the registrar within 15 days. If your name is the registrant on a client's domain, the client does not control their own address. Look up the record before the handover and fix it. Also allow time: ICANN's transfer policy lets a registrar refuse a transfer within 60 days of a domain's creation or of an earlier transfer, so start early (check your registrar's own rules).
Use a shared password manager for logins and turn on two-step sign-in. Never send passwords by email or chat. If a platform cannot be moved to the client's name, write down what happens when they leave, and see who owns your website and content, export and lock-in.
Step 2: pre-handover quality checks
Do these before the training session. Tick each box and keep the list.
- Every form sends to a real inbox the client can read. Send a test and check the spam folder.
- Every link and button works, on desktop and on a phone.
- Page titles and descriptions are written, and the site is not blocking search engines. A leftover "Disallow: /" in the robots file, a file that tells search engines what to skip, is a common mistake from the building stage.
- Old addresses redirect to new ones if the site replaced an old one. See how to keep SEO rankings when you rebuild or move a client site.
- Analytics is on, and the important actions are set up as key events (Google's term for an action that matters to the business, such as a form submit or a call click). Test one.
- Cookie banner and privacy page match what the site really does. Check local law.
- Accessibility basics. Text has enough contrast, you can tab through the page, the focus outline is visible, and clickable targets are at least 24 by 24 CSS pixels or spaced apart, as set out in the W3C's WCAG 2.2 guidance. This is a short check, not a full audit.
- If any text was written or helped by AI, a named person has checked the facts. Google's guidance (Google Search Central, its advice for site owners) says to review AI content before publishing and that using AI to make many pages without adding value may break its spam policy on scaled content abuse.
- Backups: restore one on a test copy at least once, or confirm how the platform rolls back.
- Speed and mobile spot check on the home page and the page that gets the most enquiries.
For a longer review of AI-built sites, see a quality control checklist for AI-built websites.
Step 3: decide who can edit what
Give people the lowest level of access that lets them do their job. A simple model fits most small sites:
| Role | Who | Can do | Should not do |
|---|---|---|---|
| Owner | Client owner | Billing, add or remove people, domain, publish | Share the login with staff |
| Admin | Agency lead | Settings, integrations, redirects, publish | Change billing without asking |
| Editor | Client office manager, agency staff | Change text and images, add blog posts, publish after review | Edit layout, forms, tracking |
| Viewer or reviewer | Client's boss, a lawyer | See drafts, comment | Edit |
Role names differ by platform, so map these to what yours calls them. A rule that works: the client edits words and images, and the agency edits structure, forms, redirects and tracking. Write that rule into the handover document so nobody is surprised when a form stops working after a "small tidy-up". If a freelancer or contractor needs temporary access, see how to give a freelancer or client limited access.
If you are using AI tools to edit the site, say who may use them and with what permissions. See updating client websites by chatting with Claude or ChatGPT.
Step 4: a 60 minute training session
Keep it to four jobs the client will actually do. Let them click, while you watch.
- Minutes 0 to 10: the map. Show the main pages and which ones change often (hours, prices, team, news).
- Minutes 10 to 25: change text and swap an image. The client does it, publishes to a preview if there is one, and checks the page on a phone.
- Minutes 25 to 40: add a post or a new item, such as a news story, a job or a team member.
- Minutes 40 to 50: read the leads. Where form messages arrive, how to reply, and where to see the numbers.
- Minutes 50 to 60: what not to touch, and who to call. Hand over the document and the contact for help.
Record the session with the client's permission, so it becomes the first video in their library.
Video library ideas
Short screen recordings beat long manuals. Keep each to two to four minutes, one task each, with a clear title. A starter set of eight:
- How to log in and what each menu item is
- How to change text on a page
- How to change or add an image (and how big it should be)
- How to add a blog post or news item
- How to find and answer form leads
- How to see traffic and enquiries in the report
- How to undo a mistake (restore an earlier version)
- Who to contact, and what to send them (a screenshot, the page address, what you expected)
Store them in one shared folder with a one-page index. For ways to make training material without a studio, see how to build a training video library without a studio and how to make training guides without recording video. If your client has a team that will turn over, training a team on a website platform in one week covers the next step.
The one-page handover document (template)
Copy this into a document and fill in each line.
- Site: name, address, platform, date handed over
- Accounts and owners: domain registrar (who, renewal date), platform or hosting, analytics, search console, email, forms inbox
- Logins: where they are stored (the password manager, not the document)
- Roles: who has Owner, Admin and Editor, and who approves what
- What the client may edit: text, images, blog posts
- What the agency edits: layout, forms, tracking, redirects, plugins or integrations
- Where the leads go: inbox address, who replies, expected reply time
- How to get help: email, phone, hours, what to send
- Warranty: the fix-it period and what it covers, for example "bugs in work we delivered, for 30 days" (set your own terms)
- Renewals: domain, platform, plugin, email and any licence, with dates
- Videos and guides: link to the library
- What happens if we part ways: how accounts and files are returned and how long it takes
Sign-off and the warranty period
Ask the client to confirm in writing that the site matches the agreed scope, that they have the accounts, and that training took place. A short email works if it is dated and specific: "We confirm that the site at [address] was handed over on [date], that we hold the accounts listed in the handover document, and that we were trained on the tasks listed." Then start the warranty clock. A warranty period, in plain words, is a set time after handover when you fix mistakes in your own work for free. Say what it covers and what it does not, such as new features, content changes and problems caused by someone else's edit.
Step 5: what happens after handover, and the care plan option
After handover, sites need regular attention: updates, backups, uptime checks, small fixes and a person who looks at the results. GoDaddy's 2026 cost guide puts the maintenance cost for a small to medium business site at about $50 to $500 a month, which shows how wide the range is. What you pay depends on how often a real person looks at the site. See what care plans cover for the details and for do-it-yourself options.
Offer the client a choice and let them say no. A fair set of options:
- Do it themselves. You give them the guides and the videos. They call you and pay by the hour for anything else.
- Pay as you go. Small fixes billed by the hour or in blocks.
- A care plan. A monthly fee for checks, updates, small fixes and a report.
Blur Studio's own Care plan is one example of the third option. It is a monthly plan with no lock-in that covers regular checks by a person, small fixes and updates, and a report in plain language. See the Care page for what is included and the current price. A simple site with low stakes may not need it. A site that brings in bookings or leads usually benefits from someone watching it.
A worked example (made-up)
An agency finishes a 12-page site for a physiotherapy clinic. Here is the handover week, with illustrative timing.
- Monday. The agency finds the domain is registered in the agency's name. It starts a transfer to the clinic's own registrar account and records the renewal date.
- Tuesday. Quality checks. A test form lands in the spam folder, so the agency changes how form mail is sent and retests.
- Wednesday. Roles set: the clinic owner is Owner, the receptionist is Editor, the agency lead is Admin.
- Thursday. The 60 minute session. The receptionist changes opening hours and adds a staff photo. The session is recorded.
- Friday. The handover document and eight short videos are shared. The client replies with the sign-off email. A 30-day warranty begins, and the clinic picks pay as you go for now.
Three weeks later the receptionist edits a booking button by mistake. Because she was told what not to touch and how to restore an earlier version, she fixes it herself in five minutes. That is the goal of a good handover: fewer panic calls.
Common mistakes
- Handing over passwords in an email.
- Leaving the domain or analytics in your own account.
- Training only the owner, who will not make the edits.
- No written line between what the client edits and what you edit.
- No renewal dates, so a domain or plugin licence lapses.
- No warranty terms, so every later problem becomes an argument.
- Selling a care plan as the only way to get help.
Test plan: can the client run it alone?
A week after the handover, ask the client to do five jobs without you: change a paragraph, swap an image, add a post, find the last form lead, and say who to call. Pass: all five done without help. Fail: any job needs you, so add a video for it and fix the document.
Who can use a lighter version
- One-page landing pages for a single campaign. Do steps 1, 2 and 5 only.
- Clients who want you to keep running everything. Still do steps 1 and 3, because ownership matters on the day they leave.
- Internal projects where you are the client.
How I'd approach this
I would make the handover part of the project plan from the first week, not an afterthought on launch day. Put "accounts in the client's name" in the contract, and check the domain registrant at the start, not the end.
A first-week plan if you have a launch coming: Day 1, list every account the site touches and its current owner. Day 2, fix the ones in your name. Day 3, copy the handover document template and fill what you know. Day 4, record the first three videos on a test copy. Day 5, book the 60 minute session and send the client the agenda. Decision rule: if you cannot finish step 1 before launch, delay launch, because ownership problems get harder after payment.
If you want a plan for what happens after launch, the Blur Studio Care plan is one option, and the article on what care plans cover will help you compare it with any other. If you want a custom version of this, with AI agents that use your business knowledge, connect to your CRM and calendar, and come with ongoing care, Blur Studio builds that, and you can see what that includes.
Related guide: building a client portal for your agency customers.
Questions people ask
What should be in a website handover checklist?
Accounts in the client's name, roles and permissions, quality checks (forms, links, analytics, accessibility basics, backups), a training session, a one-page document with renewal dates and contacts, and a written sign-off. The sections above give you each one.
Who should own the domain name?
The client, with their own registrar account and contact details. ICANN says the registrant takes sole responsibility for the registration and use of a domain, so look up the registrant before launch and fix it. See who owns your website and content.
How long should client training take?
Sixty minutes is enough for four jobs: change text, swap an image, add a post, and read leads. Record it and give the client short videos for each task, so the session is not the only source of help.
What editing rights should a client have?
Give the owner full control of billing and domain, and give editors the right to change text, images and posts. Keep layout, forms, tracking and redirects with the agency. Use the lowest role that lets each person do the job.
Should I charge for a care plan after handover?
Offer it as a choice, alongside do-it-yourself and pay as you go. Cost varies widely. GoDaddy's 2026 guide shows small to medium business sites at about $50 to $500 a month. See what care plans cover.
What is a warranty period for a website?
It is a set time after handover when you fix mistakes in your own delivered work at no charge. State the length, what is covered, and what is not, such as new features and edits made by others. Put it in the contract.
What if the client already has accounts in my name?
Transfer them before launch. Check the domain registrant first, move analytics ownership or invite the client as owner, and record the changes in the handover document. If a platform cannot move, write down what happens when the client leaves.
Do I need a sign-off?
Yes. A dated email that says the site matches the agreed scope, the accounts were handed over and training took place is enough for most small projects. Check your contract and local law.
More in this topic: Websites: agency delivery, quality control and margins (10 guides) →