R&D guide

NDA for Research and Development UK: Protecting Innovation Before It's Patented

How UK businesses, universities and research teams use NDAs to protect inventions, datasets and know-how before patent filing — including industry-academia partnerships, Innovate UK collaborations and pre-patent disclosure risks.

By Richard Wood, Founder10 min readUpdated 12 June 2026Last reviewed 12 June 2026R&DIPUK lawtemplates

Research and development sits at the intersection of two legal frameworks that pull in opposite directions. Patent law rewards disclosure — a granted patent is a published monopoly. Trade secret law rewards secrecy — protection lasts only while the information remains confidential. In the window between generating an R&D result and deciding what to do with it, the non-disclosure agreement (NDA) is the tool that keeps both options open.

This is general information, not legal advice

NDASafe is a document preparation service, not a law firm. Our templates are legally reviewed against applicable UK law at the point of release, but every situation is different. Where significant value, unusual risk or a cross-border element is involved, take independent legal advice before you sign.

Why R&D needs a different kind of NDA

A standard commercial NDA — adequate for sharing pricing, a customer list, or a business plan — is often insufficient for R&D. Research information has specific features that require deliberate drafting.

First, the confidential information definition must be precise enough to cover what is actually shared: experimental protocols, data sets, negative results (which are commercially valuable even when not published), software source code, and manufacturing know-how. A generic definition of confidential information may leave critical categories unprotected.

Second, R&D results are often on a path to patent filing. An NDA that allows disclosure to third parties — even with a confidentiality obligation on those third parties — can create novelty problems if those disclosures are deemed public for patent law purposes. The NDA must restrict onward disclosure tightly.

Third, publication is a normal part of academic R&D. Industry partners need a contractual right to review and delay proposed publications before they go public, to enable patent filing during the review window. Without this, the academic partner's publication obligation and the company's novelty interest are in direct conflict.

The patent novelty problem

The single most important reason an R&D NDA must be in place before any technical disclosure is the patent novelty requirement.

Under the Patents Act 1977 and the European Patent Convention, an invention must be novel — it must not have been made available to the public anywhere in the world before the filing date of the patent application. A disclosure to a single person outside the inventing team, without a binding confidentiality obligation, can count as prior art that destroys novelty and prevents a valid patent from being granted.

An NDA does not extend the novelty window — you still need to file before disclosing publicly. What an NDA does is keep disclosures private, so that they do not count as prior art. A company partner briefing a university on a technical problem under a mutual NDA does not make that information public. A conference presentation, an unprotected email chain, or a casual meeting without one does.

File before you present or publish

An NDA protects information shared under it. It does not extend the patent novelty window for information disclosed to the public — at a conference, in a paper, or in an unprotected meeting. If your R&D project may produce patentable results, file a UK priority application before any public disclosure. The NDA and the patent application work together; neither substitutes for the other.

R&D NDA scenarios

ScenarioInformation at riskRight NDA type
Industry-academia knowledge transfer partnershipCompany know-how, university background IP, joint experimental resultsMutual NDA — both parties share confidential R&D information
Briefing a contract research organisation (CRO)Technical specifications, experimental protocols, proprietary compounds or materialsOne-Way NDA (disclosing) — you brief, they receive
Co-development between two companiesTechnical designs, test data, roadmap, joint IPMutual NDA — both parties disclose
Innovate UK or Horizon Europe consortiumEach partner's background IP, joint results, commercial plansMutual NDA with grant-compliance carve-out
Pre-patent investor briefingTechnical details of the invention, unpublished resultsOne-Way NDA (disclosing) — preserves novelty while seeking investment
Commissioning R&D from an external laboratoryBrief, specification, and any results generatedNDA with IP assignment — ensures results vest in the commissioning business

Industry-academia partnerships

The most complex R&D NDA situation in the UK is the industry-academia partnership — where a company and a university (or other research institution) collaborate on a funded innovation project.

Both parties bring background IP — existing knowledge, software, methods and materials — and both create foreground IP during the collaboration. The academic partner typically has a contractual obligation with its funder (Research England, UKRI, Innovate UK) to publish results; the company partner typically wants to delay publication until a patent application has been filed.

The standard structure is: a mutual NDA at the start to enable early discussions, followed by a formal collaboration agreement that governs background IP licences, foreground IP ownership, publication approval, cost sharing, and commercialisation. The NDA is a bridge to that agreement, not a substitute for it.

Publication review windows

Academic partners can agree in the NDA (or collaboration agreement) to submit proposed publications to the company partner for review before submission. A 30-day window for reviewing publications, with the option to extend by a further 30 days if a patent application needs to be filed, is a common and workable structure. The NDA should specify that the review right does not entitle the company to suppress results indefinitely — only to seek a reasonable delay for patent prosecution.

Trade secrets: protecting what you choose not to patent

Not all R&D results are best protected by a patent. Patenting requires public disclosure of the invention in the patent specification. If a manufacturing process, formulation or algorithm is genuinely difficult to reverse-engineer from the product, keeping it secret under a trade secret regime may provide stronger and longer-lasting protection than a 20-year patent.

The Trade Secrets (Enforcement, etc.) Regulations 2018 give UK law a coherent framework for trade secret protection: information qualifies as a trade secret if it has commercial value, is not generally known, and the owner takes reasonable steps to keep it confidential. An NDA is the primary reasonable step — it is the contractual evidence that you treat the information as secret.

Unlike patents, trade secret protection has no expiry date, no registration requirement, and no public disclosure. The protection lasts for as long as the information remains genuinely confidential. The corresponding risk is that if the information is independently discovered, or leaked despite the NDA, the protection is lost.

IP assignment in R&D commissioning

When one business commissions R&D from an external laboratory, contract research organisation or specialist consultancy — rather than collaborating as joint parties — the IP position is different. The contractor will typically own the IP it creates by default, in the same way a freelance designer owns their work.

An NDA with IP assignment is the appropriate document for this relationship. It combines the confidentiality obligation (the contractor cannot disclose the commission, the brief or the results) with a clause assigning ownership of all results, inventions and know-how generated during the engagement to the commissioning business on creation.

Without the assignment, the commissioning business may have a licence to use the results but will not own them. This creates problems if the business later seeks to patent the results, licence them to a third party, or sell the business — in each case the buyer or licensor will want clear title to the IP, which requires the contractor's cooperation to establish.

R&D NDA templates

NDASafe Mutual NDA, One-Way NDA and NDA with IP Assignment are drafted for England and Wales and suitable for UK R&D partnerships. £29 each or £79 for all eight — editable Word documents, delivered instantly.

Step by step

  1. 1
    Identify what information needs protecting

    List the specific categories of R&D information you will share: technical specifications, experimental protocols, datasets, software, unpublished results, background IP. A vague definition of confidential information is the most common weakness in R&D NDAs.

  2. 2
    Choose the right NDA type

    Use a Mutual NDA when both parties will share confidential R&D information — the standard for industry-academia partnerships and co-development. Use a One-Way NDA (disclosing party) when only you are sharing — for example, briefing a contract research organisation.

  3. 3
    Address publication rights

    Academic partners typically have an obligation to publish research results. The NDA should include a publication review window (typically 30–90 days) allowing the company partner to review any proposed publication and request a delay for patent filing before the paper goes public.

  4. 4
    Agree the IP position before the project starts

    Background IP (what each party brings in) stays owned by the party that created it. Foreground IP (what is created during the collaboration) needs an explicit written agreement on ownership, licences and commercialisation. This goes in the collaboration agreement, but the NDA should cross-reference it.

  5. 5
    File any patent applications before public disclosure

    If the R&D produces patentable results, file the patent application — at minimum a UK priority application — before any publication, conference presentation, or disclosure outside the NDA. The NDA protects information shared under it; it does not extend the novelty window for a patent application.

  6. 6
    Sign the NDA before any technical discussions begin

    An NDA signed after information has already been shared does not protect that information retroactively. Get signatures in place before the first technical meeting, site visit, or data transfer — not after.

Frequently asked questions

Does disclosing R&D information without an NDA destroy patent rights in the UK?

It can. The UK Intellectual Property Office and the European Patent Office require that an invention be novel — not publicly disclosed — at the date a patent application is filed. An unguarded disclosure to an industry partner, a conference audience, or a potential investor before filing can count as prior art that destroys novelty. A signed NDA before disclosure keeps the information confidential and preserves novelty. Some applicants use the 12-month grace period for self-disclosure to the UKIPO, but this provides no grace for EPO applications or most international routes, so the safe approach is always to file before disclosing, or to disclose only under NDA.

Who owns the intellectual property created in a joint R&D project?

Jointly developed IP belongs jointly to all contributing parties by default under UK law — each owner can exploit the IP without the other's consent but cannot licence it to a third party or assign their share without agreement. This default is almost always commercially impractical. An R&D collaboration agreement (of which the NDA is one component) should specify upfront how IP ownership, exploitation rights and revenue sharing will work. The NDA protects the information during the project; a collaboration agreement governs what happens to the output.

Does a university-industry Knowledge Transfer Partnership need an NDA?

Yes. A Knowledge Transfer Partnership (KTP) places a graduate associate within a business to develop an innovation project in collaboration with a university partner. Both the university's research background IP and the company's commercial know-how are shared during the partnership. A mutual NDA should be in place at the outset, supplemented by a full collaboration agreement governing background IP licences, foreground IP ownership, publication rights and commercialisation. Innovate UK's standard KTP terms provide a framework, but the NDA between the parties is separate and earlier.

Can an NDA protect research results that are not patented?

Yes. Unpatented R&D results — experimental data, negative results, know-how, software algorithms, manufacturing processes — can be protected as confidential information under contract (the NDA) and as trade secrets under the Trade Secrets (Enforcement, etc.) Regulations 2018, which provide indefinite protection as long as the information remains genuinely secret. An NDA is often more practical than patent protection for process know-how that is difficult to reverse-engineer: it prevents disclosure without requiring public disclosure of the details in a patent specification.

What is the difference between an NDA and a full R&D collaboration agreement?

An NDA is one component of R&D contracting. It creates a confidentiality obligation — the obligation not to disclose or misuse what is shared. A full R&D collaboration agreement covers the full relationship: project scope, milestones, funding, background IP licences, ownership of foreground IP, publication approval, liability, termination, and commercialisation. In practice, an NDA is signed first to enable preliminary discussions; a full collaboration agreement follows once both parties decide to proceed. NDASafe's Mutual NDA covers the confidentiality layer; you will typically need a bespoke collaboration agreement for the full project.

Can an NDA cover Innovate UK or Horizon Europe collaboration information?

Yes, but with care. Innovate UK and Horizon Europe grants impose their own IP and publication obligations on recipients, including requirements to acknowledge public funding and in some cases to publish results. An NDA between consortium members can protect information shared during the project, but it cannot override the grant conditions. The NDA should include a carve-out allowing disclosures required by the grant terms, including mandatory reporting to the funding body, open-access publication requirements, and audit rights.

Templates mentioned in this guide