How to Write a Non-Disclosure Agreement

A non-disclosure agreement (NDA) is the quiet workhorse of business relationships. Before you share a product roadmap, a customer list, or the recipe that makes your company yours, an NDA sets the rules for who can see it and what happens if that trust is broken. This guide walks through what a strong NDA actually contains — and where most templates quietly fall short.

What an NDA actually protects

An NDA protects confidential information: anything not publicly known that gives your business an edge. That can be technical (source code, designs), commercial (pricing, suppliers, forecasts), or strategic (unreleased plans). The agreement does not make information secret by itself — it creates a legal obligation to keep it that way.

The core clauses every NDA needs

Skip any of these and the agreement gets weaker fast:

  • Definition of confidential information — specific enough to be enforceable, broad enough to cover what matters.
  • Obligations of the receiving party — how they must store, limit, and protect the information.
  • Exclusions — information already public, independently developed, or lawfully obtained elsewhere.
  • Term and survival — how long the duty lasts, and which parts outlive the agreement itself.
  • Remedies — what the disclosing party can do if the agreement is breached.

Mutual vs. one-way agreements

A one-way (unilateral) NDA protects information flowing in a single direction — typical when you disclose to a contractor or vendor. A mutual NDA protects both sides and is the norm when two companies explore a partnership. Choosing the wrong one is the most common structural mistake we see.

An NDA is only as strong as its weakest definition. Vague language is where confidentiality quietly leaks.

Common mistakes to avoid

  • Leaving the term open-ended or, conversely, too short to matter.
  • Defining confidential information so broadly a court won't enforce it.
  • Forgetting a return-or-destroy clause for materials after the relationship ends.

When to involve a lawyer

For a standard vendor relationship, a well-drafted template is usually enough. For anything cross-border, involving IP assignment, or tied to a financing or acquisition, have counsel review the specific clauses. For related templates, see our freelance contract guide.