Bought Pro? It is on your account. Sign in

Software dev template · UK · Pro

Software development agreement template for the UK

In short

The UK variant is governed by the law of England and Wales. Copyright in the code is assigned to the client in writing as each milestone is paid, as the Copyright, Designs and Patents Act 1988 requires, and any personal data must be processed in line with the UK GDPR.

A drafting aid, not legal advice. Templates are a starting point and laws change. Have a qualified lawyer review your document before you sign it or rely on it.

14 numbered clauses · 1 optional · Word, PDF and Markdown export · Updated

Pro Pro template: USD 5 for 30 days. The outline and explanations on this page are free to read.

What is a software development agreement?

A software development agreement is a services contract built for building software: a fixed price paid in milestones, acceptance testing against a specification, a change-request process, a bug-fix warranty, rules for open-source components and a full handover of source code, repositories and credentials.

It is a Pro template in Legal Drafter. It assigns the client the IP in each milestone once paid, licenses the developer's reusable tools, blocks copyleft surprises, and offers optional source code escrow.

When you need one

  • Commissioning a mobile or web app, an MVP or an internal tool from an agency or freelancer.
  • Outsourcing development to a team in another country.
  • Any project where payment should depend on accepted milestones.

Typical uses: mobile and web app builds, mvps for startups, agency and outsourced development, custom internal tools.

What changes in the UK (England and Wales)

Governing law
the laws of England and Wales
Disputes
Each party irrevocably agrees that the courts of England and Wales shall have exclusive jurisdiction to settle any dispute or claim (including non-contractual disputes or claims) arising out of or in connection with this Agreement or its subject matter or formation
Default currency
GBP
Date style
21 October 2026
Data protection law cited
the UK General Data Protection Regulation, the Data Protection Act 2018 and the Privacy and Electronic Communications Regulations 2003

Written assignment

An agency or freelancer owns the copyright in code it writes unless it is assigned in writing and signed (section 90(3) of the CDPA 1988). The IP clause does this per milestone.

Processor terms

If the developer processes personal data for you, Article 28 of the UK GDPR requires a contract with specific processor terms. The Confidentiality and data clause covers the core duties; for live systems with personal data, add a full data processing agreement.

Liability

Liability is capped at the total fees, except for fraud, death or personal injury and other liability that cannot be limited. Business-to-business caps must be reasonable under the Unfair Contract Terms Act 1977.

Third-party rights excluded

The UK General clause excludes the Contracts (Rights of Third Parties) Act 1999.

Wording that is specific to the UK version

Generated live from the template: these are the paragraphs that differ from the generic version. Placeholders in brackets are filled from the form.

Confidentiality and data

Each party shall keep the other's confidential information secret and use it only for this Agreement. Where the Developer processes personal data on the Client's behalf, it shall do so only on the Client's documented instructions, keep it secure, and comply with the UK General Data Protection Regulation, the Data Protection Act 2018 and the Privacy and Electronic Communications Regulations 2003.

Governing law and disputes

This Agreement and any dispute or claim (including non-contractual disputes or claims) arising out of or in connection with it or its subject matter shall be governed by and construed in accordance with the laws of England and Wales.

Each party irrevocably agrees that the courts of England and Wales shall have exclusive jurisdiction to settle any dispute or claim (including non-contractual disputes or claims) arising out of or in connection with this Agreement or its subject matter or formation.

Other paragraphs of this clause are the same in every version.

General

(h) Third-party rights. No one other than a party to this Agreement has any right to enforce any of its terms under the Contracts (Rights of Third Parties) Act 1999.

Other paragraphs of this clause are the same in every version.

Sample outline

The UK Software Development Agreement in clause order. Numbering shifts when optional clauses are switched off.

  1. Parties and date
  2. 1.Definitions
  3. 2.Project
  4. 3.Fees and milestones
  5. 4.Acceptance testing
  6. 5.Change requests
  7. 6.Intellectual property and source code
  8. 7.Open-source software
  9. 8.Warranty
  10. 9.Source code escrowoptional, off by default
  11. 10.Confidentiality and data
  12. 11.Limitation of liability
  13. 12.Termination
  14. 13.Governing law and disputes
  15. 14.General
  16. Signatures

Key clauses explained in plain English

Parties and date
The client commissioning the software and the developer building it.
1. Definitions
Key terms used throughout. The Specification is the yardstick for whether the software works.
2. Project
What is being built and how the client is kept informed.
3. Fees and milestones
A fixed price paid in stages, each stage due only once the client accepts that milestone. Running costs such as hosting are separate.
4. Acceptance testing
How the client checks each stage. Silence or going live counts as acceptance, so projects cannot be held up indefinitely.
5. Change requests
New ideas mid-project are priced and approved in writing before work starts, keeping the budget and timeline under control.
6. Intellectual property and source code
The client owns the code once it has paid, and receives the full source, repositories and passwords at the end. The developer keeps reusable tools but licenses them for this software.
7. Open-source software
Open-source code is fine, but some licences can force you to publish your own code. This clause stops that happening by surprise.
8. Warranty
A free bug-fix period after launch. Problems caused by others' changes or third-party services are excluded.
9. Source code escrow
Optional. Protects the client if the developer disappears before handing over the code.
10. Confidentiality and data
Both sides keep information private, and the developer must handle any personal data in the system lawfully and securely.
11. Limitation of liability
Caps liability at the contract value and excludes knock-on losses, with the usual exceptions.
12. Termination
The client can stop the project, paying for work done. In return it receives everything built so far, including the code.
13. Governing law and disputes
Says which country's (or state's) law applies and where any court case or arbitration happens. It also asks both sides to try talking it through for 30 days first, except in emergencies.
14. General
The standard "boilerplate": this document is the whole deal, changes must be in writing, neither side can hand the contract to someone else without permission, a bad clause does not sink the rest, and how formal notices are sent.
Signatures
Where each side signs. For a company, the person signing must be authorised to bind it (for example a director or a manager named on the trade licence).

Common mistakes

  • Assuming you own code you paid for. Without a written assignment, a UK client may only have an implied licence to use the code, which complicates investment and sale of the business.
  • No specification. Acceptance testing measures the software against the specification. Attach one, even a short one, as Schedule 1.
  • Paying everything upfront. Tie payments to milestones that the client accepts. The template invoices each instalment on acceptance.
  • Not getting the keys. Make sure repositories, cloud accounts, app-store accounts and domains end up in the client's name. The IP clause requires handover of credentials and administrative control.
  • Ignoring open-source licences. Some licences (for example the GPL, used in certain ways) can require you to publish your own code. The template requires open-source components to be identified and copyleft use to be approved.

FAQ

Who owns code written by a contractor in the UK?

The contractor, unless copyright is assigned in writing. Employees' code written in the course of employment belongs to the employer.

Do I need a separate data processing agreement?

If the developer will process personal data on your behalf, yes: Article 28 of the UK GDPR sets out terms that must be included.

How is a software development agreement different from a freelance contract?

It adds what software projects need: milestone payments tied to acceptance tests, a warranty period, source code and credentials handover, open-source rules and change control.

Is the software development template free?

No. It is a Pro template. Pro costs USD 5 for 30 days and also removes your personal daily AI limit (a daily AI budget shared by all users still applies) and the export footer. You can read the full clause outline and explanations on this page for free.

Draft your UK software development agreement now

Answer a short guided form and watch the draft fill in live. Party details stay in your browser. Edit any paragraph, switch optional clauses on or off, and export to Word, PDF, Markdown or text.

Draft with Pro

Pro Pro template: USD 5 for 30 days. The outline and explanations on this page are free to read.