What to Include in a Digital Agency Service Agreement (And How to Get It Signed Digitally)

Why Your Service Agreement Is the Most Important Document in Your Agency

A service agreement between a digital agency and a client is not a formality. It is the document that determines what happens when things go wrong -- and something always goes wrong eventually, whether it is a client who changes their mind about the brief, a project that runs long, or a dispute over what was and was not agreed.

Agencies that operate on verbal agreements, rough email threads, or one-page quotes without terms experience significantly more scope creep, late payment, and client disputes than those who invest in a comprehensive service agreement.

This guide covers everything your service agreement needs to include, why each clause matters, and how to get it signed without the friction of printing and scanning.

The 12 Essential Clauses in a Digital Agency Service Agreement

1. Identification of Parties

State clearly who is entering the agreement. Include:

Full legal name of the agency (not just the trading name)
Registered company address
Company registration number (if applicable)
Full legal name of the client (company name or individual)
Client's registered or trading address

This sounds obvious, but agreements signed without full legal identification are harder to enforce. "ABC Creative" is not a sufficient party name if the agency is registered as "ABC Creative Solutions Ltd."

2. Scope of Work

The scope of work is the most important operational clause in the agreement. It defines exactly what the agency will deliver.

A well-written scope includes:

A description of each deliverable
Technical specifications where relevant (e.g., "five-page WordPress website with contact form")
What is explicitly excluded (e.g., "does not include copywriting, photography, or hosting")
Number of design concepts to be presented
Number of revision rounds included
Any dependencies on third parties (e.g., client must supply copy before design begins)

The more specific the scope, the stronger your position when a client asks for work outside it.

3. Timeline and Milestones

Define the project timeline, including:

Project start date (linked to contract signing and deposit receipt)
Key milestones with target completion dates
Final delivery date
Client response windows (e.g., "client has five business days to provide feedback at each milestone")
The consequence of client delays on the overall timeline

A timeline clause that acknowledges client-caused delays is essential. If a client takes three weeks to provide feedback when the agreement says five business days, the agency should not be bound to the original final delivery date.

4. Fees and Payment Schedule

Be explicit about money. Include:

Total project fee
Payment schedule (deposit on signing, interim milestone payments, final payment on delivery)
Payment method (bank transfer, card)
Invoice terms (payment due within how many days of invoice)
Late payment penalties (under the Late Payment of Commercial Debts Act 1998, UK businesses can charge statutory interest of 8% above base rate on overdue commercial invoices)
VAT position (state whether fees are inclusive or exclusive of VAT)

5. Revision and Change Request Policy

Define what counts as a revision versus a change request, and what happens when clients exceed the agreed revision rounds.

A clear revision policy includes:

Number of revision rounds included in the fee
Definition of what constitutes a minor revision versus a scope change
The process for requesting additional revisions or changes
Day rate or hourly rate for out-of-scope work

Without a revision policy, "just one more tweak" becomes an unlimited claim on your time.

6. Client Responsibilities and Dependencies

Many agencies neglect to define what the client is responsible for delivering, and when. This is a significant omission.

Client responsibilities to document:

Providing all required content (copy, images, video) by an agreed date
Supplying brand assets in required formats
Designating a named point of contact with authority to approve work
Responding to feedback requests within the agreed window
Providing access to required platforms (see the 7-step website client onboarding process for how to structure this as a formal onboarding step)

If the project stalls because the client has not supplied copy, the client -- not the agency -- should be responsible for the resulting delay. Document this explicitly.

7. Intellectual Property

Specify who owns what, and when ownership transfers.

Standard positions:

Design concepts not selected: Agency retains ownership
Final deliverables: Client owns upon receipt of final payment
Third-party assets (stock images, fonts, plugins): Subject to their own licences, which the client must obtain

Critically, if the client has not paid the final invoice, the agency retains copyright in the deliverables. This is the default position under UK copyright law (Copyright, Designs and Patents Act 1988), but making it explicit in the contract removes ambiguity.

8. Confidentiality

Both parties may share sensitive information during the project. A confidentiality clause protects both sides:

Agency must keep client business information, credentials, and data confidential
Client must keep any proprietary agency processes, templates, or pricing confidential
Specify the duration of the confidentiality obligation (typically two to five years post-project)

9. Data Processing

Under UK GDPR, if the agency processes personal data on behalf of the client, a Data Processing Agreement (DPA) is required by law. For most website projects this is relevant when:

The agency has access to the client's CRM or email marketing platform
The agency handles contact form data or analytics data
The agency stores client or end-user data as part of the project

Many agencies overlook this and expose themselves to regulatory risk. If your work involves personal data, include a DPA or attach one as an appendix. This is particularly relevant when collecting client platform credentials -- hosting logins, CMS access, and analytics permissions are subject to the same data protection obligations.

10. Termination

Define what happens if the relationship ends early.

Termination clause elements:

How either party can end the agreement (written notice period, typically 14-30 days)
Kill fee: the amount owed to the agency if the client terminates without cause (typically 25-50% of remaining project fees)
What happens to work in progress (agency may retain completed work until outstanding fees are paid)
Client's obligation to pay for work completed to the termination date

11. Liability Limitation

Limit the agency's financial liability to the total fees paid under the agreement. Without this clause, a dissatisfied client could theoretically seek damages far exceeding the project value.

Also exclude liability for:

Losses caused by client-supplied content (defamatory copy, infringing images)
Third-party platform outages or changes (Google algorithm updates, hosting failures)
Indirect or consequential losses

Have a solicitor review your liability clause to ensure it is enforceable under the Unfair Contract Terms Act 1977 and the Consumer Rights Act 2015 (if any of your clients are consumers rather than businesses).

12. Governing Law and Jurisdiction

State that the agreement is governed by the laws of England and Wales (or Scotland if applicable) and that disputes will be subject to the jurisdiction of the English courts. This is essential if you work with international clients.

How to Get a Service Agreement Signed Without Printing or Scanning

Sending a PDF for the client to print, sign, and scan back is inefficient and creates issues with document quality and legibility. More importantly, it slows down the agreement process by days when clients are busy.

Use e-signature tools:

DocuSign -- the most widely recognised, with a free tier for limited use
Adobe Acrobat Sign -- works natively with PDF workflows
PandaDoc -- combines proposal, contract, and e-signature in one platform
Dedicated onboarding platforms like Onboard -- embed e-signature as a step within the client onboarding portal, so the client signs the agreement alongside completing other onboarding tasks in a single workflow

Electronic signatures are legally binding in the UK under the Electronic Communications Act 2000 and the eIDAS Regulation (retained post-Brexit). A qualified electronic signature (QES) carries the highest legal weight, but a simple click-to-sign or typed signature is sufficient for most commercial contracts.

Best practice:

Ask clients to sign the agreement and pay the deposit simultaneously. Agencies that separate these steps often end up with a signed contract but no payment, or a payment but no signed contract.

A client portal that presents both the agreement signing and the deposit invoice as adjacent steps in the onboarding workflow -- with progress tracking for both -- ensures neither is missed.

Frequently Asked Questions

Do I need a solicitor to draft my agency service agreement? Not necessarily for a first draft, but having a solicitor review your agreement is money well spent. An agreement reviewed by a commercial solicitor typically costs between £300 and £800 as a one-off investment, and it will be used for years across multiple clients.

Can I use a free contract template from the internet? With caution. Generic templates may not reflect UK law, may not address the specific risks of digital agency work, and may contain clauses that are unenforceable under UK consumer or contract law. Treat any template as a starting point for review, not a finished document.

What is the difference between a service agreement and a statement of work? A service agreement sets out the general terms and conditions of the working relationship. A statement of work (SOW) defines the scope, timeline, and deliverables of a specific project. Some agencies use one combined document; others use a master agreement with individual SOWs per project. Both approaches are valid.

Is an email chain sufficient to form a binding contract? In some cases, yes -- an exchange of emails agreeing to scope, price, and terms can constitute a contract under UK law. But this is significantly harder to enforce than a formal signed agreement, particularly if the email chain is ambiguous or informal. Always use a signed agreement.