You are two or three exchanges into a conversation with a potential partner, investor or contractor, and someone has to decide when the NDA appears. The short answer: whoever is about to disclose something specific sends it, and it should land right before real detail starts moving, not before either side has decided the conversation is worth having. Ask too early and you signal distrust before there is anything to distrust over. Ask too late and the sensitive material is already out, unprotected. This article is about timing and etiquette, not about what the document should say, which our mutual NDA guide and one-way NDA guide already cover.
> Quick answer: Send the NDA once a conversation moves from general interest to specific detail, financials, a product roadmap, customer names, source code, not before. Whoever is about to disclose that detail is the one who should send it, or ask for it. Sending an NDA before an agenda exists can read as overcautious and stall momentum. Waiting until after specifics have already been shared leaves you with nothing to enforce. A gated document link, requiring NDA acceptance before anything opens, collapses this sequencing problem into a single step.
The moment that actually calls for an NDA
Most early conversations do not need an NDA at all. A first call about whether a partnership is worth exploring, an initial pitch meeting, a scoping chat with a contractor, none of these typically involve anything that would hurt you if the other side repeated it. What changes the calculation is the moment either side is about to hand over something specific enough to matter: a financial model, a customer list, a working prototype, an unreleased roadmap, source code, or commercially sensitive pricing. That is the trigger, not the fact of talking to someone new.
Founders and dealmakers who ask for an NDA at the very first point of contact, before there is a defined reason to see anything sensitive, often find the other side hesitates or disengages. It reads as excessive caution or, worse, as a signal that you expect bad faith from someone who has given you no reason to. A request that arrives with no specific document or disclosure attached to it feels like paperwork for its own sake, and paperwork for its own sake is exactly what kills momentum in an early conversation that could otherwise move fast.
Who actually sends it
In a one-way situation, where only one side is going to disclose, for example a company briefing a freelancer or a recruiter, the disclosing party sends the NDA. That is a fairly settled convention: whoever is exposed drafts the protection. In a mutual situation, where both sides expect to exchange something sensitive, either party can raise it, but in practice it is usually whoever asks for the deeper meeting, the data room access, or the specifics that pushes the document forward. If you are the one requesting a look at someone else's numbers, it is reasonable, and often expected, that you propose the NDA rather than waiting to be asked.
There is a soft signal buried in who sends it first. A counterpart who proactively sends a clear, professional NDA at the right moment, rather than after being chased for one, generally reads as more serious and more organised than one who has to be prompted. It is a small tell, but experienced operators on both sides of a table notice it.
Too early, too late, and the narrow window between them
Too early looks like sending a document before either side has said anything specific enough to need protecting. It adds friction to a conversation that has not yet earned any, and it can make a counterparty wonder whether you are the kind of person who over-formalises everything. Too late looks like having already walked through a deck with real numbers, a working demo, or a client list, and only then thinking to ask for a signature. By that point the exposure has already happened. An NDA signed after the disclosure protects nothing that was said before it, which is precisely why courts and negotiators alike treat "we'll sort the paperwork after" as a bad habit rather than a shortcut.
The right window sits between those two failures: raise it at the point where the conversation is clearly about to become specific, usually the moment someone says "let me send over the numbers" or "I'll walk you through the product" or "can we get you into the room." That is the natural cue, and it is concrete enough that both sides recognise it without anyone having to force an awkward pause in the conversation.
Gating a document changes the sequence entirely
The traditional sequence, draft an NDA, email it over, wait for a signature, then separately send the sensitive material, adds real delay and gives both sides a chance to lose momentum waiting on each other. A gated document link removes a step rather than adding one. Instead of sending a Word file and waiting for a signed copy back before you dare attach anything real, you put the sensitive document behind a gate that requires NDA acceptance before it opens at all. The recipient clicks the link, is shown the NDA terms, accepts, and the document opens in the same action. There is no separate signature-then-send sequence to manage, and no window where the file sits in someone's inbox unprotected while you wait for a countersigned copy to come back.
This matters most exactly at the moment described above, where the conversation is about to turn specific and someone needs to see a deck or a data room today, not after a week of chasing signatures. On the Business tier, requiring NDA acceptance before viewing is a standing setting on the room, not a one-off email exchange, so the sequencing question resolves itself automatically every time a new recipient opens the link. Page-by-page analytics then show you whether the recipient actually accepted and read the material, which is useful evidence in its own right, a point our companion piece on NDA enforceability covers in more depth.
What if the other side won't sign
Refusal to sign an NDA at the right moment is itself useful information. A serious counterpart with a genuine interest in continuing rarely objects to protecting specifics that are about to be shared with them, particularly where the NDA is one-way and places no burden on them beyond staying quiet. Persistent refusal at the point where you are about to disclose something real is a reasonable basis to hold back the specific detail until either the NDA is signed or you have decided the relationship does not need it. It is rarely the right move to disclose anyway and hope for the best, since that is exactly the too-late scenario this article has been warning against.
This article assumes an England and Wales NDA and the confidentiality practice that goes with it. If you are dealing with a counterpart elsewhere, the underlying sequencing question, when does the conversation turn specific enough to need protection, and who should propose it, holds regardless of which country's law ends up governing the document itself.
Where an NDA has a fixed term, note the date somewhere that actually reminds you rather than trusting memory. Our guide on keeping every contract in one place covers how to track that alongside everything else you sign.
Frequently asked questions
Should I ask for an NDA before a first call?
Usually not. A first call rarely involves specific enough information to need protecting, and asking too early can feel disproportionate. Wait until the conversation is genuinely about to turn into specifics, a deck, numbers, a demo, and raise the NDA at that point instead.
Who normally drafts and sends the NDA?
Whoever is about to disclose the sensitive material, or whoever is requesting access to someone else's. In a one-way relationship it is almost always the disclosing party. In a mutual relationship it is usually whoever pushes the conversation toward specifics first.
What happens if I share information before the NDA is signed?
Nothing protects that disclosure retroactively. An NDA signed afterwards covers information shared from that point forward, not what was already said. This is exactly why timing matters more than most people assume before their first serious deal conversation.
Is a gated link the same thing as a signed NDA?
Not quite. Gating requires acceptance of NDA terms before a document opens, which functions as agreement to those terms and records that the recipient saw and accepted them. Whether that recorded acceptance operates identically to a wet-ink or e-signed standalone NDA can depend on the specific terms and circumstances, so for higher-stakes disclosures many people still want a properly signed document as well.
Can I refuse to continue a conversation if someone won't sign an NDA?
Yes. There is no obligation to disclose sensitive material to someone who declines reasonable protection for it. A refusal at the point where real detail is about to move is a fair reason to pause and either resolve the disagreement or hold back the specifics.
Draft and gate your NDA in one place
Our guide on drafting a mutual NDA with AI covers building one through AI Legal Drafting from vetted England and Wales clauses, assembled rather than invented so the wording stays traceable, then gate the document you actually send so accepting the NDA and opening the file happen in a single step. Keep the signed copy in the same rooms as the material it was meant to protect, rather than in a separate email thread nobody checks again. The free tier gives three rooms and twenty-five active links, forever, with no card required; the AI drafter and e-signature start on Pro at £19 a month. Start for free and stop treating NDA timing as an afterthought.
This article is general information, not legal advice. Whether a particular disclosure needs protecting, and what terms are appropriate, depends on the facts of your situation and is worth checking with a qualified adviser where real value or risk is involved.
Sources
- Restriction on financial promotion is a separate regime and not relevant here; the governing concept for NDAs is the common law of confidence, remedies for which are addressed in our companion article: Is an NDA Actually Enforceable, and What Would It Cost to Try?
- Electronic signatures, validity and exceptions including deeds, wills, land transfers and lasting powers of attorney: Law Commission, Electronic execution of documents (2019), https://lawcom.gov.uk/project/electronic-execution-of-documents/ ; HM Land Registry Practice Guide 82, https://www.gov.uk/government/publications/electronic-signatures-accepted-by-hm-land-registry-pg82