1---2name: review-proposed-acquisition-nda-scenario-023task_id: corporate-ma/review-proposed-acquisition-nda/scenario-024description: Guides preparation of a prioritized NDA issues memo where a draft acquisition NDA must be reviewed against a client playbook and client-specific instructions to identify deviations requiring negotiation.5activates_for: [planner, solver, checker]6metadata:7 source: https://skillmd.com/skills/finchipaiorg/review-proposed-acquisition-nda-scenario-028---910# Skill: Proposed Acquisition NDA Review (Buyer Side)1112## 1. Subject-matter triage1314- Confirm the task is a buyer-side NDA review tied to a proposed acquisition process, not a generic confidentiality agreement review.15- Identify the source set before analysis: draft NDA, client playbook, client instruction email or note, and any process letter or auction materials.16- Determine whether the NDA is for a single counterparty or part of a multi-party process; if multiple counterparties or versions exist, analyze each separately and do not blend terms across drafts.17- If the process materials impose timing or standstill constraints, treat those as part of the operative commercial context, not background.1819## 2. Failure modes the skill is correcting2021- The review lists deviations from the playbook but does not separate material negotiation points from lower-priority drafting preferences.22- Client instructions are identified in the abstract but not mapped clause-by-clause to the draft NDA.23- The process letter or auction instructions are ignored, so time-bound NDA obligations are assessed without reference to the transaction timetable.24- The memo explains risk but stops short of giving a negotiation path or revised language direction.25- The memo discusses confidentiality issues without covering the full set of buyer-side acquisition NDA pressure points: confidential information scope, exclusions, permitted recipients, standstill, no-hire or no-solicit, return and destruction, injunctive relief, residuals, and governing law / forum.26- Legal conclusions are stated without anchoring them to the controlling rule or conventional market position that supports the recommendation.2728## 3. Legal frameworks / domain conventions that apply2930- Buyer-side NDA review compares the draft against the client’s playbook positions and transaction-specific instructions; where they conflict, the transaction-specific instruction controls.31- Process materials matter because NDA terms often interact with auction timing, bid deadlines, information access rules, and any required standstill period.32- Commercially, the goal is to preserve deal optionality while avoiding unnecessary leakage, litigation leverage for the counterparty, and overbroad behavioral restraints.33- Common review points include:34 - definition of Confidential Information and exclusions;35 - who counts as a Representative and whether affiliates, financing sources, and advisers are covered;36 - use restrictions and disclosure permissions;37 - compelled disclosure handling;38 - standstill scope, exceptions, duration, and trigger mechanics;39 - no-solicit / no-hire / no-poach restrictions;40 - return, destruction, and record-retention carveouts;41 - residuals / memory clauses;42 - remedies, equitable relief, waiver, assignment, and governing law / forum.43- Where a proposition depends on a legal rule rather than a market preference, state the governing authority or generally accepted doctrine that supports it; do not present it as self-evident.4445## 4. Analytical scaffolds4647- Start by extracting all operative playbook positions and client instructions, then group them by NDA provision.48- Separate mandatory client overrides from preferred negotiation points and silent areas where the playbook governs.49- Read the draft NDA provision-by-provision and test each provision against the applicable playbook position, client instruction, and process letter requirement.50- For each deviation, identify:51 - the provision or clause family;52 - the source position being departed from;53 - the nature of the deviation and why it matters in this transaction;54 - the recommended counterproposal, including whether to push, accept, or escalate.55- Assess whether the issue is material in light of the deal context, the transaction timetable, and any standstill or exclusivity dynamics.56- When several counterparties, time periods, or competing versions exist, enumerate them first and analyze each one separately.57- End each issue with three things: a concrete scale or measure from the source materials if one exists, the clause or document interaction that makes the issue operative, and the downstream consequence for the client.5859## 5. Vertical / structural / temporal relationships6061- Treat obligations that survive signing, termination, or expiration differently from obligations that apply only during the review process.62- Track whether any disclosure, destruction, standstill, or no-contact obligation is tied to a fixed number of days, a bid deadline, a closing event, or an indefinite period.63- Watch for internal dependencies among provisions: for example, a broad definition of confidential information can undermine narrow exclusions; a residuals clause can dilute a use restriction; a standstill can be made more onerous by automatic extension or notice mechanics.64- If process materials include a schedule or deadline sequence, test whether the NDA’s timing language is compatible with that sequence.65- If the draft uses defined terms inconsistently across sections, treat that as a structural issue, not a drafting nuisance.6667## 6. Output structure conventions6869- Produce a single prioritized issues memorandum, not a redline.70- Open with a short executive summary that states overall alignment, the main negotiation posture, and the most important issues to resolve first.71- Define one ordinal severity scale at the top and apply it consistently to every issue entry.72- For each issue, use an industry-conventional analysis format, such as:73 - issue / clause;74 - severity;75 - relevant playbook or client position;76 - draft deviation;77 - why it matters;78 - recommended position or alternative language direction;79 - negotiation note or fallback.80- Group issues by severity or priority, but keep each issue discrete; do not collapse different provisions into a single combined observation.81- Make every issue actionable: include the operative fix, not just the diagnosis.82- End with a concise Recommended Actions section that assigns next steps to the appropriate role and ties them to the transaction cadence or response deadline if one is available.83- Keep the writing suitable for a Word memorandum with clear headings and short, dense issue paragraphs.