A website launch feels like the finish line, but the handover that follows it is where a lot of small businesses end up short-changed. The site goes live, the invoice gets paid, and everyone moves on, sometimes without the business owner ever actually holding the keys to what they paid for. A proper handover is not just a courtesy step; it determines whether you can update the site, move hosts, or switch providers later without starting from nothing.

Key Takeaways

  • A complete handover includes admin access to the website, the domain registrar, and hosting, not just a finished front end.
  • Ownership of the design files and source code should be confirmed in writing, since UK law defaults ownership of commissioned work to whatever the contract says.
  • Data protection responsibilities, including who holds customer data and under what agreement, need to be clarified when a web design company also manages hosting or forms.
  • A short walkthrough or written guide for making basic updates saves ongoing dependency on the original developer for minor changes.
  • Asking for a handover checklist before the project starts, not after it finishes, is the most reliable way to make sure nothing gets missed.

Most disputes at the end of a website project are not about the design itself. They are about access, ownership, and who is responsible for what once the working relationship winds down.

Access to the Website Itself

The most basic thing a handover should include is full admin access to the site: the content management system login, any plugin or theme licences tied to the account, and a clear note of what software the site runs on. Without this, even a minor text change can mean going back to the original agency, sometimes at an hourly rate, for something that should take five minutes.

A useful practical guide from a UK web design studio lists this as the first thing to check off during a handover, precisely because it is the item most often assumed rather than confirmed. Ask for the access before the final invoice is paid, not after, since your ability to insist on it tends to disappear once the bill is settled.

The word LOGIN spelled out in white keyboard-style tiles on a red background

Domain and Hosting Ownership

The domain name and hosting account are frequently overlooked because they were often set up early in the project and forgotten about by the time launch arrives. Confirm who the domain is actually registered to. If a web design company registered it on the business’s behalf, the registrant details should list the business, not the agency, and the business should hold or be able to obtain the transfer authorisation code if it ever needs to move registrars.

The same applies to hosting. If the agency manages hosting under its own account, ask what happens if the relationship ends: is the site portable, or does it depend on infrastructure only the agency controls? A business that does not clarify this can find itself effectively unable to leave, regardless of how the design itself turned out.

A website you cannot move is a website you do not fully own, no matter whose name is on the invoice.

Source Files and Design Ownership

UK guidance on intellectual property is clear that ownership of commissioned creative work is not automatic; it depends on what the contract actually says, and in the absence of a clear agreement, the creator can retain more rights than most clients assume. This applies to a website’s design files, source code and any custom graphics just as much as it would to a logo or a piece of artwork.

Before the project starts, or at the latest before final payment, get written confirmation of who owns the source files and design assets once the invoice is settled. A short guide on developer-to-developer handovers notes that even the file formats matter here: raw design files in an editable format are far more useful long term than flattened exports that cannot easily be updated by anyone else.

Two hands passing a USB drive between each other in a close-up shot

Data Protection Responsibilities

If the web design company also manages hosting, forms, or a mailing list connected to the site, it is worth clarifying who is responsible for the customer data those tools collect, and under what agreement. Official guidance on data protection distinguishes between a controller, who decides why data is collected, and a processor, who handles it on the controller’s behalf, and the contract between the two should set out each party’s responsibilities clearly.

This matters practically at handover time: if the agency continues to host forms or manage an email list after the working relationship changes, the data protection arrangement needs to be revisited, not left as an assumption from when the project first began.

A Basic Guide to Making Updates

A good handover includes more than files and access. A short walkthrough, even informal, of how to update text, swap an image, or add a new page reduces how often a business has to go back to the original developer for routine changes. This does not need to be a full manual; a recorded screen share or a one-page guide covering the most common tasks is usually enough.

This is also a natural point to mention ongoing support. A web design company that offers a light-touch maintenance option, or simply makes clear how to reach them for the occasional larger change, gives a business somewhere to turn without committing to an expensive ongoing contract it does not need.

Ask for the Checklist Before the Project Starts

The single most effective way to avoid a messy handover is to ask what it will include before the project even begins, not after the invoice is paid. A web design company that has a clear, written handover process is showing you how it treats clients on the way out, which tends to say something honest about how it treats them throughout.

Frequently Asked Questions

What is the minimum a business should receive at website handover?

Admin access to the content management system, confirmation of domain ownership and registrar access, and written clarity on who owns the design files and source code. Anything less leaves the business dependent on the original agency for things it should be able to control itself.

Who should the domain name be registered to?

The business, not the web design company, even if the agency handled the initial registration. Check the registrant details directly with the registrar if there is any doubt, since it is a simple thing to confirm and a difficult one to fix later.

Does a web design company automatically own the code they write?

Not necessarily. UK law generally lets the contract decide who owns commissioned work, so the answer depends entirely on what was agreed at the outset. If nothing was agreed, get it clarified and documented before the project closes.

What happens to customer data if a website changes hands between providers?

Responsibility for that data should be set out in a data processing agreement between the business and whoever hosts or manages the relevant tools. This needs revisiting whenever the working relationship changes, not left unaddressed.

Is it normal to pay for handover support after launch?

Some agencies include it as part of the project fee; others charge separately for a walkthrough or documentation. Either is reasonable, but it should be clear from the outset rather than appearing as a surprise once the site is already live.

Sources