Alex is Sprintlaw’s co-founder and principal lawyer. Alex previously worked at a top-tier firm as a lawyer specialising in technology and media contracts, and founded a digital agency which he sold in 2015.
Amira runs a small web design studio in Manchester. A client approves a quote for a new eCommerce website, pays the first invoice, then takes six weeks to send product images and copy. When the site is finally ready, the client asks for a full redesign and delays the final payment because it isn't exactly what they had in mind.
If that sounds familiar, you're definitely not alone. Website projects often go wrong because everyone is relying on friendly emails, a proposal and good intentions.
A clear website design contract template UK designers can tailor to their own process can help you set expectations before the first wireframe is built. It doesn't have to be complicated, but it does need to cover the parts of the project where delays, scope changes and payment disputes usually happen.
Do You Need A Website Design Contract Before You Start?
Yes, you should have a written contract before you start any website build, redesign or maintenance project. Even if the client seems easy to work with, a written agreement gives you something clear to point to if the project changes direction.
For UK web designers, your contract is usually a business-to-business services agreement. It should sit alongside your proposal, quote or statement of work, rather than being a vague set of website terms copied from somewhere else.
Without a written agreement, you may struggle to recover unpaid invoices, charge for extra work, pause the project when content is late, or show who owns the finished website files.
Your contract should make it clear:
- what you're building, and what you aren't building
- what the client needs to provide, such as copy, brand assets, logins and feedback
- when you get paid, and what happens if payment is late
- how revisions, approvals and testing will work
- who owns the design, code, content and third-party tools
- what support is included after launch
If you work with consumers as well as businesses, you'll also need to think about the Consumer Rights Act 2015 and consumer cancellation rules. Most agencies work mainly with business clients, but the right terms can change depending on who your client is and how you sell your services.
What Should A Website Design Contract Template Include?
A good website development agreement should include the commercial, practical and legal terms that match the way you actually run projects. A downloaded template can be a useful starting point, but it should be tailored before you use it with paying clients.
Here is a fill-in outline you can use to plan your website design contract. This isn't a finished legal document, but it shows the clauses you'll usually want covered.
- Parties: Write the legal names, company numbers if relevant, registered addresses and contact details for you and your client.
- Project Scope: Describe the website, pages, features, platforms, integrations and deliverables you're responsible for.
- Out Of Scope Work: List what is excluded, such as copywriting, SEO, paid ads, photography, hosting, plugin licences or custom integrations.
- Timeline And Milestones: Set the project stages, target dates and the client inputs needed at each stage.
- Fees And Payment: State deposits, milestone invoices, final payment, VAT if applicable, late payment rules and expenses.
- Client Responsibilities: Explain what the client must provide, such as content, approvals, access credentials and brand guidelines.
- Revisions And Change Requests: Set how many revision rounds are included and how extra work will be quoted.
- Acceptance Testing: Set the review period, approval process and what counts as acceptance.
- Intellectual Property: Explain what transfers to the client, what you retain and when any handover happens.
- Third-Party Tools: Deal with plugins, themes, fonts, stock images, hosting, APIs and licence fees.
- Data Protection: Cover UK GDPR and Data Protection Act 2018 obligations where you handle personal data.
- Support And Maintenance: State what is included after launch and what needs a separate support plan.
- Termination: Explain when either side can end the contract and what is payable if that happens.
- Liability: Set sensible limits for losses, downtime, third-party failures and indirect losses.
- Governing Law: State that the contract is governed by the laws of England and Wales if that's the legal framework you want.
The more specific your scope is, the less room there is for awkward conversations later. If you simply say you'll build a website, the client may assume that includes everything from copywriting to SEO to fixing old email settings.
How Should Milestone Payments And Client Delays Work?
Your service agreement should tie payments to clear milestones and explain what happens if the client causes delay. This is one of the most useful protections in a web designer contract in the UK.
A common structure is:
- an upfront deposit before work starts
- a payment after discovery, wireframes or design approval
- a payment when development reaches a set stage
- a final payment before launch, migration or handover
You don't need to use these exact stages. The right structure depends on your project size, cash flow and how much work you do before the client sees a finished version.
A Worked Example
Say Amira agrees a £6,000 website project with a business client. Her contract says the client pays £2,000 on signing, £2,000 when homepage and key page designs are approved, and £2,000 before launch.
The client is meant to provide all copy and images within 10 business days after the discovery call. They provide half the content after three weeks, then ask Amira to keep the launch date the same.
Because Amira's contract has a client delay clause, she can:
- move the project timeline back by the same period of delay
- charge extra if the client wants priority work to catch up
- pause work until the missing content is provided
- invoice the next milestone if the delay prevents her from completing the stage
This keeps the conversation commercial rather than personal. You aren't blaming the client. You're applying the process both sides agreed to.
You may also want your terms to deal with late payment interest under the Late Payment of Commercial Debts (Interest) Act 1998 for business clients. Whether and how you use that right depends on your client relationship and your usual credit control process.
What Should Your Client Approval Clause Say?
Your client approval clause should say how long the client has to review work, what counts as approval and what happens if they stay silent. This is especially useful when a project is almost finished but the client keeps asking for small changes.
For example, your contract might say the client has 5 business days to review a design or staging site and provide one consolidated round of feedback. If they don't respond within that period, the work is treated as approved unless they raise a genuine defect.
Be careful with how you word this. You want the clause to be fair and workable, not a trap. The aim is to stop projects sitting in limbo for weeks because the client hasn't got around to reviewing them.
Acceptance Testing
For a website development agreement template, acceptance testing is the process for checking whether the website meets the agreed scope.
Your contract should cover:
- which browsers, devices and screen sizes you'll test
- whether testing covers design, functionality, forms, links, checkout flows or integrations
- what is treated as a defect compared with a change request
- how quickly the client must report issues
- when the website is deemed accepted
A defect is usually something that doesn't match the agreed scope, such as a contact form not sending messages. A change request is usually something new or different, such as adding a booking calendar that wasn't included in the original brief.
This distinction matters because defects are usually fixed as part of the project fee, while change requests can be quoted separately.
Who Owns The Website, Content And Code?
Ownership depends on what your contract says and what has been created, licensed or supplied by someone else. Don't assume that the client automatically owns everything just because they paid your invoice.
Under UK copyright law, the person or business that creates original design work, code, copy or graphics will often own the copyright unless it's assigned in writing. For companies, works created by employees in the course of employment are usually owned by the employer. Contractors are different, so your subcontractor arrangements matter too.
Your contract should say what you assign to the client, what you license, and when that handover happens. Many designers only transfer agreed project IP after all invoices have been paid.
Common categories include:
- Client content: copy, logos, photos, brand assets and product information the client gives you.
- Project deliverables: custom page designs, templates, graphics or code created specifically for the client.
- Your pre-existing materials: frameworks, snippets, processes, layouts or tools you already use across projects.
- Third-party materials: plugins, themes, fonts, stock images, APIs and software owned by someone else.
If you design logos, brand marks or product names as part of a broader web project, you should also think about trade marks. In the UK, trade marks are registered through the UK Intellectual Property Office. Your website contract doesn't register a trade mark, but it can make clear who is responsible for clearance searches, filing fees and ownership.
Getting this right protects both sides. The client knows what they can use after handover, and you don't accidentally give away reusable tools or code you need for your business.
What Should You Say About Plugins, Hosting And Support?
Your contract should clearly separate the website build from third-party tools, hosting and ongoing support. This is where many web design terms and conditions become too vague.
Most modern websites rely on things you don't fully control, such as:
- WordPress themes and plugins
- Shopify apps or marketplace extensions
- payment gateways
- email marketing platforms
- booking tools and CRMs
- hosting providers and domain registrars
- stock photo, font and icon licences
Your client may assume these are all included forever. Your contract should say who chooses them, who pays for them, who holds the accounts and what happens if a third-party service changes its pricing, breaks, is discontinued or creates a security issue.
If you host websites for clients, your website terms and conditions should also cover uptime expectations, backups, security updates, access limits and what happens if the client doesn't pay. Avoid promising 100% uptime if you can't control every layer of the service.
Data Protection And Website Forms
If you build contact forms, analytics, newsletter sign-ups or eCommerce features, personal data will usually be involved. That means UK GDPR and the Data Protection Act 2018 may be relevant.
Your contract should explain whether you're acting as a processor for the client, what personal data you can access and what security steps you'll take. The client may also need website terms of use, a privacy policy, cookie wording and proper consent settings for certain tracking tools.
For post-launch support, be specific. You might include 14 or 30 days of bug fixes after launch, but not new pages, new integrations, SEO work, plugin renewals or content updates. If you offer maintenance plans, put those terms in a separate support agreement or schedule so the client knows exactly what they're paying for.
Key Takeaways
- A website design contract helps you set the scope, payment stages and approval process before work starts.
- Your template should deal with client content delays, change requests and what happens if feedback is late or unclear.
- A strong approval clause should explain review periods, acceptance testing and when work is treated as approved.
- IP ownership should be clear, especially for custom designs, reusable code, client content and third-party plugins.
- Hosting, maintenance, plugin licences and data protection obligations should be separated from the core build so there are no hidden assumptions.
- Templates work best when they're tailored to your services, client type and project process before you send them out.
If you'd like help with your website design contracts, client approval clauses, IP handover terms or support and maintenance agreements, you can reach us at 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.
Drafted by Taylor, Sprintlaw's AI, and overseen by Alex Solo. How we write
Protect your brand
What intellectual property should you protect?
If a name, logo, design or other creative work matters to the business, check who owns it, what permissions you need and whether clearance or registration is appropriate.








