Review guide

NDA Review Checklist: What to Check Before You Sign

An NDA looks short until it is enforced. Read the definition, the permitted use, and the exit obligations together, because that is where most disputes actually start.

Gemma4.net review library Updated 2026-11-13 中文版

Identify the purpose before the paper

Start with why information is being exchanged. A vendor evaluation, a potential acquisition, a joint bid, and a hiring conversation need different scopes, and a template written for one purpose often fits another badly. Write the purpose in one sentence and check that the agreement’s permitted-use clause matches it. If the clause is narrower than the discussion you plan to have, the discussion itself may breach the agreement.

Identify the parties precisely. A mutual NDA signed by a parent company does not automatically bind the subsidiary that will receive the files, and a one-way NDA signed by the wrong direction creates an obligation where none was intended. Check the legal names, the registration details where given, and the signatories’ authority.

Check an NDA draft against eight common points

Mark what the draft already covers and see what is still open, with the questions worth asking before signature. The draft itself stays in your browser.

Read the definition of confidential information

The definition does the real work. A broad definition covers anything disclosed in connection with the purpose, whether or not it is marked. A narrow definition may require written marking, identification within a set number of days for oral disclosures, or a specific schedule. If the definition is narrow, your operational process has to match it: label documents, confirm oral disclosures in writing, and keep a schedule.

Read the exclusions as carefully as the definition. Information already public, independently developed, received from a third party without duty, or known before disclosure is normally excluded. The burden of proving an exclusion usually falls on the recipient, so keep the evidence that supports it: prior versions, third-party sources, development records.

Watch for definitions that pull in “derived” or “summarised” information without limit. Derivations are often the most commercially sensitive output of a discussion, and a definition that silently excludes them may leave your analysis unprotected.

Check permitted use and permitted disclosure

Permitted use should be limited to evaluating or performing the stated purpose, and it should allow the internal work the purpose requires. A clause that permits disclosure only to directors, for example, may not cover the engineers who need to assess the integration. List the roles that will actually see the information, then check the clause against that list.

Disclosure to advisers, affiliates, and subcontractors is usually permitted if they are bound by equivalent obligations and the discloser remains responsible. Confirm that the clause covers the categories you use, and that the “need to know” standard is workable in practice. A clause that requires prior written consent for every affiliate disclosure will be breached in the first week.

Compelled disclosure needs a carve-out that permits disclosure required by law or a regulator, ideally with notice to the other party where lawful. Without it, a routine regulatory request puts the recipient in an impossible position.

Term, survival, and the scope of the obligation

Check when the obligation starts, how long it lasts, and what happens to information received near the end of the term. A three-year term that runs from the date of disclosure is different from a term that runs from signature. Trade secrets are often carved out of the time limit and protected for as long as they remain secret, which is a different obligation in practice.

Look for obligations that continue after termination: return or destruction, surviving confidentiality, and any non-solicit or standstill. These are the clauses that generate disputes months after the project ends, because the operational team has moved on and the obligation has not.

Return, destruction, and residual knowledge

A return-or-destruction clause should cover copies, including those held in backup systems, email archives, and by advisers. In practice, complete deletion is often technically impossible within backup cycles, so the clause should allow retention required by law or by documented backup policy, with continued confidentiality. If the clause demands immediate certified destruction of all copies, confirm your systems can deliver it before signing.

Residual-knowledge clauses allow the recipient to use information retained in the unaided memory of personnel. They are common in technology agreements and unpopular with disclosers. Read one against the definition of confidential information: if residuals are permitted broadly, the definition’s protection is thinner than it looks. Decide whether you are comfortable, and if the clause is unavoidable, narrow it to general knowledge rather than specific documents.

Remedies, liability, and governing law

Confidentiality breaches are hard to value, so NDAs often include injunctive relief and acknowledge that damages may be inadequate. Check whether the agreement limits liability, and whether that limit applies to confidentiality breaches. A cap that covers breach of confidentiality can make the obligation largely symbolic for a well-resourced counterparty.

Governing law and venue decide where a dispute is fought and which rules apply. For cross-border discussions, check whether the chosen law is workable for both sides and whether the dispute clause includes a practical escalation step. Also check the language of the agreement and of any dispute; a translated version can differ from the signed original.

Practical points before signature

Confirm who will actually receive the information, how it will be stored, and when it will be deleted. An NDA is only as good as the handling process behind it. If the team plans to use a shared drive with open access, or to paste excerpts into a public tool, the agreement does not describe the real workflow.

Check the signature block and the entity, keep a copy of the executed version, and record the key dates in the same place as the project record. When the discussion ends, the return-or-destruction obligation becomes live, and someone has to own it.

Boilerplate that quietly changes the deal

NDAs often carry clauses that have nothing to do with confidentiality: non-solicitation of employees, a standstill on acquiring securities, exclusivity on discussions, or a requirement to return all materials on request. These are substantive obligations, and they are easy to accept because the document is short and the label says confidentiality.

Read those clauses against the purpose. A non-solicit that runs for twelve months after the discussion can constrain hiring in a small market. A standstill can limit an investment strategy. An exclusivity clause can prevent parallel conversations with other counterparties. If the discussion is exploratory, these obligations usually belong in a separate agreement or should be removed.

Check the variation and entire-agreement clauses as well. If the NDA says it is the entire agreement, an email promising a narrower scope will not change it. If the variation clause requires a signed writing, an account manager’s confirmation is not enough. These details decide whether the paper matches the commercial understanding.

When an NDA is not the right document

If the discussion involves personal data, a confidentiality agreement alone is usually not enough; you may need a data processing or data sharing arrangement that describes roles, purposes, and retention. If the discussion involves a potential transaction, the NDA is one document in a wider set that includes standstill, exclusivity, and process terms. And if the other side refuses any written confidentiality obligation, that refusal is itself information about how the discussion will go.

This checklist is educational. Enforceability and required terms depend on the governing law and the facts, so have qualified counsel review anything material before signature.

Next step

Scope a private review by email

Send the matter, file volume, formats, deadline, and decision question. A person confirms fit, handling, and timing before files move.