WordPress client handoff guide

By Adrian Diaz

Confirm ownership and access

Document who owns the domain, hosting, WordPress installation, paid licenses, analytics, and integrations. Give the client access through individual accounts with appropriate roles. Review temporary developer accounts and agree when they will be removed. Share credentials through an appropriate secure channel rather than placing passwords in a public document.

Explain the editing workflow

Show the client how to update the pages and content they are expected to maintain. Demonstrate how to preview changes, publish them, and check the live result. Identify areas that need special care, such as global navigation, reusable templates, and forms. Provide a short recording or written instructions for the most common tasks.

Document the site

Provide a concise inventory of the theme, page builder, plugins, integrations, and custom functionality. Explain what each important component does and who maintains it. Include links to relevant accounts and documentation without exposing passwords. Note any known limitations, pending decisions, and dependencies that should be considered before making changes.

Agree on maintenance

Explain the update, backup, monitoring, and support arrangements. Identify who will check updates, how changes are tested, and what to do if an update causes a problem. Confirm where backups are stored and who can restore them. If support is not included, say so clearly and provide a practical route for obtaining help.

Test the handoff together

Ask the client to perform a common task while you observe: edit a heading, update an image, or review a form submission. Resolve unclear instructions and confirm that their account has the required access. Test a backup restoration through the agreed process when appropriate. A successful handoff means the owner can find information and carry out their responsibilities.

Close and follow up

Deliver the final documentation and identify the contact for outstanding issues. Record the date of the handoff and the versions or configurations that matter. Schedule any agreed follow-up and clarify how new requests will be handled. Keep the document current when ownership, providers, or the maintenance arrangement changes.

Give the owner a starting point

Organize the handoff around the questions the owner will have later: where do I log in, how do I change content, who handles an issue, and how do I recover the site? A short index can point to the relevant instructions without requiring the client to read a technical inventory from beginning to end. Keep account ownership and support contacts current.

Separate routine content editing from changes that need a developer. A client may be comfortable updating a paragraph but need assistance changing global templates or payment integrations. Agree on those boundaries during the walkthrough. Where a task is important, ask the owner to perform it once while support is available.

Example: a content-editing walkthrough

Pick a change the client expects to make regularly, such as updating a paragraph or replacing an image. Start from their own account and show how to find the page, open the correct editor, preview the change, and publish it. Then ask the client to repeat the process while you observe. A step that seems obvious to the builder may need an explicit instruction for the owner.

Explain the difference between a page-specific edit and a change to a global template, header, or reusable component. Show where form submissions go and who should be contacted if they stop arriving. For image changes, demonstrate how to choose an appropriate image and write useful alternative text when the image conveys information.

Finish by checking the published page on a phone and desktop. Add any confusing steps to the handoff notes and confirm the owner can locate the support contact. Do not put passwords in a document that might be shared widely. Use a suitable secure channel for credentials and record ownership and recovery arrangements separately.

Make responsibilities explicit

A handoff should state who pays for hosting and licenses, who can approve updates, who watches backups, and where support requests go. If the client manages a task, explain how they will know it has been completed. If an outside provider manages it, record the provider and the contact process.

List known issues separately from completed work and agree on their status. Set a date for any follow-up that is included in the project. These details prevent an owner from assuming that monitoring or maintenance continues automatically when no such arrangement was agreed.

Put the guidance into practice

Start with the page or workflow that matters most to the people using the site. Write down the current behavior, the change you intend to make, and the person responsible for reviewing it. If the site has a staging environment, test the change there before applying it publicly. Keep a record of the previous configuration and make sure the team knows how to restore it if the change causes a problem.

After the change, repeat the original task with realistic content. Check it on a small screen and with a keyboard, and include any form, payment, or integration that the change could affect. Record the date, result, and any follow-up. Share the outcome with the site owner in terms of what visitors can now do and what remains uncertain. Revisit the check when the underlying content, theme, or connected tools change.

Explore related services.

Need a hand?

Discuss your project