You are currently viewing What Should a UK Services Agreement Include?

What Should a UK Services Agreement Include?

Entrepreneur Legal UK · Insight

What Should a UK Services Agreement Include?

Published 22 September 2026 | Last substantive legal review 18 September 2026 General information · Not legal advice

General information focused on ordinary B2B services under the law of England and Wales. Consumer-facing, regulated, public-sector, employment-like and cross-border arrangements may require additional or different rules.

Services agreement at a glance

At-a-glance question Practical answer
Who is this for? Businesses buying or supplying ordinary B2B services under an England and Wales contractual framework.
When does it arise? Before services begin, when a new project or statement of work is agreed, or when scope, pricing or delivery responsibilities materially change.
Is a Services Agreement legally required? There is no universal rule requiring every B2B service relationship to use a document with this title. Written terms are usually commercially advisable, and specific laws can require particular contractual terms in defined situations.
Routine drafting route StartWise® Services Agreement where the commercial arrangement is reasonably standard and the parties understand the deal they want to document.
Get legal advice first when The engagement is heavily negotiated, regulated, consumer-facing, cross-border, unusually high-value, involves complex IP/data issues or needs bespoke liability/indemnity architecture.

Clause checklist: what a services agreement normally needs

Clause area What it should answer Founder mistake to avoid
Parties and authority Which legal entities are contracting, and who can bind them? Using a trading name when the contracting company is different.
Services and scope Exactly what will be done, what is excluded, and what assumptions apply? Relying on a proposal or chat thread that conflicts with the signed contract.
Deliverables and timing What is delivered, by when, and what dependencies sit with the client? Promising a deadline without tying it to client inputs or approvals.
Fees and payment Price, VAT, invoicing, expenses, due dates, deposits and late-payment treatment. Stating a price but not the trigger for invoicing or payment.
Changes and acceptance How scope changes are approved and how deliverables are accepted. Letting extra work become an informal expectation.
IP and licence Who owns pre-existing materials and newly created work, and what licence is granted? Assuming paying a freelancer or agency automatically transfers copyright.
Confidentiality and data What information is protected and whether personal-data processing needs separate terms. Using confidentiality wording as a substitute for data-protection obligations.
Warranties and standards What level of performance is promised and what is expressly not promised? Giving outcome guarantees the supplier cannot control.
Liability and indemnities What losses are covered, excluded or capped, subject to legal limits? Copying an aggressive liability cap without testing whether it is enforceable or commercially acceptable.
Term and termination When does the contract start/end, and what happens on termination? Forgetting payment, handover, IP and data obligations on exit.
Law and disputes Which law governs and where/how disputes are handled? Choosing a jurisdiction by habit in a cross-border deal.

Why founders usually discover the problem after the work has started

Imagine a small product studio agrees an £18,000 website and brand project for a fast-growing client. The proposal says “website redesign and launch support”, but it does not define how many page templates are included, who supplies copy, how many revision rounds are permitted, when the client is deemed to have accepted a deliverable, or who owns the design system before the final invoice is paid.

Two weeks later, the project is not failing because the parties distrust each other. It is failing because the commercial deal was never translated into operational rules.

That is the practical purpose of a services agreement. It is not simply a longer version of a quote. It creates a shared operating framework for delivery, payment, ownership, risk and exit.

1. Define the parties and the actual service

Start with the contracting entities, not merely the people speaking to each other. A founder may negotiate with “Alex at Northstar”, while the legal counterparty is Northstar Digital Ltd. The agreement should identify the correct entity and make clear which party is the supplier and which is the client.

Then make the scope operational. Describe the services, deliverables, excluded work, milestones, client dependencies and assumptions. If there is a separate statement of work, proposal or order form, say how it fits with the main agreement and which document takes priority if the documents conflict.

2. Make payment mechanics precise

A useful payment clause covers more than the headline fee. It can address deposits, milestone invoices, recurring fees, VAT, approved expenses, invoice requirements, payment dates, disputed invoices and consequences of late payment.

Under the current late-payment regime for qualifying business-to-business debts, statutory interest can arise at 8 percentage points above the applicable Bank of England reference rate unless the contract provides a different remedy that qualifies as a substantial remedy under the Late Payment of Commercial Debts (Interest) Act 1998. Where businesses expressly agree a payment date, a payment period longer than 60 days is permitted only where the longer period is expressly agreed and is not grossly unfair to the supplier. If no payment date is agreed, statutory interest generally begins 30 days after the relevant statutory trigger.

3. Control scope creep with change and acceptance rules

A services relationship often changes after signature. The agreement should explain how additional work is requested, priced and approved. For project work, an acceptance process can also define when a deliverable is accepted, what counts as a valid rejection, and how genuine defects are corrected.

This is particularly useful where the client’s internal delay can affect the supplier’s timeline. A founder should be able to answer: what happens if feedback arrives two weeks late, if a key decision-maker changes the brief, or if the client wants a feature that was never part of the agreed scope?

4. Deal expressly with intellectual property

IP is one of the most common places where commercial expectation and legal ownership diverge. UK Intellectual Property Office guidance explains that a freelancer or independent contractor will usually retain copyright in work they create unless the parties agree otherwise. Commissioning and paying for work does not automatically transfer copyright ownership. A valid copyright assignment should be in writing and signed by the copyright owner.

A services agreement should therefore distinguish pre-existing IP from project-created IP and decide whether the client receives an assignment, an exclusive licence, a non-exclusive licence, or a more limited right of use. It should also address third-party materials, open-source components and portfolio use where relevant. Copyright is one common services-output issue, but patents, registered and unregistered designs, trade marks, database rights and other IP can follow different ownership or transfer rules and should be addressed where relevant.

5. Deal separately with confidentiality and data protection

Confidentiality and data protection are related but not interchangeable. The agreement should define confidential information and permitted use, but a confidentiality clause does not by itself satisfy data-protection requirements.

If the supplier processes personal data as a processor on the client’s behalf, UK GDPR Article 28 requires the processing to be governed by a binding contract or other legal act containing specified terms. Those provisions can sit in the Services Agreement or a separate data processing agreement. If the parties act as independent controllers instead, a different analysis applies.

6. State the standard of performance without over-promising

For many business service contracts, the Supply of Goods and Services Act 1982 implies a term that a supplier acting in the course of business will carry out the service with reasonable care and skill. Where the contract does not fix time or price in the relevant circumstances, the Act can also imply reasonable time and reasonable charge provisions.

The written agreement can make the commercial standard more specific, but founders should avoid converting a professional obligation into an uncontrolled outcome guarantee. A marketing consultant can promise to perform agreed services with defined care and deliverables; promising a particular level of revenue is a different risk.

7. Treat liability clauses as risk allocation, not boilerplate

Liability provisions should be written around the actual risk profile of the service. They may address direct losses, excluded categories of loss, financial caps, indemnities, insurance, responsibility for client materials and claims brought by third parties.

Freedom of contract is not unlimited. Under section 2 of the Unfair Contract Terms Act 1977, liability for death or personal injury resulting from negligence cannot be excluded or restricted. Restrictions on liability for other negligence losses are subject to a reasonableness requirement. Other statutory controls can also apply depending on the parties and terms.

8. Plan the end of the relationship before there is a dispute

Termination clauses can cover expiry, termination for material breach, insolvency events, termination on notice, cure periods and the consequences of exit. The consequences matter: outstanding invoices, return of confidential information, transfer of work in progress, ongoing licences, deletion or return of data, transition assistance and clauses that survive termination.

For a routine B2B services relationship where the commercial deal is already understood, StartWise® Drafting can provide a guided route to a tailored first draft. Choose the Services Agreement, answer guided questions about the parties and commercial terms, generate the first draft, then review any Drafting Notes that may highlight assumptions, points to confirm or circumstances where lawyer review may be appropriate.

StartWise® is not a substitute for legal judgement. Consider legal support before relying on a standard drafting route if the engagement is heavily negotiated, regulated, consumer-facing, cross-border, unusually high-value, involves sensitive data, contains complex IP licensing, or requires bespoke indemnity or liability architecture.

Create a free StartWise® account to explore available documents. Drafting credits are required when you are ready to generate a document.

Common services agreement mistakes

  • Using a scope that describes the project but not the boundaries of the project.
  • Leaving client responsibilities and dependencies out of the timeline.
  • Treating payment terms as an invoice-template issue rather than a contractual issue.
  • Assuming ownership of commissioned work follows payment automatically.
  • Copying limitation-of-liability wording without checking legal controls or the actual commercial risk.
  • Failing to say what happens to work, data, licences and payment obligations when the relationship ends.

FAQs

Is a services agreement legally required for every UK B2B project?

Not every B2B service relationship is subject to a single rule requiring one document called a “Services Agreement”. Contracts can arise in different ways. The practical reason for a written agreement is to record the deal, reduce ambiguity and allocate risk before a problem occurs.

Can a proposal or statement of work replace the main agreement?

It can form part of the contractual framework, but it should be clear what terms apply and which document prevails if the documents conflict. A proposal often describes the commercial scope but does not address the full legal and operational relationship.

Do I automatically own work I paid a contractor to create?

Not necessarily. In the UK, commissioned or freelance copyright will usually remain with the creator unless ownership is dealt with contractually. A copyright transfer should be recorded in a written, signed agreement.

Can I cap all liability at the amount of the fees?

A financial cap can be commercially useful, but it is not automatically effective for every type of liability. Legal controls, including the Unfair Contract Terms Act 1977 in relevant B2B situations, can restrict exclusions and limitations.

When should I ask a lawyer to review the agreement?

Review is more valuable when the agreement is heavily negotiated, the liability exposure is material, the service is regulated or consumer-facing, the deal is cross-border, or the IP, data or indemnity provisions are not routine.

Author, review date and jurisdiction

Author / reviewer: Gabriel C. Mbanefo — Solicitor of the Senior Courts of England and Wales; Director & CEO, Entrepreneur Legal UK.

Publication date: 22 September 2026.

Last substantive legal review: 18 September 2026.

Jurisdiction statement: General information focused on ordinary B2B services under the law of England and Wales. Consumer-facing, regulated, public-sector, employment-like and cross-border arrangements may require additional or different rules. Not legal advice.

Important information

StartWise® Drafting is not legal advice, lawyer review, legal approval or legal sign-off. Creating an account, purchasing drafting credits or generating a document does not by itself create a lawyer-client relationship. Entrepreneur Legal UK is the trading name of Entrepreneur Legal Ltd. Entrepreneur Legal Ltd is not regulated by the Solicitors Regulation Authority and does not carry on reserved legal activities.

Choose the right next step

Draft through StartWise. Review for less.

Explore the current guided UK workflows, or contact Entrepreneur Legal UK where your matter requires review, consultation or bespoke support.