Engineering & infrastructure

NDA for UK Engineering Firms: Protecting Designs, Specifications and Project Information

UK civil, structural, mechanical, electrical and environmental engineers share sensitive technical information — preliminary designs, specifications, cost models and BIM data — long before formal contracts are executed. This guide explains when engineering firms need an NDA, what it must cover under UK law, and which template to use.

By Richard Wood, Founder7 min readUpdated 22 June 2026Last reviewed 22 June 2026NDAengineeringcivil engineeringstructural engineering

UK engineering firms — civil, structural, mechanical, electrical, environmental and geotechnical — operate in a project-based environment where commercially sensitive information is shared throughout the pre-contract phase. Preliminary designs, structural calculations, cost models, tender pricing, BIM data and proprietary methodologies are all disclosed before formal appointments are made. An NDA ensures that information shared during evaluation, tender or early-stage design is protected by a binding confidentiality obligation, not merely by professional courtesy.

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 UK engineering firms need an NDA

An NDA is appropriate in the following engineering contexts:

  • Design competitions and two-stage tenders: before an engineer submits a preliminary design or technical approach to a client-side evaluation panel who will also see competing designs.
  • Specialist subcontractor appointments: before a main contractor or lead designer shares detailed engineering specifications, drawings or cost targets with specialist subcontractors being evaluated for appointment.
  • Joint ventures and consortium bids: before two or more engineering firms begin sharing design methodology, resource plans and commercial strategies to prepare a joint bid.
  • Pre-patent technical disclosures: before an engineer discloses a novel design system, innovative structural concept or proprietary engineering process to a client, investor or partner — an NDA is essential to preserve patent novelty under the Patents Act 1977.
  • Technology and software licensing: before an engineering software company shares a proprietary analysis tool, design platform or data model with a prospective licensee or engineering partner.
  • Research and innovation partnerships: before an engineering consultancy shares unpublished research findings, test data or novel methodology with a university, Catapult centre or corporate R&D partner.
  • Infrastructure project financing: before an engineering firm shares detailed technical reports, feasibility studies or risk assessments with infrastructure investors or project finance providers evaluating a scheme.

What an engineering NDA must cover

A general commercial NDA may be inadequate for engineering projects. An engineering NDA should explicitly address:

  • Comprehensive definition of confidential information: including drawings, design calculations, structural models, geotechnical data, BIM files, IFC data, method statements, specifications, tender pricing, cost plans and proprietary methodologies. A catch-all definition alone is insufficient — listing specific categories prevents disputes about what is and is not covered.
  • Purpose restriction: limiting the recipient's use of disclosed information strictly to the specific project or engagement — prohibiting use of a competitor's design approach, pricing model or engineering methodology for any purpose outside the agreed evaluation.
  • Multi-tier sub-disclosure controls: requiring the recipient to impose equivalent confidentiality obligations on any sub-consultant, subcontractor or technical adviser before disclosing. Engineering projects involve many layers of disclosure and obligations must flow through the supply chain.
  • Trade secret and patent protection: an express trade secret survival clause under the Trade Secrets (Enforcement, etc.) Regulations 2018, and a prohibition on disclosing any pre-patent design detail that could constitute a public disclosure under the Patents Act 1977.
  • BIM and digital data provisions: explicit coverage of BIM models, IFC files, CDE-hosted content and associated metadata as confidential information, with restrictions on copying, exporting or reverse-engineering model data.
  • Return or destruction: tender documents, preliminary design packages, cost models and BIM data should be returned or securely deleted if the engineering appointment does not proceed.

Engineering NDA duration: what is appropriate?

Duration should be matched to the sensitivity and lifecycle of the information:

  • Tender pricing and cost models: three years from the date of disclosure — sufficient to cover a re-tendering cycle for similar projects.
  • Preliminary designs and specifications: three to five years, or until the project is constructed and the information is publicly visible through planning submissions or regulatory filings, whichever is earlier.
  • BIM data: five years, or for the duration of the project plus two years after practical completion.
  • Proprietary engineering methodologies and novel design processes: indefinite, covered by a trade secret survival clause — these retain commercial value regardless of the project outcome.
  • Patent-pending designs: protected until a patent is granted; after grant, the patent regime provides statutory protection and the NDA obligation transitions to protecting implementation details not disclosed in the patent.

Which NDASafe template to use

The right template depends on the structure of the engineering relationship:

  • Mutual NDA (£29): the default for most engineering relationships — JV bids, design-build contractor evaluations, specialist subcontractor pre-appointments and research partnerships — where both parties are sharing sensitive design, technical or commercial information.
  • One-Way NDA, Disclosing (£29): use where only one party discloses — a client issuing a confidential engineering brief to prospective consultants, or an engineering firm sharing a preliminary design with a client who is not sharing sensitive information in return.
  • NDA with IP Assignment (£29): use where an engineer or design firm is developing bespoke designs specifically for a client and the client needs to own the resulting IP — for example, a proprietary structural system or novel component design commissioned for a specific project.
  • Freelancer NDA (£29): use for self-employed engineering consultants and specialist contractors where IR35 status must be acknowledged and contributions to IP need to be addressed.
  • Complete NDA Bundle (£79): all eight NDA variants. Suitable for engineering consultancies managing a range of client, JV partner, subcontractor, investor and research relationships simultaneously.
UK engineering NDA templates — legally reviewed, instant download

NDASafe's NDA templates are editable Word documents appropriate for UK civil, structural, mechanical, electrical and environmental engineering firms, contractors and specialist subcontractors. Single template £29. Complete bundle (all 8 variants) £79. Delivered instantly as an editable .docx file.

Step by step

  1. 1
    Sign before sharing any design drawings, specifications or tender pricing

    Engineering projects generate commercially sensitive information from the earliest concept stage. Before a structural engineer shares preliminary calculations with a specialist subcontractor, before a civil engineer shares a feasibility study with a prospective JV partner, and before an engineer shares tender pricing with a client-side cost manager, the NDA must be signed. A single unprotected disclosure of a novel design approach, a proprietary analysis method or a competitive tender price can destroy the engineer's commercial position without any enforceable recourse.

  2. 2
    Define confidential information to cover engineering-specific data categories

    A standard commercial NDA definition — “all information disclosed in connection with the proposed engagement” — may not be adequate for engineering projects. The definition should explicitly cover: preliminary drawings, design calculations, structural and geotechnical models; specifications, method statements, engineering reports and feasibility studies; BIM data, IFC files, federated models and CDE-hosted content; tender pricing, cost plans, bills of quantities and procurement strategies; proprietary analysis software, design tools and engineering methodologies; patent-pending designs and novel technical processes; and project-specific risk and programme information.

  3. 3
    Address the multi-party structure of engineering projects

    Major engineering and infrastructure projects involve a complex supply chain: client, employer's agent, main contractor, specialist subcontractors, consultants and technology providers. Information is shared across all tiers. The NDA should identify which parties will receive confidential information, impose equivalent confidentiality obligations on each, and include a sub-disclosure restriction requiring each recipient to impose parallel obligations on any subcontractor or sub-consultant before disclosing. For multi-party tenders, all prospective contractors should sign before the employer's requirements and tender documents are issued.

  4. 4
    Include a trade secret clause for patentable designs and novel processes

    An engineer sharing an unpatented structural innovation, a novel geotechnical technique or a proprietary analysis methodology faces a dual risk: commercial misuse by the recipient and destruction of patent novelty. An NDA must be signed before any pre-patent disclosure — under the Patents Act 1977, sharing technical details of an invention with a third party without adequate confidentiality protection may constitute a “public disclosure” that bars a subsequent patent application. The NDA should include a trade secret survival clause under the Trade Secrets (Enforcement, etc.) Regulations 2018 for any engineering IP that retains commercial value beyond the project.

  5. 5
    Set duration appropriate to the project lifecycle

    Engineering projects have long lifecycles. Appropriate NDA durations depend on the type of information: tender pricing and cost models — three years from the date of disclosure, to cover the re-tender cycle for similar projects; design drawings and preliminary specifications — three to five years or until the project is constructed and publicly visible, whichever is later; proprietary design methodologies, analysis techniques and novel engineering processes — indefinite, covered by a trade secret survival clause; patent-pending designs — protected by the NDA until a patent is granted; programme and strategic information — two years from disclosure. For projects with long planning and construction periods, tie the duration to project completion rather than a fixed calendar period.

Frequently asked questions

Why do UK engineering firms need an NDA?

Engineering firms routinely share three categories of highly sensitive information before formal contracts are executed: technical designs (preliminary drawings, structural calculations, specifications and models); commercial information (cost estimates, tender pricing, procurement strategies and financial models); and proprietary methodology (design approaches, analysis techniques, patented or patent-pending engineering processes). An NDA creates a binding contractual obligation of confidence from the moment information is shared, limits its use to the agreed purpose, and provides enforceable remedies — including injunctive relief — if it is misused. For engineers sharing pre-patent designs or novel processes, an NDA is also essential for preserving novelty under the Patents Act 1977.

Should an engineering NDA be mutual or one-way?

It depends on the structure of the relationship. Mutual NDAs are appropriate where both parties are sharing genuinely sensitive information — a structural engineer and a specialist subcontractor both sharing design methodology and pricing during a design-build tender, or two engineering firms collaborating on a joint bid. A one-way NDA is appropriate where only one party discloses — a client issuing a detailed engineering brief to prospective consultants who are only providing capability information in return, or an engineering firm sharing preliminary designs with a client who is not sharing sensitive information in return. When in doubt, a mutual NDA is the safer choice.

What is a BIM NDA and do I need one?

Building Information Modelling (BIM) data is a specific category of confidential information in engineering and construction. A BIM NDA is simply an NDA that explicitly includes BIM models, associated metadata, IFC files and federated model data within the definition of confidential information. BIM data for a major infrastructure or building project is commercially sensitive — it contains the entire design intent, spatial co-ordination, cost data, programme information and often commercially sensitive client requirements. A standard NDA that does not expressly mention BIM data may leave that information unprotected. For projects procured under ISO 19650 frameworks, the Common Data Environment (CDE) protocol governs sharing within the project team; an NDA covers the pre-contract evaluation and contractor selection phase.

Can an NDA protect an engineer's proprietary design methodology?

Yes. A proprietary structural analysis technique, a novel foundation design method, a bespoke cost modelling approach, or a patented structural system all constitute trade secrets or confidential information under UK law. An NDA that explicitly covers these categories and prohibits the recipient from reverse-engineering, replicating or using them outside the agreed purpose provides contractual protection. The Trade Secrets (Enforcement, etc.) Regulations 2018 give indefinite protection to information that qualifies as a trade secret — the NDA converts that regulatory protection into a directly enforceable contractual right.

Does an NDA replace a JCT or NEC contract in engineering projects?

No. A JCT building contract, NEC engineering contract or professional services agreement governs the substantive engineering relationship — design obligations, programme, payment, liability and risk. An NDA protects the period before those contracts are executed: the tender phase, preliminary design sharing, contractor evaluation, and any pre-contract collaboration. An NDA does not address design liability, professional indemnity, programme or payment — and a JCT or NEC contract does not include pre-contract confidentiality provisions covering the evaluation period. Both documents are needed: the NDA covers what is shared before the contract; the contract governs the project itself.

Templates mentioned in this guide