A new WordPress website is ready to launch, the design has been approved and everyone wants to move on to the next project. This is also the moment to ask a less exciting question: who will look after it next month?
A website handover should leave the business able to operate its site and find help without relying on somebody’s memory. It is a practical transfer of knowledge, responsibilities and access. A folder of design files alone does not achieve that.
If ongoing care is being transferred to a service such as BugShield, include that team in the handover arrangements. Agree what the designer is handing over, what the business will manage and which maintenance tasks the new provider is taking on.
Establish ownership before exchanging passwords
Start with an account inventory. Identify the domain registrar, hosting provider, WordPress administrator accounts and any paid services the site depends on. Record the business owner of each account and the person responsible for renewals.
Use business-controlled contact details where appropriate so renewal notices do not disappear when a staff member or contractor leaves. Where an agency owns a licence used on your website, document that arrangement rather than assuming it transfers with the site.
Share access through an agreed secure process. Do not turn the handover document into an unprotected list of passwords. Its job is to explain where accounts are managed and who can grant access.
Walk through the everyday jobs
Ask for a demonstration of the tasks your team will actually perform. These might include editing opening hours, changing a service description, uploading a suitably sized image or publishing a news post.
Take notes that describe your own setup. General WordPress tutorials can be useful, but they may not match the theme, page builder or custom features installed on your website. A brief recording or annotated guide can save repeated support requests later.
Include the limits of routine editing. Staff should know which areas they can safely change and when to ask for help. Clear boundaries make people more confident about using the site.
Test the customer journey together
Use the handover meeting to follow a visitor’s route through the website. Try the navigation on a phone, open the main calls to action and complete an agreed test of enquiry or booking forms.
Check the receiving side as well. A successful on-screen message does not establish that an enquiry reached the right person. Confirm who receives notifications and how someone notices if the normal process stops working.
Write down anything that still needs attention. Give each issue an owner and a completion date, and distinguish a launch defect from a request for extra functionality. That avoids disagreement over what the final handover includes.
Identify the services behind the pages
Many websites rely on more than WordPress and hosting. A contact form may use an email delivery service; a booking button may connect to a separate calendar; an online shop may depend on a payment account.
Record the purpose of each important connection and where its settings are managed. You do not need to document every internal detail, but the next person supporting the site needs a starting point when something fails.
Include subscription renewal dates and the consequences of cancellation. A service that appears optional in an accounts spreadsheet may support an important part of the customer journey.
Agree the maintenance responsibilities
Make a simple responsibility list for updates, backups, monitoring, routine checks and fault reporting. Name a person or supplier against each activity, including tasks the business intends to handle itself.
Discuss how changes will be requested and approved. For example, decide whether the maintainer can apply routine changes directly or should arrange a time with your team. Important campaigns and busy trading periods are useful context.
Establish how the business can review completed work. A shared record of changes and outstanding issues is often more useful than scattered messages, especially when several people are involved in the website.
Prepare for absence and emergencies
Imagine the usual contact is unavailable when the website stops working. Someone else should be able to find the relevant support route, explain the symptoms and identify which accounts belong to the business.
Include a recovery overview with the location of backup management and the person authorised to arrange a restore. Avoid promising that a restore is always the right response; the support team still needs to assess what happened.
Keep a copy of essential handover information somewhere accessible without logging into the website itself. A recovery plan hidden inside an unavailable site is difficult to use at exactly the wrong moment.
Finish with a review date
A handover document becomes less reliable as the website changes. Set a date to review it after the first few weeks of real use, then revisit it whenever a provider, feature or key team member changes.
Use that first review to resolve confusing instructions and confirm that the agreed support arrangements work in practice. Ask the people handling enquiries and content updates what they still need.
A successful handover gives the business more than a finished design. It leaves a website people can operate, a record others can understand and a clear route to ongoing care.
