Software Development Agreement Template (UK)
Updated on 2 October 2026
A software development agreement governs a project in which one party builds software for another: scope, price, timing, acceptance, ownership and what happens when it goes wrong. Almost all the disputes concentrate in two places — whether the thing delivered is what was ordered, and who owns it.
A naming point first. "Development agreement" is ambiguous: in property law it means an agreement about developing land, which is an entirely different instrument. The template this page replaces is titled "Development Agreement", says it is for "real estate and software development", and is in fact a software contract. We have named this family honestly.
Tap any highlighted blank in the document below and type straight into it.Free — no sign-up, no watermark
Choose your version
Software Development Agreement
This Software Development Agreement is made on between of (the "Developer") and of (the "Client").
This agreement concerns the development of software. It is not a land or property development agreement.
1. Scope of work
The Developer will design, develop and deliver the following:
Deliverables and delivery dates: . The detailed scope, technical requirements and acceptance criteria are set out in the specification , which forms part of this agreement. Where this agreement and the specification conflict, this agreement prevails on legal terms and the specification prevails on technical requirements.
2. Change control
Either party may request a change to the scope, the deliverables or the timeline. The Developer will assess the request and provide a written impact statement covering cost and schedule. No change takes effect until both parties have agreed it in writing. Verbal instructions do not vary this agreement.
3. Fees and payment
The fee is payable against milestones as follows: . A milestone payment becomes due on acceptance of the deliverable to which it relates. The total budget is .
Expenses and third-party costs: . Invoices are payable within days. Late payment: . The Developer may suspend work on written notice if undisputed invoices remain unpaid for more than thirty days.
4. Client responsibilities
. Where the Client does not provide access, information, content, decisions or approvals when needed, the affected dates move by at least the length of the delay and the Developer may charge for time that cannot be redeployed.
5. Delivery and acceptance
On delivery of each deliverable the Client has working days to test it against the acceptance criteria:
- if the deliverable meets the criteria, the Client will confirm acceptance in writing;
- if it does not, the Client will give written notice within the test period specifying each failure by reference to the criteria;
- the Developer will correct the failures and re-deliver within working days, and a fresh test period then runs;
- if the deliverable still fails after correction cycles, the Client may reject it, terminate this agreement in respect of that deliverable and recover the amounts paid for it;
- the deliverable is deemed accepted if the Client does not give notice within the test period, or if the Client puts it into production use.
6. Intellectual property
With effect from payment in full for the relevant deliverable, the Developer assigns to the Client all copyright and other intellectual property rights throughout the world in the deliverables created specifically for the Client under this agreement, including future rights. This clause is intended to operate as an assignment in writing signed by or on behalf of the assignor for the purposes of the Copyright, Designs and Patents Act 1988. The Developer will promptly sign any further document and do any further act reasonably required to vest, perfect or record those rights, and warrants that it has obtained from every employee, contractor and subcontractor who contributes to the deliverables a written assignment sufficient to allow it to make this assignment.
The Developer retains ownership of its pre-existing tools, libraries, frameworks, methodologies and know-how, and of anything developed independently of this agreement ("Background Materials"). To the extent any Background Material is incorporated into a deliverable, the Developer grants the Client a perpetual, irrevocable, worldwide, non-exclusive, royalty-free, sublicensable licence to use, modify and distribute it as part of the deliverable. Until payment in full is received for a deliverable, no rights in it pass to the Client and the Client may not use it in production.
7. Open source and third-party components
The Developer will maintain, and deliver with each deliverable, a list of all third-party and open-source components incorporated, with their versions and licences. The Developer will not incorporate any component under a licence that imposes obligations to disclose, license or distribute source code of a larger work without the Client’s prior written consent, and warrants that the components used are licensed on terms compatible with the Client’s use of the deliverables as described in this agreement.
8. Generative AI tools
The Developer will disclose in writing any material use of generative artificial intelligence tools in producing the deliverables, including the tools used and the parts of the work affected. Use of such tools does not reduce the Developer’s warranties, and in particular the Developer warrants that the deliverables do not infringe the intellectual property rights of any third party however they were produced.
9. Handover
On acceptance of each deliverable, and in any event on completion or termination, the Developer will deliver: . Delivery is in a form that allows a competent developer to build, deploy and maintain the software without further assistance.
10. Warranty
The Developer warrants that the deliverables will conform in all material respects to the specification for days after acceptance, and that the services will be performed with the reasonable skill and care of a competent professional developer. During the warranty period the Developer will correct any non-conformity at no charge. The warranty does not cover defects caused by the Client’s own modifications, use outside the specification, third-party software or infrastructure the Developer does not control, or the Client’s failure to apply a correction supplied.
11. Intellectual property indemnity
The Developer will defend and indemnify the Client against any third-party claim that the deliverables, as delivered, infringe that third party’s intellectual property rights, and will pay the damages and costs finally awarded or agreed in settlement. The Client will notify the Developer promptly, give the Developer control of the defence and settlement, and co-operate at the Developer’s expense.
If use of a deliverable is or is likely to be restrained, the Developer will at its option procure the right for the Client to continue using it, modify it so that it is non-infringing while remaining materially conformant, or refund the fees paid for it. This indemnity does not apply to claims arising from the Client’s own materials, from modifications made by anyone other than the Developer, or from combination with anything the Developer did not specify.
12. Confidentiality
Each party will keep the other’s confidential information confidential, use it only for this agreement, protect it with reasonable safeguards, and disclose it only to personnel and advisers who need it and are bound by equivalent obligations. These obligations continue for years after this agreement ends, and for as long as the information remains a trade secret. Disclosure required by law or a court is permitted, with prompt notice where lawful.
13. Data protection and security
- process personal data belonging to the Client only on the Client’s documented instructions and only as needed for this project;
- apply appropriate technical and organisational security measures, including access control, encryption in transit and at rest where appropriate, and logging;
- not use real personal data in development or test environments; test data will be synthetic or anonymised unless the Client authorises otherwise in writing;
- process and store data only in the following locations: , and not transfer it elsewhere without the Client’s prior written consent;
- notify the Client of any actual or suspected personal data breach or security incident within hours of becoming aware of it, and co-operate with the Client’s response;
- ensure that personnel authorised to process the data are bound by confidentiality, and not engage a sub-processor without the Client’s prior written authorisation;
- return or securely delete the Client’s data on completion or termination, except where retention is required by law.
Where the Developer processes personal data on the Client’s behalf, the parties will enter into a data processing agreement containing the terms required by UK GDPR, and that agreement prevails over this clause to the extent of any conflict.
14. Insurance
The Developer will maintain professional indemnity insurance of not less than and cyber liability insurance of not less than throughout this agreement and for two years afterwards, and will provide evidence on request.
15. Limitation of liability
Neither party is liable to the other for indirect, consequential or special loss, including loss of profit, loss of revenue, loss of anticipated savings, loss of business opportunity or loss of data, however arising. Subject to the next paragraph, each party’s total aggregate liability arising out of or in connection with this agreement is limited to .
Nothing in this agreement limits or excludes liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, for breach of the confidentiality obligations, for infringement of the other party’s intellectual property rights, for the Developer’s obligations under the intellectual property indemnity, or for any other liability that cannot lawfully be limited or excluded.
16. Term, termination and transition
This agreement starts on the agreement date and continues until the deliverables have been accepted and paid for, unless terminated earlier. Either party may terminate for convenience on days’ written notice, or immediately if the other materially breaches and fails to remedy the breach within days of written notice, or becomes insolvent.
On termination the Client pays for all work properly performed to the termination date, the Developer delivers all completed and partially completed work together with the handover items for anything paid for, and provides reasonable transition assistance for up to thirty days at its standard rates. The clauses on intellectual property, confidentiality, data protection, indemnity, limitation of liability and governing law survive.
17. General
- Status: the Developer is an independent contractor and nothing creates a partnership, joint venture, agency or employment relationship. Where the Developer supplies services through an intermediary company, the parties will consider whether the off-payroll working rules apply.
- Force majeure: neither party is liable for delay caused by events beyond its reasonable control, with prompt notice and reasonable efforts to resume.
- Amendment: only by a written document signed by both parties.
- Assignment: neither party may assign without the other’s written consent, except to a successor in a merger or sale of substantially all assets that assumes these obligations.
- Entire agreement: this agreement, the specification and any signed change orders are the whole agreement on their subject matter.
- Severability: if any provision is invalid or unenforceable the rest continues in force.
- Counterparts and electronic signature: this agreement may be signed in counterparts and electronically.
18. Governing law and disputes
This agreement is governed by the law of . The parties will first attempt to resolve any dispute by discussion between senior representatives, and failing that will submit it to .
Developer
Date signed:
Client
Date signed:
Who owns the code, and why "shall own" is not enough
Under the Copyright, Designs and Patents Act 1988 the author of a work is the first owner of the copyright in it, except where a work is made by an employee in the course of employment, in which case the employer is first owner subject to any agreement to the contrary. A development agency or a freelance developer is not an employee of the client.
So commissioning software does not make the client the owner. And an assignment of copyright is not effective unless it is in writing signed by or on behalf of the assignor. A clause saying the client "shall own all rights, title and interest" is a statement of intention, not a conveyance.
This template uses an express assignment taking effect on payment in full, with a further-assurances obligation and — the clause that matters most at a later acquisition — a warranty that the developer has obtained written assignments from every employee and contractor who contributed. That is the point at which diligence usually fails: a contractor wrote a core module three years ago and never signed anything.
One UK-specific nuance worth knowing: the right to be identified as author does not apply to a computer program or a computer-generated work. That removes one issue that complicates design contracts, though the other moral rights and the general position still need thought where the project includes design assets rather than only code.
Acceptance testing: the clause free templates do not have
The source document warrants that deliverables will "substantially conform to the agreed specifications" for a period after delivery — and provides no mechanism for establishing whether they conform. No test procedure, no acceptance criteria, no test period, no consequence of silence, no re-delivery process. Every significant software dispute runs through that gap.
This template adds the standard structure: the developer delivers, the client has a stated number of working days to test against the agreed acceptance criteria, the client either accepts or gives written notice of the specific failures, the developer corrects and re-delivers within a stated period, and the cycle repeats a limited number of times before the client can reject and recover payments. Deemed acceptance applies on silence and on production use.
Write the acceptance criteria into the specification, not into the lawyer’s clause. "Conforms to the specification" is only as good as the specification.
UK GDPR, test data and the processor agreement
A developer building and testing a system almost always touches the client’s data, and frequently real personal data because test environments get seeded from production. Where the developer processes personal data on the client’s behalf it is a processor, and UK GDPR requires a written contract containing prescribed terms.
The template includes proportionate security and incident terms — processing only on documented instructions, agreed security measures, no real personal data in test environments without written authorisation, controlled sub-processing, a short breach notification window so the client can meet its own seventy-two hour obligation, and return or deletion at the end — and points to a separate data processing agreement for the prescribed terms rather than pretending a paragraph covers them.
A liability cap that survives, and the IP indemnity
The source caps liability at fees paid and carves out only fraud, wilful misconduct and confidentiality. That omits death and personal injury caused by negligence, which cannot be excluded, and exclusion clauses in UK business contracts are also subject to a reasonableness test. An incomplete carve-out list puts the clause at risk rather than just the offending part.
This template keeps a cap and writes the carve-outs properly, and makes the exclusion of consequential loss mutual, which is both fairer and more likely to hold. It also adds an IP infringement indemnity with defence control, co-operation and a remedy ladder — procure, modify or refund — which the source has nowhere at all. If the software infringes someone’s rights, the person sued is usually the client using it.
Software development agreement clause guide
- Parties and engagement
- Legal entities and the independent contractor relationship.
- Statement of work and specification
- The scope, deliverables, technical requirements and acceptance criteria, attached as a schedule rather than summarised in a clause.
- Change control
- Written change requests, an impact assessment covering cost and schedule, and no change binding until both sides agree in writing.
- Fees, milestones and expenses
- Fixed price, time and materials or milestone-based, with what is included and how expenses and third-party costs are handled.
- Client responsibilities and dependencies
- Access, data, decisions and approvals, with the consequence of delay stated.
- Delivery and acceptance testing
- Test period, acceptance criteria, written notice of failures, correction and re-delivery, limited cycles, deemed acceptance on silence or production use.
- Intellectual property transfer
- An express transfer of the deliverables on payment in full, drafted to meet the formalities the governing law requires.
- Background IP and licence back
- The developer keeps its pre-existing tools and frameworks and licenses them so the client can actually use the deliverables.
- Open source and third-party components
- A delivered component list with licences, consent required for copyleft components, and a compatibility warranty.
- Source code, documentation and handover
- What is delivered, in what form, with build instructions, environment details and credentials.
- Source code escrow
- Optional, where the client depends on software whose source it does not receive.
- Warranty and warranty period
- Conformance to specification for a stated period with correction at no charge, and the exclusions that properly belong there.
- IP indemnity
- Developer indemnity for third-party IP claims with defence control, co-operation and a remedy ladder.
- Confidentiality
- Mutual, with a defined period, defined carve-outs and personnel bound on equivalent terms.
- Data protection and security
- Processing only on instructions, agreed security measures, no real personal data in test environments, sub-processor control, incident notification and return or deletion at the end.
- Insurance
- Professional indemnity and cyber cover with stated limits, where the project warrants it.
- Limitation of liability
- A cap with properly drafted carve-outs for the liabilities that cannot lawfully be limited, and a mutual exclusion of consequential loss.
- AI tool disclosure
- Whether generative AI tools were used in producing the code, and the warranties that attach regardless.
- Term, termination and transition
- Notice, cure, payment for work done, delivery of work in progress, and reasonable transition assistance.
UK software development agreement checklist
The copyright formalities are decisive; the rest is commercial risk allocation that costs nothing at the start and a great deal later.
Do not assume commissioning transfers the copyright
The author is the first owner except where the work is made by an employee in the course of employment. A development agency or freelance developer is not an employee of the client.
Copyright, Designs and Patents Act 1988, section 11Put the assignment in writing and sign it
An assignment of copyright is not effective unless it is in writing signed by or on behalf of the assignor. Use an express present assignment with further assurances.
Copyright, Designs and Patents Act 1988, section 90(3)Secure assignments from every contributor
The developer’s assignment is worth nothing if it never obtained rights from the contractor who wrote a core module. Require a warranty and evidence on request.
Note that the paternity right does not apply to computer programs
The right to be identified as author does not apply to a computer program or a computer-generated work, which removes one complication present in design contracts.
Copyright, Designs and Patents Act 1988, section 79Build a real acceptance procedure, not a bare warranty
Test period, written notice of specific failures, correction and re-delivery, limited cycles, and deemed acceptance on silence or production use.
Require an open-source component list before go-live
Copyleft licences can impose obligations on how the software is distributed. Require a component list and prior consent for anything copyleft.
Put a UK GDPR processor agreement in place
Where the developer processes personal data on the client’s behalf, a written contract containing the prescribed terms is required.
ICO — contracts and liabilities between controllers and processorsKeep real personal data out of test environments
Seeding test environments from production is routine and a common cause of avoidable breaches. Require synthetic or anonymised data.
Draft the liability carve-outs completely
Include death or personal injury caused by negligence, fraud, confidentiality, IP infringement and anything that cannot lawfully be limited. Exclusion clauses are also subject to a reasonableness test.
Include an IP infringement indemnity
If the software infringes, the party sued is usually the client. Include defence control, co-operation and a remedy ladder of procure, modify or refund.
How to complete the software development agreement
- Write the specification before the contract. Scope, deliverables, technical requirements and acceptance criteria belong in a schedule you attach. Everything else refers back to it.
- Choose the pricing model. Fixed price, time and materials, or milestone-based. Enter the figures, the milestone triggers and what expenses are additional.
- Set the acceptance mechanics. The test period in working days, the correction period, the number of cycles before rejection, and what counts as deemed acceptance.
- Get the IP transfer right for your jurisdiction. Use the express assignment taking effect on payment in full, and require the developer to warrant it holds written assignments from every contributor — that is where diligence usually fails.
- Complete the data protection terms. Set the processing locations and the breach notification window, and switch on the pointer to a separate UK GDPR processor agreement containing the prescribed terms.
- Set the cap and turn on the optional clauses. Enter the liability cap, then switch on escrow, support and maintenance, insurance and non-solicitation if the project warrants them.
- Agree the handover before you sign. Source code, build instructions, repository access, credentials and documentation, so it is a contractual obligation rather than a favour.
Software development agreements in the UK — frequently asked questions
Who owns the code if the contract says nothing?
Generally the developer, which surprises most clients. Under the Copyright, Designs and Patents Act 1988 the author is the first owner, with an exception only where the work was made by an employee in the course of employment. A development agency or freelance developer is not an employee of the client, so paying for code does not transfer the copyright in it.
Is a clause saying the client "shall own" the deliverables enough?
It is weaker than it should be. An assignment of copyright is not effective unless it is in writing signed by or on behalf of the assignor, and a present-tense assignment with further-assurances wording leaves no room for argument. The free template this page replaces uses the "shall own" formulation with no assignment, no further assurances and no obligation on the developer to obtain rights from its own contributors.
What is the biggest IP risk at a later funding round or sale?
A contributor who never signed anything. The developer’s assignment to the client is worth only as much as the rights the developer actually holds, so a contractor who wrote a core module three years ago without an assignment is a genuine problem at diligence. Require the developer to warrant it holds written assignments from every employee and contractor, and to produce evidence on request.
Do moral rights matter in a software contract?
Less than in a design contract. The right to be identified as author does not apply to a computer program or to a computer-generated work, which removes the most awkward issue. The position still needs thought where the project includes design assets, documentation or other material alongside the code.
What should acceptance testing look like?
The client gets a defined number of working days to test against acceptance criteria forming part of the specification, then either accepts in writing or gives written notice of the specific failures. The developer corrects and re-delivers within a defined period, and the cycle repeats a limited number of times before the client may reject and recover what it paid. Silence for the test period, or production use, counts as acceptance.
Do I need a separate data processing agreement?
If the developer will process personal data on your behalf, yes. UK GDPR requires a written contract containing prescribed terms between controller and processor, and a general confidentiality clause does not meet them. The development agreement should contain proportionate security and incident terms and point at the separate agreement rather than trying to do its job.
Related templates
Disclaimer
This template and guide are general information only, not legal, tax, insurance, employment, consumer-credit, construction, dental or intellectual-property advice. No lawyer has reviewed your facts, and nothing here is certified as compliant with any law. Rules differ between jurisdictions and change over time — check the current position for your situation, and take professional advice before you sign or send.


