# Defined Pilot Collaboration Agreement — Example Template

**Reference:** DPCA-001 | **Version:** 1.0 | **Date:** 9 November 2026  
**Status:** Illustrative example — not an executed agreement or legal advice  
**Jurisdiction assumed:** England and Wales

> **Important:** This is an educational starting point, not an official or universally suitable contract. Each participant must adapt its terms and seek qualified legal, tax and regulatory advice before signature. No company, partner or commercial relationship is implied.

## 1. Parties
This illustrative agreement is between **[PARTY A LEGAL NAME, NUMBER, ADDRESS]** and **[PARTY B LEGAL NAME, NUMBER, ADDRESS]** (the "Parties"), dated **[DATE]**. Additional parties must be named and sign separately. Each signatory warrants authority to contract; a development-stage project without separate legal personality must identify the person or entity contracting.

## 2. Purpose and possible outcomes
The Parties intend to conduct the limited pilot described in Schedule A. Outcomes might include closure, an extended pilot, supply or licensing contracts, a strategic alliance, a consortium, a separately incorporated joint venture, a holding-company arrangement, asset or share acquisition, or merger. **None occurs automatically.** This agreement creates no partnership, agency, equity transfer, exclusivity or obligation to negotiate any subsequent transaction.

## 3. Scope, duration and changes
Start: **[DATE]**. End: **[DATE]**. Only tasks, deliverables, exclusions and acceptance measures in Schedule A are authorised. Changes, extensions and additional costs require signed written approval from authorised representatives before implementation.

## 4. Roles and oversight
Each Party will supply the people, equipment, inputs and approvals assigned in Schedule A, perform its obligations with reasonable skill and care, comply with relevant law, and flag material delays or risks promptly. Named project representatives may coordinate work but cannot amend this contract or commit unapproved expenditure.

## 5. Costs, revenue and resources
Schedule B records contributions, budget limits, authorised expenses, fees, invoicing, insurance and any agreed revenue sharing. Otherwise each Party bears its own costs. No one may bind another Party financially without prior written authority. No implied profit share arises from participating.

## 6. Intellectual property
**Background IP:** Each Party retains its pre-existing research, data, models, software, designs, inventions, documentation, know-how and brands. Schedule C identifies relevant assets and third-party restrictions.

**Pilot-only licence:** To the extent required to perform the agreed work, each Party permits the other a non-exclusive, non-transferable, limited-duration licence to use specifically listed Background IP solely for this pilot. No unrelated exploitation, transfer or sublicensing is implied.

**New outputs:** Unless Schedule C expressly provides otherwise, each Party owns outputs created solely by its own staff. Ownership, use and registration of joint outputs must be agreed in writing before any commercial exploitation. Where title is uncertain, neither Party may presume exclusive rights.

**Later use:** Manufacture, resale, deployment, publication, exclusivity, royalties, source-code access and assignment require express terms. Third-party software and open-source licences remain effective.

## 7. Confidentiality
Each Party must safeguard the other's clearly confidential information, share it only with personnel/advisers who need it under appropriate duties, and use it only for the pilot. Exclusions: lawfully public information, independently created material, information lawfully received without restriction and legally compelled disclosure. This duty continues **[THREE] years** after termination; qualifying trade secrets remain protected while legally confidential.

## 8. Data protection, AI and cybersecurity
The Parties must document their data-protection roles before sharing personal data and execute required data-processing, controller-sharing or joint-controller arrangements. Schedule D specifies systems, access rights, security standards, retention, lawful international transfers, incident notification and deletion. No use of another Party's personal or confidential data for external AI-model training, tuning or evaluation without explicit prior consent and appropriate legal basis. Assign responsibility for AI accuracy, human oversight, safety and security testing.

## 9. Milestones and acceptance
Schedule A sets dated deliverables and measurable success criteria. Receiving Parties shall review a delivery within **[10 BUSINESS DAYS]**, accepting it or providing objective written reasons for rejection. A reasonable cure period must be recorded. Acceptance does not transfer ownership or waive mandatory legal rights.

## 10. Liability and insurance
Each Party is responsible for its own people and conduct. Any aggregate cap **[AMOUNT AND SCOPE]**, exclusions of consequential losses, and carve-outs for IP, confidentiality, data and security must be specifically negotiated and assessed for fairness and enforceability. No provision excludes fraud, fraudulent misrepresentation, death or personal injury caused by negligence, or other liability that cannot legally be excluded. Insurance obligations are listed in Schedule B.

## 11. Independence and public statements
The Parties remain independent, with no authority to represent, commit or appoint agents for another Party. No Party may publish another's name, logo, confidential results, implied endorsement or relationship without prior written approval. Any anonymised reference must not reasonably identify the other Party.

## 12. Termination and exit
This agreement ends on its scheduled end date. It may end earlier by written agreement; for uncured material breach after **[15 BUSINESS DAYS]** notice; immediately where continued work is unlawful or creates a serious unmitigable security risk; or on **[20 BUSINESS DAYS]** notice for convenience subject to agreed payment for authorised completed work. On exit, cease unauthorised use, settle authorised charges, return or securely delete protected assets subject to lawful retention, and complete handover in Schedule A. Accrued obligations, surviving IP rights, confidentiality and dispute terms continue.

## 13. Review and future transactions
At completion, the Parties may document performance, cost, feasibility, risks, learning and further opportunities. A successful pilot never automatically creates an acquisition, joint venture, equity interest, merger or investment commitment. Any corporate transaction requires separate valuations, due diligence, tax and regulatory assessment, approval and definitive documentation.

## 14. Disputes and general terms
Project leads shall seek resolution first, followed by escalation to senior representatives within **[15 BUSINESS DAYS]** and consideration of mediation. Courts of England and Wales have exclusive jurisdiction and that law governs, unless agreed otherwise. Amendments require written signature by affected Parties. Transfers require consent. The Contracts (Rights of Third Parties) Act 1999 applies only if expressly stated. Invalid provisions are severable insofar as lawful. This document and its schedules form the pilot agreement, subject to expressly preserved agreements.

---

## Schedule A — Pilot definition
| Field | Insert details |
|---|---|
| Project and objective | [TITLE, NEED, USERS] |
| Dates and stages | [START, END, MILESTONES] |
| Tasks and exclusions | [IN SCOPE / OUT OF SCOPE] |
| Parties' responsibilities | [WHO DOES WHAT] |
| Deliverables | [OUTPUTS] |
| Success / acceptance criteria | [MEASURES AND APPROVER] |
| Pilot exit and handover | [STEPS, MATERIALS, OWNER] |

## Schedule B — Commercial terms
| Field | Insert details |
|---|---|
| Cash and in-kind contributions | [PARTY BY PARTY] |
| Spending cap and fees | [AMOUNTS, CURRENCY, VAT] |
| Payments / approved expenses | [TIMING AND APPROVALS] |
| Revenue allocation if any | [TERMS OR NONE] |
| Insurance | [REQUIRED COVER] |
| Liability limits and exceptions | [NEGOTIATED CAP / EXCLUSIONS] |

## Schedule C — Intellectual-property register
| Field | Insert details |
|---|---|
| Background IP and owner | [ITEMS AND PROOF OF RIGHTS] |
| Permitted pilot licences | [SCOPE AND DURATION] |
| Excluded assets and third-party rights | [ITEMS] |
| Newly created IP | [OWNER / PROCEDURE] |
| Jointly created work | [APPROVALS, ACCESS, EXPLOITATION] |
| Publication and post-pilot use | [CONSENT / FUTURE LICENCES] |

## Schedule D — Data and AI controls
| Field | Insert details |
|---|---|
| Personal-data roles | [CONTROLLERS / PROCESSORS] |
| Supporting agreements | [DPA / SHARING ARRANGEMENT] |
| Approved systems and security | [ACCESS, ENCRYPTION, BACKUPS] |
| AI use / training restrictions | [PERMISSIONS, MODEL, PURPOSE] |
| Incident notification | [WHO, HOW, WHEN] |
| Retention, return and deletion | [PERIOD / EVIDENCE] |
| International transfers | [TRANSFER MECHANISM IF NEEDED] |

## Signatures (only after legal review)
**Party A:** Name [ ]; title [ ]; signature [ ]; date [ ].  
**Party B:** Name [ ]; title [ ]; signature [ ]; date [ ].  
**Additional parties:** Repeat as required.

---
**Further guidance:** UK IPO Lambert toolkit: https://www.gov.uk/guidance/university-and-business-collaboration-agreements-lambert-toolkit ; ICO controller–processor contracts: https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/accountability-and-governance/contracts-and-liabilities-between-controllers-and-processors-multi/what-needs-to-be-included-in-the-contract/ ; UK merger review: https://www.gov.uk/mergers-when-they-will-be-investigated .
