How to hand over a WordPress website to a client

Give the client the access they need

Agree which client account owns the site and which people need editor access. Use individual accounts rather than a shared team login. Review WordPress’s official role documentation when deciding permissions; capabilities can also be changed by installed plugins.

Record access status in the handover without including passwords. Remove temporary access only after the client confirms that the replacement access works and it is appropriate under your agreement.

Explain the recurring parts

List hosting, domain renewals and paid plugin or theme licenses. Name the billing owner and renewal source for each. If a license belongs to your agency, explain what the client needs to arrange if that relationship ends. Do not imply that every license is transferable.

Show the everyday workflow

Give the client a short walkthrough covering the tasks they will perform: edit text, replace an image, update hours and review a form submission. Use their actual editor; instructions for the block editor may not match a site built with a page builder.

Ask the client to perform one ordinary edit with you present. This makes missing access or unclear instructions visible before the project closes.

Document backup and update responsibility

Record the backup service, backup location, responsible person and recovery instructions. Verify how restoration works with the hosting provider. Do not mark recovery tested unless someone has actually tested it.

Explain who reviews updates and how changes are checked before reaching customers. The right schedule depends on the site and service agreement.

Leave a short, usable record

Put the owners, recurring services, support contact and outstanding actions into the handover builder. Keep detailed developer notes separate when they would overwhelm the client.

Reference: WordPress roles and capabilities — https://wordpress.org/documentation/article/roles-and-capabilities/