Pharma & drug development

NDA for the UK Pharmaceutical Industry: Protecting Clinical Data, Formulations and Research Partnerships

UK pharmaceutical companies share clinical trial data, API formulations and proprietary research with CROs, CMOs and licensing partners before formal contracts are signed. This guide explains when a pharmaceutical NDA is needed, what it must cover, and which template is appropriate.

By Richard Wood, Founder8 min readUpdated 20 June 2026Last reviewed 20 June 2026NDApharmaceuticalpharmaclinical trials

Pharmaceutical development involves constant disclosure of commercially sensitive information before formal agreements are in place. A potential contract research organisation receives compound data to prepare a feasibility proposal. A contract manufacturing partner reviews synthesis routes before accepting a project. A licensing partner evaluates preclinical results ahead of term sheet negotiations. Each of these disclosures exposes proprietary science that can take years and hundreds of millions of pounds to develop — and without an NDA, that disclosure creates no binding obligation of confidence.

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.

When pharmaceutical NDAs are needed

An NDA should be in place before any confidential information is shared in the following pharmaceutical contexts:

  • CRO engagement: before sharing compound structures, study protocols, or preclinical data with a contract research organisation during feasibility discussions or proposal preparation.
  • CMO and CDMO selection: before sharing synthesis routes, process parameters, formulation information or manufacturing specifications with a contract development and manufacturing organisation during qualification and proposal stages.
  • Licensing and partnering discussions: before sharing clinical data, regulatory status, IP position or commercial projections with a potential licensee, sub-licensee or co-development partner.
  • Academic collaboration: before sharing proprietary compounds or methodologies with a university or research institution, particularly where the academic partner may wish to publish.
  • Investor and strategic partner discussions: before sharing clinical pipeline data, regulatory strategy or financial projections with a potential investor, acquirer or corporate partner.
  • Regulatory consultancy: before sharing regulatory submission data, MHRA correspondence or regulatory strategy with an external regulatory affairs consultant.

What a pharmaceutical NDA protects

The confidential information definition in a pharmaceutical NDA should cover all information generated or shared across the drug development lifecycle:

  • Compound and molecule data: chemical structures, synthesis routes, formulation parameters, stability data, and any proprietary compound libraries or screening data.
  • Preclinical data: in vitro pharmacology, toxicology, ADME data, and any animal study results or biomarker data.
  • Clinical data: clinical trial protocols, investigator brochures, clinical study reports, patient data (pseudonymised), pharmacokinetic and pharmacodynamic results, and safety and efficacy data.
  • Regulatory submissions: IND/CTA applications, MHRA meeting minutes, EMA scientific advice correspondence, orphan designation applications, and any other regulatory filings.
  • Manufacturing and process information: API synthesis routes, process chemistry parameters, quality control specifications, batch records and analytical methods.
  • Commercial and financial information: clinical development budgets, commercialisation forecasts, licensing terms, pricing models, and deal structure proposals.
Unprotected disclosures can destroy patent novelty

Under UK and European patent law, a compound or process must not have been publicly disclosed before the patent application filing date. Any disclosure to a CRO, academic collaborator or licensing partner without an NDA in place may count as prior art. Always sign an NDA before sharing unpublished compound data or methodology.

CRO and CMO agreements: one-way or mutual?

In a typical CRO engagement, both parties share confidential information: the pharmaceutical company shares compound data and study protocols; the CRO shares its standard operating procedures, pricing models, facility information and, in some cases, proprietary analytical methods. A mutual NDA is the standard structure for CRO relationships.

For CMO and CDMO relationships, the same principle applies. The pharmaceutical company shares synthesis routes and process parameters; the CMO may share its proprietary manufacturing technology, equipment specifications or process know-how. A mutual NDA is appropriate where the CMO is genuinely sharing confidential technical information.

A one-way NDA (with the pharmaceutical company as the disclosing party) is appropriate where the CRO or CMO is performing a standard commoditised service and sharing no proprietary information of its own beyond standard pricing and timing.

Regulatory carve-outs and pharmacovigilance obligations

A pharmaceutical NDA must include mandatory carve-outs for regulatory disclosure. These carve-outs reflect statutory obligations that no contractual confidentiality obligation can override:

  • MHRA and EMA disclosure: disclosure required by the Medicines and Healthcare products Regulatory Agency, the European Medicines Agency, or any other competent authority under applicable medicines law.
  • Adverse event and pharmacovigilance reporting: any report required under the Yellow Card scheme, the Pharmacovigilance Risk Assessment Committee rules, or equivalent post-marketing surveillance obligations.
  • GCP and GMP inspections: disclosure required by a GCP or GMP inspectorate during an audit or inspection of clinical trial conduct or manufacturing practices.
  • Clinical trial transparency: disclosure required by EUCTR, ClinicalTrials.gov, or any applicable clinical trial registration and transparency obligation.
Regulatory disclosure carve-outs are mandatory, not optional

A pharmaceutical NDA that purports to prevent MHRA, EMA or pharmacovigilance disclosures is unenforceable to that extent. These carve-outs should be stated explicitly — a general 'required by law' carve-out is sufficient as a minimum, but naming the relevant regulators provides greater clarity in practice.

Duration and trade secret protection

Standard commercial NDA terms of two to three years are usually inadequate for pharmaceutical information. The appropriate duration depends on the nature of the asset:

  • Compound and early-stage science: minimum five years, or from execution until the later of five years or the grant of a relevant patent. Where no patent application will be filed, indefinite protection as a trade secret is appropriate.
  • Clinical data and regulatory submissions: five to ten years, or the longer of the express term and any data exclusivity, orphan designation or supplementary protection certificate period.
  • CMC and manufacturing data: five to ten years. Manufacturing process information for approved drugs retains commercial value well beyond the initial development period, particularly where generic competitors will seek to replicate the process.
  • Commercial and financial projections: two to three years is often proportionate for commercial forecasts and deal terms, as this information typically becomes stale or publicly available on completion of a transaction.

Where information constitutes a trade secret under the Trade Secrets (Enforcement, etc.) Regulations 2018 — kept secret, having commercial value because of that secrecy, and subject to reasonable protective steps — protection survives the NDA term indefinitely. An NDA is one of those reasonable steps.

Which NDASafe template to use

The appropriate template for a pharmaceutical engagement depends on the information flow:

  • Mutual NDA (£29): use for CRO, CMO and CDMO engagements where both parties share confidential information — compound data and protocols from the pharmaceutical company; SOPs, pricing and proprietary methods from the CRO or CMO.
  • One-Way NDA, Disclosing (£29): use where only the pharmaceutical company is sharing confidential information and the service provider is not sharing genuinely proprietary information in return.
  • One-Way NDA, Receiving (£29): use where a pharmaceutical company is receiving confidential compound or study data from an academic institution, co-development partner or in-licensor.
  • Complete NDA Bundle (£79): all eight NDA variants. Suitable for pharmaceutical and biotech legal teams, business development functions and procurement teams that manage multiple CRO, CMO and licensing relationships simultaneously.
UK pharmaceutical NDA templates — legally reviewed, instant download

NDASafe's NDA templates are editable Word documents with trade secret survival clauses, regulatory carve-outs, and confidential information definitions appropriate for UK pharmaceutical and drug development relationships. Single template £29. Complete bundle (all 8 variants) £79. Delivered instantly as an editable .docx file.

Step by step

  1. 1
    Sign before any scientific or clinical disclosure

    A pharmaceutical NDA must be executed before any compound information, study protocol, preclinical data or proprietary methodology is shared — including during a feasibility call or a chemistry discussion that precedes a formal proposal. The most common gap is the ‘informal preliminary conversation’ in which a potential CRO or licensing partner is given enough information to evaluate the opportunity before an NDA is in place. Treat this as a disclosure requiring NDA protection.

  2. 2
    Define confidential information to cover the full lifecycle of data

    The definition should explicitly include: compound structures and synthesis routes; preclinical pharmacology and toxicology data; clinical trial protocols and results; regulatory submissions and correspondence (including MHRA and EMA filings); proprietary assay methodologies; manufacturing process parameters; pharmacokinetic and pharmacodynamic data; and any data generated by the receiving party in connection with the study or collaboration. A catch-all ‘all information shared in connection with the engagement’ clause is a useful backstop but is not sufficient on its own in pharmaceutical contexts.

  3. 3
    Include explicit MHRA, EMA and regulatory carve-outs

    Pharmaceutical NDAs must explicitly carve out mandatory regulatory disclosures: disclosures required by the MHRA, EMA, NICE, or any other competent authority; adverse event and pharmacovigilance reporting obligations; inspections and audits by GCP inspectorates; and any disclosure required by the Clinical Trials Regulation as retained in UK law. A general ‘required by law’ carve-out is a minimum; specifying the relevant regulators by name reduces ambiguity in practice.

  4. 4
    Address data ownership and publication rights

    An NDA does not automatically determine who owns data generated during a study. The NDA should be supported by a work order or collaboration agreement that specifies data ownership (sponsor-owned as a default), publication rights (requiring sponsor consent before any CRO or academic partner can publish), and the return or destruction of all raw data, reports and electronic files on termination. Without these provisions, a CRO or collaborating institution may argue the right to publish study results independently.

  5. 5
    Set a duration matched to the regulatory and commercial lifecycle

    Match the NDA term to the commercial life of the information. For early-stage compounds where patent applications are pending, a minimum of five years is appropriate. For clinical data and regulatory submissions, consider tying the confidentiality obligation to the longer of five years from the effective date or the period during which any regulatory exclusivity (data exclusivity, orphan designation) is in force. A survival clause for trade secrets — ensuring protection continues beyond the express term while the information remains secret — should be included for core pharmaceutical assets.

Frequently asked questions

Can a pharmaceutical NDA protect a drug compound before a patent is filed?

Yes, and it is essential to do so. Under UK and European patent law, a drug compound must not have been publicly disclosed before the patent application filing date — any unprotected disclosure to a CRO, academic partner or potential licensee can count as prior art and destroy novelty. A signed NDA converts the disclosure from a public act to a private confidential communication, preserving patent eligibility. The NDA and a patent application work together — the NDA protects the pre-filing period; the patent protects the invention once granted.

Can a pharmaceutical NDA prevent disclosure to the MHRA or EMA?

No. A pharmaceutical NDA cannot lawfully prevent disclosure to the MHRA, EMA, NICE, a clinical trial inspectorate, or any other competent regulatory authority where disclosure is required by law or regulation. Any clause purporting to do so is void. This is a standard carve-out in pharmaceutical NDAs and should be drafted explicitly — the obligation to keep information confidential does not override mandatory regulatory reporting. Similarly, an NDA cannot prevent a pharmacovigilance disclosure or a mandatory adverse event report.

Should a CRO NDA be mutual or one-way?

Usually mutual. In a typical CRO engagement, the pharmaceutical company shares the compound, protocol, preclinical data and any proprietary assays or methodologies. The CRO shares its standard operating procedures, pricing models, facility information and sometimes proprietary analytical methods developed independently. Because both parties share genuinely confidential information, a mutual NDA is the more appropriate structure. A one-way NDA is appropriate where the CRO is simply performing a standard service and sharing no proprietary information of its own.

Does a pharmaceutical NDA cover data generated by a CRO during a study?

It depends on how the NDA is drafted. The confidential information definition should expressly include study results, analytical data, clinical trial outputs and any reports generated under the agreement. Without this, a CRO could argue that data they generated is theirs to use or publish. Many pharmaceutical companies use a combined NDA and work order that addresses both confidentiality and data ownership — specifying that all study data belongs to the sponsor, that the CRO must not publish without consent, and that the NDA obligation covers the generated data as well as the input information.

How long should a pharmaceutical NDA last?

Longer than standard. Most commercial NDAs run for two to five years, but pharmaceutical information — particularly compound structures, synthesis routes, clinical data and regulatory submission data — may retain commercial and regulatory value for ten years or more. A term tied to the longer of five years or the duration of any regulatory exclusivity period is appropriate for core pharmaceutical assets. Where the information constitutes a trade secret under the Trade Secrets (Enforcement, etc.) Regulations 2018, protection survives the NDA term for as long as the information remains secret.

Templates mentioned in this guide