Mutual vs one-way
Always use mutual for partner conversations. A one-way NDA where only the partner protects information signals that the vendor has nothing to share, which is rarely true and never the message you want to send.
The mutual NDA assumes both parties will share confidential information and that both parties have equivalent obligations. This is more accurate to partnership conversations and removes the asymmetry-of-leverage problem that slows one-way NDAs through legal review.
What every working NDA must contain
- Definition of Confidential Information. Information disclosed in writing and marked confidential, OR disclosed orally and confirmed in writing within 30 days. Avoid the trap of "all information shared" — that is unenforceable and chills conversation.
- Permitted use. Confidential Information may be used only for the purpose of evaluating and pursuing the partnership.
- Standard exclusions. Information that is or becomes public, was independently developed, was lawfully received from a third party, or was already known prior to disclosure.
- Term and survival. Most agreements survive for 2-3 years post-termination. Avoid "perpetual" survival except for trade-secret level information.
- Return or destruction of materials on termination, with a residual knowledge carve-out for general information retained in employee memory.
- Governing law and venue. Aligned with your standard customer agreements.
Clauses to cut
Standard NDAs often include clauses that add friction without protection:
- Non-solicitation of employees. Belongs in a separate agreement if it belongs anywhere. Including it in an NDA scares partners.
- Non-circumvention. Unenforceable in most contexts and signals distrust.
- Liquidated damages. Standard NDAs do not need them; if a breach happens, courts can determine damages.
- Multi-year survival on all information. Use tiered survival: 3 years for general confidential information, indefinite for clearly marked trade secrets.
The residual knowledge carve-out
The most contentious clause in modern NDAs is the residual knowledge clause: a carve-out stating that information retained in the unaided memory of employees after the engagement does not constitute breach. Tech vendors increasingly require this because their engineers see many products and cannot un-learn architecture patterns.
The template includes a standard residual knowledge clause. Some legal teams will refuse to accept it; in those cases, the alternative is a shorter survival period (12-18 months) which has roughly the same practical effect.
Signature workflow that actually closes in 24 hours
The NDA is the first friction point in every partner relationship. The path that gets it signed in a day, not a month: present a 2-page template (the included one), put it in an e-signature tool, do not invite "redlines welcome" — say "we use this standard template for all partner conversations to maintain consistency." Partners who require material redlines on a mutual NDA are signaling they will require material redlines on every subsequent document. That is useful information.