Web Strategy

Handing Over a WordPress Site to a Client: Documentation, Training and Ownership

Handing Over a WordPress Site to a Client: Documentation, Training and Ownership

The moment a website launches can feel like the finish line, but for the client, it’s the start. They now have to live with the site: update content, answer questions about it, keep it secure and grow it. How you hand it over shapes whether they feel confident or confused, and whether they come back to you or quietly look for someone else.

Early in my freelance career, I treated handover as an afterthought: a short email with a login and “let me know if you need anything”. The result was a stream of basic questions, edits made in ways that broke layouts and, occasionally, clients who didn’t know where their domain was registered when something went wrong.

Now handover is a defined part of every project. Here’s the process I follow.

Start handover planning early

Handover isn’t something to think about on launch day. Plan for it from the beginning:

  • Agree on who will own each account: domain, hosting, email, analytics and premium plugins.
  • Agree on who will maintain the site after launch.
  • Understand who will edit content and how comfortable they are with WordPress.
  • Build the site with the editors in mind: clear patterns, sensible restrictions and an uncluttered admin.

A site built with handover in mind is much easier to hand over.

Transfer ownership properly

The client should own their digital assets. That protects them and builds trust in you.

Domain

The domain should be registered in the client’s name, in an account they control. If you registered it during the project, transfer it or the account to them.

Hosting

Ideally, the hosting account belongs to the client, with you added as a user or given access. If you host the site on your own infrastructure as part of a maintenance service, make the arrangement clear in writing, including how they can move the site if they choose.

Premium licences

Themes and plugins with licences should be registered to the client, or clearly documented if covered by your agency licence. Explain what happens when licences expire.

Third-party services

Analytics, Search Console, email marketing, payment gateways, CRM and other services should be in the client’s accounts, with you added as a user where needed.

Code

If you built custom themes or plugins, the client should receive the code and the right to use it. If you keep it in a repository, consider giving the client access or a copy.

Set up accounts and access

  • Create a WordPress administrator account for the client’s main contact, using their own email address.
  • Create appropriate accounts for other team members with the right roles: editors, authors or shop managers rather than administrators.
  • Keep your own account, if you’ll provide support, with a clear understanding of when you’ll use it.
  • Enable two-factor authentication for administrators.
  • Share passwords securely, using a password manager’s sharing feature rather than plain email.

Write documentation

Documentation reduces support requests and helps the client feel in control. Keep it practical and written for non-technical readers.

What to include

Site overview

  • What the site includes: main pages, features and integrations.
  • The theme and key plugins, and what each does.

Accounts and services

  • Where the domain, hosting, DNS and email are, without including passwords in the document itself.
  • Third-party services connected to the site.
  • Renewal dates for domain, hosting and licences.

How to do common tasks

  • Adding and editing posts and pages.
  • Using block patterns to create new pages.
  • Adding images, with guidance on size and alt text.
  • Editing menus.
  • Updating contact details, opening hours or other frequently changed information.
  • Managing products and orders, for stores.
  • Managing form submissions.

What not to do

  • Avoid installing plugins without checking, especially on stores.
  • Avoid editing theme settings that affect the design.
  • Don’t change certain settings, like permalinks or URLs.

Maintenance and support

  • Who maintains the site and what’s included.
  • How to request help.
  • What to do in an emergency.

Format

A shared document with screenshots works well. Short screen recordings of common tasks are often even more helpful than written instructions; clients can watch them whenever they need to.

Some developers add a custom dashboard widget with links to documentation and support contact details, so help is always one click away.

Train the editors

A training session, in person or over video, makes a huge difference. I usually run a session of about an hour, tailored to the people who’ll actually edit the site:

  • Logging in and finding their way around the dashboard.
  • Editing an existing page and publishing changes.
  • Creating a new page from a pattern.
  • Writing and publishing a blog post with images.
  • Updating menus.
  • Store tasks: adding a product, processing an order, issuing a refund.
  • Where to find documentation and how to ask for help.

Let them do the tasks themselves during the session, rather than only watching you. Record the session, with permission, so they can revisit it.

Explain what the site needs to stay healthy

Many clients don’t realise a website needs ongoing care. Explain clearly:

  • WordPress, plugins and themes need regular updates for security and compatibility.
  • Backups need to be running and tested.
  • Domain, hosting and licences need renewing.
  • Security monitoring helps catch problems early.

Then offer clear options:

  • A maintenance plan where you handle updates, backups, monitoring and small changes.
  • Self-maintenance with guidance on what to do and how often.
  • Ad-hoc support for occasional help.

Be honest about the risks of doing nothing. A neglected site becomes slower, less secure and more likely to break.

Define a warranty period

Many developers include a warranty period after launch, such as 30 days, during which they fix bugs in the work delivered at no charge. Define clearly what’s covered:

  • Covered: things that don’t work as agreed in the project scope.
  • Not covered: new features, design changes, content updates, problems caused by the client installing plugins or editing code and issues from third-party services.

A clear warranty sets expectations and avoids awkward conversations.

Launch checklist for handover

Before declaring the project complete, confirm:

  • The client has administrator access and has logged in successfully.
  • Ownership of domain, hosting and services is correct.
  • Backups are running and stored off-site.
  • Security measures are in place.
  • Analytics and Search Console are set up and accessible to the client.
  • Forms send to the right email addresses.
  • Documentation is delivered.
  • Training is completed.
  • Maintenance arrangements are agreed in writing.
  • Staging sites are protected or removed.
  • Your temporary accounts and test data are cleaned up.

Follow up after launch

Check in a week or two after launch:

  • Ask how editing is going and whether they have questions.
  • Review any issues from the first weeks.
  • Look at early analytics together, if helpful.
  • Discuss next steps, like content plans, SEO or new features.

This follow-up often turns a one-off project into an ongoing relationship.

What clients remember

Clients rarely remember the technical details of how their site was built. They remember whether they felt supported, whether they understood how to use it and whether you were there when something went wrong. A thorough handover is one of the most effective ways to earn referrals and repeat work.

Keep a handover template

Create a reusable handover document template and checklist for every project. Each new site then gets the same thorough handover, without relying on memory.

Update the template after each project with anything you wish you had covered, so every handover improves on the last.

Frequently asked questions

Should the client own the hosting account?

Ideally, yes, or at least have a clear written agreement about hosting provided as part of your service and how they can move the site if they choose.

How much documentation is enough?

Enough for the client’s editors to handle common tasks without calling you. Focus on practical tasks with screenshots or short videos, rather than technical details.

Should clients have administrator access?

The main contact should have administrator access to their own site. Other team members should have roles that match their tasks.

What if the client doesn’t want a maintenance plan?

Explain the risks clearly, provide guidance on maintaining the site themselves, document it in writing and make sure they know how to reach you if problems arise.

Final thoughts

A good handover turns a launched website into a confident client. Make sure the client owns their domain, hosting and services, set up accounts securely, deliver practical documentation, train the people who’ll use the site, explain what ongoing care is needed and define support clearly. Then follow up. The care you put into handover is often what clients remember most, and it’s what brings them back.