When you engage a contractor — whether that is a freelance developer, a marketing consultant, a design agency, or any other independent supplier — you will almost certainly share sensitive information before work begins: a project brief, a product roadmap, client data, commercial terms. A contractor NDA is the document that protects that information, sets the boundaries of the engagement, and makes clear that the relationship is not employment. This guide explains when to use one, what it should say, and why getting the template right matters.
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 a business needs a contractor NDA
The moment to put a contractor NDA in place is before you share anything sensitive — not after the engagement is underway. In practice that means signing before:
- Sharing a project brief or scope of work that reveals your product direction, client names, or commercial priorities.
- Giving access to systems, code or data — a codebase, a CRM, a customer database, or internal analytics.
- Discussing pricing, margins or business strategy during a scoping or discovery call.
- Disclosing unreleased products, features or plans that a contractor could share with a competitor or use to their own advantage.
- Any engagement involving client data — where you have your own confidentiality obligations to the underlying clients.
The NDA does not need to wait for a formal engagement letter or statement of work. A short-form contractor NDA can be signed at the discovery or proposal stage, before either party has committed to anything further.
What a contractor NDA should cover
A well-drafted contractor NDA covers five things:
| Clause | Why it matters |
|---|---|
| Definition of confidential information | Names what is protected — project briefs, source code, client data, business plans. Specific definitions are easier to enforce than vague blanket wording. |
| Permitted purpose | States that confidential information may be used only for the specific engagement — not to inform a pitch to a competitor, a personal project, or a different client. |
| Non-employment statement | Expressly confirms the contractor is independent, not an employee or worker. This reinforces the outside-IR35 position and prevents the NDA being read as an employment instrument. |
| IP assignment | Transfers ownership of project deliverables to the client while preserving the contractor's background IP (their pre-existing tools and libraries). |
| Duration and return/destruction | Sets how long the obligation lasts (typically two to three years) and what happens to confidential materials when the engagement ends. |
What a contractor NDA should NOT cover
Equally important is what not to include. A contractor NDA should not:
- Use employment language. Phrases like "during your employment", "as a member of staff", or references to HR policies and internal procedures all import employment framing that blurs the independent-contractor line.
- Impose unlimited personal service. Wording that assumes only this named individual can ever do the work — with no possibility of substitution — echoes a key employment test. A contractor NDA should acknowledge that the contractor may use their own team or substitute.
- Act as an open-ended availability obligation. Confidentiality is about information, not the contractor's time. An NDA that reads like an ongoing duty to attend or be available is doing the wrong job.
- Silence protected disclosures. Like any UK confidentiality agreement, a contractor NDA cannot prevent someone reporting a crime or a regulatory breach to the appropriate authority.
Why an employee NDA is the wrong choice
Businesses sometimes reach for the Employee NDA when engaging contractors because it is the confidentiality document they already have. This is a mistake, and not a minor one.
An employee NDA is written on the assumption that the person signing it is an employee: it references the employment relationship, includes mandatory whistleblowing carve-outs designed for employees, and may contain non-compete obligations designed for the employment context. A contractor who signs it has signed something that says — at least in part — that they are being treated as an employee.
Asking a contractor to sign an employee NDA is one of the easiest ways to give HMRC evidence pointing towards an inside-IR35 finding. The document treatment of the relationship is part of the overall picture, and employee-NDA language sits firmly on the wrong side of that line.
A contractor NDA — specifically a freelancer/contractor NDA — uses language that treats the parties as independent, and includes provisions (IP assignment, limited-company contracting) that belong in a self-employment context and not in an employment one.
See the employee NDA guide for a full picture of what an employee NDA is designed to do — and why that scope is the wrong fit for an independent contractor.
Limited company contractors: contract with the company
A significant proportion of UK contractors operate through their own personal service company (PSC) — typically a limited company where the contractor is the sole director and shareholder. In this situation, the legal party you are contracting with is the company, not the individual.
This matters for the NDA in two ways. First, the NDA should name the limited company as the party and be signed by the director in their capacity as company officer — not signed by the individual in a personal capacity. Second, the confidentiality obligation binds the company as the contracting party, which is the correct structure if IR35 is in play.
Contracting with the company rather than the individual also means that the substitution right — a key outside-IR35 indicator — is real: the company can, in principle, send a different individual to do the work. An NDA that is addressed to and signed by the individual personally implicitly assumes personal service.
The NDASafe Freelancer NDA includes a field to contract with either an individual or their limited company, keeping the structure consistent with the rest of the engagement.
IP assignment: who owns the deliverables
This is the clause most often missing from improvised contractor NDAs — and the omission is expensive. Under UK law, the intellectual property in work created by a contractor does not transfer to the client automatically. Unlike an employee (where work created in the course of employment vests in the employer under section 11 of the Copyright, Designs and Patents Act 1988), a contractor retains the copyright in their deliverables unless there is a written assignment.
That means a contractor who builds a bespoke website, writes marketing copy, or develops proprietary software legally owns the IP in what they created — even if they were paid in full and the work was built to the client's specification — unless the contract expressly assigns it.
| Who creates it | Who owns the IP by default | What changes it |
|---|---|---|
| An employee, in the course of employment | The employer — automatically | Nothing required; it is the legal default |
| A contractor or freelancer | The contractor — not the client | A written IP assignment in the contract or NDA |
| A contractor's limited company | The company — not the client | A written assignment from the company to the client |
A contractor NDA with an IP assignment clause transfers ownership of the project deliverables to the client while preserving the contractor's background IP — the pre-existing tools, libraries, frameworks and know-how they bring to the work. This distinction matters: you do not want to accidentally claim ownership of open-source libraries or a developer's reusable internal utilities.
If an IP assignment is missing and a dispute arises, the client has an implied licence to use the deliverables for the purpose they were commissioned — but the scope of that licence is uncertain and the contractor retains the underlying copyright. Fixing this after the fact requires a retrospective assignment, which requires the contractor's co-operation.
IR35 signal: why the wording matters
An NDA does not determine a contractor's IR35 status — working practices do. But the language of every document in the engagement, including the NDA, forms part of the overall picture that HMRC and employment tribunals examine when deciding whether a relationship looks like employment.
An NDA that treats the contractor as independent, contracts with their company, acknowledges substitution, and uses non-employment language is a consistent, useful signal pointing away from employment. An employee NDA, or any NDA with employment-style wording, is a signal pointing the wrong way.
For a full treatment of how NDA language interacts with IR35, see the IR35 and freelancer NDAs guide.
Choosing between a one-way and mutual NDA for a contractor engagement
Most contractor engagements call for a one-way NDA in the client's favour: the client is sharing the brief, the codebase, the customer data — and the contractor is receiving. But some engagements involve two-way disclosure:
- One-way (client as discloser) — the standard shape. Use the Freelancer NDA, which is a one-way NDA with IP assignment and IR35-aware language built in.
- Mutual — use when the contractor will also share proprietary materials: their own methodology, a proprietary framework, background IP they are licensing to you. In that case both sides need protection. A Mutual NDA alongside the Freelancer NDA (for IP and employment language purposes) may be appropriate.
The NDASafe Freelancer NDA uses IR35-aware, explicitly non-employment language, handles individual and limited-company contractors, includes IP assignment, and is written for UK law. £29, instant editable Word download — or £79 for all eight templates.