[email protected]
0333 050 1245

UK web design contracts: 3 clauses every practitioner insists on

  1. Home
  2. »
  3. Blog
  4. »
  5. UK web design contracts: 3 clauses every practitioner insists on

Use a written UK website development agreement that names scope, payment milestones, acceptance criteria, IP terms and data duties, and never rely on verbal promises. Before you sign anything, confirm the deliverables in writing, agree milestone payments tied to clear triggers, and pin down who owns the intellectual property once the invoice is paid. Get those three right and most disputes never happen.

TL;DR:

  • A detailed contract should specify scope, delivery deadlines, and ownership rights to avoid disputes over IP and project responsibilities.
  • Payment should be tied to clear milestones, with explicit criteria for acceptance and a defined remedy period for fixing defects post-launch.
  • Ownership of website IP requires written transfer; simply paying an invoice does not confer full rights, and background tools or third-party components must be clearly licensed.
  • The client must control domain registration, hosting access, and receive a comprehensive handover pack with source files, backups, and documentation at project completion.
  • Data responsibility and compliance must be clearly allocated, including cookie management, privacy notices, and ongoing accessibility obligations post-handover.
Kukoocreative
Build a Website With Clarity
Kukoocreative creates impactful logos and websites that help UK business owners build recognition and connect with the right people.

Table of Contents

What to include in a web design contract UK businesses can actually rely on

A vague brief is where most website disputes start. Forbes Solicitors describe a properly drafted web design and development agreement as a roadmap that keeps both sides pointed the same way, precisely because it separates a genuine defect from a client simply wanting something new. That distinction alone resolves a huge share of the arguments that end up with an agency and a client no longer speaking.

Start with scope, and be brutally specific:

  • The exact number of pages, templates and features included
  • Every integration named (booking system, CRM, payment gateway, email tool)
  • Who supplies copy, images and product data, and by what date
  • File formats for handover (design files, source code, exports)
  • What’s explicitly excluded, such as ongoing SEO, copywriting, or stock photography licensing

Payment terms need the same precision. A typical UK web project asks for a deposit of around one-third to half, with the balance split across milestones tied to specific, checkable events, such as “wireframes approved” or “site live on staging”.

Timelines depend on both parties, not just the developer. Build in explicit client dependencies: content delivery dates, feedback windows, and approval turnaround. Practitioners recommend a deemed acceptance clause of five to ten working days, so that if a client goes quiet, the project doesn’t stall indefinitely and the agency retains the right to invoice for work already delivered.

Acceptance testing needs its own clear definition:

  1. Define what a “defect” is (something that fails an agreed specification)
  2. Define what an “enhancement” is (something new, outside the original brief)
  3. Set a fixed remedy period for genuine defects, typically 30 to 90 days
  4. Require sign-off in writing, not a verbal “looks fine”

Where multiple specialists are involved, such as a designer, a back-end developer and an SEO consultant, LexisNexis guidance recommends a single master agreement, or clearly linked subcontracts, so nobody’s responsibilities fall through the gap between two suppliers.

Finally, agree a change control procedure before you need one. Every change request should be documented, priced, and given a time impact, with written sign-off before work starts. This is the clause that stops “just one small tweak” turning into three unpaid weeks of extra work.

Who owns the website: IP, background code and third-party licences

Here’s what catches many UK business owners out: under the Copyright, Designs and Patents Act 1988, the person who creates the work owns the copyright by default, not the client who paid for it. Paying an invoice does not automatically transfer ownership. Assignment has to be in writing and signed.

You have three realistic options to request:

  • Full assignment on final payment. The client owns everything created specifically for the project once the last invoice clears.
  • Licence limited to the site. The developer retains ownership but grants the client a licence to use it, common where an agency reuses frameworks across clients.
  • Assignment of deliverables only. The client owns the finished output, while the agency keeps its own background tools, plugins and reusable code.

Ask for background IP to be carved out explicitly, with a perpetual, non-exclusive licence to use those components within your own site. This protects the agency’s right to reuse its own toolkit, while guaranteeing you can keep running your site indefinitely without a rights dispute. Insist too on full disclosure of any open-source or third-party licensed components, since ongoing compliance with those licences often becomes your responsibility once the site is live.

Data protection, cookies and accessibility: who is responsible?

Most commercial websites collect personal data somewhere, whether it’s a contact form or a checkout. That makes UK GDPR relevant to almost every build, and the contract needs to say who is the controller (usually you, the client) and who is the processor (the developer), with data processing terms attached where the developer handles that data on your behalf, as Sprintlaw UK advises.

Illustration of controller processor data flow

Pro Tip: Get your developer to state in writing who builds the cookie banner and privacy notice, and who updates it when the rules change. “The client is responsible” sounds fine until nobody actually does it.

Build in three specific requirements:

  • Disclosure of every cookie and tracking script used, with a compliant consent mechanism under PECR
  • Named responsibility for privacy notices and cookie banners at launch
  • An agreed accessibility baseline, typically WCAG 2.1 AA, with clarity that ongoing compliance usually sits with you as the site operator once handover happens

Our UK website legal requirements guide covers the GOV.UK and ICO detail behind these obligations in more depth.

Hosting, domains and what happens at handover

Domain ownership should sit in your name, not your agency’s, from day one. It’s a small administrative point until you try to switch suppliers and discover you don’t control the asset your business depends on.

Before signing, secure these four things:

  1. Domain registered under your business name and account, not the agency’s
  2. Full admin access to hosting, CMS and DNS settings, not just editor-level logins
  3. A written handover pack on completion or termination: exported content, source files, backups, credentials and documentation
  4. Migration assistance terms if you leave, including any hourly rate for support during the switch

Pro Tip: Ask for the handover pack to be delivered within a fixed number of working days of final payment, not “on request”. Open-ended handover promises are the single easiest clause to quietly ignore.

Warranties, liability caps and how disputes get resolved

A reasonable warranty period covers bug fixes for a limited time after launch, excluding faults caused by third-party plugin updates or content you’ve added yourself. Liability caps commonly limit the developer’s exposure to fees paid, sometimes a multiple of that figure, with indirect losses like lost profits excluded entirely.

  • Ask for an indemnity covering IP infringement claims arising from work the developer created
  • Confirm you’re separately liable for the accuracy of materials you supply, such as images or copy
  • Set a dispute ladder: internal escalation first, then mediation, with governing law fixed as England and Wales
  • Check the contract doesn’t try to exclude liability the Unfair Contract Terms Act 1977 or Consumer Rights Act 2015 wouldn’t allow it to exclude

Negotiating checklist and red flags before you sign

Run through this before putting pen to paper:

  1. Scope is defined in writing, including exclusions
  2. Acceptance tests and a deemed acceptance window are both stated
  3. IP transfer or licence terms are explicit, not implied
  4. You control the domain and have full hosting access
  5. Data processing responsibilities are assigned under UK GDPR
  6. Change control has a documented process with cost impact
  7. Termination terms specify exactly what gets handed over, and when

Watch for red flags: vague phrases like “rights will transfer as appropriate”, no defined acceptance criteria at all, a supplier holding sole control of your domain, unlimited rights to suspend your site, or liability exclusions written broadly enough to cover almost anything.

Pro Tip: Ask for a small paid discovery phase before the main contract. It surfaces scope gaps early, and it tells you a great deal about how the agency actually works before you commit to the full budget.

Tactically, it’s reasonable to ask for source code escrow on higher-value builds, to make final payment conditional on formal acceptance, and to request examples of a previous handover pack before you sign. A supplier confident in its own process will have no problem showing you one.

Kukoo Creative’s view on getting the contract right

We’ve built websites for UK small businesses for over a decade, and the projects that go smoothly almost always share one trait: a milestone-driven contract agreed before a single line of code gets written, not scribbled in afterwards to fix a disagreement. Our pricing bands and quote breakdown guide exist because clarity upfront saves both sides weeks of pain later.

— Kukoo

How Kukoo Creative helps you build a contract-ready website

Some web agencies offer a collaborative four-step process with milestone payments and unlimited revisions on branding and web system work, so scope, cost and IP terms are agreed upfront, not argued about at handover.

Kukoocreative

Our web design and development service covers the full build, and once your site is live, our maintenance and improvement plans keep it running without a fresh negotiation every time something needs fixing. If you’d rather start small, our £25 website speed improvement is a low-risk way to see how we work before committing to a full rebuild. For businesses planning a launch and thinking about PR afterwards, PR and communications support is worth lining up in parallel.

Get in touch for a scope-first quote, and ask us to walk you through a draft heads of terms before you commit to anything.

Sources

FAQ

Does a web design contract have to be in writing?

It doesn’t have to be by law, but it should be. Verbal agreements leave scope, IP ownership and payment terms open to dispute, and written assignment of copyright is required under the Copyright, Designs and Patents Act 1988.

The developer owns it by default under UK law unless the contract explicitly assigns copyright to you in writing on final payment; without that clause, you may only hold a licence to use it.

What does Kukoo Creative charge for a website?

Kukoo Creative’s website design and development pricing isn’t published as a fixed figure and depends on project scope; current pricing bands are detailed on the Kukoo Creative site.