How to compare provisions across a contract portfolio for Non-Disclosure Agreements

Compare mutual NDAs by clause function, not by matching headings or counting wording differences. Establish the operative document set, group agreements with comparable purposes, and extract provisions with their source locations and qualifications. Assess each party’s position as both discloser and recipient against your organization’s approved instructions and proposed activity. The deliverable is a source-linked comparison matrix that distinguishes substantive differences from evidence gaps, explains practical exposure, and assigns decisions about access restrictions, amendments, or further review.

When to use this workflow

Use this workflow when commercial counsel or an in-house team needs to determine whether existing mutual NDAs support a proposed activity: opening diligence rooms, expanding technical collaborations, involving affiliates, or sharing additional categories of information.

The scope is portfolio comparison, not complete renegotiation or an obligation-monitoring program. Separate company-to-company mutual NDAs from employee confidentiality agreements and one-way undertakings. Group acquisition-evaluation agreements separately from product-testing agreements when their purposes and information flows differ.

This guide uses a US transactional orientation. Contract rights depend on actual wording, governing law, facts, and deal context; state-law enforceability and cross-border questions require separate analysis. Mutual drafting does not establish equal practical exposure: one party may disclose source code while receiving only pricing information.

What you need

Collect executed agreements, amendments, schedules, incorporated documents, and relevant termination or release notices. Keep drafts separately, and preserve originals alongside searchable copies. Identify the final approved draft if execution-version verification is part of the assignment.

Obtain a short business description for each relationship covering:

• The proposed activity, expected disclosures, and information sensitivity in each direction.
• Intended recipients, including affiliates, advisers, contractors, and financing sources.
• Storage arrangements, backup practices, and who could return or destroy information.
• Known disclosure dates, termination events, destruction requests, and evidence of prior possession or independent development.

Also obtain the team’s negotiation checklist and review instructions, including version, preferred positions, fallbacks, and escalation owners. This is an internal baseline, not evidence of market practice. If none exists, have counsel approve comparison criteria before reviewers characterize provisions as acceptable or deficient.

Use the template

Use Non-Disclosure Agreements — Contract comparison matrix. You can copy this table into your working document or spreadsheet. Create one row per agreement and clause function; split rows when different directions, triggers, or exceptions produce different results.

Assign stable row IDs, such as NDA-014-R03, rather than relying on spreadsheet row numbers. “Record / cohort” identifies the document, operative version, governing law, and comparison group. “Clause / source” gives section and page references, including amendments.

“Evidence / status” contains material wording or a precise source-linked summary, verification status, and confidence. Distinguish verified, ambiguous, not present after review, unreadable, and unavailable. “Function / direction” identifies the concept, obligated party, and beneficiary.

Capture the trigger, action, and timing without converting qualitative deadlines into invented dates. Preserve exceptions and cross-references. The final fields identify the baseline version, consequences for both sides, disposition, owner, and unresolved dependency. Split crowded cells into additional rows rather than dropping qualifications.

Step by step

1. Establish the operative set and comparison groups

Assign document IDs and determine whether each available copy is executed, amended, superseded, or a draft. Check signatures, dates, schedules, and incorporated material. Where available, compare the execution copy with the approved draft, including attachments; text extraction alone is not complete verification.

Group agreements by transaction purpose and governing law, then distinguish technical disclosures, financing participation, or other material differences. An acquisition-evaluation purpose should not be treated as equivalent to permission for product development.

Record: identity, version, cohort, execution status, and missing components, with an owner for obtaining them. Do not describe an incomplete document set as fully verified.

2. Define clause functions and two-direction tests

Use a consistent sequence: protected information; exclusions; permitted purpose; recipients; protection duties; compelled disclosure; protected reporting; term and survival; return or destruction; residuals; and additional restrictions or remedies.

For each function, test your organization as discloser and recipient. A broad definition may protect its prototypes but burden receipt of routine communications. A narrow representative definition may prevent either party from using its intended testing affiliate.

Give standstills, non-solicitation provisions, reverse-engineering restrictions, and IP-related terms separate rows when present. They should not disappear into a general confidentiality score.

Record: function, direction, baseline instruction, and the business question the comparison must answer.

3. Extract wording with its dependencies

Capture definitions, operative language, exceptions, and incorporated references together. Check marking requirements, oral or visual disclosures, and recipient-created analyses rather than assuming they receive identical treatment.

The historical SAP–SuccessFactors agreement addresses oral and visual disclosures and recipient analyses in § 2, with representative controls in § 3. These are examples of drafting choices, not presumed terms of other NDAs (filed agreement, §§ 2–3).

Distinguish “not present after review” from “not found in extraction.” A missing schedule is an evidence gap, not proof that a qualification is absent.

Record: wording or precise summary, clause/page citation, linked definitions, evidence status, and confidence. Require source inspection before closing low-confidence findings.

4. Normalize function without erasing qualifications

Use consistent comparison terms while retaining wording that changes the result. For exclusions, distinguish prior possession from unrestricted prior possession. Capture any proof requirement for independent development or third-party receipt; do not import one from another agreement. Identify the records needed to test the exclusion.

Keep disclosure windows, agreement terms, early termination, and surviving duties separate. SAP–Sybase § 18 separates its one-year agreement term and written early-termination mechanism from identified surviving provisions; this illustrates structure, not a default duration (filed agreement, § 18).

Record: normalized function beside the actual trigger, duration, qualification, and dependency. Preserve “promptly” as written and capture applicable notice mechanics rather than inventing a day count.

5. Test actual information flows and operational constraints

Map each intended recipient category against authorization, need-to-know conditions, downstream duties, and responsibility for breaches. Check workspace membership and permissions. Permission to share with one counterparty does not establish permission to expose its information to another counterparty.

Test return and destruction against email, backups, derived analyses, representative copies, and retention constraints. Identify who could substantiate a certification. SAP–SuccessFactors §§ 6 and 9 contain specific residual-memory permissions and qualified return, destruction, and retention provisions; read permissions with their conditions rather than treating them as blanket rights (filed agreement, §§ 6 and 9).

Record: operational mismatch, affected direction, supporting facts, uncertainty, and proposed response. Have operational owners verify capabilities independently of contract wording.

6. Separate legal questions from commercial deviations

Set priority using sensitivity, disclosure likelihood, operational feasibility, and consequences. Explain the result in each direction. A departure from preferred wording is not automatically a legal defect.

Separate contractual confidentiality coverage from statutory trade-secret status. Federal law requires reasonable secrecy measures and qualifying independent economic value attributable to secrecy; an NDA label alone does not establish those elements (18 U.S.C. § 1839(3), official 2024 edition).

Review compelled-disclosure notice separately from voluntary protected reporting. SEC guidance explains Rule 21F-17(a)’s prohibition on impeding individuals’ direct communications with SEC staff about possible securities-law violations, including outside employment. Its staff FAQs identify potentially conflicting notification provisions. Check approval, notice, and cooperation language together; this is not a universal disclosure exception (SEC Whistleblower Protections).

Record: commercial preference or legal uncertainty, priority rationale, and responsible counsel.

7. Reconcile comparisons and assign dispositions

Review comparable rows together, then return to the documents before finding equivalence. Identical destruction wording may operate differently because another provision permits retained copies. Confirm that proposed redlines preserve defined terms and cross-references.

Assign a disposition: accept for the specified activity, restrict disclosures, seek permission, propose amendment, or obtain evidence. Keep proposed changes separate from operative rights. Summarize recurring portfolio issues only after confirming shared qualifications, and state the reviewed population behind any counts.

Record: decision, rationale, owner, and prerequisites. Deliver the matrix with an agreement-level summary linked to detailed rows; do not conceal open issues inside an aggregate score.

Worked example

Entirely fictional scenario. Alder Circuit Labs plans separate prototype evaluations with Brindle Instruments, Cairn Testing, and Dovetail Systems under mutual NDAs. Alder will disclose designs and receive testing methods. Procurement proposes one workspace for all three relationships, accessible to Alder’s testing affiliate. Counsel’s internal baseline requires express affiliate access and storage-compatible destruction duties.

The parties, documents, excerpts, and business facts below are fictional. The completed rows are representative, not a complete review.

Counsel rejects the common workspace design pending recipient and access review. Separate relationship workspaces prevent the design itself from exposing one counterparty’s material to the others; individual permissions still require verification.

F-01 supports withholding affiliate access pending permission. F-02 remains unresolved because the missing schedule may qualify destruction; its contents cannot be assumed. F-03 requires disclosure-date evidence and separate treatment of disclosures outside the agreed window. None of these entries establishes that an entire agreement is acceptable.

Common mistakes

• Comparing headings instead of duties. Read definitions and linked provisions before finding equivalence.
• Recording one expiry date. Separate disclosure windows, termination, and surviving event-based duties.
• Treating mutual language as practical symmetry. Test information sensitivity, recipients, and performance capabilities in both directions.
• Flattening exceptions into yes/no fields. Preserve residuals conditions, retained-copy restrictions, and exclusion proof requirements.
• Treating missing evidence as missing protection. Assign source collection separately from substantive review.
• Treating separate NDAs as permission for shared access. Verify each information owner’s authorized recipients before combining workspaces.

Final quality check

• Each agreement has a stable ID, version, governing law, and execution status.
• Findings trace to inspected wording, including relevant amendments and definitions.
• Comparisons preserve direction, trigger, timing, exception, and notice mechanics.
• “Not present” findings follow review of the complete relevant document set.
• Recipient access and destruction duties have been tested against the proposed activity.
• Priority explanations distinguish commercial preference from legal uncertainty.
• Open issues have owners and explicit decision dependencies.
• Summaries link to detailed rows; proposed amendments are not described as effective terms.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its transactional capabilities include tabular review across multiple documents. Contract review can support examination of individual provisions before counsel approves comparison findings. The matrix and negotiation checklist remain the team’s work products; source verification, operational validation, and legal decisions remain with reviewers. To discuss applying this workflow to your NDA portfolio, book a demo.

Frequently asked questions

Should each NDA occupy one row?

Not in the detailed matrix. Use one row per agreement and clause function, adding directional or exception-specific rows when needed. An agreement-level summary should link to those findings rather than replace them.

Can different governing laws appear in one matrix?

Yes, provided governing law remains visible and cohorts are identified. Compare wording across groups, but reserve enforceability and remedies conclusions for jurisdiction-specific analysis. Similar text does not establish identical legal effect.

How should we compare silent provisions?

Check definitions, schedules, and amendments first. If the complete reviewed set contains no provision, record “not present” and the resulting decision question. Do not import another NDA’s permission or your preferred wording. Mark incomplete sets as unresolved instead.

Does every deviation require renegotiation?

No. A recipient restriction may be managed through access controls; an incompatible destruction duty may require amendment before further receipt. Record the approved activity, assumptions, and limits so the disposition is not mistaken for approval of unrelated future uses.

Sources

• 18 U.S.C. § 1839, official 2024 Code edition: federal trade-secret definition.
• SEC Whistleblower Protections: Rule 21F-17 discussion and staff reporting guidance.
• SAP–Sybase mutual NDA: example-specific term and survival structure.
• SAP–SuccessFactors mutual NDA: example-specific coverage, recipients, residuals, and retention provisions.

Scope: General professional workflow guidance dated October 13, 2026, not advice for a particular matter. The statutory source is the official 2024 edition, not certification of a complete intervening-law update. Historical agreements illustrate wording, not market standards.

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.