1---2name: draft-data-room-population-plan-s013task_id: corporate-ma/draft-data-room-population-plan/scenario-014description: Guides preparation of a data room population plan from deal materials, requiring critical review of the request list for errors, separate tracking of contracts with assignment or change-of-control restrictions, distinction between copyleft and permissive open-source licenses, board minute redaction protocol, and resolution of instruction conflicts.5activates_for: [planner, solver, checker]6metadata:7 source: https://skillmd.com/skills/finchipaiorg/draft-data-room-population-plan-s018---910# Skill: Draft Data Room Population Plan (Scenario 01)1112## 1. Subject-matter triage13- Treat the assignment as a sell-side VDR population plan for an acquisition, not a generic document checklist.14- Start from the DDRL, org chart, contract inventory, prior deal indices, and partner instructions; reconcile them against each other before drafting the plan.15- If the materials point to multiple entity levels, business lines, or document owners, enumerate them first and assign collection responsibility separately rather than using one blended pass.16- Preserve the deal team’s practical objectives: populate the room, surface corrections, and flag pre-closing process items that need separate tracking.1718## 2. Failure modes the skill is correcting19- Following the request list mechanically without checking whether an item is misstated, misplaced, or inconsistent with the transaction.20- Collapsing consent-sensitive contracts into the main collection workflow instead of maintaining a separate consent-tracking workstream.21- Treating open-source risk as a single bucket instead of separating copyleft components from permissive-license components.22- Uploading board minutes without a pre-upload redaction review for privileged, strategic, or otherwise sensitive content.23- Ignoring conflicts between partner instructions and the request list instead of flagging them for resolution before the VDR opens.24- Missing shareholder-consent coordination as a deal-execution item that must be tracked alongside, but not inside, the document-population plan.25- Writing a generic upload list without assigning owners, deadlines, and priority order tied to the expected opening and closing sequence.2627## 3. Legal frameworks / domain conventions that apply28- Request-list validation: the request list is a starting point, not an error-free source; review it critically and correct obvious factual or deal-structure mismatches before collection begins.29- Anti-assignment and change-of-control restrictions: contracts containing consent requirements should be tracked separately because they may require third-party approvals before closing; use a dedicated consent tracker with owner, outreach step, and deadline.30- Open-source licensing: distinguish copyleft licenses from permissive licenses; where proprietary software may be combined with copyleft components, require an audit to identify source-disclosure or distribution-trigger risk, while permissive licenses are generally lower-friction.31- Board-minute privilege and sensitivity review: board minutes often contain merger discussions, legal advice, litigation strategy, and projections; they should be reviewed and redacted by counsel before upload.32- Instruction hierarchy: if a supervising lawyer directs that a document be withheld or handled specially, that instruction controls over a rote request-list item until the conflict is resolved.33- Shareholder consent rights: consent solicitation is a transaction-management task, not merely a collection task; assign a responsible person and a timing plan.34- Standard VDR taxonomy: organize by conventional M&A folders, typically corporate, financial, intellectual property, material contracts, employment, real estate, regulatory and environmental, litigation, insurance, and transaction-specific supplements.3536## 4. Analytical scaffolds37- Build the plan in two layers:38 1. the folder architecture and collection schedule; and39 2. a separate issues / exceptions tracker.40- For each requested category, test whether the item is:41 - correctly described for this deal,42 - complete for all relevant entities or periods,43 - sensitive enough to require redaction or withholding,44 - subject to consent, approval, or external rights,45 - better handled in a separate tracker rather than the main room.46- For each contract that may require consent, capture:47 - contract identifier and business owner,48 - why consent may be needed,49 - who must pursue the consent,50 - what needs to happen before upload versus before closing,51 - whether the item should be listed in the room pending consent or withheld until cleared.52- For software / technology materials, run a targeted license screen:53 - inventory relevant codebases, libraries, and dependencies,54 - identify copyleft items separately from permissive items,55 - flag any mixed-use area where proprietary and open-source components interact,56 - note whether a follow-up technical/legal review is needed before disclosure.57- For board minutes, create a redaction protocol:58 - identify custodian and reviewing lawyer,59 - specify that redactions are approved before upload,60 - distinguish redaction from withholding,61 - keep an audit trail of the basis for redaction.62- For instruction conflicts, state:63 - the instruction,64 - the conflicting request-list item,65 - the proposed resolution path,66 - whether the item should be deferred, redacted, or withheld.67- For each issue or exception, attach a severity level using one consistent ordinal scale defined at the outset, and include the practical consequence for the VDR plan.6869## 5. Vertical / structural / temporal relationships70- Separate pre-upload tasks from pre-closing tasks; do not let consent solicitation, counterparty outreach, or shareholder approvals disappear into the document-collection schedule.71- Track entity-level documents by relevant vertical: parent, subsidiaries, and business units, with special attention to any non-domestic entities or gaps in the org chart.72- Preserve the sequence: validate request list, assign collection owners, screen for sensitive materials, run consent and open-source reviews, then finalize the upload sequence.73- If the expected VDR opening date is known, work backward from it to set collection deadlines, review deadlines, and escalation points.74- If a document is both responsive and sensitive, identify the governing action order: review first, redact or clear next, upload last.7576## 6. Output structure conventions77- Use an industry-conventional plan, not a rubric-shaped checklist.78- Begin with a concise summary of the VDR approach, scope assumptions, and any request-list corrections.79- Include a folder architecture section organized by standard M&A categories.80- Include a collection matrix or schedule showing document category, owner, reviewer, deadline, and status.81- Include a separate exceptions / issues section with an ordinal severity label for each entry.82- Include a dedicated consent-tracking subsection for anti-assignment, change-of-control, and shareholder-consent items.83- Include a dedicated open-source subsection that distinguishes copyleft from permissive components.84- Include a board-minutes redaction protocol subsection before the upload plan.85- Include an instruction-conflict subsection identifying any partner-instruction conflicts and proposed resolution.86- End with an action list that assigns next steps to specific roles and ties them to the VDR-opening or closing timeline.87- Keep the plan operational: every flagged item should tell the team what to do next, who owns it, and when it must happen.