Review a mutual NDA by tracing what each party will disclose, why the recipient needs it, who may access it, and when protection ends. Test definitions, exclusions, permitted use, disclosure permissions, survival, and return provisions together rather than approving clauses in isolation. Record findings against the operative draft, distinguish missing language from missing facts, and assign decision owners. The deliverable is a source-linked checklist supporting a focused redline and a clear recommendation about signature and information sharing while unresolved issues remain.
Use this workflow when commercial counsel or an in-house team receives a mutual NDA before supplier evaluation, technical demonstrations, partnership discussions, or preliminary transaction diligence. Start before sensitive information moves. If disclosure has already occurred, identify the exchange instead of assuming the draft covers it.
The scope is key-term review, not negotiation of the eventual commercial agreement. Evaluate your client as both discloser and recipient, even if one party expects to provide more valuable information. Reciprocal wording does not eliminate differences in information sensitivity or compliance capabilities.
This is a general US-oriented workflow. Contract rights depend on the actual wording, governing law, facts, and deal context. Foreign-law issues, regulated information, and competitor exchanges require separate review where relevant.
Collect these inputs before approving substantive terms:
Ask the sponsor to identify the most damaging plausible misuse. Also establish whether the exchange includes personal data, third-party confidential material, or information the client may not be entitled to share. Record those questions without expanding the NDA into a substitute for necessary permissions or separate agreements.
Copy the Non-Disclosure Agreements — Contract review checklist into your working document or spreadsheet. Use one row per issue, including material terms accepted after review.
| ID | Term | Source | Evidence or gap | Two-way effect | Priority | Action / reason | Owner / status |
|---|---|---|---|---|---|---|---|
In Source, record the document ID, version, clause, and page where available. For missing language, identify the provisions checked and write “not present”; do not invent a citation. In Evidence or gap, separate the draft's wording from facts awaiting confirmation.
Two-way effect captures discloser protection and recipient burden. Define Priority by consequence: blocks planned disclosure, requires approval before signature, or drafting cleanup. Action / reason states the proposed change and rationale. Owner / status identifies the decision-maker, disposition, and any required response date.
Keep rows tied to a named draft. When numbering changes, update citations. Cross-reference related rows—for example, a residuals finding and its permitted-use finding—so approval of one does not obscure the other.
Check legal entities, signature blocks, affiliate definitions, and effective date against the disclosure plan. Distinguish affiliates whose information is protected from affiliates permitted to receive it. Check how any existing NDA interacts with the new draft, especially an entire-agreement or supersession clause.
Replace a vague business-opportunities purpose with the actual evaluation activity. Determine whether technical testing falls within it or requires separate permission. Identify earlier exchanges and decide whether express retrospective coverage is needed.
Record party mismatches, purpose ambiguities, and date gaps separately. The output is a proposed purpose and an identified list of disclosures whose coverage remains uncertain.
Walk through a marked deck, oral demonstration, unmarked spreadsheet, prototype, and notes derived from them. Check whether each satisfies the definition, marking requirements, and any written-confirmation deadline.
Review exclusions for public information, prior knowledge, independent development, and lawful third-party receipt. Check that public availability resulting from a recipient's breach does not become an exclusion. Decide what evidence should substantiate an exclusion without imposing impractical recordkeeping.
Do not equate contractual confidentiality with trade-secret status. Federal law requires reasonable secrecy measures and qualifying independent economic value; an NDA label alone does not establish those elements. See 18 U.S.C. § 1839(3). (govinfo.gov)
Record covered categories, failed formalities, and outstanding facts. The output is targeted definition language, not indiscriminate expansion.
Check for an express purpose-limited use obligation, not merely confidentiality. Search the entire draft for residual knowledge, product development, feedback rights, testing, and reverse engineering permissions.
Treat residuals as a substantive permission requiring reconciliation with restricted use. A filed mutual NDA illustrates the distinction: section 7 permits competing development without using protected information, while section 8 separately addresses narrowly construed residuals. This is negotiated wording, not a market benchmark. See the SEC-filed mutual NDA, §§ 7–8. (sec.gov)
For prototypes, decide expressly whether reverse engineering should be restricted. The federal definition of improper means excludes reverse engineering and independent derivation; that exclusion does not itself settle the effect or enforceability of a separate contractual restriction. See 18 U.S.C. § 1839(6). (govinfo.gov)
Record each permission beside the restriction it qualifies. The output is an approved use boundary or an assigned escalation.
Compare permitted recipients with actual access needs. Check need-to-know limits, confidentiality obligations, and responsibility for representatives. Do not accept an identical-signed-NDA requirement without confirming how employees and professional advisers are bound.
Review the protection standard and misuse-notification obligation. Consider whether a same-care-as-own-information standard needs an independent minimum, and whether the team can perform promised safeguards and reporting.
Search for special permissions elsewhere. Section 9 of the filed example permits specified diligence findings to reach purchasing personnel, illustrating why the general recipient clause is not the whole review. See the SEC-filed mutual NDA, § 9. (sec.gov)
For compelled disclosure, examine notice where legally permitted, disclosure limits, cooperation, and costs. Flag protected reporting and regulator-contact restrictions for applicable-law review; a subpoena exception is not a substitute for that analysis.
Record recipient-access decisions, safeguards, and unresolved exceptions in separate rows.
Distinguish the period during which disclosures are covered from the period during which obligations survive. Identify whether survival runs from disclosure, termination, or a fixed date. Test the wording against the expected first and last exchanges.
Consider separate treatment for trade secrets based on sensitivity, useful life, and governing-law analysis—not an asserted standard duration. Check whether retained information remains subject to both confidentiality and restricted use.
Test return and destruction against notes, derived analyses, email, backups, legal holds, and regulatory retention. Narrow any retention exception to identified needs; it should not silently authorize business use. Review certification language against what the certifier can verify.
Record the trigger, proposed duration, retained-copy treatment, and operational confirmation needed. The output is a coherent protection timeline and a performable deletion obligation.
Identify governing law, forum, arbitration, emergency relief, liability limitations, indemnities, and fees. Check whether another agreement limits or otherwise affects confidentiality remedies.
Escalate language purporting to make injunctive relief automatic. The Federal Rules of Civil Procedure govern proceedings in US district courts, not state courts or arbitration; review the applicable forum's requirements separately rather than treating contractual wording as sufficient. See the US Courts' Federal Rules of Civil Procedure. (uscourts.gov)
Check non-solicitation, exclusivity, standstill, publicity, intellectual-property licenses, information warranties, and obligations to proceed. Identify disclaimers that reach beyond information accuracy and potentially affect liability for an NDA breach.
Record each substantive additional restriction or disclaimer with its commercial rationale and authorized approver. The output is a focused escalation list, not an assumed enforceability conclusion.
Reopen every cited provision in the operative draft. Test edits against definitions, exceptions, cross-references, and survival. Confirm that a revision helping your client as discloser does not create an unacceptable recipient obligation.
Separate text problems from factual questions. Unknown backup capability requires operational confirmation; unrestricted residuals require a drafting decision. Neither should disappear into a generic approved status.
Record each disposition: accepted, revised, escalated, or awaiting facts. The output is the redline, completed checklist, and a short decision distinguishing permission to sign from permission to share particular information. State which unresolved matters block either decision.
Fictional scenario: Bracken Circuit LLC and Merefield Robotics Inc. are evaluating a joint sensor demonstration. Bracken will disclose calibration methods; Merefield will provide component pricing. All parties, documents, and terms in this example are fictional.
Draft D01 v3 limits use to evaluation. Section 1 requires written confirmation of oral disclosures; section 9 covers disclosures from its stated effective date. Section 6 permits unrestricted use of remembered information. Section 7 requires every copy to be deleted within five days of request, without a retention exception.
Sponsor email E01 confirms an earlier oral calibration demonstration. The packet contains no written confidentiality confirmation. IT has not confirmed selective backup deletion. These gaps do not establish that other protection is absent or deletion impossible.
| ID | Term | Source | Evidence or gap | Two-way effect | Priority | Action / reason | Owner / status |
|---|---|---|---|---|---|---|---|
| R1 | Earlier oral disclosure | D01 v3 §§ 1, 9; E01 | Earlier demo confirmed; written confirmation not supplied | Bracken needs coverage; Merefield needs identifiable scope | Blocks further calibration sharing | Identify demo and request express coverage; present packet does not establish NDA coverage | Commercial counsel / open |
| R2 | Residuals | D01 v3 §§ 2, 6 | Evaluation limit qualified by unrestricted remembered-information use | Methods and pricing both exposed | Blocks sensitive sharing | Delete broad permission; preserve independent development without use of protected information | Both legal leads / revision requested |
| R3 | Destruction | D01 v3 § 7 | Five-day all-copy deletion; backup capability unknown | Both face unverified compliance burden | Before signature | Obtain IT facts; propose narrow retention exception with continuing restrictions | IT and counsel / awaiting facts |
The decision is not simply to extend duration. R1 requires treatment of an identified earlier event and missing confirmation. R2 changes permitted use. R3 requires evidence before final drafting. Counsel recommends withholding additional calibration details until R1 and R2 are resolved, and sensitive pricing until R2 is resolved. Signature approval remains conditional on an acceptable destruction obligation.
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review in Word lets counsel select the represented party or neither and provide deal-specific instructions. Findings quote and locate clauses, rank severity, and flag missing language as not present. Counsel can edit and insert suggestions as ordinary tracked changes under the signed-in Word user's name, or dismiss findings with reasons. Verify findings and keep approval decisions in the working checklist. To assess this mutual-NDA workflow, book a demo. (decover.ai)
Begin with reciprocity, then test actual disclosures and compliance capabilities. Record justified differences so the approver understands why nominal symmetry does not resolve the risk.
Identify information, recipients, dates, and existing restrictions. Consider express coverage and required confirmations; do not describe the draft as curing an earlier gap without reviewing agreed wording.
Treat acceptance as a business and legal decision. Identify what could be remembered, how permission qualifies restricted use, and whether sensitive disclosures require deletion of the permission or separate handling.
Provide the completed checklist, assigned factual questions, and a disclosure recommendation. Explain which issue blocks signature or sharing and whose decision or confirmation is required.
This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.