A complete WordPress handover gives the client control over the website without handing over insecure or undocumented systems. Treat it as a small operating manual and an acceptance record, not merely an email with a password.
This guide focuses on the practical decision points for wordpress client handover checklist. The examples are educational and should be adapted to your site, provider, client agreement or application requirements rather than copied without verification.
WordPress Client Handover Checklist: Practical Guide
Before you start: gather the right information
Write down the current environment, version numbers or business requirements. For a live website, create a known-good backup and make potentially disruptive changes on staging first. For business documents, confirm the client, scope and acceptance criteria before using a sample.
Step-by-step walkthrough
- Confirm the client owns or controls the domain registrar, hosting subscription and billing contacts.
- Create a named administrator account for the client and remove temporary access that is no longer needed.
- Use a secure password-sharing method, not a plaintext spreadsheet emailed to several people.
- Document the theme, key plugins, premium licences, update responsibility and renewal dates.
- Provide a concise guide for editing pages, menus, posts, images and contact information.
- Identify forms, email routing, backups, restore procedure and uptime/security monitoring ownership.
- Confirm analytics, Search Console and other accounts are under appropriate client access.
- Record final acceptance, known limitations, warranty/support period and paid maintenance options.
Worked example or reference template
Handover acceptance example
| Deliverable | Recipient confirms |
|---|---|
| Website and hosting ownership | Account access works |
| Administrator access | Named client account created |
| Backup and recovery | Schedule and restoration owner known |
| Training | Content editing demonstrated |
| Support | Response process and expiry date recorded |
How to verify the result
Check the output from the perspective of the person who will use it. Test the critical workflow, note what was changed and preserve enough evidence to reverse a failed update. For public-facing sites, repeat the check while logged out and on a mobile browser. For templates, verify totals, wording and payment or ownership terms before sharing.
Common mistakes to avoid
- Do not share your agency-wide hosting credentials.
- Do not leave accounts with unnecessary administrator rights.
- Do not promise lifetime support unless contracted.
Related BDKick tutorials
For the next step, see WordPress Website Launch Checklist: Pre-Launch PDF Guide, Website Maintenance Report Template for Clients (Monthly Example). These pages are part of the same article batch; publish the linked posts before promoting this page.
Frequently asked questions
Should I give the client the hosting password?
Prefer a client-owned account and scoped user access rather than sharing a master password.
What about licence renewals?
Document which party pays and who receives renewal reminders.
Should I retain admin access?
Only with client permission and a documented maintenance or support purpose.
Is a video tutorial useful?
Yes, a short client-specific walkthrough can reduce recurring support questions.
Final checklist
Confirm the instructions match your specific environment, save a backup or clean document copy, test the main outcome and record any remaining risks. If you are publishing technical guidance, revisit it after major product updates.
Frequently Asked Questions
Should I give the client the hosting password?
Prefer a client-owned account and scoped user access rather than sharing a master password.
What about licence renewals?
Document which party pays and who receives renewal reminders.
Should I retain admin access?
Only with client permission and a documented maintenance or support purpose.
Is a video tutorial useful?
Yes, a short client-specific walkthrough can reduce recurring support questions.