Handover is part of the project
A website can look finished while the business still depends on a supplier’s personal account, an undocumented password or files nobody can find. A useful handover makes it clear who controls the important services, how routine edits are made and whom to contact when something stops working.
Agree the handover scope before launch rather than waiting until a relationship ends. The exact documents and access depend on the platform and contract. The goal is not to give every person administrator privileges; it is to ensure the business has an appropriate, secure way to manage and recover what it owns or is entitled to use.
Record the domain, DNS and hosting
List the domain registrar, renewal date, account owner and recovery route. Record where DNS is managed and which provider hosts the website. Email may sit with another supplier, even when it uses the same domain. Keep a current explanation of that arrangement so a future website change does not inadvertently affect business email.
Confirm whether the bare domain and www version both work as intended, who manages the HTTPS certificate and what to do if verification or renewal fails. Store credentials in a suitable secure system rather than a public handover file. The record can identify the account and responsible person without exposing passwords or recovery codes.
Give the right people appropriate access
Check who owns the content-management account, hosting, domain, analytics and any booking or form service. Give the business an independent owner or recovery route where supported. Add editors with the permissions needed for their work, and document how access is reviewed when staff or agencies change.
Use unique credentials and additional sign-in protection for important accounts where available. Do not share one administrator login across a team. If a supplier needs temporary access, agree the level and duration. When access is removed, check that the remaining business owner can still manage renewals, backups and routine content.
A complete website handover
- AccountsOwnership, access and renewals
- AssetsContent, originals and permissions
- CareSupport, updates and approvals
- RecoveryBackups, restore and export
Collect the content and source assets
Request the agreed text, original images, logo files, design assets and any commissioned documents in useful formats. Check that the business can find the versions used on the live site. If a component is licensed rather than owned, preserve the licence and understand whether it permits future editing, advertising or transfer to a new supplier.
Keep a record of image permissions, credits and restrictions, including images supplied by customers or third-party libraries. Ask which fonts, plugins or subscriptions the site depends on and whether they are included after launch. A screenshot of the website does not replace editable content or the right to reuse an asset.
Explain editing, approvals and support
Ask for a demonstration or short written guide covering the tasks the team will actually do: change contact details, edit a service page, add an article and replace an approved image. Show how to preview the result and who approves factual or specialist statements before publication.
Record what ongoing support includes, how to request a change, expected response arrangements and any extra charges. Clarify who updates software and plugins, monitors the contact form and reviews content accuracy. A project can be successfully handed over while ongoing support remains in place, provided the responsibilities are explicit.
Document backups and recovery
List what is backed up, where the copy is stored, the schedule and who can request or perform a restore. A typical WordPress recovery may involve both files and a database; external forms, bookings and email may require separate arrangements. Ask when restoration was last tested and what information a test covered.
Confirm how the site can be exported or moved if the platform or supplier changes. An export may not recreate every design component or integration automatically. Knowing the limitations in advance is more useful than discovering them during an urgent move. Protect backup archives because they may contain confidential information.
An illustrative handover
Imagine a Hertfordshire business receiving a redesigned website from an external supplier. The owner checks access to the registrar and CMS, confirms that email remains with its existing provider and receives a list of the approved images and their permissions. The team practises changing an opening time in a safe or agreed workflow.
In this hypothetical example the supplier also documents the backup schedule, contact-form provider and support arrangement. The owner tests a representative page on a phone and agrees a controlled enquiry test. If an item is missing, it is assigned to a named person with a date rather than assumed to be complete.
A final handover review
Confirm the owner and recovery route for the domain, DNS, host and CMS; list important subscriptions and renewal dates; obtain the agreed content and rights information; and identify who maintains each integration. Check the main customer journeys, including contact or booking, with permission from the people who receive test messages.
Store the handover record where an authorised colleague can find it if the usual owner is unavailable. Review it after a supplier, platform or payment change. Good handover is an ongoing record of responsibility and access, not a one-off folder that becomes outdated as soon as the site evolves.
Use a responsibility matrix
Make a table with one row for each important item: domain renewal, DNS changes, hosting, CMS updates, backups, form delivery, image permissions and content approval. For each row, name the business owner, the person or supplier doing the work and where to find the account or documentation. Include a review date and an escalation route. Keep passwords and recovery codes in the approved secure system, not in the table.
Walk through one ordinary change and one failure scenario. Ask who would update an opening time and who would investigate a failed enquiry form. If the answer is “the old designer” without a current agreement or access route, resolve the gap. Revisit the matrix when a supplier leaves or an integration is added, and make sure the people named know that they are responsible. Check the support contact and renewal date directly with the provider when either detail is uncertain.
