Most agency disputes were entirely foreseeable. The client thought the contract included unlimited revisions. You thought it obviously didn’t. Neither of you wrote it down clearly enough. Now you have a choice between swallowing three weeks of unpaid work or having a conversation that damages the relationship either way.
Weak contracts are not just a legal risk — they are an operational one. They generate scope creep, delayed payments, unclear deliverables, and the kind of end-of-project arguments that ruin what would otherwise have been a successful engagement. Every clause in a well-drafted agency contract exists because someone, somewhere, got stung by its absence.
This guide covers what every UK digital agency client contract must include. It is not legal advice, and for high-value or complex engagements you should always have a solicitor review your documents. But it will ensure you have covered the essentials that most agency contracts get wrong — and give you a framework to build from.
Scope of Work: The Most Important Clause in the Contract
If you take nothing else from this article, take this: write the scope of work as if a stranger with no context will have to judge whether it was met. Because that is exactly what happens when a contract dispute goes to mediation or court. Vague language — “ongoing marketing support,” “regular social media management,” “a website redesign” — is essentially worthless. Specific language is what protects you.
A proper scope of work clause should specify what is included, what is explicitly excluded, and what the deliverables are. For a website project, that means naming the number of pages, the technology stack, whether copywriting and photography are included or client-supplied, how many design concepts will be presented, and how many rounds of revisions are covered. For a retainer, it means the number of hours per month (or the specific activities), the reporting cadence, and what happens when the client requests work outside the defined scope.
The exclusions section is as important as the inclusions. If you are building a website but not providing SEO, say so. If you are managing paid social but not organic, say so. Clients rarely read contracts carefully before signing — they read them when something goes wrong. An explicit exclusion stops a future “but I assumed that was included” conversation before it starts.
Practical tip: attach a separate Statement of Work (SoW) document to the master contract for each project or retainer engagement. The master contract covers the legal and commercial terms; the SoW covers the specific deliverables. This makes it easy to update scope on new engagements without redrafting the whole agreement.
Payment Terms and Late Payment Provisions
Your contract should leave absolutely no ambiguity about when money is due and what happens when it is not paid. The UK’s Late Payment of Commercial Debts (Interest) Act 1998 gives you the right to charge statutory interest on overdue invoices — currently 8% above the Bank of England base rate — but most agencies never invoke it because their contracts do not reference it. Knowing the right exists is not enough; it needs to be in your agreement.
Specify your payment terms explicitly: net 14 days, net 30, or whatever you have agreed. Then state what happens if payment is not received within that period. A well-drafted clause will include the statutory interest rate you will apply, a fixed sum charge under the Late Payment Act (£100 for debts over £10,000), and your right to suspend work and withhold deliverables until the account is cleared.
For project-based work, your contract should specify a payment schedule tied to milestones rather than delivery. A common structure for a £10,000 website project might be 40% on signature, 40% on design approval, and 20% on launch. This ensures you are never more than one milestone of exposure at any point in the project. For retainers, invoice in advance — the first invoice before work begins, subsequent invoices on the first of each month. Never invoice in arrears if you can avoid it; it puts you in the position of chasing money for work already done.
Include a clause confirming that ownership of deliverables does not transfer to the client until all outstanding invoices are paid in full. This gives you a practical remedy if a client tries to use your work while disputing an invoice.
Intellectual Property and Licence Terms
IP clauses are the ones most likely to cause a dispute long after the engagement ends. The default legal position in the UK is that the creator of a work owns the copyright — not the person who commissioned it. This means that unless your contract explicitly assigns IP to the client, you retain it. Some agencies use this deliberately, licensing work rather than assigning it. Others want to assign it but forget to say so. Either way, be explicit.
For most client engagements, the sensible approach is to assign all intellectual property in the final deliverables to the client on receipt of full payment. Note the “on receipt of full payment” condition — this is your most effective leverage if a client disputes an invoice. Until it is paid, you own the work.
Be clear about what is and is not being assigned. Third-party licences — stock photography, fonts, software plugins, licensed music — cannot be assigned because you do not own them. Your contract should specify that the client is responsible for ensuring they have appropriate licences for any third-party assets incorporated into their deliverables. This is particularly relevant for WordPress agencies: a theme or plugin licence is almost never transferable to the client by default, and the consequences of an unlicensed installation can include takedowns and fines.
If you use proprietary tools, frameworks, or code libraries in your work — things you have built and use across multiple clients — you should retain ownership of those components and grant the client a licence to use them, rather than assigning them outright. Otherwise you risk signing away your own toolkit to the first client who commissions it.
Change Requests and Scope Creep
Scope creep is not a client failing — it is a process failing. Clients will always want more than the original brief covers; that is human nature and often reflects genuine business need. The question is whether your contract gives you a mechanism to manage that expansion commercially rather than absorbing it.
Your contract needs a formal change request process. Every request for work outside the agreed scope should be documented in writing (a change request form, a follow-up email, a note in your project management system — anything with a timestamp), confirmed as out of scope with reference to the original SoW, and quoted separately before work begins. The contract should state explicitly that the agency is not obliged to begin out-of-scope work until a change request has been signed and, where applicable, an additional deposit paid.
This is not about being difficult with clients — it is about running a business. An agency that absorbs scope creep silently trains its clients to expect it. Document the change request process in your onboarding, explain it at kick-off, and apply it consistently. Clients who understand the process generally respect it; the ones who push back were probably going to be difficult regardless.
For retainer clients, define what happens when they exceed their monthly allocation. Either the excess hours roll into the following month’s invoice at an agreed rate, or they carry forward as credit for future months. Either approach is fine — but one of them needs to be in the contract, with the hourly rate specified, or you will have this conversation every month.
Termination, Notice Periods, and Kill Fees
Termination clauses are where the interests of agency and client diverge most sharply, and they repay careful drafting. A client who can walk away on 24 hours’ notice is a client who has all the leverage. A contract that prevents a client from leaving a bad relationship destroys trust and generates disputes. The right answer sits between those extremes.
For retainer agreements, a 30-day written notice period is standard and generally accepted by clients. For longer retainers or those involving significant setup investment (a bespoke client portal, a custom integration, dedicated resource allocation), 60 days is reasonable and usually accepted if explained at the time of signing. Build in a minimum initial term — typically three months — during which neither party can terminate without cause. This protects you from a client who signs, gets the initial work done, and immediately cancels.
For project-based work, include a kill fee clause. If a client terminates a project mid-delivery, they should be liable for all work completed to date plus a kill fee — typically 25–30% of the remaining project value. This compensates you for the pipeline opportunity cost of having committed that resource. Without a kill fee, a client can walk away from a 60% complete project having paid only for the work they received, leaving you with a half-finished portfolio piece and a resource hole.
Also specify what termination for cause looks like on both sides. Your rights to terminate immediately should include non-payment beyond a specified period (typically 30 days overdue), client instructions that are illegal or reputationally damaging, and material breach of the agreement. The client’s right to terminate for cause should be narrowly defined — typically limited to serious failures to deliver against contracted milestones.
Liability Limitations and Indemnity
A liability clause will not make you popular, but it will stop a single mistake from ending your agency. The principle is straightforward: you are limiting the financial exposure you accept in connection with the engagement. Without a cap on liability, a client who suffers a significant loss that they attribute — however spuriously — to your work can theoretically pursue you for the full value of that loss.
The standard approach for UK agencies is to cap your total liability under the agreement to the value of fees paid in the 12 months preceding the claim. So if a client pays you £3,000 per month and something goes wrong, your maximum exposure is £36,000 — not whatever their business losses amount to. This figure should sit comfortably within your professional indemnity insurance cover.
Your contract should also specifically exclude liability for indirect and consequential losses — lost profits, lost contracts, reputational damage, business interruption. These are the categories of loss that can be disproportionately large relative to the fee value of the engagement. A client who loses a £500,000 contract due to a website outage on a day when you were running a scheduled maintenance window — however unfairly they attribute causation — should not be able to pursue you for that figure.
Include a mutual indemnity clause covering third-party claims arising from each party’s own material. If the client supplies you with copy that infringes someone’s copyright and a third party sues, that should be the client’s problem, not yours. Conversely, if your design work infringes third-party IP, that is your indemnity to provide.
Confidentiality and Data Protection
UK agencies handling client data need a contract that addresses data protection obligations explicitly, particularly since the UK GDPR came into force. If you process personal data on behalf of a client — managing their CRM, running their email marketing, building their e-commerce platform — you are acting as a data processor and the client is the data controller. This is not just a technical distinction; it creates specific legal obligations that belong in the contract.
Your contract should include a data processing addendum (DPA) that specifies what personal data you process, for what purpose, for how long, and what security measures you apply. The DPA should confirm that you will only process data on the client’s documented instructions, that you will assist the client in meeting their own data subject obligations (access requests, erasure requests), and that you will notify the client promptly in the event of a data breach.
The confidentiality clause should be mutual: you agree not to disclose the client’s confidential business information, and they agree not to disclose your proprietary methods, pricing, and unreleased work. Include a carve-out allowing you to reference the client relationship in your portfolio and marketing — but make this carve-out explicit rather than assumed. Some clients are sensitive about being named as customers, particularly in competitive industries, and a blanket confidentiality clause that you assumed allowed case studies could prevent you from using work you are proud of.
Governing Law and Dispute Resolution
This section rarely matters — until it does. Specify that the contract is governed by English law (or Scots law if that is more appropriate for your location), and that disputes will be subject to the exclusive jurisdiction of the English courts. For agencies working with overseas clients, this is particularly important — without a governing law clause, a dispute could theoretically be litigated in the client’s home jurisdiction under local rules.
Consider including a tiered dispute resolution clause: before either party can commence formal legal proceedings, they must first attempt resolution through good-faith negotiation (typically 30 days), and if that fails, through mediation. The Centre for Effective Dispute Resolution (CEDR) offers mediation services that cost a fraction of litigation and resolve most commercial disputes without reaching court. Building this into the contract can save both parties significant time and cost.
Finally, include a clause confirming that each party has had the opportunity to take independent legal advice before signing. This is not a formality — it strengthens the enforceability of the agreement, particularly for onerous clauses like the liability cap, which a court might scrutinise more carefully if there is any suggestion that the weaker party did not fully understand what they were agreeing to.
Signing, Storing, and Tracking Your Contracts
A well-drafted contract that sits in a Google Drive folder you can never find is not much more useful than no contract. The operational side of contract management matters as much as the legal drafting.
E-sign is legally valid in the UK under the Electronic Communications Act 2000 and the eIDAS regulation. Both parties clicking “I agree” on a documented digital signature service — or even an email exchange in which both parties confirm acceptance — constitutes a binding agreement. You do not need wet signatures for commercial contracts. Use an e-sign workflow: it is faster, it creates an audit trail, and it eliminates the “I sent it, they haven’t signed it yet” limbo that lets projects start without a contract in place.
Store every signed contract linked to the relevant client record, with a clear record of the date signed, the parties, the value, and the key dates (contract start, minimum term end, notice period, renewal date). Marque CRM’s contract management module handles this natively — you can build a contract template once, send it for e-sign directly from the platform, and have it automatically attached to the client record when countersigned. Renewal reminders and minimum term alerts come built in, so you are not relying on a calendar entry someone set up two years ago.
Review your standard contract template at least once a year. Law changes, your services evolve, and the gaps you discover in live engagements should feed back into the template. Every time you encounter a dispute that your contract did not adequately cover, that is a note to update the document. After two or three years of this process, your template will be genuinely robust — not because you spent £5,000 on a solicitor to draft it perfectly from scratch, but because it has been tested against reality.
For more on building the operational infrastructure that supports strong client relationships, read our guide to building a client onboarding process that retains from day one, our overview of billing systems that do not leak revenue, and the full breakdown of Marque CRM’s contracts and e-sign features.