NDAs Explained for Non-Lawyers
General information only, not legal advice. Laws differ by country and situation; consult a qualified lawyer for advice about your specific circumstances.
You’re about to tell a potential partner your business idea. Or share your client list with a contractor. Or show a supplier your product designs. And someone says “we should sign an NDA first.” You nod, and quietly wonder what you’re actually signing.
A non-disclosure agreement (NDA) is one of the most common business documents in existence, and one of the least understood. This guide explains what NDAs do, when you need one, what the key terms mean in plain English, and the mistakes that make them useless.
Why This Matters
Ideas are shared before they’re protected. Business happens through conversations: pitching to partners, briefing contractors, exploring deals. In each conversation you reveal something valuable, plans, numbers, methods, contacts. An NDA sets the ground rule before you speak: what’s shared here stays here.
Without one, you have little recourse. If someone uses your confidential information after you’ve shared it freely, your options are limited and expensive. With a signed NDA, you have a clear, written commitment, which usually prevents the misuse in the first place. Most NDA value is deterrent, not legal action.
They’re expected. In many industries, refusing to sign a reasonable NDA, or having none of your own, looks unprofessional. Having a standard NDA ready signals that you take your business (and others’ information) seriously. It speeds up deals instead of slowing them down.
They protect both sides. The best NDAs are mutual: both parties’ information is protected. When you’re sharing with a potential partner who’ll also share with you, mutual protection builds the trust the relationship needs.
Key Concepts
What an NDA actually is. A contract in which one or both parties agree to keep certain shared information confidential and not to use it except for an agreed purpose. That’s it. It doesn’t transfer ownership, create a partnership, or guarantee a deal, it just governs how shared information is handled.
Confidential information, defined. The NDA must say what counts as confidential. Good definitions are specific: business plans, financial data, client lists, product designs, technical methods. Vague definitions (“all information shared”) are weaker, if everything is confidential, arguably nothing is. Some NDAs require confidential information to be marked as such; know whether yours does.
One-way vs mutual. A one-way NDA protects one party’s information (you’re pitching to an investor). A mutual NDA protects both sides (you’re exploring a partnership). Use mutual as the default unless there’s a clear reason not to, it’s fairer and gets signed faster.
The purpose clause. The NDA should state why information is being shared, “to evaluate a potential partnership,” for example, and limit use of the information to that purpose. This stops the recipient from using your information for their own competing project while technically “keeping it confidential.”
Exclusions. Standard NDAs exclude information that was already public, already known to the recipient, independently developed, or received from someone else legitimately. These exclusions are normal and fair, an NDA can’t make public facts secret.
Duration. Two timeframes matter: how long the duty to keep information confidential lasts (often 2–5 years, sometimes longer for genuinely sensitive material like trade secrets), and how long the agreement itself covers disclosures. Make sure both are stated.
What happens on breach. The NDA should say what remedies apply, typically the right to seek a court order stopping further disclosure, plus damages. You don’t need to understand the legal mechanics deeply, but the clause should exist. An NDA with no consequences is a polite request.
Practical Steps
1. Have a standard mutual NDA ready. Don’t draft one from scratch each time. Prepare a simple, balanced mutual NDA template, have it reviewed by a lawyer once, and keep it ready to send. Speed matters, deals stall when “we need to sort out the NDA” takes two weeks.
2. Sign before sharing, not after. The NDA must be signed before the confidential information changes hands. Sharing first and signing later leaves the early disclosures unprotected. Make it step one of the conversation, not an afterthought.
3. Be specific about what’s confidential. When you share particularly sensitive material under the NDA, note what it is, mark documents confidential, or follow up an unmarked conversation with an email listing what was disclosed. Specificity strengthens protection.
4. Read NDAs you’re asked to sign. When someone sends you their NDA, read the whole thing before signing. Check: is it mutual or one-way? What counts as confidential? How long does the obligation last? Are the exclusions reasonable? Is there anything unusually broad, like a non-compete hidden inside? Never sign what you haven’t read.
5. Keep signed copies filed. Every signed NDA goes in your records with the date, the parties, and what it covered. If a question ever arises about what was shared with whom, the file answers it.
6. Brief your team. An NDA signed by you doesn’t help if your employee then posts the details in a public forum. Anyone who’ll handle the confidential information should know it exists and what it covers. For key situations, individual confidentiality acknowledgements add a layer.
7. Know when you need more than an NDA. An NDA protects information; it doesn’t protect inventions (that’s patents), brands (that’s trademarks), or creative work (that’s copyright). And for truly critical trade secrets, an NDAs one layer among several, access controls, need-to-know sharing, and proper security matter as much as the paper.
Common Mistakes
Sharing before signing. The single most common NDA failure. The conversation happens, the information is out, and the NDA signed afterwards can’t retroactively protect what was already disclosed.
Signing without reading. Especially when the other party is bigger or the deal feels urgent. Buried terms, overbroad definitions, excessive durations, hidden non-competes, only surface when it’s too late. Read every NDA, every time.
Overbroad definitions. Defining “everything we discuss” as confidential makes the NDA hard to enforce and annoying to live under. Specific definitions protect what matters and get signed without argument.
No time limit, or an absurd one. A perpetual confidentiality obligation for ordinary business information is unreasonable and often unenforceable; no meaningful duration at all leaves you exposed. Match the duration to the sensitivity.
Using an NDA as a substitute for trust. An NDA with someone you fundamentally distrust is weak protection, enforcement is slow and expensive. Use NDAs with people you’ve vetted, as one layer among several.
Forgetting the NDA exists. Signing it, filing it, and then sharing the protected information freely, with staff who don’t know, in public settings, in unsecured channels. The agreement only works if behaviour matches it.
Using a template from another country unchanged. NDA enforceability and norms vary by jurisdiction. A template drafted for another country’s law may include terms that don’t work where you are. Have your standard NDA reviewed for your jurisdiction.
Relevant Templates
- Non-Disclosure Agreement Template, a balanced mutual NDA covering definitions, purpose, exclusions, duration, and remedies.
- Confidentiality Acknowledgement Form, individual acknowledgements for team members handling protected information.
- Data Processing Record Sheet, where the confidential information includes personal data, record how it’s processed.
- General Disclaimer Template, set expectations alongside your NDA where you’re sharing materials more broadly.
This article is general information, not legal advice. Consult a qualified lawyer about your specific situation and jurisdiction.