Service Agreements in the UK: Defining Deliverables and Liability Limits

You have a client. They want a project done. You agree on a price. But somewhere between that handshake and the final invoice, things go sideways. Maybe the scope crept up. Maybe you delivered exactly what they asked for, but it doesn't work for their business. Or worse, your code caused a data breach, and now they are pointing at you for damages.

In the United Kingdom, a verbal agreement might hold water in small claims court, but it is a nightmare to enforce when real money or reputation is on the line. The difference between a profitable project and a legal disaster often comes down to two specific sections of your service agreement: the definition of deliverables and the limits of liability.

This isn't just about protecting yourself; it's about setting clear expectations so both parties can succeed. Let’s look at how to draft these critical components under current UK law.

The Trap of Vague Deliverables

The most common mistake freelancers and agencies make is describing the outcome rather than the output. If you write "I will improve your website speed," you have opened yourself up to endless revisions. What does "improve" mean? A 1% increase? A 50% increase? Until Google PageSpeed scores 100?

To avoid this, you need to define deliverables with surgical precision. In UK contract law, clarity prevents disputes over whether the service was performed with "reasonable care and skill," a standard implied by the Supply of Goods and Services Act 1982.

Here is how to structure your deliverables section:

• Specific Outputs: List every file, document, or asset you will hand over. Instead of "marketing strategy," specify "a 20-page PDF outlining Q3 social media tactics, including three sample posts per week."
• Acceptance Criteria: Define what "done" looks like. For software, this might be passing a specific set of unit tests. For design, it could be meeting the brand guidelines provided in Appendix A.
• Timelines: Attach dates to milestones. "First draft due by June 1st" is better than "within a reasonable time."
• Exclusions: Explicitly state what you are not doing. This stops scope creep before it starts.

If you are dealing with intellectual property, which is creations of the mind such as inventions, literary and artistic works, designs, symbols, names and images used in commerce, you must also specify when ownership transfers. Under the Copyright, Designs and Patents Act 1988, copyright remains with the creator unless explicitly assigned in writing. Your agreement must state that IP rights transfer only upon full payment.

Setting Liability Caps That Make Sense

Liability clauses are where many contracts fail because they try to exclude all responsibility. Be careful. Under the Consumer Rights Act 2015 and the Unfair Contract Terms Act 1977, you cannot simply say "we are not liable for anything." Such clauses are often deemed unenforceable, especially if you are contracting with consumers or if the exclusion is unreasonable.

Instead of trying to escape liability entirely, you should cap it. The goal is to ensure that the penalty for a mistake is proportional to the value of the contract.

A standard and widely accepted cap is the total value of the contract or the fees paid in the preceding six months. This aligns risk with reward. If a client pays you £5,000 for a logo, they should not be able to sue you for £500,000 in lost sales because they didn't like the color blue. However, you cannot cap liability for death, personal injury, or fraud. These exclusions are illegal.

Intellectual Property: Who Owns What?

As mentioned earlier, IP is a major component of modern service agreements. Whether you are writing code, designing graphics, or creating content, the question of ownership is paramount.

In the UK, the default position is that the creator owns the copyright. If you build a website for a client, you own the code until you assign it to them. Your agreement needs to address three key areas:

1. Moral Rights: Under UK law, creators have moral rights, such as the right to be identified as the author. Clients often require you to waive these rights so they can modify your work without crediting you. Include a waiver clause if this is relevant to your industry.
2. Background IP: You likely use tools, libraries, or templates that you created previously. These are your "background IP." You should license these to the client rather than transferring ownership. This ensures you can reuse your efficient code snippets or design elements for other clients.
3. Foreground IP: This is the new work created specifically for the client. Ownership of foreground IP usually transfers to the client upon final payment. Make sure this condition is explicit.

If you fail to define this, you might find yourself unable to use your own portfolio pieces later, or conversely, the client might claim ownership of your pre-existing tools.

Payment Terms and Breach

A service agreement is useless if you don't get paid. Link your deliverables and liability to payment terms. Standard practice in the UK includes:

• Milestones: Break payments into stages. 30% upfront, 40% on draft delivery, 30% on completion. This keeps cash flow healthy and gives you leverage.
• Late Fees: Specify interest rates for late payments. The Late Payment of Commercial Debts (Interest) Act 1998 allows you to charge statutory interest, but stating a higher rate in the contract (up to 8% above Bank of England base rate) can be more effective.
• Suspension of Work: Include a clause that allows you to pause work if payment is overdue by a certain number of days (e.g., 14 days). This protects you from continuing to invest time in a project that may never be compensated.

Breach of contract occurs when one party fails to meet their obligations. Your agreement should outline what happens next. Does the client get a chance to cure the breach? How much notice do you give before terminating the contract? Clear termination clauses prevent long, expensive legal battles.

Dispute Resolution: Avoiding Court

Litigation in the UK is expensive and slow. Most service agreements include a dispute resolution clause that mandates negotiation or mediation before going to court. This is not just a formality; it saves everyone time and money.

You might specify that any dispute will first be referred to senior management for good-faith negotiation. If that fails, mediation through a recognized body like the Centre for Effective Dispute Resolution (CEDR) is often required. Only if mediation fails should either party seek legal action. This step-by-step approach demonstrates reasonableness, which can be beneficial if the case does end up in front of a judge.

Reviewing Your Agreement Regularly

Laws change. In 2026, we are seeing increased scrutiny on digital services and data privacy following updates to GDPR enforcement. Your service agreement should not be a static document filed away after signing. Review it annually to ensure it complies with current regulations.

Pay particular attention to data protection clauses if you handle personal information. Ensure your liability caps still reflect your insurance coverage. As your business grows, your risk profile changes, and your contracts should evolve with it.