Summarize Key Legal Issues Data Room

Skill: Due Diligence Memorandum from Data Room Review

1. Subject-matter triage (only if applicable)

• Start by mapping the data room index into standard diligence workstreams and flag any missing or thinly populated folders before reviewing substance.
• Group documents by subject matter, then by issue cluster within each subject matter, so the memo reflects both category-level and deal-level risk.
• If multiple entities, facilities, agreements, or time periods are in scope, identify the full set first and analyze each item separately rather than using a single representative pass.
• Surface any apparent hierarchy, interdependence, or sequencing among documents that affects risk allocation, closing conditions, or post-closing integration.

2. Failure modes the skill is correcting

• The memo recites documents category by category without synthesizing how findings compound across operational, contractual, regulatory, intellectual property, employment, financial, and real estate themes.
• Risk labels are used inconsistently across sections, so the same severity term implies different levels of concern in different workstreams.
• Issues are described abstractly and never tied to transaction consequences, cross-document interactions, or deal protections.
• Information gaps are left implicit, even when the index shows standard diligence categories were not produced or were materially incomplete.
• Recommendations stay generic instead of translating each material issue into a specific protection tied to the deal structure and the stage of the transaction.

3. Legal frameworks / domain conventions that apply

• Use a conventional diligence memo frame: executive summary, workstream-by-workstream analysis, then open items and follow-up needs.
• Apply one ordinal severity scale throughout the memo, defined once at the outset and used uniformly for every issue.
• For each issue, assess practical significance by reference to the scale of the exposure, the relevant document terms, and the way the issue interacts with other materials in the data room.
• Anchor any legal proposition in the controlling source of law or standard practice relevant to the issue area; do not state legal conclusions as bare assertions.
• Treat common diligence themes as separate workstreams only when the documents support that separation; otherwise combine closely related materials into a single analytical section.
• Use deal-protection tools that match the risk profile: targeted representations, specific indemnities, escrow or holdback, purchase price adjustment, conditions to closing, closing deliverables, covenants, or post-closing undertakings.
• If regulatory, litigation, or remediation materials appear, evaluate status, timing, likely enforcement or disruption risk, and whether the issue should affect signing, closing, or post-closing integration.
• If commercial concentration or supply dependence appears, evaluate operational fragility, continuity risk, and whether additional contractual or operational protections are warranted.
• If intellectual property claims or technology dependencies appear, consider whether they affect the target’s ability to operate core business lines and whether claim-specific or functionality-specific protections are needed.
• Compare the production set against standard diligence categories and identify missing folders, absent schedules, or unexplained gaps as follow-up items.

4. Analytical scaffolds

• Review the index first, then note missing categories, sparse production, duplicate materials, and documents that appear to belong in more than one workstream.
• For each workstream, identify the principal issues, the document support, the severity, the legal or transactional interaction, and the downstream consequence for the buyer.
• Scale each issue to the relevant source materials, cross-reference the clause, schedule, or related document that changes the risk picture, and state the practical effect on valuation, closing, operations, liability allocation, or integration.
• Use the same severity rubric in every section; if an issue appears only partial or contingent, explain why it is not fully mature or why the severity is moderated.
• Synthesize across workstreams to identify compounding risks, such as a contractual problem that overlaps with regulatory exposure or an employment issue that affects key operations.
• Convert each material issue into a specific protection or follow-up step that is tailored to the transaction and to the role best positioned to implement it.
• Organize the memo so that the executive summary previews the highest-risk themes, the body addresses each subject matter category, and the end of the memo lists open items and recommended next steps.

5. Vertical / structural / temporal relationships (only if applicable)

• Where documents show a timeline, separate historical facts, current status, and expected future milestones.
• Where a matter has vertical dependencies, identify the base agreement, amendments, side letters, schedules, approvals, notices, or remediation documents that modify the risk.
• Where one document changes the meaning of another, explain the interaction explicitly rather than citing the documents in isolation.
• Where a risk turns on scale, state the relevant document-based measure before discussing severity or protection.
• Where the same issue appears in multiple workstreams, avoid duplication by noting the primary section and cross-referencing the related one.

6. Output structure conventions

• Produce a single due diligence memorandum in a professional deal-diligence format.
• Begin with a concise severity key, then an executive summary that states the overall risk posture, the principal cross-category themes, and the most important protections.
• Follow with subject-matter sections that each contain: key findings, severity, relevant document context, legal or transactional significance, and recommended deal protections.
• Include a separate open-issues or information-gaps section that identifies missing production and follow-up requests.
• End with an explicit Recommended Actions block that uses imperative verbs, names the responsible role or team, and ties each action to a timing anchor or transaction milestone.
• Keep the writing analytical and deal-focused; avoid document recitation that does not change the risk assessment.