A finished website should come with a usable handover
Your new website looks good, the invoice is settled and customers can find you. Then a simple question comes up: who can renew the domain, change a staff member’s details or check where an enquiry went? If the answer depends on finding a former supplier, the handover needs more work.
A website handover checklist helps small-business owners leave a project with practical control. It records which accounts exist, who manages them and what happens when something needs attention. You do not need to become a developer. You need enough information to keep your business moving when people or suppliers change.
Use this checklist before signing off a new site, moving agencies or taking over an existing business. It focuses on ownership and continuity rather than another round of design feedback.
View the website handover checklist and use it to record what is complete and what still needs an owner.
Start with an account register, not a folder of passwords
Ask for one document listing the domain registrar, hosting provider, website platform, business email, booking system, form service and analytics accounts. For each, record the account owner, your level of access, the billing contact and the person responsible for support.
Keep passwords in a password manager rather than in that document. Where a service supports separate users, ask for your own invitation instead of sharing a supplier’s login. Check that your recovery email and authentication method are available to your business.
For a small plumbing company, this might be a short register with six services. For a clinic with online appointments, there may be more. The useful test is whether someone you trust could understand the setup without reconstructing it from old emails.
Confirm who controls the domain and renewals
Your domain is the address customers remember. Ask which registrar holds it, which account controls it and when it renews. Check that renewal messages reach a monitored business inbox and that the payment method will still work after the project ends.
Make a distinction between managing the domain and managing the website. A designer may need access to update technical settings without being the only person who can renew or transfer the address. Write down the arrangement rather than relying on an informal understanding.
Before anyone changes domain settings, identify whether business email also depends on them. A website move and an email move are different tasks. Ask the person doing the transfer to explain what they intend to change and how they will check that email continues working.
Write down what your business can reuse or move
Ask your supplier to explain what is included in the handover: page copy, original photographs, logo files, design files, code and any purchased assets. Record any usage restrictions or ongoing licences. This is especially useful when images, fonts or extensions came through a supplier’s subscription.
Some websites can be moved between hosting providers; others depend on a particular platform. Neither arrangement tells the whole story by itself. What matters is understanding what you can export, what would need rebuilding and who would carry out that work.
Get any unclear ownership or licence terms clarified in writing. Treat this as a practical project question, with specialist advice where an agreement needs interpreting. Our website services are a starting point for discussing the kind of setup your business actually needs.
Prove the customer journey works from start to finish
Do one final walkthrough using a real phone and an email address outside your business. Send a test enquiry, request a booking and follow any important download or payment link. Only test the features your site actually uses, and agree how to identify test transactions before creating them.
- Can you find the enquiry in the destination inbox or system?
- Does the customer receive the expected confirmation?
- Can the right team member see and handle the request?
- Is there a named person to contact if a step fails?
Record the result and date in the handover notes. A form that displays a success message has not completed its job if nobody receives the enquiry. This is an operational acceptance check, separate from whether the page looks finished.
Ask for a short recording of everyday changes
A long technical manual rarely helps the owner who needs to change opening hours between appointments. Ask for a short walkthrough showing the tasks you are likely to do: editing contact details, updating a service, replacing an image and publishing a change.
Agree which areas you should edit yourself and which need supplier support. Include how to preview changes and what to do if you publish a mistake. If the site uses a development workflow rather than a visual editor, document how you request updates and what turnaround to expect.
Keep the recording somewhere your business controls. A link inside a departing employee’s personal account is a fragile handover. Looking at previous website projects can help you identify the kinds of content your team may need to maintain.
Make support, backups and recurring costs explicit
Ask what happens after launch. Who receives fault reports? What support is included? Which changes are chargeable? Where are backups held, what do they cover and who can restore them? Ask how a restore would be requested rather than assuming a backup label guarantees a complete recovery.
List recurring charges with their renewal dates and billing owners. Include hosting, the domain, platform plans, booking tools and any separately billed services. This gives you a usable operating budget without needing to guess from the original project price.
Also agree how supplier access will be reviewed when the relationship ends. Remove access that is no longer needed once the handover has been checked, while preserving the accounts and permissions your business relies on.
Finish with a simple acceptance record
Your final handover record can be one page: account register received, access tested, renewals recorded, customer journeys checked, editing walkthrough saved and support arrangements agreed. Add the date and any outstanding items with a responsible person.
If you are inheriting a website, use the same checklist to find gaps before commissioning a redesign. Missing account access or an unclear renewal arrangement may deserve attention before changing colours or adding pages. A clear brief makes the next conversation with a supplier more productive.
Your website handover checklist
Work through these checks before signing off your website. Tick each item as you review it. Your ticks are temporary and may reset when you leave or refresh this page.
For anything incomplete, agree who will handle it and a target date before your final sign-off.
Book a strategy call about your website handover
Need a website you can run confidently after launch? Book a strategy call with Limeflow. Bring your current account list and the changes you struggle to make. We can discuss the gaps, your team’s responsibilities and a practical brief for a new website or a better handover. You can also send us the background before the call.