1---2name: draft-diligence-summary-memo3task_id: corporate-ma/draft-diligence-summary-memo4description: Guides preparation of an investment-committee-ready acquisition diligence summary memo synthesizing multi-workstream findings by severity, presenting implied multiples at management and QoE EBITDA, and recommending pre-closing covenants for identified structural deficiencies.5activates_for: [planner, solver, checker]6metadata:7 source: https://skillmd.com/skills/finchipaiorg/draft-diligence-summary-memo8---910# Skill: Draft Diligence Summary Memo1112## 1. Subject-matter triage13- Use this skill for acquisition diligence synthesis where the output is an IC-ready memo, not a workstream report.14- Treat the source set as multiple diligence inputs that must be consolidated into one decision document.15- If only one diligence theme exists, say so explicitly; otherwise enumerate the full set of issues before analysis.1617## 2. Failure modes the skill is correcting18- Organizing the memo by workstream instead of by issue severity, which hides the decision-critical picture.19- Listing findings without quantifying their scale against the deal, the diligence figures, or the relevant operational threshold.20- Omitting the downstream consequence of a finding, so the committee cannot see why it matters.21- Failing to cross-link findings to the governing document, schedule, license, covenant, or diligence exhibit that drives the risk.22- Treating structural defects as mere monitoring items when they require a covenant, closing condition, or specific indemnity.23- Presenting adjusted EBITDA and valuation in a way that obscures the difference between management-reported and QoE-adjusted economics.24- Stating legal or regulatory risk conclusions without naming the controlling authority or document basis.25- Ending with diagnosis only, without concrete action items tied to a responsible role and timing.26- Drafting a memo that is descriptive rather than investment-committee-ready.2728## 3. Legal frameworks / domain conventions that apply29- IC-ready diligence memos typically include a transaction overview, valuation bridge, financing summary, severity-ranked issues, mitigation recommendations, and an overall recommendation.30- Implied enterprise multiple should be shown at both management EBITDA and QoE-adjusted EBITDA, with the adjustment bridge made explicit enough to show the turn differential.31- Seller-reported EBITDA should be tested for normalization issues, including owner compensation, non-recurring items, and any add-backs that are not supported by the source materials.32- Change-of-control, assignment, consent, exclusivity, termination, and similar provisions can create closing risk if the target depends on the affected contract or license.33- Missing employment, IP assignment, regulatory, tax, litigation, or similar foundational documents may require pre-closing covenants, closing conditions, or a targeted indemnity rather than a simple risk note.34- For legal conclusions, cite the controlling authority or document basis that supports the proposition, using the source materials where available and recognized authorities where needed.3536## 4. Analytical scaffolds37- Start with a short transaction overview: parties, deal structure, consideration framework, financing mix, rollover if any, and the headline valuation context.38- Build the valuation bridge from management EBITDA to QoE-adjusted EBITDA by itemizing each adjustment and stating the resulting valuation implication.39- Organize issues in ordinal severity tiers, defined once and applied consistently:40 - Critical: can impair closing, threaten license to operate, or create immediate transaction break risk.41 - Material: meaningfully affects valuation, integration, enforceability, or post-close risk allocation.42 - Monitor: important but not deal-shaping absent further facts or escalation.43- For every issue, complete the triad:44 - quantify the issue against a deal figure, threshold, exposure, or other source-based measure;45 - cross-reference the related clause, exhibit, schedule, license, agreement, or diligence input;46 - state the practical consequence for the buyer.47- For every Critical or Material item, add a mitigation path, such as price adjustment, specific indemnity, escrow, closing condition, consent, waiver, representation update, or RWI diligence check.48- When an issue implicates a closing dependency, separate what can be cured pre-signing, what must be delivered at closing, and what can be monitored post-close.49- If the source set includes more than one party, contract, license, site, claim, or period, enumerate the full set first and then analyze each item; do not compress distinct risks into a single blended observation.50- Use source-document terminology for roles, thresholds, and timing where available; otherwise use standard transaction language and make the timing anchor relative to signing, signing-to-closing, or closing.5152## 5. Vertical / structural / temporal relationships53- Trace each issue upward from the underlying document or diligence exhibit to the transaction implication, then downward to the mitigation step.54- Distinguish pre-signing cleanup, signing-to-closing deliverables, and post-closing monitoring so the committee can see when the risk is actually controlled.55- Where a deficiency depends on future consent or waiver, state whether the risk is contingent, probable, or immediate based on the document path and transaction timing.56- If a license, contract, permit, or other right sits at the center of the business model, explain whether the risk is localized or enterprise-wide.57- Keep the memo decision-oriented: facts first, then implication, then action.5859## 6. Output structure conventions60- Write an IC-ready diligence summary memo, not a file-by-file diligence log.61- Use conventional memo sections such as:62 - Transaction Overview63 - Valuation Bridge / Implied Multiples64 - Financing and Sources of Funds65 - Key Diligence Findings by Severity66 - Mitigation / Deal Protections67 - Recommended Pre-Closing Covenants and Closing Conditions68 - Overall Recommendation69- Present the severity tiers explicitly at the start of the issues section and use them consistently for every item.70- Include a concise table for the valuation bridge and another for the issue summary if the source set supports tabular presentation.71- For each issue entry, state: severity, issue, scale or magnitude, document basis or cross-reference, consequence, and recommended protection.72- Do not bury critical items inside a narrative paragraph; surface them where the committee will look first.73- End with an explicit Recommended Actions block that names the action, the responsible role, and the timing anchor.74- Keep the memo ready for direct conversion to a .docx investment committee deliverable.