How to build a clause extraction table for Non-Disclosure Agreements

Build an NDA clause extraction table by identifying the controlling document, separating operative rules from their exceptions, and recording source-linked wording alongside consistent summaries. For a mutual NDA, test every row in both directions: each party can be a discloser and a recipient, but their information and operating constraints may differ. The deliverable is a verified table showing coverage, permitted uses, recipient controls, timing, and unresolved decisions—not merely clause headings. Keep contractual wording, reviewer interpretation, and proposed changes distinguishable throughout.

When to use this workflow

Use this workflow when commercial counsel or an in-house contracts team needs to compare a mutual NDA against its negotiating checklist, prepare an obligation handoff, or review several NDAs without losing their qualifications. Concrete triggers include technical evaluations, joint product discussions, acquisition assessments, and diligence requests involving confidential exchanges.

Extraction supports approval; it does not establish enforceability. This guide uses a US transactional orientation. Contract rights depend on the actual language, governing law, facts, and deal context. Address material state-law and cross-border questions separately.

What you need

Collect the complete NDA, attachments, amendments, incorporated documents, signature pages, and available version history. Identify whether the assignment concerns a proposed draft, an executed agreement, or differences between them.

Obtain these business inputs:

• The proposed purpose, information exchanged in each direction, and expected disclosure dates.
• Participating entities and recipients, including affiliates, advisers, contractors, and financing sources.
• Disclosure channels, storage locations, and practical limits on retrieving or deleting copies.
• Sensitive information each party expects to disclose, including demonstrations and recipient-created analyses.
• The organization’s negotiating checklist, fallback positions, and escalation owners.

Record the checklist version. It is the team’s work product, not an assumed saved-playbook software feature. Without the business inputs, extraction can identify wording but cannot reliably assess whether it fits the proposed exchange.

Use the template

Non-Disclosure Agreements — Clause extraction table

Copy this table into your working document or spreadsheet. Use one row per operative rule; link additional rows when exceptions or timing provisions need separate treatment.

Use stable row IDs, such as R01, and version-specific document IDs, such as NDA-01-v3. In Source / text, preserve exact operative wording with section and page references. Link qualifications elsewhere rather than quoting a duty without its exception.

Duty / benefit identifies the obligated and protected parties. Trigger / action separates the activating event from the response. Limits / timing captures exceptions, deadlines, duration, and dependencies.

In Status / concern, distinguish verified text, ambiguity, unreadable material, unreviewed material, and language not present after complete review. Record extraction confidence separately from risk. Decision / owner identifies the next action, responsible person, and relevant checklist deviation. Expand grouped fields into separate columns when needed without discarding these distinctions.

Step by step

1. Establish the source and extraction boundaries

Assign a document ID, version, and status before extracting clauses. Check the file against the intended review copy, including schedules and amendments. Identify missing pages or incorporated documents immediately; do not assume their contents.

Define whether the assignment covers confidentiality obligations alone or every restriction in the NDA. Check expressly for residuals permissions, standstills, IP restrictions, remedies, and governing-law provisions rather than allowing the document title to determine scope.

Record: a control row identifying the source, completeness, scope, checklist version, and reviewer. Preserve originals and link later corrections to the relevant version.

2. Map mutual roles and information coverage

Identify the parties and defined disclosers, recipients, affiliates, and representatives. Extract coverage for marked documents, oral disclosures, visual demonstrations, prior disclosures, and recipient-created analyses. Check whether confirmation or marking requirements condition protection.

The SAP–SuccessFactors NDA, § 2 illustrates express treatment of oral and visual identification and recipient-created material. These are drafting choices, not terms to import into another agreement.

Keep contractual confidential information distinct from statutory trade secrets. Federal trade-secret status requires reasonable secrecy measures and qualifying independent economic value; an NDA label alone does not establish those elements (18 U.S.C. § 1839(3)).

Record: coverage rows, applicable roles, and gaps between the definition and each party’s planned disclosures.

3. Extract permitted use and recipient controls

Read the purpose definition together with use restrictions and the standard of care. Preserve whether use is limited to evaluation, negotiation, implementation, or another specified activity. Do not normalize a narrow evaluation purpose into “business purposes.”

Map recipients by category. Capture need-to-know conditions, downstream duties, responsibility for breaches, and consent requirements. The SAP–SuccessFactors NDA, § 3 illustrates participation or need-to-know limits and representative compliance requirements; another NDA may allocate responsibility differently.

Record: each permission and its conditions, care obligations, and mismatches with the actual project team. Test both parties’ operations rather than assuming mutual wording produces equal burdens.

4. Separate exclusions from disclosure permissions

Distinguish information excluded from protection from disclosure permitted despite continuing protection. Capture any proof requirement exactly. Do not infer exclusions for prior possession, independent development, public availability, or third-party receipt.

The SAP–Sybase NDA, § 4 illustrates several exclusions, including written release from restrictions. Its wording establishes neither mandatory exclusions nor a universal evidentiary burden.

Review compelled disclosure separately from voluntary protected reporting. The SEC explains that Rule 21F-17(a) prohibits impeding individuals’ direct reports of possible securities-law violations, including through confidentiality agreements. Its guidance identifies potentially conflicting notice requirements and confirms that protection extends beyond employment relationships (SEC Whistleblower Protections).

Record: conditions, proof requirements, related approval or notice language, and reporting conflicts requiring counsel’s review. Do not collapse these distinctions into “legal disclosures permitted.”

5. Parse timing into distinct obligations

Separate effectiveness, the disclosure window, agreement termination, confidentiality survival, use restrictions, and event-triggered notices. Identify whether execution, disclosure, termination, receipt of a request, or another event starts each period.

Preserve qualitative wording. “Promptly” is not a fixed day count; a termination notice period is not necessarily a confidentiality period. The SAP–Sybase NDA, §§ 7 and 18 illustrates prompt compelled-disclosure notice subject to legal prohibition, a separate agreement term, and surviving provisions.

Record: each rule’s trigger, affected duty, notice method, address, receipt mechanics, and cross-references. Identify missing facts or ambiguous counting rules instead of inventing dates.

6. Extract return, destruction, and retained-copy rules

Identify whether disposition follows a request, termination, or another trigger. Capture who chooses the method, covered material, certification requirements, and treatment of representative copies, analyses, backups, and legally retained records.

Pair retention permissions with continuing restrictions. The SAP–SuccessFactors NDA, § 9 illustrates request-triggered obligations, certification, and specified retention exceptions—not blanket retention authority for other NDAs.

Record: the conditional obligation and operational questions for information security, records management, and the business owner. Identify who could support a certification; do not treat an unverified deletion capability as confirmed compliance.

7. Verify summaries and assign decisions

Read each summary back against the source, checking definitions, exceptions, cross-references, and amendments. For executed agreements, compare the execution copy with the last approved draft, including signatures, dates, attachments, and incorporated documents—not just extracted text.

Separate legal uncertainty from commercial preference. A residuals permission may require analysis of its scope; a narrow evaluation purpose may conflict with planned development. Explain the consequence for each affected party and link the applicable checklist position.

Record: verification status, priority with reasons, proposed action, and owner. Close resolved questions with evidence; assign unresolved questions a specific next action rather than a generic “review needed” label.

Worked example

Fictional scenario: Alder Circuit LLC and Beacon Test Systems Inc. are considering a joint sensor evaluation. Alder expects to disclose design diagrams; Beacon expects to disclose test methods during a live laboratory demonstration. Alder also plans to involve an outside testing contractor.

Their fictional draft, NDA-F01-v2, contains the clauses below. The complete draft has been reviewed; no other provision expands oral or visual coverage or supplies retention exceptions. No contractor undertaking or records-management assessment has been supplied. These are missing operational evidence, not missing pages.

The extraction changes three decisions. Beacon should not rely on the NDA definition for its demonstration without addressing coverage. Alder’s contractor access depends on evidence of a qualifying written undertaking. Both parties need an operational basis for the destruction promise before accepting it.

The table does not establish that disclosure is unlawful or deletion impossible. It distinguishes source-supported wording from unresolved facts. If negotiations change these provisions, create entries for the revised version and preserve the original extraction history.

Common mistakes

• Treating “mutual” as proof of symmetry. Map each party’s disclosures and recipients; identical wording can create different practical exposure.
• Flattening conditional permissions. Replace “contractors allowed” with the permission, prerequisites, and responsibility provisions.
• Combining expiration and survival. Separate the duties and preserve the event starting each period.
• Declaring language absent too early. Distinguish incomplete files, unreadable pages, and unreviewed material from verified absence.
• Importing familiar terms. Keep proposed exclusions, residuals rights, and retention exceptions out of the extracted summary; record them as negotiation requests.

Final quality check

• Every substantive entry identifies the document version and precise source location.
• Exact wording, normalized summaries, and proposed amendments remain distinguishable.
• Definitions, qualifications, and cross-references match the complete source.
• Both parties’ roles and planned disclosures have been tested.
• Timing entries preserve triggers and qualitative deadlines without invented dates.
• Missing evidence is distinguished from missing contractual language.
• Every open issue has an owner and next action; resolved issues retain supporting evidence.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review and tabular review capabilities support reviewing clauses across documents. In Word, choose the represented party or neither and provide deal-specific instructions. Findings quote and locate clauses, rank severity, and identify missing language as not present. Lawyers can edit or insert suggestions as ordinary tracked changes in the signed-in Word user’s name, or dismiss findings with reasons. Verify findings against the complete NDA and retain legal judgment over the table and decisions. To discuss this workflow, book a demo.

Frequently asked questions

Should each NDA occupy one row?

Not for detailed clause extraction. Use one row per operative rule, linked by document ID. A later one-row-per-NDA portfolio summary should remain traceable to the clause-level entries.

How much exact text should the table preserve?

Enough to verify the rule and material conditions. Use linked rows for lengthy exceptions and cross-references, and keep the complete source available. A heading or unexplained excerpt is insufficient.

Can categories be reused across NDAs?

Yes. Normalize by function while preserving qualifiers and defined terms. Compare similar transaction contexts and governing laws against the organization’s approved baseline, not unsupported market-standard claims.

Should extraction confidence determine risk priority?

No. A confidently extracted clause may create significant risk; an uncertain reading may concern a minor issue. Assess sensitivity, planned disclosure, feasibility, and consequences separately, explaining whose interests are affected.

Sources

• 18 U.S.C. § 1839 — Definitions, official 2024 Code edition
• SEC — Whistleblower Protections
• SAP–Sybase Mutual Non-Disclosure Agreement
• SAP–SuccessFactors Mutual Non-Disclosure Agreement

The statutory citation uses the official 2024 Code edition, not a certified intervening-law update through October 13, 2026. Historical filed agreements illustrate drafting choices, 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.