Draft Bilateral Nda From Deal Parameters

---
name: draft-bilateral-nda-deal-parameters
task_id: intellectual-property/draft-bilateral-nda-from-deal-parameters
description: Bilateral NDA for a potential strategic acquisition and an accompanying cover memorandum explaining key drafting decisions and open issues, based on deal parameters and dual-party playbook inputs.
activates_for: [planner, solver, checker]
---

# Skill: Draft Bilateral NDA from Deal Parameters

## 1. Subject-matter triage

Identify the transaction posture before drafting: bilateral diligence NDA for a potential strategic acquisition, with both parties’ form language, playbook positions, and deal parameters potentially in play.

Determine which form is the better starting point, and explain why in the cover memorandum. If one side’s form controls for practical reasons, say so and note what was imported from the other side’s paper.

Check whether the deal materials show one counterparty, multiple affiliated recipients, sponsor participation, or any other nonstandard access path. If only the two named parties are in scope, say that expressly rather than drafting around a hypothetical broader group.

## 2. Failure modes the skill is correcting

- Drafting a generic mutual NDA that ignores acquisition-specific use limits, process expectations, and information sensitivity.
- Starting from one form but silently dropping the other side’s nonstandard asks, leaving avoidable first-pass objections.
- Treating the deal parameters as complete without checking the related diligence or correspondence set for special categories of protected information.
- Missing whether the transaction calls for employee non-solicit, standstill, residuals, sponsor access, or similar acquisition-specific terms.
- Failing to distinguish open drafting judgment calls from true playbook conflicts that should be escalated.
- Producing a memo that explains choices in the abstract but does not tell the client what is still unresolved and why it matters.

## 3. Legal frameworks / domain conventions that apply

- Mutual acquisition NDAs generally limit use of confidential information to evaluating the specified transaction and related financing or diligence steps only if the deal materials so permit; the governing clause should track the permitted-purpose language in the source set.
- Confidential information definitions in M&A NDAs often need to cover oral, written, electronic, and derived materials, with express treatment of disclosures by representatives and controlled affiliates.
- Residual knowledge clauses, if included, should be checked against the parties’ playbooks and any IP-sensitive instructions; carve-outs for independently developed know-how or protected inventions may be required.
- Return, destruction, and retention provisions should address legal hold, backup systems, and archival copies, consistent with ordinary NDA practice and any source-document instructions.
- Acquisition NDAs may include employee non-solicit, standstill, no-contact, no-publicity, or similar deal-control terms; include only what the deal materials support and flag any omitted market-standard protection.
- If the diligence package touches patents, trade secrets, source code, product roadmaps, or other IP-heavy categories, tailor confidentiality, use restrictions, and residuals language accordingly.
- Any legal conclusion in the memo should be tied to the governing document or a recognized commercial NDA convention; do not state a position as if it were self-evident.

## 4. Analytical scaffolds

- Base-form selection: choose the drafting anchor, then explain the choice, the principal imported provisions, and the principal departures.
- Deal-parameter integration: map the business terms into NDA language, including scope of permitted use, duration, recipients, compelled disclosure handling, and any process guardrails.
- Dual-playbook reconciliation: identify each true conflict, note whether it is a drafting issue or a business decision, and recommend the least-friction resolution.
- Transaction-specific tailoring: test whether standstill, non-solicit, affiliate access, financing-party access, or publicity controls are required or should be excluded.
- IP-sensitivity integration: ensure the draft protects the categories of information actually implicated by the deal materials, not a generic acquisition file set.
- Open-issue framing: separate settled points, negotiable points, and escalation items so the memo can be used in live negotiations.

## 5. Vertical / structural / temporal relationships

For each provision that depends on sequencing or duration, preserve the relationship among initial exchange, permitted diligence period, extension or termination, return/destruction obligations, survival, and any post-termination restrictions.

Where the draft references representatives, affiliates, potential financing sources, or advisors, make clear who may receive information before closing, who may retain it afterward, and what use limits continue to apply.

If the materials imply multiple phases of the transaction, keep the NDA language aligned to those phases rather than collapsing them into a single undifferentiated review period.

## 6. Output structure conventions

- Draft the bilateral NDA as the primary deliverable first, in execution-ready form, with operative clauses rather than commentary.
- Prepare the cover memorandum only after the NDA draft is complete and non-empty.
- The cover memorandum should cover:
  - the drafting anchor and why it was selected;
  - the main business and legal decisions embedded in the draft;
  - any playbook conflicts or open issues;
  - the provisions most likely to draw counterparty comments;
  - the recommended negotiation posture on unresolved items.
- Use conventional legal drafting headings and clause architecture; do not mirror any hidden checklist or rubric structure.
- Keep the memorandum advisory and practical, but grounded in the actual deal materials and the drafted language.
- Before finishing, confirm that both named output files are produced, non-empty, and contain the requested operative work product.