Who owns the copyright in bespoke software under English law?

Under section 11(1) of the Copyright, Designs and Patents Act 1988, the author of a literary work (which includes computer programs under section 3(1)(b)) is the first owner of copyright. Unlike the position in an employment relationship, where section 11(2) automatically vests copyright in the employer, a client who commissions software from an independent developer does not automatically acquire copyright ownership. The developer retains copyright unless the agreement contains an express assignment clause. This is a fundamental difference from many other jurisdictions and makes a written software development agreement with clear IP provisions essential. An assignment of copyright must be in writing and signed by the assignor to be effective (section 90(3)). For future works, the assignment can take effect as a present assignment of future copyright under section 91, which operates automatically when the copyright comes into existence.

What is source code escrow and when should it be used?

Source code escrow is an arrangement where the developer deposits a copy of the software's source code with an independent third-party escrow agent. The source code is released to the client upon the occurrence of specified trigger events, typically the developer's insolvency, cessation of business, or material breach of the agreement. Escrow is particularly valuable when the client depends on the software for critical business operations and the developer retains ownership of the IP (or where ongoing maintenance and updates are needed). Leading UK escrow providers include NCC Group and Iron Mountain. The escrow agreement is a separate three-party contract between the client, developer, and escrow agent. The deposited materials should include all source code, build scripts, database schemas, configuration files, and documentation necessary to compile, run, and maintain the software independently.

How does IR35 affect a software development engagement in the UK?

The IR35 off-payroll working rules, contained in Chapter 10 of Part 2 of the Income Tax (Earnings and Pensions) Act 2003, are designed to ensure that individuals who work through an intermediary (typically a personal service company) but who would be employees if engaged directly pay broadly the same tax and National Insurance as employees. Since April 2021, medium and large private-sector clients (as defined by section 382 of the Companies Act 2006) are responsible for determining whether an engagement falls inside or outside IR35. The determination depends on three key tests: control (does the client direct how the work is done?), substitution (can the developer send a replacement?), and mutuality of obligation (is there an obligation to offer and accept work?). A genuine software development project engagement, where the developer works to a specification rather than under day-to-day supervision, can send a substitute, and is engaged for a specific project with no ongoing obligation, is more likely to fall outside IR35.

What protection does the Computer Misuse Act 1990 provide?

The Computer Misuse Act 1990 creates three principal offences relevant to software development. Section 1 makes it an offence to knowingly cause a computer to perform any function with intent to secure unauthorised access to any program or data, punishable by up to two years' imprisonment. Section 2 creates an aggravated offence of unauthorised access with intent to commit or facilitate further offences, carrying up to five years' imprisonment. Section 3 makes it an offence to do any unauthorised act in relation to a computer with intent to impair its operation or to prevent or hinder access to data, punishable by up to ten years' imprisonment. A software development agreement should include a warranty that the developer will not introduce malicious code, will only access client systems within the scope authorised by the agreement, and will comply with all applicable provisions of the Act.

Can a developer limit their liability in a UK software development contract?

Under English law, contractual limitation of liability clauses are permitted but are subject to the Unfair Contract Terms Act 1977 (UCTA). Section 2(1) of UCTA prohibits the exclusion of liability for death or personal injury caused by negligence. Section 2(2) permits the exclusion of liability for other losses caused by negligence only insofar as the clause satisfies the requirement of reasonableness under section 11. Section 3 applies where one party deals on the other's written standard terms and limits the ability to exclude or restrict liability for breach of contract. When assessing reasonableness, courts consider the parties' relative bargaining positions, whether the client received an inducement (such as a lower price) in return for accepting the limitation, the availability of insurance, and the practical consequences of the clause. Common limitation structures in software development contracts include a cap on aggregate liability equal to the total fees paid, or the amount recoverable under professional indemnity insurance, with carve-outs for fraud, wilful default, IP infringement, and data protection breaches.

Software Development Agreement (UK) — United Kingdom

Create a comprehensive UK Software Development Agreement for England and Wales governing the engagement of a developer or software development company to design, build, test, and deliver bespoke software. This template addresses the critical issue of intellectual property ownership under the Copyright, Designs and Patents Act 1988, which vests first ownership of copyright in the author (the developer) rather than the commissioning client, unlike the position for employees. The agreement provides two IP models: full assignment of all IP rights to the client, or retention by the developer with a licence granted to the client. The template covers project scope and specification, development methodology selection (Agile Scrum, Kanban, Waterfall, or Hybrid), milestone-based deliverables with acceptance testing procedures, technology stack specification, and formal change request processes. Fee structures include fixed project fees, time and materials (daily or hourly rates), and milestone-based payments, all payable in GBP with late payment interest under the Late Payment of Commercial Debts (Interest) Act 1998. IR35 off-payroll working provisions address the developer's employment status under the Income Tax (Earnings and Pensions) Act 2003, including control, substitution, and mutuality of obligation tests. The agreement includes optional source code escrow provisions to protect the client if the developer becomes insolvent. Security provisions address obligations under the Computer Misuse Act 1990, and data protection clauses comply with the Data Protection Act 2018 and UK GDPR, including data protection by design requirements. Warranty provisions, limitation of liability, professional indemnity insurance, and comprehensive termination and handover provisions complete the agreement. Suitable for software developers, agencies, and businesses commissioning bespoke software across England and Wales. Fill out the wizard, preview in real time, and download as PDF or Word.

What Is a Software Development Agreement (UK)?

A UK Software Development Agreement is a legally binding contract between a client and a software developer (or development company) that governs the design, development, testing, and delivery of bespoke software in England and Wales. This agreement is essential whenever a business commissions custom software from an external developer rather than purchasing off-the-shelf products or developing in-house.

The most critical legal issue in any UK software development engagement is intellectual property ownership. Under section 11(1) of the Copyright, Designs and Patents Act 1988 (CDPA), the author of a computer program is the first owner of the copyright in that program. This means that, unlike an employment situation where section 11(2) automatically vests copyright in the employer, a client who commissions software from an independent contractor does not automatically own the resulting intellectual property. Without an express written assignment, the developer retains all IP rights. Section 90(3) of the CDPA requires that an assignment of copyright must be in writing and signed by the assignor. For future works, section 91 permits a present assignment of future copyright, which takes effect automatically when the copyright comes into existence. A well-drafted software development agreement should therefore contain an express assignment clause (if the client is to own the IP) or clearly define the licence terms (if the developer retains ownership).

The IR35 off-payroll working rules, contained in Chapter 10 of Part 2 of the Income Tax (Earnings and Pensions) Act 2003, add a further layer of complexity. Since April 2021, medium and large private-sector clients have been responsible for determining whether a developer engaged through a personal service company should be treated as an employee for tax purposes. The agreement should address the three key IR35 tests: control, substitution, and mutuality of obligation.

Security is another essential consideration. The Computer Misuse Act 1990 creates criminal offences for unauthorised access to computer systems (section 1), unauthorised access with intent to commit further offences (section 2), and unauthorised acts intended to impair the operation of a computer (section 3). The agreement should include warranties that the developer will comply with this legislation and will not introduce malicious code into the client's systems.

Where the software will process personal data, the agreement must comply with the Data Protection Act 2018 and the UK General Data Protection Regulation (UK GDPR). Article 25 of the UK GDPR requires data protection by design and by default, meaning the developer should build privacy and security features into the software from the outset rather than as an afterthought.

When Do You Need a Software Development Agreement (UK)?

A Software Development Agreement is needed whenever a business engages an external developer, development agency, or freelance programmer to create bespoke software. The most common situations in England and Wales include:

Commissioning a web application, mobile app, or enterprise software system from an independent development company. The agreement defines the project scope, technical specification, development methodology (Agile, Waterfall, or Hybrid), milestones, deliverables, acceptance testing procedures, and fees.

Engaging a freelance developer or contractor through a personal service company (PSC) for a software development project. The agreement must address IR35 status under the Income Tax (Earnings and Pensions) Act 2003 and include provisions on control, substitution, and mutuality of obligation to demonstrate genuine self-employment.

Developing software that will process personal data (customer records, employee data, health information, financial data). The Data Protection Act 2018 and UK GDPR require appropriate technical and organisational measures, data protection by design (Article 25), and where the developer acts as a data processor, a written processing agreement meeting the requirements of Article 28.

Projects where the client needs to own the intellectual property in the developed software for commercial exploitation, resale, or strategic reasons. Without a written assignment clause, the developer retains copyright under section 11(1) of the Copyright, Designs and Patents Act 1988.

Situations where the client wishes to protect against the risk of the developer becoming insolvent or ceasing to trade by establishing a source code escrow arrangement with a third-party escrow agent.

Without a properly drafted agreement, disputes commonly arise over who owns the IP, what is included in the project scope, whether additional work constitutes a chargeable change request, the extent of the developer's warranty and support obligations, and the process for terminating the engagement and retrieving source code.

What to Include in Your Software Development Agreement (UK)

A comprehensive UK Software Development Agreement for England and Wales should contain the following essential elements:

Project Scope and Specification -- A detailed description of the software to be developed, including functional requirements, technical specification, technology stack, and any third-party integrations. A formal change request procedure should govern any modifications to the original scope.

Development Methodology -- The agreed development approach (Agile Scrum, Kanban, Waterfall, or Hybrid), sprint or phase durations, reporting frequency, and the client's involvement in reviews and feedback.

Milestones and Acceptance Testing -- Defined deliverables with target dates, an acceptance testing procedure (typically 10 business days per milestone), and a process for identifying and remedying defects before formal acceptance.

Intellectual Property -- Clear allocation of IP rights under the Copyright, Designs and Patents Act 1988. If the client is to own the IP, the agreement must contain an express written assignment compliant with section 90(3). If the developer retains IP, the licence terms (exclusive or non-exclusive, perpetual or time-limited, royalty-free or paid) must be clearly defined. The treatment of open-source components and pre-existing developer IP must also be addressed.

Source Code Escrow -- Optional provisions for depositing source code with a third-party escrow agent, with defined release triggers (insolvency, cessation of business, material breach).

IR35 Employment Status -- Provisions addressing the developer's self-employment status under the off-payroll working rules in the Income Tax (Earnings and Pensions) Act 2003, including control, substitution, and mutuality of obligation.

Fees and Payment -- The fee structure (fixed, time and materials, or milestone-based), payment terms, currency (GBP), VAT treatment, and late payment interest under the Late Payment of Commercial Debts (Interest) Act 1998.

Warranties -- Developer warranties that the software conforms to specification, is free from defects and malicious code, does not infringe third-party IP, and complies with applicable law including the Computer Misuse Act 1990.

Data Protection -- Compliance with the Data Protection Act 2018 and UK GDPR, including data protection by design (Article 25) and data processing provisions (Article 28) where applicable.

Limitation of Liability -- Aggregate caps on liability subject to the Unfair Contract Terms Act 1977, with carve-outs for death, personal injury, fraud, IP infringement, and data protection breaches.

Governing Law -- A clause confirming that the agreement is governed by the laws of England and Wales with exclusive jurisdiction in the courts of England and Wales.

What Is a Software Development Agreement (UK)?

When Do You Need a Software Development Agreement (UK)?

What to Include in Your Software Development Agreement (UK)

Frequently Asked Questions

Related Documents

Consultancy Agreement (UK)

Service Agreement (UK)

Non-Disclosure Agreement (NDA) (UK)