Software Development Agreement (UK)
This Software Development Agreement (the "Agreement") is entered into on [Agreement Date] (the "Effective Date") by and between:
(1) [Client Name], [Who Client], whose registered or trading address is [Client Address], [Client City], [Client County], [Client Postcode] (company registration number: [Client Company Number]) (the "Client"); and
(2) [Developer Name], [Who Developer], whose address is [Developer Address], [Developer City], [Developer County], [Developer Postcode] (company registration number: [Developer Company Number]) (the "Developer").
The Client and the Developer are collectively referred to as the "Parties" and individually as a "Party".
Background
(A) The Client wishes to engage the Developer to design, develop, test, and deliver the software described in this Agreement.
(B) The Developer has the skills, qualifications, and experience necessary to carry out the development work.
(C) The Parties wish to record the terms on which the Developer will provide software development services to the Client.
NOW IT IS AGREED as follows:
1. Project Scope and Specification
1.1 The Developer shall design, develop, test, and deliver the software project known as "[Project Name]" (the "Software") in accordance with the specification set out in this Agreement.
1.2 Project Description: [Project Description]
1.3 Technology Stack: [Tech Stack]
1.4 The Developer shall follow the [Methodology] development methodology throughout the project.
1.5 Any changes to the project scope, specification, or requirements after the Effective Date shall be agreed in writing by both Parties through a formal change request process. The Developer shall assess the impact of any change request on the timeline and fees and shall provide a written estimate before work on the change commences.
2. Milestones and Deliverables
2.1 The Developer shall deliver the Software in accordance with the following milestones and deliverables: [Milestones Description]
2.2 Upon delivery of each milestone, the Client shall have 10 business days to review and either accept the deliverable or provide written notice of any defects or non-conformities. If the Client does not respond within the review period, the deliverable shall be deemed accepted.
2.3 If the Client identifies defects or non-conformities, the Developer shall remedy them within a reasonable time at no additional cost, and the review process shall be repeated.
3. Fees and Payment
3.1 The Client shall pay the Developer a [Fee Structure] of £[Total Fee] for the development of the Software.
3.2 The Developer shall issue invoices to the Client, and the Client shall pay each invoice within [Payment Terms] days of receipt by [Payment Method].
3.3 If the Developer is VAT-registered (VAT number: [Developer VAT Number]), VAT at the prevailing rate shall be added to all invoices.
3.4 If any invoice remains unpaid for more than 14 days after the due date, the Developer may charge interest on the overdue amount at the rate of 8% per annum above the Bank of England base rate, together with compensation for late payment, in accordance with the Late Payment of Commercial Debts (Interest) Act 1998.
3.5 The Developer shall not be obliged to continue work on the Software while any undisputed invoice remains overdue by more than 30 days.
4. IR35 and Employment Status
4.1 The Developer is engaged under this Agreement as an independent contractor and not as an employee, worker, partner, or agent of the Client. The Parties have assessed this engagement as falling [Ir35 Status] under the off-payroll working rules in Chapter 10 of Part 2 of the Income Tax (Earnings and Pensions) Act 2003.
4.2 The Developer shall have full control over the manner and method of carrying out the development work, including the right to determine when and where work is performed (subject to any reasonable requirements for attendance at meetings or access to the Client's systems).
4.3 The Developer shall have the right to provide a suitably qualified substitute to carry out the development work, provided that the substitute is approved by the Client (such approval not to be unreasonably withheld).
4.4 There is no mutuality of obligation between the Parties. The Client is not obliged to offer further work to the Developer after completion of the project, and the Developer is not obliged to accept further work from the Client.
4.5 The Developer shall be solely responsible for paying all income tax, National Insurance contributions, and any other taxes due on the Developer's earnings from this engagement.
5. Warranties and Acceptance Testing
5.1 The Developer warrants that the Software shall: (a) materially conform to the specification set out in this Agreement; (b) be free from material defects in design and workmanship; (c) not contain any malicious code, viruses, Trojan horses, worms, or other harmful components; (d) not infringe any third-party intellectual property rights; and (e) comply with all applicable laws, including the Computer Misuse Act 1990 and the Data Protection Act 2018.
5.2 The warranty period shall be [Warranty Period] from the date of final acceptance of the Software by the Client (the "Warranty Period"). During the Warranty Period, the Developer shall promptly remedy any defects in the Software at no additional cost to the Client.
5.3 The Developer's warranty does not extend to defects caused by: (a) modifications made by the Client or third parties without the Developer's approval; (b) use of the Software in a manner not contemplated by the specification; or (c) failures in third-party hardware, software, or infrastructure.
6. Data Protection
6.1 Both Parties shall comply with the Data Protection Act 2018 and the UK General Data Protection Regulation (UK GDPR) in respect of all personal data processed in connection with this Agreement.
6.2 Where the Developer processes personal data on behalf of the Client during the development or testing of the Software (including test data derived from live personal data), the Developer shall: (a) process such data only on the Client's documented instructions; (b) implement appropriate technical and organisational security measures in accordance with Article 32 of the UK GDPR; (c) not transfer personal data outside the United Kingdom without the Client's prior written consent and appropriate safeguards; (d) notify the Client without undue delay upon becoming aware of a personal data breach; and (e) delete or return all personal data upon termination of this Agreement.
6.3 The Developer shall ensure that the Software is designed and developed with data protection by design and by default in accordance with Article 25 of the UK GDPR, where applicable.
7. Security and Computer Misuse
7.1 The Developer shall implement reasonable security measures to protect the Client's systems, data, and source code from unauthorised access, loss, or damage.
7.2 The Developer warrants that they will not engage in any activity that constitutes an offence under the Computer Misuse Act 1990, including unauthorised access to computer material (section 1), unauthorised access with intent to commit or facilitate further offences (section 2), or unauthorised acts with intent to impair or with recklessness as to impairing the operation of a computer (section 3).
7.3 The Developer shall store all source code in a secure version control system and shall implement appropriate access controls, encryption, and backup procedures.
8. Confidentiality
8.1 Each Party agrees to keep strictly confidential all information obtained during the course of this Agreement relating to the other Party's business, technology, source code, trade secrets, clients, or affairs ("Confidential Information"), and shall not disclose such information to any third party without the prior written consent of the disclosing Party.
8.2 The obligations of confidentiality shall not apply to information that: (a) is or becomes publicly available through no fault of the receiving Party; (b) was already known to the receiving Party before disclosure; (c) is disclosed by a third party not bound by confidentiality; or (d) is required to be disclosed by law or court order.
8.3 The obligations of confidentiality shall survive the termination of this Agreement indefinitely in respect of trade secrets, and for a period of five years in respect of other Confidential Information.
9. Insurance
9.1 The Developer shall maintain, at the Developer's own expense, valid insurance cover throughout the duration of this Agreement, including: (a) professional indemnity insurance with a minimum cover of £[PI Insurance Amount]; and (b) public liability insurance with a minimum cover of £[Public Liability Amount].
9.2 The Developer shall provide the Client with copies of current insurance certificates upon request and shall notify the Client immediately if any insurance policy lapses or is materially varied.
10. Limitation of Liability
10.1 Subject to clause 12.3, the Developer's aggregate liability under this Agreement (whether in contract, tort, negligence, or otherwise) shall not exceed the higher of: (a) the total fees paid or payable by the Client under this Agreement; or (b) the amount recoverable under the Developer's professional indemnity insurance.
10.2 Neither Party shall be liable to the other for any indirect, consequential, or special losses, including loss of profits, loss of business, loss of anticipated savings, loss of data, or loss of goodwill, howsoever arising.
10.3 Nothing in this Agreement shall exclude or limit either Party's liability for: (a) death or personal injury caused by negligence; (b) fraud or fraudulent misrepresentation; (c) infringement of the other Party's intellectual property rights; or (d) any other liability that cannot be excluded or limited under the laws of England and Wales, including the Unfair Contract Terms Act 1977.
11. Term and Termination
11.1 This Agreement shall commence on the Effective Date and shall continue until the Software has been delivered, accepted, and the Warranty Period has expired, unless terminated earlier in accordance with this clause.
11.2 Either Party may terminate this Agreement by giving the other Party not less than [Notice Period] written notice.
11.3 Either Party may terminate this Agreement immediately by written notice if the other Party: (a) commits a material breach and (where the breach is capable of remedy) fails to remedy it within 14 days of receiving written notice; (b) becomes insolvent, enters administration, or has a winding-up order made against it; or (c) ceases or threatens to cease carrying on its business.
11.4 Upon termination: (a) the Client shall pay the Developer for all work completed and accepted up to the date of termination; (b) the Developer shall deliver to the Client all source code, documentation, and work in progress; (c) all licences granted under this Agreement shall survive termination except where the Agreement is terminated for the Developer's material breach; and (d) the Developer shall provide reasonable assistance to facilitate handover to the Client or a replacement developer.
12. General Provisions
12.1 Entire Agreement. This Agreement constitutes the entire agreement between the Parties and supersedes all prior negotiations, representations, and agreements relating to its subject matter.
12.2 Variation. No variation of this Agreement shall be effective unless it is in writing and signed by both Parties.
12.3 Severability. If any provision of this Agreement is found by a court of competent jurisdiction to be invalid, illegal, or unenforceable, the remaining provisions shall continue in full force and effect.
12.4 Waiver. A failure or delay by a Party to exercise any right under this Agreement shall not constitute a waiver of that right.
12.5 Third Party Rights. No person other than the Parties shall have any rights under this Agreement by virtue of the Contracts (Rights of Third Parties) Act 1999.
12.6 Force Majeure. Neither Party shall be liable for any failure to perform or delay in performing its obligations under this Agreement to the extent that such failure or delay is caused by circumstances beyond the reasonable control of the affected Party, including but not limited to acts of God, war, terrorism, pandemic, fire, flood, governmental action, or cyber-attack.
12.7 Notices. Any notice required under this Agreement shall be in writing and delivered by hand, sent by first class recorded delivery post, or sent by email to the addresses specified in this Agreement.
13. Governing Law and Jurisdiction
13.1 This Agreement and any dispute or claim 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.
13.2 The Parties irrevocably agree that the courts of England and Wales shall have exclusive jurisdiction to settle any dispute or claim arising out of or in connection with this Agreement.
IN WITNESS WHEREOF, the Parties have executed this Agreement as of the Effective Date.
Client
Name: [Client Name]
Address: [Client Address], [Client City], [Client County], [Client Postcode]
Developer
Name: [Developer Name]
Address: [Developer Address], [Developer City], [Developer County], [Developer Postcode]
Client
________________
Signature
Date: ________________
Developer
________________
Signature
Date: ________________
What Is a Software Development Agreement (UK)?
A Software Development Agreement in the United Kingdom sets the scope, deliverables, fees, and acceptance terms under which the work or system is produced for the client, and is shaped by the Designs and Patents Act 1988.
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.
The legal framework governing the Software Development Agreement (UK) in United Kingdom draws on several key statutes and regulatory bodies. Under the Companies Act 2006, Companies House maintains the register of UK companies. Section 386 of the Companies Act 2006 sets accounting record obligations. The Competition and Markets Authority (CMA) enforces the Consumer Rights Act 2015. The Financial Conduct Authority (FCA) regulates financial services under the Financial Services and Markets Act 2000. The High Court of Justice has jurisdiction under the Senior Courts Act 1981. Parties executing a Software Development Agreement (UK) in United Kingdom should confirm the document reflects current law, including any amendments enacted since the original drafting date. The Companies Act 2006 sets the foundational requirements.
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.
Parties in United Kingdom should prepare a Software Development Agreement (UK) proactively rather than waiting for a dispute to arise. Courts interpret agreements based on the written terms rather than oral representations. Under the Companies Act 2006, Companies House maintains the register of UK companies. Section 386 of the Companies Act 2006 sets accounting record obligations. The Competition and Markets Authority (CMA) enforces the Consumer Rights Act 2015. The Financial Conduct Authority (FCA) regulates financial services under the Financial Services and Markets Act 2000. The High Court of Justice has jurisdiction under the Senior Courts Act 1981. Where the transaction involves regulated activities, prior approval from the relevant authority may be required before execution.
What to Include in Your Software Development Agreement (UK)
A thorough 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.
Additional compliance elements for a Software Development Agreement (UK) used in United Kingdom include: Under the Companies Act 2006, Companies House maintains the register of UK companies. Section 386 of the Companies Act 2006 sets accounting record obligations. The Competition and Markets Authority (CMA) enforces the Consumer Rights Act 2015. The Financial Conduct Authority (FCA) regulates financial services under the Financial Services and Markets Act 2000. The High Court of Justice has jurisdiction under the Senior Courts Act 1981. Forms-legal.com provides this template as a starting point for United Kingdom-compliant documentation.
Cite this page
Reference this free template in an article, syllabus, or research note:
Forms Legal. (2026). Software Development Agreement (UK) (United Kingdom) [Legal document template]. Forms Legal. https://forms-legal.com/uk/business/contracts/software-development-agreement-uk
"Software Development Agreement (UK) (United Kingdom)." Forms Legal, 2026, https://forms-legal.com/uk/business/contracts/software-development-agreement-uk.
@misc{formslegal-software-development-agreement-uk,
author = {{Forms Legal}},
title = {Software Development Agreement (UK) (United Kingdom)},
year = {2026},
howpublished = {\url{https://forms-legal.com/uk/business/contracts/software-development-agreement-uk}},
note = {Free legal document template. Based on Companies Act 2006}
}Also available for these jurisdictions:
Frequently Asked Questions
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.
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.
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 confirm 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.
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 help 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.
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.
This template is provided for informational purposes only and does not constitute legal advice. Laws vary by jurisdiction and change over time. Consult a qualified attorney for advice specific to your situation.Full disclaimer
Found an error? Let us knowRelated Documents
You may also find these documents useful:
Consultancy Agreement (UK)
Create a detailed UK Consultancy Agreement governed by the laws of England and Wales. This template covers scope of services, fees and payment in GBP, intellectual property ownership, confidentiality, data protection (UK GDPR / Data Protection Act 2018), IR35 off-payroll working status, right of substitution, non-solicitation, insurance requirements, limitation of liability, and indemnity. Suitable for limited companies, LLPs, sole traders, partnerships, and individuals. Fill out the wizard, preview in real time, and download as PDF or Word.
Service Agreement (UK)
Create a detailed UK service agreement governed by the laws of England and Wales. Covers the Consumer Rights Act 2015, Supply of Goods and Services Act 1982, Late Payment of Commercial Debts (Interest) Act 1998, UK GDPR, IR35, VAT, intellectual property, and confidentiality. Suitable for consultants, freelancers, agencies, and businesses of all sizes.
Non-Disclosure Agreement (NDA) (UK)
Protect your confidential business information in England and Wales with a legally sound Non-Disclosure Agreement. Whether you are sharing trade secrets with a prospective partner, disclosing proprietary technology to a developer, or presenting financial projections to a potential investor, a properly drafted UK NDA keeps your sensitive information under strict legal protection. Our template is drafted in accordance with English common law and incorporates the key provisions required for enforceability in England and Wales.