Colin Lee MacLeod — More Better Good
MENU ☰

Prepare a Website Handover the Owner Can Actually Use

Hand over the knowledge, responsibilities and recovery plan, not just a homepage link.

Illustration of a fictional designer and business owner reviewing organized website documentation
AI-created conceptual illustration, not a photograph of a completed client project.

A website handover should leave the owner able to understand what was delivered, who maintains it and what to do when something goes wrong. A link to the homepage and a cheerful “all done” do not answer those questions.

This is our practical handover-planning framework, developed from the delivery questions in our independent website design studies. It is not a claim that a specific client project has been completed, nor a substitute for the project’s agreed scope or qualified technical advice.

Start with a one-page service map

List the public website address and the services it depends on: domain registration, hosting, website administration, business email, forms and any other essential integration. Beside each, record who owns the account, who pays for it, who is authorized to manage it and who provides support.

The map is not a password sheet. Do not put passwords, recovery codes or payment details into a shared handover document. Arrange any necessary access through an agreed secure process with the owner. Do not remove the previous administrator before confirming that the authorized replacement can do the required work.

Mark uncertainty plainly. “Renewal owner not yet confirmed” is a useful open task. Guessing that the designer will renew something forever is not a maintenance arrangement.

Separate deliverables from ongoing services

Write down what was actually delivered: implemented pages, original design files, edited copy, approved images, custom code, documentation and training. Then list ongoing tasks separately: content changes, updates, renewal checks, monitoring and support.

For each ongoing task, name an owner and an agreed review point. If a task is outside the project, say so. This prevents a one-time design delivery from being mistaken for an unlimited support service.

Keep the image and font permissions information with the relevant assets. Do not assume that every item visible in a mockup is available for unrestricted reuse. Record what the owner has approved and what still needs to be resolved.

Describe the backup, not just the backup button

For a typical WordPress site, the official backup guidance distinguishes the database from the site files and says both are needed for a full restoration. A handover note should identify what the actual backup covers, where authorized people can find it and who is responsible for checking it.

WordPress’s Tools Export documentation describes a WXR XML file containing content such as posts, pages, comments and taxonomies. Do not treat that content export alone as evidence that the complete site can be restored, including its files and configuration.

Ask the technical maintainer to document a suitable recovery test and its outcome in a safe environment. A filename or a green success message is not the same as a demonstrated recovery. Do not practise restoring over the live business site merely to tick this box.

Give the owner three real tasks

Agree on a small acceptance session. For example: find the correct page to edit an opening-hours notice, identify where an enquiry should arrive, and locate the support contact for a site outage. Use test content and an approved environment where a real edit or submission would have consequences.

Ask the owner to perform the steps while following the notes. If the instructions require the designer to explain every sentence, improve the instructions. Keep a short screen recording only when everyone agrees and private account information is excluded.

Record the unfinished work

Use a clear list with four columns: issue, owner, next action and agreed date. Examples might include a missing approved photograph, a form-delivery check awaiting the owner, or a mobile layout issue still being repaired.

Separate an accepted limitation from a forgotten defect. “We discussed it” is weaker documentation than a plain description of what remains and what the parties agreed to do next.

Finish with a usable next-day plan

The owner should know whom to contact, what information to include and what support has actually been agreed. Avoid invented response-time promises. Keep the handover version and review date visible so an old instruction sheet is not mistaken for the current arrangement.

After handover, keep individual changes in a website update log. The handover explains responsibility for the system; the log explains what changed. Both are more useful when they describe what really happened rather than what someone hoped would happen.

WordPress references checked November 16, 2026. The service map and acceptance exercise are our suggested planning tools.

Build something clear and useful.

Tell us which visitor task needs work and what information is already confirmed. We can discuss a practical next step.

Ask about website design →
The Four Finger Rule. Real life. Real conversations. Explore the Four Finger Rule.