A non-disclosure agreement only does its job if each clause is doing real work. A vague NDA, one that names the parties, says “keep this confidential,” and stops there, is easy to write and hard to enforce, because a court asked to rule on it has almost nothing to interpret: what counted as confidential, for how long, and what happens if the other side ignores it. A properly drafted NDA answers those questions clause by clause, so there is no ambiguity to argue about later. Here is what belongs in each one, in the order you should draft them.
Step 1: Name the Parties and Set the Direction
Start by naming exactly who is bound: full legal names (not “the Company” and “the Contractor” with no entity behind them), and whether the obligation runs one way or both ways. A one-way (unilateral) NDA only restricts the party receiving information, appropriate when you’re the only one disclosing anything, pitching an idea to a potential contractor, sharing a prototype with a manufacturer, or hiring an employee who will see confidential systems but isn’t sharing anything of their own. A mutual NDA binds both sides, needed whenever the relationship is genuinely two-directional, co-founder talks, a partnership where each side reveals its own plans, or vendor evaluations where you’re comparing proposals that include the vendor’s own proprietary process.
Getting the direction wrong in either direction creates a real problem. A one-way NDA in a mutual relationship leaves your own disclosures unprotected. A mutual NDA where only one side is actually sharing anything adds obligations, and negotiating friction, that don’t need to exist.
Step 2: Define What Counts as Confidential Information
This clause carries most of the enforcement weight, so it needs to be specific rather than aspirational. There are two common approaches. A narrow, itemized definition lists exactly what’s covered (a specific document, dataset, or prototype), which is easy to enforce but risks missing something you meant to protect if it isn’t on the list. A broad, catch-all definition covers anything disclosed in connection with the discussion, whether marked confidential or not, which covers more ground but invites disputes over what actually falls inside the scope.
Narrow vs. broad confidentiality definition
| Narrow (itemized) | Broad (catch-all) | |
|---|---|---|
| Covers | Only items specifically listed | Anything disclosed in the relationship |
| Best for | One specific document or dataset | Open-ended, ongoing evaluation |
| Main risk | Unlisted items may slip through | Recipient disputes vague scope |
| Drafting effort | Higher: must enumerate items | Lower upfront, disputes later |
Most NDAs for an ongoing relationship (a co-founder conversation, a vendor evaluation) use the broad definition with a marking requirement waived for anything “reasonably understood to be confidential given the context.” A one-time exchange of a specific document is often cleaner with the narrow, itemized approach.
Step 3: Carve Out What’s Excluded
No confidentiality obligation is absolute, and a court will read exclusions into the agreement even if you don’t write them explicitly, so it’s better to state them. Standard exclusions cover information that was already public before disclosure through no fault of the recipient, information the recipient already knew before signing, information independently developed without reference to what was disclosed, and information the recipient is legally compelled to disclose by a court order or regulator (usually with a requirement to notify the discloser first, so they can object or seek a protective order).
Skipping these carve-outs doesn’t make the NDA stronger. It makes it overbroad, and an overbroad NDA is more likely to get narrowed by a court or ignored by the other side as unenforceable on its face.
Step 4: Set the Term and the Confidentiality Period
Two different clocks run here, and conflating them is a common drafting mistake. The term of the agreement is how long the NDA itself stays active, often tied to the length of a negotiation or evaluation period. The confidentiality period is how long the obligation to protect the information survives after that, and it’s typically longer, many standalone NDAs set a confidentiality period of two to five years past disclosure, regardless of how long the underlying relationship or negotiation actually runs.
For trade secrets specifically, some drafters set the confidentiality period as “indefinite, for as long as the information remains a trade secret,” since trade secret protection under law doesn’t expire on a fixed schedule the way a contractual term might. For anything short of a genuine trade secret, a defined multi-year period is easier for both sides to plan around and easier for a court to enforce than an open-ended promise.
Step 5: Write Remedies That Actually Hold Up
The remedies clause states what happens if the recipient breaches the agreement. Because damages from a leaked trade secret or business plan are often hard to calculate in dollar terms after the fact, most NDAs include language acknowledging that a breach causes “immediate and irreparable harm” and that the discloser is entitled to seek injunctive relief (a court order stopping further disclosure or use) without having to first prove monetary damages. Without that acknowledgment, a court may require you to quantify a dollar loss before granting an injunction, which can take longer than the harm takes to happen.
If the NDA is with an employee or independent contractor rather than another company, there’s a federal requirement that’s easy to miss: the Defend Trade Secrets Act (18 U.S.C. § 1833(b)) requires that any agreement with an employee or contractor governing trade secrets include notice of whistleblower immunity, that the individual can’t be held liable for disclosing a trade secret in confidence to a government official or attorney solely to report a suspected violation of law. Leaving this notice out doesn’t void the NDA, but it does forfeit your ability to recover exemplary damages and attorney’s fees in a federal trade secret misappropriation claim against that person, so it belongs in every NDA signed with an employee or contractor.
Putting the Clauses in Order
Once each clause is drafted, a few structural pieces round out the document: a requirement to return or destroy confidential materials at the end of the relationship, a governing law and venue clause, and a signature block for each party. None of those individually decide whether the NDA holds up, but leaving them out is the kind of gap that turns a routine dispute into an argument about which state’s law even applies.
If you’d rather not draft each clause from a blank page, our NDA generator builds the full agreement, mutual or one-way, from a short set of questions about your relationship, so the definition, exclusions, term, and remedies clauses are populated correctly from the start rather than copied from a template that doesn’t quite fit. If you’re still deciding between a mutual and one-way agreement, see Mutual NDA vs One-Way NDA for how to match the type to your relationship, and NDA vs Confidentiality Clause if you’re not sure a standalone document is even what you need.
