1---2name: prepare-responses-to-ddrl-scenario-023task_id: corporate-ma/prepare-responses-to-ddrl/scenario-024description: Guides preparation of a sell-side diligence response matrix that maps buyer requests to the seller's available diligence materials, identifies coverage gaps, and flags sensitive information for deal-team review before disclosure.5activates_for: [planner, solver, checker]6metadata:7 source: https://skillmd.com/skills/finchipaiorg/prepare-responses-to-ddrl-scenario-028---910# Skill: Sell-Side Due Diligence Response Matrix1112## 1. Subject-matter triage13- Treat the buyer request list and the VDR index as separate source sets that must be reconciled item by item.14- Confirm the request universe up front and preserve the request numbering in the response matrix.15- If the request list, VDR index, and deal-team notes are all present, use all three; if one is missing, note the limitation and proceed only with what exists.16- This is a comparison-and-gap task, not a substantive legal memo; the output should show coverage, exceptions, and escalation points.1718## 2. Failure modes the skill is correcting19- Requests are matched to VDR materials without confirming that the material actually covers the requested entity, period, topic, or transaction scope.20- Items that are missing, incomplete, or only partially responsive are treated as satisfied instead of being flagged as gaps.21- Sensitive, privileged, confidential, or deal-sensitive materials are surfaced in the matrix without a clear hold/review flag.22- The matrix collapses distinct outcomes into one bucket instead of separating: fully responsive, partially responsive, non-responsive, needs follow-up, and needs legal/deal-team approval.23- The response set is not tied back to the VDR indexing system, making it hard for reviewers to locate the source materials.24- The deliverable omits next-step ownership, so open items are not assigned to the right business, legal, or deal-team participant.2526## 3. Legal frameworks / domain conventions that apply27- Sell-side diligence response matrices are working tools for disclosure management; they must track what is responsive, what is not, and what cannot be released yet.28- VDR referencing should use the room’s own file names, folder paths, document IDs, or equivalent index references so a reviewer can find the source quickly.29- Responsiveness is a coverage question: a document may exist but still fail the request if it misses the relevant period, subsidiary, contract set, or subject matter.30- Sensitive-item handling should reflect privilege, confidentiality, strategic sensitivity, third-party restrictions, or disclosure controls that require approval before release.31- Because this is a disclosure-management deliverable, the matrix should support internal triage and not imply authorization to produce any item marked sensitive.32- When the source set suggests a legal or regulatory overlay, name the governing concept or authority only if it is actually implicated by the materials; do not generalize beyond the record.3334## 4. Analytical scaffolds35- First enumerate the full request set in request order and preserve each request’s identifier.36- Then enumerate the VDR contents by the indexing scheme used in the room.37- For each request, locate all potentially responsive materials, then test each candidate for coverage of:38 - time period,39 - entity or business line,40 - contract/document type,41 - subject matter specificity,42 - completeness.43- Classify each request into one of the working outcomes:44 - responsive,45 - partially responsive,46 - no responsive material located,47 - responsive material exists but is not yet uploaded,48 - needs clarification,49 - sensitive/hold for review.50- If more than one material addresses a request, keep all references that matter and explain how they fit together rather than naming only one representative file.51- Review deal-team notes separately for items that should be held back, redacted, or escalated before disclosure.52- Where a request cannot be answered from existing materials, state the concrete follow-up: locate, upload, obtain, draft, redraft, or escalate.53- Use a consistent severity scale for action items:54 - Critical,55 - High,56 - Medium,57 - Low.58- Apply the severity label to every gap or sensitivity issue and keep the label tied to the recommended action.5960## 5. Vertical / structural / temporal relationships61- Track whether the request is aimed at the parent company, a subsidiary, a business unit, a plant, a product line, or a historical period, and ensure the VDR reference matches that level.62- Distinguish current-state materials from historical materials; a current policy or contract often does not satisfy a request aimed at a prior period, and vice versa.63- If the same topic appears across multiple folders or versions, show the relationship between the documents rather than flattening them into one entry.64- When a request touches multiple subject areas, keep the response keyed to the primary request while cross-referencing the supporting materials that sit in adjacent folders.65- For sensitive materials, distinguish “present in VDR but blocked,” “not yet uploaded,” and “available only after approval,” because those statuses drive different deal-team actions.6667## 6. Output structure conventions68- Produce one consolidated diligence response matrix as the sole deliverable.69- Organize rows by buyer request number and preserve the original request order.70- Use conventional columns such as:71 - request number,72 - request description,73 - responsive VDR reference(s),74 - response status,75 - response summary,76 - gap / follow-up,77 - sensitivity flag,78 - severity,79 - owner / action.80- Make the status field explicit; do not force the reader to infer whether a request is satisfied.81- Distinguish partial responses from complete responses with plain-language labels.82- For every open item, include a short action note that identifies what must happen next and who should handle it.83- For every sensitive item, mark the need for deal-team approval, legal review, or redaction before any external disclosure.84- Keep references precise enough that another reviewer can locate the underlying document without additional context.85- End the matrix only after every request has a row and every gap or sensitivity issue has a corresponding action entry.