The phone rang at 11:40 at night. It was a client whose website my team had launched just four days earlier. He was panicking because his homepage had “disappeared.” What actually happened: he had tried to “clean up” the dashboard, deleted the page set as the homepage, and then emptied the trash for good measure. I fixed it in twenty minutes from a backup, but I did not sleep well that night — and I knew the handoff had been my failure, not his.
I am Fatima Noor, and I have handed off more than eighty WordPress sites to clients over the years. The midnight-call phase of my career taught me something important: clients do not break websites because they are careless. They break them because nobody taught them what not to touch.
If you run an agency or freelance with WordPress, you know the fear. You deliver a beautiful site, and then you spend the next month answering the same questions, fixing the same avoidable mistakes, and doing free support work you never quoted for. In this guide, I will walk you through the exact five-step handoff process my team uses on every single project — the same process that took us from panicked midnight calls to clients who email us once a quarter.
Whether you are handing off your first client site or your fiftieth, this is the system I wish someone had handed to me when I started.
Here is what this guide covers:
- Step 1: Audit Everything Before the Handoff
- Step 2: Transfer Ownership the Right Way
- Step 3: Write Documentation Clients Actually Read
- Step 4: Train the Client (Without a Three-Hour Call)
- Step 5: Set Up Ongoing Support (and Get Paid for It)
- The Complete Handoff Checklist
- Frequently Asked Questions
- Final Thoughts
Ready? Let us make your next handoff boring — in the best possible way.
Why WordPress Handoffs Go Wrong
Most handoffs fail for one simple reason: the agency treats the launch as the finish line, while the client experiences it as the starting line. You are celebrating a finished project. They are staring at a dashboard with forty menu items, wondering which button deletes their business.
I have seen the same three failures repeat for years. First, access is transferred messily — passwords in chat messages, admin accounts shared like a streaming login, nobody sure who owns the domain. Second, there is no documentation, or there is a fifty-page PDF nobody will ever open. Third, the client was never trained, so every small task becomes a support ticket.
The cost is real. Every “quick question” eats thirty minutes. Every avoidable breakage costs you goodwill. And the worst cost: a client who feels stupid using their own website will never refer you to anyone. A smooth handoff is not paperwork. It is the last impression you leave, and last impressions decide whether clients stay, refer, and pay for care plans.
Step 1: Audit Everything Before the Handoff
Before you share a single password, audit the site as if you have never seen it before. I do this on every project, even the ones I built myself, because familiarity makes you blind. You stop noticing the test page called “asdf,” the plugin you installed “just to try,” and the admin notice you have been dismissing for three months.
Start with the technical audit. Update WordPress core, themes, and plugins to their latest versions, then test the key pages again — updates have broken many “finished” sites the day before handoff. Remove every unused theme, plugin, and media file. Check that forms actually deliver to the right inbox, that the contact page shows the right phone number, and that there are no broken links hiding in the footer.
Then do the client-eye review. Log out, open the site on your phone, and pretend you are the client seeing it for the first time. Click everything. Try to break it. Every confusing label, every dead end, every slow page you find now is a support ticket you will never receive.
One thing I never skip: I write down every login the site depends on — hosting, domain registrar, WordPress admin, email marketing, analytics, payment gateway — and I verify each one works. There is nothing more embarrassing than handing over a password document where half the passwords are expired. This list becomes the access sheet you transfer in Step 2.
Step 2: Transfer Ownership the Right Way
Ownership transfer is where most agencies get lazy, and it is where the biggest risks hide. A proper transfer has one rule: the client must own everything, and you must be removable without breaking anything.
Start with the domain and hosting. The domain must be registered in the client’s name with their email on the account — not yours, not your agency’s. I have seen businesses held hostage by a domain registered to a freelancer who disappeared three years ago. If the site lives on your agency hosting, migrate it to the client’s own hosting account during the handoff, or put the arrangement in writing with a clear exit path.
For WordPress itself, create a dedicated admin account for the client with their own email address — never share one admin login between people. Many agencies give the client an Editor-level role for daily work while keeping a separate admin account for emergencies, and WordPress’s official documentation on roles and capabilities explains exactly what each role can and cannot do. Remove your personal test accounts, and change any shared passwords you used during development.
Deliver the access sheet from Step 1 through a password manager or an encrypted document — never plain email or chat. Walk the client through it on a call, have them log into each account while you watch, and confirm they can get in without you. The handoff is not complete until the client has proven they can open every door themselves.
Step 3: Write Documentation Clients Actually Read
Here is the uncomfortable truth: nobody reads documentation written for developers. Your client will not read a fifty-page technical manual, and they should not have to. Good client documentation is short, visual, and built around tasks — not features.
I keep every handoff document to the same simple structure. First, the everyday tasks: how to publish a post, how to edit a page, how to add a photo, how to check form submissions. Each task gets numbered steps with a screenshot for every click that matters. Second, the “do not touch” list: the settings and areas that can break the site, explained in plain language with the reason (“don’t change the permalink settings — it breaks every link Google knows”). Third, the emergency page: what to do if the site goes down, who to call, and where the backups live.
Write like you are explaining it to a smart friend who has never seen WordPress. Short sentences. No jargon — or jargon translated on first use. Screenshots instead of paragraphs wherever possible. I record a five-minute screen video walking through the three most common tasks and link it at the top of the document, because most clients would rather watch than read, and a video they can replay at midnight is worth ten pages.
Keep the document where the client will actually find it — a shared Google Doc or a page on their own site — and tell them exactly where it is during training. Documentation nobody can find is the same as no documentation.
Step 4: Train the Client (Without a Three-Hour Call)
Training is not a lecture. It is a rehearsal. The goal is simple: by the end of the session, the client has performed every common task themselves, on their own computer, while you watch.
I run every training as a forty-five-minute screen-share call with a fixed agenda. Ten minutes: dashboard tour — what each menu item does, in plain language, skipping everything they will never need. Twenty minutes: the client shares their screen and publishes a test post, edits a page, and uploads an image while I guide. Fifteen minutes: questions, the “do not touch” list, and where to find the documentation and the emergency contacts.
The screen-share part is non-negotiable. Watching someone click through a task themselves reveals every misunderstanding instantly — the client who nods along while you demo will still get lost alone at midnight. When they do it themselves, with you watching, the knowledge sticks. Record the call and send them the recording; it becomes their personal training video.
One more thing I learned the hard way: train the person who will actually update the site, not just the person who signed the contract. The marketing manager who does the daily work needs this call far more than the CEO who attended the kickoff meeting. Ask who will touch the site weekly, and make sure that person is on the call.
Step 5: Set Up Ongoing Support (and Get Paid for It)
The handoff is not the end of the relationship. It is the beginning of the most profitable part — if you structure it right. Every site needs updates, backups, monitoring, and someone to call when things go wrong. That someone should be you, on a paid care plan, not you answering free messages at midnight.
Present the care plan as part of the handoff, not as an afterthought. I include a one-page summary in every handoff package: what the plan covers (updates, daily backups, uptime monitoring, small content changes), what it costs per month, and what happens without it (the client handles updates themselves, with the documentation as their guide). Framed this way, most clients say yes — because you just spent four steps showing them how much can go wrong.
Be explicit about boundaries either way. If the client declines the plan, put in writing what free support includes: I offer fourteen days of bug fixes for anything we built, and after that, help is billed hourly. This is not about being harsh. It is about being clear. Clients respect clear boundaries far more than resentful free labor, and “just one quick question” has a way of becoming twenty.
The agencies that grow are the ones that turn handoffs into recurring revenue. A client on a care plan is a client who stays, refers, and buys their next project from you. The handoff is your best sales conversation of the whole project — do not waste it.
The Complete Handoff Checklist
I run this checklist on every project before I consider the handoff done. Steal it.
- Technical audit complete: core, themes, and plugins updated and tested
- Unused themes, plugins, test pages, and media removed
- Forms tested end-to-end, contact details verified, no broken links
- Client-eye review done on desktop and mobile
- Domain registered in the client’s name with their email
- Site on the client’s hosting (or hosting arrangement in writing)
- Dedicated WordPress admin account created for the client with their email
- Test and shared accounts removed, development passwords changed
- Complete access sheet delivered securely (password manager or encrypted doc)
- Client has logged into every account on the sheet while you watched
- Documentation written: everyday tasks with screenshots, “do not touch” list, emergency page
- Five-minute video walkthrough recorded and linked in the documentation
- Forty-five-minute training call completed with the person doing the daily work
- Call recording sent to the client
- Care plan presented in writing, boundaries and free-support period defined
- Final invoice sent and launch announcement scheduled
Frequently Asked Questions
What if the client refuses to put the domain in their name? Explain it once, plainly: whoever owns the domain owns the business’s online identity. If they still refuse, put the arrangement in writing — who pays, who controls the account, and how everything gets transferred when the relationship ends. Never let ownership stay ambiguous.
Should the client get full administrator access? For most small-business clients, yes — it is their site. But pair it with training and the “do not touch” list. For larger organizations, an Editor role for daily staff plus one admin for their IT person is the safer pattern, and WordPress’s role system supports exactly this.
How long should free support last after handoff? Fourteen to thirty days for bugs in work you delivered is the industry norm. Define it in writing before the handoff, including what counts as a bug versus a new request. After the period ends, support is billed — and the care plan you presented makes that an easy yes.
What do I do when the client breaks the site a month later? Fix it cheerfully the first time, then use it as the reason for the care plan conversation: “This is exactly what the plan prevents.” Clients who experience one scare convert to care plans faster than any sales pitch.
Who should attend the training call? The person who will actually update the site week to week. Get their name before scheduling, and do not accept “just train the boss and he’ll pass it on” — the knowledge never survives the relay.
Final Thoughts
That midnight phone call years ago changed how I run every project. The client was not careless — I had handed him the keys to a machine with no manual and no driving lesson, then acted surprised when he crashed it. Every handoff since has been my apology for that night, systematized into five steps.
If you take one thing from this guide, let it be this: the handoff is not the end of your work. It is the final product. Clients forget beautiful designs within a year, but they never forget the agency that made them feel competent and safe with their own website. Build the audit, the access sheet, the documentation, the training, and the care plan into every project — and your handoffs will stop being headaches and start being your best source of recurring revenue.
Have a handoff horror story of your own, or a step I missed? Leave a comment below — I read every one, and the best stories teach us all.
