NDA Template UK — Copy-Paste Mutual & One-Way Examples for Freelancers

A prospective client emails: "Before we discuss the project, I need to share some sensitive financials and product roadmap details. Can we have a discovery call first?"

You pause. You want the project. But if they share confidential information and things do not work out, you do not want them claiming you used their ideas elsewhere.

Or worse: you share your pricing structure, process, and strategic recommendations on the call, and they take it to a cheaper competitor.

This is when you need a non disclosure agreement (NDA) — also called a confidentiality agreement.

An NDA is not about distrust. It is about clarity. It protects both sides when sensitive information is shared before a contract is signed. It sets boundaries, defines what is confidential, and states what happens to that information after the call or project ends.

This guide gives you three copy-paste UK NDA templates (mutual and one-way) with invented studio names for designers, developers, writers, and consultants, explains when to send an NDA versus when you do not need one, shows you mutual versus one-way NDAs and which to pick, includes a field checklist, and provides email scripts for sending an NDA before a discovery call, handling pushback, and moving from signed NDA to contract.

What an NDA is (and when UK freelancers should use one)

A non disclosure agreement (NDA) — also called a confidentiality agreement — is a legal contract that prevents one or both parties from sharing or using confidential information disclosed during discussions or work.

An NDA protects information that is sensitive, proprietary, or not yet public. This might include:

✓ Financial data (revenue, profit margins, cashflow forecasts)
✓ Product roadmaps or unreleased features
✓ Customer lists or pricing strategies
✓ Competitive research or market analysis
✓ Trade secrets or proprietary processes
✓ Creative concepts before they are trademarked

Example: A fintech startup wants to hire you to design their app. Before the discovery call, they need to show you their user data, revenue projections, and competitor analysis. Without an NDA, they have no protection if you share that data with another client or use it for your own product.

NDA vs contract vs confidentiality clause

NDA (standalone): A separate agreement signed before the main contract. Used when confidential information will be shared during discovery, pitching, or scoping — before you have agreed terms.

Confidentiality clause (in contract): A section within your freelance contract that protects confidential information shared during the project. This covers work after the contract is signed.

When to use which:

• NDA before discovery call → Client will share sensitive information before you have agreed to work together
• Confidentiality clause in contract → Sensitive information will only be shared after you start work
• Both → Client shares sensitive information during discovery AND during the project (most common for brand strategy, fintech, healthcare, legal, or product launches)

Tip: If the client will share confidential information on a discovery call but you have not signed a contract yet, send a standalone NDA first. Once the contract is signed, the confidentiality clause in your contract takes over.

When to send an NDA — the decision tree

Not every project needs an NDA before the contract. Here is when to send one and when to skip it.

Send an NDA before the discovery call when:

✓ The client says they will share sensitive information (financials, trade secrets, product details, competitive data) before you have agreed to work together
✓ You are working in a regulated industry (finance, healthcare, legal, government) where confidentiality is standard
✓ The client asks for an NDA — some clients will not share project details without one
✓ You will share your pricing, process, or strategic recommendations on the call and do not want the client taking it to a competitor
✓ The project involves unreleased products or campaigns that have not been announced publicly

Do NOT send an NDA when:

✗ The discovery call is casual — just budget, timeline, and general scope. No sensitive data shared.
✗ The client is discussing publicly available information (e.g. redesigning a public website with no confidential research)
✗ You have already signed a contract — the confidentiality clause in your contract covers you. No separate NDA needed.
✗ The client is a small business owner discussing a straightforward project (e.g. logo for a local café). Asking for an NDA might scare them off.

Bottom line: If sensitive information will be shared before a contract is signed, send an NDA. If the call is just a vague "tell me about your services" chat, skip it.

Mutual NDA vs one-way NDA — which to use

There are two types of NDA: mutual (both sides are protected) and one-way (only one side is protected).

Mutual NDA (two-way)

Both you and the client agree not to share each other's confidential information.

Use a mutual NDA when:

✓ You will share your pricing structure, process, or strategic recommendations on the discovery call
✓ The client will share their sensitive data with you
✓ You both have something to protect

Example: You are a brand consultant. On the discovery call, the client shares their revenue data, competitive analysis, and product roadmap. You share your pricing model, case studies, and strategic framework. Both sides need protection.

Common for: Strategy consultants, agencies, product designers, developers discussing proprietary systems.

One-way NDA

Only one party (usually the client) is protected. You agree not to share their confidential information. They make no promises about yours.

Use a one-way NDA when:

✓ Only the client is sharing sensitive information
✓ You are not sharing anything proprietary on the call
✓ The client requests a one-way NDA (common for large corporates)

Example: A corporate client sends you their detailed product brief and asks you to quote. They share sensitive information. You only share a standard proposal. A one-way NDA is fine.

Common for: Simple discovery calls, pitching to corporates, quoting on a detailed brief.

Which should UK freelancers use?

Default to mutual unless the client insists on one-way. Mutual NDAs protect you if you share your methodology, pricing, or strategic thinking during the call. One-way NDAs only protect the client.

If a client pushes back on a mutual NDA, ask why. If they say "our legal team only signs one-way NDAs," negotiate or accept it. If they say "I do not want to be bound by confidentiality," walk away — that is a red flag.

What to include in a UK freelance NDA — field checklist

A good NDA is short, clear, and enforceable. Here is what to include.

Required fields

✓ Title: "Non Disclosure Agreement" or "Confidentiality Agreement"
✓ Parties: Full legal names and addresses (you and the client, or your limited company name if applicable)
✓ Purpose: Why confidential information is being shared (e.g. "to discuss a potential brand design project")
✓ Definition of confidential information: What counts as confidential (e.g. "financial data, product plans, customer lists, pricing, business strategies")
✓ Exclusions: What is NOT confidential (e.g. information already public, already known, independently developed, legally required to disclose)
✓ Obligations: What you cannot do with confidential information (do not share, do not use for other projects, do not disclose to third parties)
✓ Return or destruction clause: What happens to confidential information after the project or NDA ends (return or destroy documents, delete files)
✓ Term: How long the NDA lasts (e.g. 2–3 years from the date of signing)
✓ Intellectual property clause: Clarify that the NDA does not transfer IP ownership. The client's confidential information stays theirs. Your work stays yours until the contract says otherwise.
✓ Governing law: "This agreement is governed by the laws of England and Wales" (or Scotland if you are based there)
✓ Signatures: Date and signature from both parties

Optional but recommended

✓ Permitted disclosures: You may disclose confidential information to contractors or team members if they are also bound by confidentiality
✓ No employment relationship: Clarify that the NDA does not create an employment or partnership relationship
✓ Amendment clause: "This agreement may only be amended in writing, signed by both parties"

Tip: Keep it under two pages. Long legal documents scare small business owners. A simple, clear NDA is more likely to be signed.

Three copy-paste UK NDA templates

These templates are ready to adapt. Swap the names, addresses, and dates. Keep the structure. All examples use invented studio names (Northline Studio, Oak & Pixel, Maya Cole Consulting) and invented client names.

Example 1 — Mutual NDA for brand consultant and fintech client

NON DISCLOSURE AGREEMENT (MUTUAL)

This agreement is made on 1 October 2026 between:

(1) Maya Cole Consulting (the "Consultant")
12 Harbour Lane, Bristol, BS1 4DJ
maya@mayacoleconsulting.co.uk

and

(2) Fusion Financial Ltd (the "Client")
Registered office: 48 King Street, Manchester, M2 4LQ
Company number: 12345678

Background

The parties wish to discuss a potential brand strategy project. Both parties will share confidential information during these discussions. This agreement protects that information.

1. Definition of confidential information

Confidential information means any information disclosed by one party to the other (whether in writing, orally, electronically, or by any other means) that is marked as confidential or that a reasonable person would understand to be confidential, including but not limited to:

• Financial data, revenue projections, and business plans
• Product roadmaps, features, and unreleased concepts
• Customer lists, pricing strategies, and market research
• Strategic plans, processes, and proprietary methodologies

2. Exclusions

Confidential information does NOT include information that:

(a) Is or becomes publicly available through no breach of this agreement
(b) Was already known to the receiving party before disclosure
(c) Is independently developed by the receiving party without reference to the confidential information
(d) Is required to be disclosed by law or court order (provided the receiving party gives reasonable notice to the disclosing party)

3. Obligations

Each party agrees to:

(a) Keep confidential information strictly confidential
(b) Not disclose confidential information to any third party without prior written consent
(c) Not use confidential information for any purpose other than discussing and potentially working on the project described above
(d) Take reasonable steps to protect confidential information with the same level of care used to protect their own confidential information

4. Permitted disclosures

Each party may disclose confidential information to their employees, contractors, or advisors who need to know the information for the purpose stated above, provided those individuals are bound by confidentiality obligations at least as strict as those in this agreement.

5. Return or destruction of confidential information

Upon written request by the disclosing party, or upon termination of this agreement, the receiving party will:

(a) Return all confidential information (including copies) to the disclosing party, or
(b) Destroy all confidential information and confirm destruction in writing

6. Intellectual property

This agreement does not transfer ownership of any intellectual property. All confidential information disclosed by one party remains the property of that party. Any work created after a project contract is signed will be governed by that contract, not this agreement.

7. Term

This agreement will remain in force for three (3) years from the date of signing.

8. No business relationship

This agreement does not create a partnership, joint venture, employment, or agency relationship between the parties.

9. Governing law

This agreement is governed by the laws of England and Wales. Any disputes will be subject to the exclusive jurisdiction of the courts of England and Wales.

10. Amendments

This agreement may only be amended in writing, signed by both parties.

Signed:

For Maya Cole Consulting:

Signature: ____________________
Name: Maya Cole
Date: ____________________

For Fusion Financial Ltd:

Signature: ____________________
Name: ____________________
Title: ____________________
Date: ____________________

Example 2 — One-way NDA for developer and corporate client

NON DISCLOSURE AGREEMENT (ONE-WAY)

This agreement is made on 1 October 2026 between:

(1) Lumen Digital Ltd (the "Disclosing Party")
Registered office: 22 Oxford Street, London, W1D 1AU
Company number: 87654321

and

(2) Oak & Pixel Ltd (the "Receiving Party")
28 Park Lane, Bristol, BS2 8QR
Company number: 12345678
billing@oakpixel.co.uk

Background

The Disclosing Party wishes to share confidential information with the Receiving Party to discuss a potential web application development project. This agreement protects that information.

1. Definition of confidential information

Confidential information means any information disclosed by the Disclosing Party to the Receiving Party (whether in writing, orally, electronically, or by any other means) that is marked as confidential or that a reasonable person would understand to be confidential, including but not limited to:

• Product specifications, technical architecture, and feature roadmaps
• User data, analytics, and customer insights
• Business strategies, financial data, and pricing models
• Trade secrets, proprietary processes, and unreleased products

2. Exclusions

Confidential information does NOT include information that:

(a) Is or becomes publicly available through no breach of this agreement
(b) Was already known to the Receiving Party before disclosure, as evidenced by written records
(c) Is independently developed by the Receiving Party without reference to the confidential information
(d) Is received from a third party who had no obligation of confidentiality
(e) Is required to be disclosed by law or court order (provided the Receiving Party gives reasonable notice to the Disclosing Party)

3. Obligations of the Receiving Party

The Receiving Party agrees to:

(a) Keep confidential information strictly confidential
(b) Not disclose confidential information to any third party without prior written consent of the Disclosing Party
(c) Not use confidential information for any purpose other than discussing and potentially working on the project described above
(d) Take reasonable steps to protect confidential information with at least the same level of care used to protect its own confidential information

4. Permitted disclosures

The Receiving Party may disclose confidential information to its employees, contractors, or advisors who need to know the information for the purpose stated above, provided those individuals are bound by confidentiality obligations at least as strict as those in this agreement.

5. Return or destruction of confidential information

Upon written request by the Disclosing Party, or if the parties do not proceed with the project, the Receiving Party will:

(a) Return all confidential information (including all copies, notes, and summaries) to the Disclosing Party, or
(b) Destroy all confidential information and confirm destruction in writing

6. No licence or transfer of rights

This agreement does not grant the Receiving Party any licence, rights, or ownership in the confidential information or any intellectual property of the Disclosing Party.

7. Term

This agreement will remain in force for three (3) years from the date of signing. Obligations regarding confidential information will survive termination of this agreement.

8. No business relationship

This agreement does not create a partnership, joint venture, employment, or agency relationship between the parties.

9. Governing law

This agreement is governed by the laws of England and Wales. Any disputes will be subject to the exclusive jurisdiction of the courts of England and Wales.

Signed:

For Lumen Digital Ltd (Disclosing Party):

Signature: ____________________
Name: ____________________
Title: ____________________
Date: ____________________

For Oak & Pixel Ltd (Receiving Party):

Signature: ____________________
Name: ____________________
Title: Director
Date: ____________________

Example 3 — Mutual NDA for designer and startup client (short version)

CONFIDENTIALITY AGREEMENT (MUTUAL)

This agreement is made on 1 October 2026 between:

Northline Studio (the "Designer")
14 Canal Street, Manchester, M1 3EZ
hello@northlinestudio.co.uk

and

Horizon Labs Ltd (the "Client")
Registered office: 10 Station Road, Bristol, BS1 6QH
Company number: 23456789

Purpose

The parties wish to discuss a potential brand identity project. This agreement protects confidential information shared during those discussions.

Confidential information

Confidential information includes (but is not limited to): business plans, product details, customer data, pricing, financial information, proprietary processes, creative concepts, and any information marked as confidential or that would reasonably be considered confidential.

Confidential information does NOT include:

• Information already public
• Information already known before disclosure
• Information independently developed
• Information required to be disclosed by law (with notice given)

Obligations

Both parties agree to:

1. Keep confidential information strictly confidential
2. Not disclose it to third parties without written consent
3. Not use it for purposes other than the project discussions
4. Protect it with reasonable care
5. May share it with employees or contractors who are also bound by confidentiality

Return of information

On request, or if the project does not proceed, each party will return or destroy all confidential information received from the other party and confirm this in writing.

Intellectual property

No ownership or IP rights are transferred by this agreement. All confidential information remains the property of the disclosing party.

Duration

This agreement lasts for two (2) years from the date of signing.

Governing law

This agreement is governed by the laws of England and Wales.

Signed:

Northline Studio:

Signature: ____________________
Name: ____________________
Date: ____________________

Horizon Labs Ltd:

Signature: ____________________
Name: ____________________
Title: ____________________
Date: ____________________

Email scripts — sending an NDA, handling pushback, and moving to contract

Script 1 — Sending an NDA before a discovery call

Subject: NDA for discovery call — [Your studio name] + [Client name]

Hi [Client name],

Thanks for confirming the discovery call on [Date/Time]. I am looking forward to discussing the project.

You mentioned you will share some sensitive product details and financial data on the call. To protect both of us, I have attached a mutual non disclosure agreement (NDA).

It is short — under two pages — and covers:

• What counts as confidential information
• That neither of us will share or misuse what is discussed
• That the NDA lasts for three years

Could you review, sign, and return it before our call? If you have any questions or need adjustments, let me know.

Best,
[Your name]

Attachment: NDA_YourStudioName_ClientName_Oct2026.pdf

Script 2 — When the client pushes back on signing an NDA

Subject: Re: NDA for discovery call

Hi [Client name],

Thanks for your message. I understand NDAs can feel formal, but they protect both of us.

The NDA ensures that:

• The sensitive information you share (financials, product roadmap, customer data) stays confidential
• Any strategic recommendations or pricing I share on the call is not taken to competitors
• We both have legal protection if anything is misused

It is a standard practice for projects like this, and it only takes a few minutes to review and sign. If you have concerns about specific clauses, I am happy to discuss adjustments.

Let me know if you would prefer to adjust the NDA or if you would rather limit what we discuss on the call.

Best,
[Your name]

Script 3 — After the NDA is signed, confirming next steps

Subject: NDA signed — Next steps for [Project name]

Hi [Client name],

Thanks for signing the NDA. It is now in place, and we are good to go for the discovery call on [Date/Time].

On the call, I will ask about:

• Project goals and success metrics
• Budget and timeline
• Key stakeholders and decision-makers
• Any sensitive information you want to share about the product, customers, or competitors

After the call, I will send you a project brief or proposal (depending on what we discuss). If we both decide to move forward, the next step will be a signed contract and scope of work.

See you on [Date/Time].

Best,
[Your name]

Script 4 — Moving from NDA to contract after the discovery call

Subject: Proposal and contract — [Project name]

Hi [Client name],

Thanks for the discovery call yesterday. It was great to hear more about [brief project recap].

I have attached:

1. Proposal — Outlines scope, timeline, and fee (£X,XXX + VAT)
2. Contract — Covers payment terms, IP ownership, revisions, and confidentiality (this replaces the NDA once signed)

The contract includes a confidentiality clause that will cover any sensitive information shared during the project. Once the contract is signed, the standalone NDA we signed earlier is superseded by the contract terms.

If you are happy to proceed:

1. Review and sign the contract
2. I will send a deposit invoice (40% — £X,XXX)
3. Once the deposit clears, we will schedule the kickoff meeting

Let me know if you have any questions or need adjustments.

Best,
[Your name]

Attachments: Proposal_ClientName_Oct2026.pdf, Contract_ClientName_Oct2026.pdf

How an NDA fits into your freelance workflow — from enquiry to contract

An NDA is part of your pre-contract workflow. Here is where it sits in the process.

Stage 1 — Initial enquiry (no NDA needed yet)

Client emails: "I am interested in a brand refresh. Can we chat?"

You reply: "Yes, happy to discuss. Do you have time for a short call this week to talk about your goals, budget, and timeline?"

No NDA needed at this stage. The enquiry is vague and no sensitive information is being shared.

Stage 2 — Discovery call scheduled (NDA sent if needed)

Client replies: "Yes, let's schedule a call. I will need to share our product roadmap, customer data, and financial projections with you so you understand the scope."

You reply: "Great. To protect both of us, I will send a mutual NDA for us to sign before the call."

Send NDA now because the client has said they will share sensitive information.

Stage 3 — NDA signed, discovery call happens

Both parties sign the NDA. You have the discovery call. The client shares their roadmap, data, and projections. You share your pricing structure and strategic recommendations.

NDA protects both sides during this call.

Stage 4 — Proposal or project brief sent

After the call, you send a proposal or ask the client to fill in a project brief so you can quote accurately.

No new NDA needed. The signed NDA is still in place.

Stage 5 — Contract signed

The client accepts your proposal. You send a freelance contract and scope of work.

The contract includes a confidentiality clause that covers sensitive information shared during the project. Once the contract is signed, the standalone NDA is superseded by the contract.

Tip: State in your contract: "This agreement supersedes any prior standalone confidentiality agreement or NDA between the parties."

Stage 6 — Project kickoff

You schedule a kickoff meeting, collect brand assets, and start work. The confidentiality clause in your contract now protects both sides.

No new NDA needed. The contract covers confidentiality during the project.

Summary of when to use an NDA vs confidentiality clause

Bottom line: Use a standalone NDA before a contract is signed if sensitive information will be shared. Once the contract is signed, the confidentiality clause in your contract takes over.

Common NDA mistakes that weaken protection (and how to avoid them)

Not defining what counts as confidential. If the NDA just says "confidential information" without defining it, it is hard to enforce. Always include examples: financial data, product plans, customer lists, pricing strategies.

Forgetting to exclude public information. If the client shares something that is already public (e.g. their website, a press release), it should not be covered by the NDA. Always include exclusions for public knowledge, already-known information, and independently developed work.

No return or destruction clause. If the NDA does not say what happens to confidential documents after the project ends, the client has no way to enforce that you delete or return their data. Always include a return-or-destroy clause.

Using a US NDA template for UK work. US templates reference US laws and may not be enforceable in UK courts. Always state "governed by the laws of England and Wales" (or Scotland).

Not stating the term (how long it lasts). If the NDA does not have an end date, it could theoretically last forever (which may not be enforceable). State a clear term: 2–3 years is standard for freelance projects.

Signing an NDA that transfers IP ownership. Some NDAs include clauses that say "any work created using confidential information belongs to the client." That is an IP transfer clause, not an NDA clause. Do not sign an NDA that transfers ownership of your work. IP ownership should be in your contract, not your NDA.

Not keeping a signed copy. If a dispute arises, you need proof that both parties signed the NDA. Always save a signed PDF (not just an email confirmation).

When NOT to send an NDA — alternatives and red flags

The client is a small business owner discussing a simple project (e.g. logo for a local café). Sending an NDA might scare them off. For simple projects with no sensitive data, skip the NDA and include a confidentiality clause in your contract instead.

You have already signed a contract. If the contract includes a confidentiality clause, you do not need a separate NDA. The contract covers you.

The discovery call is vague (no sensitive data will be shared). If the client just wants to chat about budget and timeline, skip the NDA. You can always send one later if the conversation becomes more detailed.

The client refuses to sign an NDA but wants to share sensitive information. This is a red flag. Ask why. If they say "we do not sign NDAs on principle," either limit what you discuss on the call or walk away. Serious clients understand why NDAs matter.

You are asked to sign an NDA with no mutual protection and the client wants detailed strategic recommendations on the call. This is a one-way NDA that protects the client but not you. If you will share valuable insights, pricing, or methodology on the call, push back and request a mutual NDA instead.

Bottom line: If sensitive information is being shared and no contract is in place yet, send an NDA. If the call is casual or the contract already covers confidentiality, skip it.

Decision checklist — should I send an NDA for this situation?

Use this checklist to decide whether you need an NDA before the discovery call.

Send an NDA if:

✓ The client says they will share financials, product details, customer data, or competitive research on the call
✓ You will share your pricing structure, strategic recommendations, or proprietary methodology
✓ The client works in a regulated industry (finance, healthcare, legal) where confidentiality is standard
✓ The project involves unreleased products, campaigns, or trade secrets
✓ The client asks for an NDA

Do NOT send an NDA if:

✗ The discovery call is casual (just budget, timeline, general scope)
✗ The client is discussing publicly available information
✗ You have already signed a contract with a confidentiality clause
✗ The client is a small business owner and the project is simple (might scare them off)

Ask yourself:

• Will the client share something that is not already public?
• Will I share valuable insights, pricing, or strategy that I do not want taken to a competitor?
• Is there a signed contract in place already?

If the answer to the first two is yes and the third is no, send an NDA.

Related guides

NDAs are one tool in protecting your freelance business. Once the NDA is signed and you have had the discovery call, the next step is to send a project brief to gather detailed requirements before quoting, or send a one-page proposal if the scope is already clear.

After the client accepts your proposal, send a freelance contract to cover payment terms, IP ownership, and liability, and a scope of work to define deliverables and boundaries.

Once the contract is signed, follow the new client onboarding checklist to collect deposits, schedule kickoff, and gather brand assets before work starts.

For ongoing projects, use invoicing best practices from our freelance invoice template examples guide.

SoloPad helps UK freelancers manage contracts, NDAs, proposals, invoicing, and client onboarding — so you spend less time on admin and more time on billable work. Pricing: Starter £5/month, Solo £12/month, Pro £29/month. Try free for 30 days. Questions? info@solopad.io

Sources and references

Research, official guidance, and keyword data used while writing this guide:

1. GOV.UK Intellectual Property Office — Non-disclosure agreements
2. Ubersuggest UK keyword data (location ID 2826, 1 October 2026): "nda template" (720/mo, search difficulty 35), "non disclosure agreement template" (720/mo, SD 30), "nda template uk" (320/mo, SD 23), "non disclosure agreement template uk" (320/mo, SD 19), "confidentiality agreement template" (480/mo, SD 24), "uk non disclosure agreement template" (480/mo, SD 33)

Method note: SERP competitors reviewed (not copied): GOV.UK Intellectual Property Office NDA publication, LawDepot UK, Better Proposals NDA guide, Sprintlaw NDA templates, Practical Law confidentiality agreements, Rocket Lawyer UK, PACT (Producers Alliance for Cinema and Television) NDA guidance. UK freelancer NDA templates with invented studio names (Northline Studio, Oak & Pixel, Maya Cole Consulting) and invented client names (Fusion Financial, Lumen Digital, Horizon Labs), mutual vs one-way decision tree, field checklist, email scripts for sending NDAs before discovery calls and handling pushback, and worked examples for brand consultants, developers, and designers are original SoloPad editorial content.

This article is for general education. It is not legal, tax, or accounting advice. Contract law, confidentiality obligations, and enforceability may vary by business structure, jurisdiction, and specific circumstances. When in doubt, consult a solicitor.