Reporting and Deliverables

Commercial due diligence ends in decisions, not in datasets. This chapter codifies how to turn weeks of analysis into crisp, decision‑grade deliverables that Investment Committees, lenders, and operators can underwrite and act on. The core package typically includes: a short presentation deck (the “spine”) with a larger appendix, the driver‑based model and QA sign‑off, a risk pack with triggers and playbooks, an integration feasibility brief, a value‑capture roadmap, and a small set of evidence exhibits (pricing waterfall audits, parcel/cloud bills, AR/AP agings, VoC notes—anonymized). Everything must reconcile to the current model version, use the same segmentation and definitions, and respect legal guardrails (clean‑team, antitrust, privacy, platform policies).

18.1 Presentation Deck Structure Template

A strong deck is short, answer‑first, and cash‑first. It opens with the recommendation and the dollars that move CM2, cash, and quarterly covenant headroom in the hold period; it then proves those claims with three to five MECE arguments and the minimum number of exhibits. Use the template below to storyboard, build, and QA the deck. Adapt page counts to your audience, but keep the logic intact.

Purpose and design rules

Purpose: enable a buy/price/terms decision in under 20 minutes; equip lenders and operators with the numbers, gates, and protections they need.
Answer‑first titles: every headline is a complete sentence with a number and a verb (e.g., “Realized price can rise 80–120 bps in Enterprise without churn delta”).
Cash‑first exhibits: show bridges, deltas, and bands (not raw levels). Quote ΔCM2, ΔCash, and headroom for Year‑1/Year‑2.
Model‑anchored: each number is traceable to named driver cells and the current model version stamp.
One page, one message: three proof bullets max per page; everything else moves to the appendix.
Guardrails: constant currency and organic perimeter; capacity and SLO caps enforced; clean‑team rules observable on every page.

Deck skeletons you can pick up and run

IC “spine” (10–12 pages): use when time is tight (PE Investment Committee).
Full decision deck (20–30 pages): add domain sections where exposure is material (e.g., marketplaces, cloud/FinOps, returns).
Lenders supplement (10–15 pages): deeper downside, 13‑week cash, covenant math, borrowing‑base.
Strategic buyer variant (15–20 pages): add integration posture (Fuse/Federate/Interface) and option value; still cash‑first for 24 months.

Slide‑by‑slide structure (copy‑ready)

0) Cover & control information

Title, client/target, workstream, confidentiality stamp, model version ID, perimeter and currency notes, date, version number (e.g., v1.3).

1) Executive recommendation (answer‑first)

“Buy at $X EV with Y terms (indexation, certification CPs, reserve caps, inventory/service covenants, earnout on NRR/realized price). Base delivers ΔCM2 $A and ΔCash $B in Year‑1; min headroom ≥ H bps across scenarios.”
Footnote: constant currency, organic scope; link to model cell range.

2) Why this works (three reasons that move cash)

Unit economics & price power (realized price +P–Q bps; elasticity proof).
Cost‑to‑serve improvements (returns −r bps, parcel/cloud −u%, minutes/contact −m).
GTM & capacity (conversion +c pp, attach +a pp; capacity rung #1 booked; CAC payback ≤ t months).

3) Market reality & scenarios

TAM/SAM/SOM and buyer‑segment exposure; growth driver decomposition; scenario fan (base, recession, stagflation) with p10/p90 shading; triggers to flip cases.

4) True unit economics

Pricing waterfall to realized price; CM1→CM2 bridge by segment/channel; sensitivity to price, returns, freight/cloud/API; unit‑driver definitions.

5) Competitive position & disruptors

Share and momentum by segment; differentiation scorecard (moats/advantages); disruptor threat scenarios and mix shift risk.

6) GTM & channel performance

Funnel diagnostics (stage conversion, cycle time, win rate); channel mix economics; CAC payback guardrails; marketplace policy thresholds in view.

7) Operations, CTS, and capacity

Capacity ladder (rungs, lead times, SLO impact); CTS benchmarks (shipping, returns, support, payment bps, cloud/API unit costs); cost‑to‑serve improvement plan.

8) Forecast & headroom (scenario‑anchored)

Driver‑based base vs. downside vs. managed response; quarterly headroom path and first breach month (passive); cost of actions that avoid breach.

9) Risks, mitigations, and residuals

Top‑10 Cash‑VaR heat‑map; triggers and playbooks; residual Cash‑VaR, CVaR, reserves and liquidity buffer; early‑warning indicators.

10) Value creation & synergies we underwrite

Revenue: attach/re‑rating math, gates, timing; ΔCM2, ΔCash.
Cost & CTS: procurement/logistics/FinOps; run‑rate vs. in‑period cash; one‑time costs.

11) Integration feasibility & cutover gates

Fuse/Federate/Interface by domain; Day‑1 controls; Go/No‑Go acceptance tests (billing/entitlement ≥99.5%; certifications; SLO headroom ≥15%); TSA scope and exits.

12) Terms we need & 90‑day plan

Term‑sheet translations tied 1:1 to residual risks; dated 90‑day actions with owners and KPIs; model toggles that flip on gate clearance.

Appendix index (first page of appendix)

Organized by model driver (price, mix, conversion, returns, freight, cloud, minutes/contact, take‑rates, DSO/DIO/DPO, reserves); each subsection lists exhibits, sources, and extract dates.

Exhibit archetypes (pick the smallest artifact that proves the point)

Bridges: last actual → Year‑1 → Year‑2 for CM2 and cash with bars labeled price, volume, mix, CTS, opex, working capital.
Waterfalls: realized price from list to cash (on‑invoice, off‑invoice, fees, penalties, returns).
Fans/bands: scenario bands with p10/p90 shading; label triggers.
Tornados: sensitivity rank by absolute ΔCM2 or ΔCash from standardized shocks.
Heat‑maps: risk or concentration by segment/channel.
Ladders: capacity rungs with throughput, lead time, and SLO effect.
Grids: two‑way thresholds (e.g., realized price vs. elasticity; DSO vs. base rate; return rate vs. paid placement penalties).

Required “page furniture” (put these elements on every slide)

Header: project name, confidentiality, audience label (IC / Lenders / Strategic).
Footer: model version, perimeter and currency, page number, and last update date.
Footnotes: sources with extract dates; clean‑team note where relevant (“Aggregated/anonymized; no customer‑identifying data”).
Units: currency code (USD/EUR/…), time base (monthly for 8–12 quarters, then annual), segmentation keys.

Style and accessibility standards

Titles in sentence case; numbers in titles where possible (bps, pp, $/unit, days).
Minimum font 11 pt for body; avoid color‑only meaning (contrast‑safe palette).
Round consistently (nearest whole $m; bps to nearest 10 unless small).
Keep decimal places scarce (≤1 where needed); mark estimates with ranges and confidence labels (H/M/L).
Add concise alt text for critical charts (for accessibility and search).

Source coding and data hygiene

Use a simple source code in footnotes (e.g., “S1 Company ERP extract 2025‑08‑01; S2 Parcel invoices Apr–Jun 2025; S3 Cloud bills L3M; S4 VoC N=32 anonymized”).
Reconcile to last actual and LTM; state constant currency and organic perimeter; show FX overlay only if material.
Never include raw PII or customer‑identifying data; never include competitor‑sensitive pricing beyond public sources.

File and version control

Naming: Client_Target_CDD_v{major.minor}_{YYYY‑MM‑DD}_{Audience}.pptx (e.g., ACME_Foxtrot_CDD_v1.3_2025‑08‑15_IC.pptx).
Change log: slide‑level deltas with “what/why/who/when”; paste onto the hidden “Changelog” slide.
Lock: freeze the model version ID when exporting the final numbers; restamp if anything changes.

Audience‑specific add‑ons

Lenders/Credit Committee: add 13‑week cash, covenant math per quarter, borrowing‑base eligibility and advance rates, passive vs. managed downside (cost of action explicit).
Strategic/Corporate: add integration posture, customer/brand risk, and option value (beyond hold period) but still present cash/CM2 for 24 months.

Slide build checklist (run before you export)

Title is answer‑first with a number and a verb.
Three or fewer proof bullets; each cites an exhibit and source date.
Numbers reconcile to the current model version in ≤3 clicks.
Units, time base, segmentation, constant currency/perimeter stated.
Capacity/SLO caps, platform policies, and regulatory limits enforced.
Passive vs. managed paths separated; cost of action shown where relevant.
Early‑warning indicators and gate acceptance tests present where they matter.
Legal/privacy footers present; no PII; clean‑team scope respected.

Ten must‑have exhibits (include unless clearly non‑applicable)

Executive bridge: last actual → Year‑1 and Year‑2 ΔCM2 and ΔCash.
Pricing waterfall to realized price (with invoice and settlement audit references).
CM1→CM2 margin tree by segment/channel.
Funnel diagnostics (conversion, win rate, cycle time) and CAC payback.
CTS summary (returns %, parcel $/shipment, cloud/API $/unit, minutes/contact).
Capacity ladder with SLO headroom and rungs.
Scenario fan (base, recession, stagflation) and quarterly headroom.
Sensitivity tornado (top five drivers) with break‑even thresholds.
Risk heat‑map with Cash‑VaR and residuals after mitigations.
90‑day value‑capture plan with dated gates and owners.

72‑hour deck sprint plan (from analysis to IC‑ready)

Day 0: Freeze model version/perimeter/FX; select skeleton (spine/full/lenders/strategic); draft answer‑first titles for pages 1–12.
Day 1: Populate exhibits from the model and evidence files; stamp sources and extract dates; insert headroom path and scenario bands; load sensitivity tornado and break‑evens.
Day 2: Add risks/residuals and term‑sheet translations; integrate integration gates and TSA exits; build the 90‑day plan; reconcile bridges to model.
Day 3: Red‑team (one pass for numbers, one for logic); run the slide build checklist; lock file name and model ID; export PDF alongside PPTX; prepare appendix index by driver.

Acceptance criteria for a decision‑grade deck

Recommendation page states buy/price/terms and quantifies ΔCM2, ΔCash, and headroom across scenarios, consistent with the current model.
Each insight page answers‑first, cites exhibits with extract dates, and ties to named driver cells.
Bridges, bands, and tornados appear where expected; capacity/SLO and policy constraints enforced.
Residual risk and reserves are quantified; term‑sheet asks map 1:1 to residuals; 90‑day actions are dated and owned.
Appendix is organized by driver and includes evidence audits (pricing, parcel/cloud bills, AR/AP agings, VoC notes—anonymized).
Legal/privacy statements present; clean‑team scope respected; no PII.
A second person can reproduce any headline number from the model in ≤3 clicks.

Use this template to keep your deck tight, auditable, and actionable—so busy committees can say “yes” (or “no”) with confidence, and operators know exactly what to do on Day 1.

18.2 Data-Room Documentation Checklist

A strong virtual data room (VDR) makes diligence faster, cleaner, and safer. It should let a second person reproduce any headline number in ≤3 clicks from a machine‑readable source, while protecting sensitive data with a clean‑team and antitrust guardrails. Use this checklist to stand up (seller‑side) and interrogate (buyer‑side) a data room that is complete, auditable, and legally compliant. Organize everything to mirror the segmentation and driver logic used throughout this playbook (product × route‑to‑market × region × customer tier) and the same definitions of realized price, CM2, and cash.

Core principles (do these first)

Answer‑ and cash‑first: prioritize documents that explain price, volume, mix, cost‑to‑serve, working capital, and headroom within the hold period.
Machine‑readable over pretty: CSV/XLSX/Parquet for data; searchable PDFs for signed contracts/policies; avoid screenshots and pivoted spreadsheets.
One source of truth per metric: declare the system of record and extract date for every file; reconcile last actuals and LTM to GL.
Legal guardrails: enforce clean‑team, antitrust, privacy, platform policy, and sector‑specific rules (e.g., HIPAA/PCI) with written protocols.
Provenance and versioning: every file carries a header with owner, extract timestamp, perimeter, currency, and change log.
Reproducibility: any number in the deck must trace to a file and row/field in the VDR; keep a cross‑reference (“evidence registry”).

VDR setup & governance (seller‑side)

Security: SSO + MFA, watermarking, print/download controls, IP‑range limits, session timeouts, user‑level audit logs, timed access.
Structure: numbered folder taxonomy, short names, and a single README at root explaining layout, definitions, and contact/SLA.
Q&A: enable threaded Q&A with routing to functional owners; set a 48‑hour response SLA and escalation path.
Change control: weekly refresh window, version suffix in filenames, and a delta subfolder for changes since the last drop; maintain a change log.
Destruction: define post‑process retention period and require certifications of destruction from all parties.

Recommended folder taxonomy (mirror your model drivers)

0_ReadMe_Definitions_ChangeLog
1_Market_and_Scenarios (third‑party studies, category indices, demand indicators, scenario assumptions)
2_Product_Pricing_Packaging (price books, fences/DOA, promos, rebate programs, CPQ rules, SKU catalogs)
3_Revenue_and_Customers (ARR/NRR roll‑forwards, bookings/opportunities, invoices/credit memos, top accounts—clean‑team ready)
4_GTM_and_Channels (pipeline by stage, win/loss, channel/partner contracts, MDF, marketplace settlement files and policy dashboards)
5_Cost_to_Serve_and_Operations (returns/RMA, warranty, parcel/carrier invoices, WMS/TMS extracts, payment processing/chargebacks, support tickets/minutes)
6_Technology_and_Cloud (cloud bills/CUR, API usage, reliability/SLO, SOC/ISO reports, DPIAs, incident logs)
7_Supply_Chain_and_Procurement (BOMs, supplier rate cards, rebates, duties/tariffs, capacity ladders)
8_Financials_and_Working_Capital (GL trial balance, revenue recognition memos, AR/AP agings, inventory ledgers, bank recs, debt/covenants)
9_Regulatory_Legal_ESG (licenses, certifications, consents/novations, ESG metrics, EPR/packaging fees, privacy policies)
10_HR_and_Incentives (org charts, comp plan templates, sales commission rules—no PII)
11_Integration_TSA (systems maps, interface inventories, TSA scope/SLAs, cutover plans)
12_Evidence_Registry_and_Model_Links (source codes S1…Sn, model cell mapping, exhibit list)

File naming & versioning (use a consistent pattern)

Pattern: Area_Subarea_Descriptor_Perimeter_Currency_ExtractYYYYMMDD_v{major.minor}.ext
Example: Revenue_Invoices_LineItems_Global_USD_20250731_v1.2.csv
Include: extract date, time zone, perimeter (organic vs. total), currency, and version.
Change log: who changed what and why; list added/removed fields, filters, and corrections.

Required metadata & provenance (top of every file or a sidecar .txt)

System of record, owner, extract timestamp and time zone.
Definition of key metrics/dimensions (e.g., “Active,” “Churn,” “Order,” “Shipment,” “Invoice,” “Seat,” “Unit”).
Perimeter notes (exclusions, discontinued SKUs, non‑core entities).
FX policy and constant‑currency assumptions where applicable.
Data refresh cadence and next planned drop.

Data formats & hygiene standards

Formats: CSV/XLSX/Parquet; JSON/NDJSON acceptable for logs; PDFs only for signed documents.
No merged cells, hidden columns, or macros; one header row; one record per row; UTC timestamps or a stated local time zone.
Keys and joins: unique IDs for customers, orders, invoices, shipments, tickets; provide crosswalks and maintain referential integrity.
Missingness and duplicates: missing critical fields <1%; duplicates <0.5%; document any known gaps.
Quality checks: totals reconcile to GL (revenue/CM1/CM2/cash); test sums vs. dashboards; sample 30–60 records to source screens.
Integrity: supply checksums (e.g., MD5/SHA‑256) for large files; avoid zipped files >1 GB—split logically and label parts.

Time windows, grain, and segmentation

Time coverage: minimum 36 months + YTD by month; 24 months by weekly/daily grain where available (orders, invoices, tickets, shipments, usage).
Cuts: always include product family, route‑to‑market, region/country, customer tier; add channel/partner, marketplace, and cohort period where relevant.
Snapshots vs. events: deliver event‑level where possible (e.g., each invoice line, each RMA, each ticket) and a monthly snapshot for ARR/NRR and inventory.

Clean‑team, PII, and antitrust guardrails

Red/Amber/Green data classes:
Green (shareable): aggregated by segment; anonymized line items with hashed IDs; public policies.
Amber (clean‑team only): row‑level customer transactions, detailed price/discount logs, partner‑level settlement.
Red (prohibited pre‑close): named customer pricing alongside competitive strategy, individual rep performance, non‑public competitor data.
Pseudonymization: hash customer and individual IDs; mask emails/domains; share geography at city‑or‑higher level unless needed.
Privacy & security: DPAs, SCCs/TIAs for cross‑border transfers; HIPAA/PCI scope statements; data minimization and retention plan; access log export at close.
Antitrust: no joint pricing/market allocation planning; scripts for any joint customer interactions pre‑close.

Core datasets & exact field lists (provide these verbatim)

Revenue & customers (ERP/Billing/CRM)

Invoices & credit memos: invoice_id, invoice_line_id, order_id, customer_key (hashed), booking_date, invoice_date, sku_id, sku_name, quantity, list_price, on_invoice_discount, off_invoice_discount/rebates, fees/penalties, taxes, net_revenue, currency, salesperson_id (hashed), channel, region, terms, due_date, payment_date, write‑off_flag, credit_memo_id, reason_code.
ARR/NRR roll‑forward (SaaS): start_ARR, new, expansion, contraction, churn, reactivation, end_ARR by cohort/segment; logos and seats/usage counts (hashed).
Pipeline/bookings (CRM): opportunity_id, stage, amount, product, source, open/close dates, outcome, reason_code, competitor.
Price waterfall audit: list, fences, standard discount, promo, rebates, pocket price, realized price.

Channels & marketplaces

Settlement files: order_id, sku_id, gross, fees by type (take‑rate, FBA/fulfillment, advertising), chargebacks/claims, returns, net payout, payout_date; policy metrics (OTIF, late‑ship, return rate, claim ratio).
Partner contracts: tiers, MDF, commission grids, parity and exclusivity clauses, termination/notice periods.

Cost‑to‑serve & operations

Returns/RMA: rma_id, order_id, reason_code, disposition, recovered_value, reverse_log_cost, refurb_cost, time_to_refund.
Parcel/carrier invoices: shipment_id, carrier, zone, weight, DIM, base_rate, fuel, accessorials (by type), total; service level and on‑time flag.
Payment processing: settlement_id, processor, method, fees (interchange + markup), reserves/holdbacks, chargeback count $ and reasons; fraud/risk decisions.
Support/service desk: ticket_id, channel, topic, first_response_time, handle_time/minutes, resolution, CSAT, refunds/credits issued.
Warranty/quality: defect codes, returns within warranty, repair cost, replacements, field failure rate.

Technology & cloud

Cloud cost & usage (CUR or equivalent): account, service, usage_type, usage_quantity, blended/unblended_cost, reservation/commit coverage, egress, region.
API/provider usage: calls, plan, overages, throttling; cost per call.
Reliability: incident log (start/end, severity), p95 latency series, uptime, SLA credits paid, error‑budget burn.
Security & privacy: SOC2/ISO reports, pen test summaries, vulnerability backlog, DPIAs, RoPAs, breach notifications (if any).

Supply chain & procurement

BOMs and component costs; supplier rate cards and rebates; PO lines with lead times; duty/tariff schedules; inventory transactions and valuations; network maps (plants/DCs/carriers).

Financials & working capital

GL trial balance and mapping to management P&L; revenue recognition memos; AR/AP agings with dispute/reason codes; inventory ledger and costing method; bank statements; debt agreements and covenant calculations; borrowing‑base certificates.

Regulatory, legal & ESG

Licenses, certifications/attestations (e.g., HIPAA, PCI, CE/UL, FedRAMP/StateRAMP, EPR registrations), audits and expiry dates; privacy policies; environmental metrics (energy, emissions scopes if available), packaging/EPR fee history and forecasts.

HR & incentives (no PII)

Org charts; role counts and fully loaded cost by function/region; sales comp plans and DOA matrices; quota coverage; retention/attrition metrics in aggregate.

Integration & TSA

Systems inventory, data flows, interfaces, entitlements/billing catalog, CPQ configuration, identity/SSO footprint; TSA scope, SLAs, pricing, and exit milestones.

Evidence registry (link sources to the model and deck)

For each exhibit/number in the deck: source code (S1…Sn), file path, extract date, system of record, model assumption cells touched, QC checks passed, owner, confidence (H/M/L).

Refresh cadence & change control

Refresh calendar: weekly window with a posted time (e.g., Wednesdays 17:00 UTC).
Delta files: only changes since last drop, with both adds and deletes flagged; maintain stable IDs.
Freeze windows: lock data two business days before IC or lender meetings.
Version bump rules: increase major when structure changes; minor for data refresh; restamp model if numbers move.

Q&A process & SLA

Routing: each folder has an owner; questions auto‑route; legal reviews gate anything in Amber/Red classes.
SLA: initial acknowledgment within 24 hours; complete response within 48 hours or date certain.
Evidence requests: allow anonymized samples for clean‑team review (e.g., 30 invoices, 30 returns, 30 tickets).
Audit trail: keep a Q&A export in the VDR; summarize unresolved risks weekly.

Industry‑specific addenda (include where relevant)

SaaS/data: entitlement/billing accuracy reports, tenant migrations, usage telemetry, marketplace private‑offer logs, SSO/IAM maps; ARR policy memos.
Fintech/payments: scheme rules, processor agreements, reserve/holdback policies, fraud vendor contracts, PCI scope and ROC/AOC.
Healthcare/life sciences: QMS (cGMP/ISO13485), device labeling/UDI, clinical/real‑world evidence claims controls, HIPAA BAAs.
Retail/CPG & marketplaces: planograms, OTIF dashboards, returns triage, paid placement spend logs, brand registry, GS1/GTIN ownership.
Industrial/field service: warranty terms, installed base by asset, field service routes, safety and certification registers.
Public sector: accreditation packages (FedRAMP/StateRAMP/IRAP), data residency attestations, subcontracting clauses.

Pre‑upload quality checks (seller‑side)

Numbers tie: last actual month in model equals ERP/GL; LTM reconciled; bridges foot to price/volume/mix/CTS/working capital.
Completeness: every checklist line above either posted or marked “N/A” with rationale.
Data quality: missingness, duplicates, referential integrity within thresholds; random record audit back to source screens.
Legal: clean‑team redactions/pseudonymization applied; privacy/sector controls documented; no competitor‑sensitive content.
Accessibility: filenames readable; documents searchable; scanned PDFs OCR’d; no password‑protected files inside the VDR (use VDR access controls instead).

README and definitions present; change log current; model version in deck matches VDR extract dates.
Evidence registry exists and maps to driver cells; spot‑check two numbers to raw rows.
Clean‑team scope and roster approved by counsel; access permissions reflect data classes.
Q&A board live with owners; 48‑hour SLA confirmed.

Red flags—and immediate fixes

Only dashboards/PDFs; no raw data. Fix: request CSV/XLSX extracts and a data dictionary; freeze analysis until provided.
Invoices lack discount/fee detail; returns lack reason codes. Fix: request full price waterfall and RMA fields; annotate gaps and haircut realized price/CM2 in the model.
Marketplace files missing fee breakdown or policy dashboards. Fix: require settlement detail and policy metrics; apply take‑rate risk haircuts.
Cloud bills summarized (no CUR) or API overages absent. Fix: request CUR/line‑item usage and provider plan terms; run FinOps baselines.
Privacy/antitrust exposure (named customers with sensitive pricing outside clean‑team). Fix: quarantine folder; re‑post anonymized/hard‑masked files; document incident.
No GL tie‑out or ARR roll‑forward that doesn’t foot. Fix: halt underwrite; schedule a reconciliation session; downgrade model confidence and widen ranges.

72‑hour sprint plan to stand up a decision‑grade VDR (seller‑side)

Day 0: Publish folder tree, README, definitions, clean‑team protocol, and change log; load financials (GL, TB, revenue policy) and invoice/credit/RMA extracts.
Day 1: Post pricing (books, fences, promos), CRM pipeline/win‑loss, channel settlement and contracts, parcel/carrier and payment processor files, support tickets; add evidence registry shell.
Day 2: Add cloud/CUR and API usage, reliability/security packs, procurement/supplier and inventory ledgers, regulatory/ESG and certifications, TSA and systems maps.
Day 3: Reconcile last actuals and LTM; run QC; label gaps as “N/A” with rationale; open Q&A and set the 48‑hour SLA.

72‑hour sprint plan to validate a VDR (buyer‑side)

Day 0: Confirm security, permissions, and clean‑team scope; download evidence registry; tie two deck numbers to raw rows; post initial Q&A.
Day 1: Reconcile revenue/CM1/CM2 to GL; ARR roll‑forward to contract/event data; price waterfall to invoices; parcel and cloud costs to provider bills.
Day 2: Validate returns/chargebacks, processor reserves, and support minutes/contact; test scenario inputs (demand indicators, take‑rate policies, fuel/FX).
Day 3: Log residual gaps; update model confidence; set refresh requests and cadence; align on term‑sheet protections for data‑proven risks.

Acceptance criteria for a decision‑grade data room

All core datasets above are posted in machine‑readable form with metadata, definitions, and extract dates; files reconcile to GL and policy memos.
Clean‑team/antitrust/privacy protocols are documented and enforced; sensitive data is anonymized or restricted.
Evidence registry maps each deck/model number to a source file, field, and row; a second person can reproduce any figure in ≤3 clicks.
Q&A is staffed with a 48‑hour SLA; change control is active with versioned refreshes and deltas.
Gaps and exceptions are explicitly labeled with impact on ΔCM2, ΔCash, and headroom and are priced into the model.

Use this checklist to turn the VDR into a decision engine: one taxonomy, one set of definitions, one evidence registry, clean raw data tied to the model, and legally sound protocols—so committees can underwrite with speed and confidence, and operators can act on Day 1.

18.3 Client Read-Out Facilitation Guide

A great read‑out converts analysis into a decision, with clear terms and Day‑1 actions. Your audience is busy and skeptical; they want an answer‑first, cash‑first narrative tied to the model—not a tour of work. Facilitation matters as much as content: the way you open, pace, navigate the model, handle objections, and close determines whether the room underwrites the recommendation or leaves with homework. This guide gives you a practical, repeatable way to run a decision‑grade read‑out in any setting—IC, lenders, or strategic buyers—without losing control of time, scope, or legal guardrails.

Outcomes to lock before you present

You should walk in knowing exactly what you want the room to do. Define the outcomes in one sentence each and keep them in sight on your first slide and your notes.

A buy/price/terms decision (or a dated decision plan with explicit conditions precedent).
Agreement on ΔCM2, ΔCash, and quarterly covenant headroom within the hold period.
Approval of the 90‑day value‑capture actions (owners, dates, acceptance tests).
Agreement on residual risks, reserves, and term‑sheet protections.
Alignment on integration gates (what must be true before each dollar lands).

Roles you must staff (and what each person does)

Lead Presenter (one voice): owns the story spine; opens answer‑first; manages time and transitions.
Model Navigator (“number runner”): drives the live model on request, with a read‑only copy and named toggles; never edits core assumptions live.
Workstream SMEs: pricing, GTM, CTS/ops, tech/FinOps, regulatory; each speaks only to two or three pre‑agreed claims.
Scribe: captures decisions, conditions, asks, and follow‑ups in real time; maintains the parking lot.
Timekeeper/Chat Monitor: watches the clock, the chat (virtual), and signals when to move on.
Legal/Compliance Liaison: interjects if a clean‑team, antitrust, platform‑policy, privacy, or sector rule is at risk.

Default run‑of‑show (adapt to 60, 90, or 30 minutes)

Opening (3–5 min): recommendation, price/terms, Year‑1/Year‑2 ΔCM2, ΔCash, minimum headroom by quarter, and the three reasons that move cash.
Market & unit economics (10–12 min): scenario fan for demand; pricing waterfall and CM1→CM2 bridge; sensitivity to price/returns/freight/cloud.
GTM, channel, capacity (8–10 min): funnel diagnostics, CAC payback, channel mix, capacity ladder and SLO guardrails.
Forecast & scenarios (6–8 min): base vs. downside vs. managed response; cost of action; quarterly headroom path.
Risks & terms (6–8 min): Cash‑VaR heat‑map, triggers, residual risk and reserves; term‑sheet translations.
Value capture & 90‑day plan (6–8 min): dated actions, owners, acceptance tests; integration gates.
Decision and next steps (5 min): restate the ask; confirm decisions, conditions, owners, and dates.

For a 30‑minute session, deliver the opening and three proof pages (unit economics, scenarios/headroom, risks/terms), then the decision. For a 90‑minute session, add deep‑dive exhibits only for exposures that move ≥2% revenue or ≥100 bps CM2.

Pre‑wire the room (the day before matters more than the day of)

Map stakeholders: deciders, recommenders, influencers, potential spoilers; note their likely concerns (price power, lender headroom, platform policies, integration risk).
Pre‑brief 1:1: share the executive summary and the ten‑page spine; test the toughest claim with each skeptic and capture their “must‑see” evidence.
Align expectations: circulate the agenda, model version stamp, definitions (realized price, CM2, headroom), and clean‑team scope; confirm time box and decision ask.
Dry run: rehearse hand‑offs, teach the Navigator the toggle names, pressure‑test the top five tough questions, and practice the closing script.

The hour‑before, ten‑before, and first minute

60 minutes before: freeze deck and model version IDs; load back‑pocket exhibits (pricing waterfall, CM2 bridge, scenario fan, tornado, risk heat‑map, integration gates, term‑sheet grid).
10 minutes before: test audio/video; confirm screen‑share; open a read‑only model; place the decision line in your presenter notes; assign a chat monitor.
First minute script: “We’ll recommend [buy at $X with Y terms]. In Year‑1 that yields ΔCM2 $A and ΔCash $B, with min headroom ≥ H bps across scenarios. I’ll prove that with unit economics, execution capacity, and risk protections. We’ll leave five minutes at the end to confirm decisions and owners.”

Facilitation techniques that keep control without being rigid

Answer‑first, then proof: state the claim with the number; show one bridge or fan; pause for a beat; ask “Does anyone need more on this before we move on?”
Use the parking lot: when a deep dive won’t move the decision, park it with an owner and a date.
Narrate transitions: close each section with one sentence that sets up the next (“Price power is real, so now let’s test the headroom path if demand turns.”).
Time checkpoints: call out a halfway and five‑minute‑remaining checkpoint; adjust pace explicitly.
Names, not departments: assign actions to people, not functions.
No orphan charts: if a page doesn’t change a decision, it lives in the appendix.

Read‑only first: open a protected copy with toggles mapped to named drivers (price bps, attach, conversion, returns %, parcel/cloud $/unit, take‑rate bps, minutes/contact, DSO/DIO/DPO, processor reserves).
Standard shocks: show sensitivity using pre‑built “+/−” buttons from Chapter 14.3; avoid free‑typing new assumptions live.
Scenario switches: flip between baseline, recession, stagflation, and exposure cases; always display ΔCM2, ΔCash, and quarterly headroom and the cost of action.
Guardrails: if a requested change exceeds observed evidence or capacity rungs, say so and log it as an offline what‑if.

Handling objections and difficult questions (scripts you can use)

“Your realized price lift is optimistic.”
“We’re not moving list prices; we’re tightening fences. The invoice audit shows +80–120 bps in segments A/B with no churn delta in VoC. Here’s the waterfall and the cell we move in the model. Want me to show the −50 bps downside elasticities band?”
“Show me how we avoid a covenant breach on the downside.”
“In the passive p10, headroom bottoms at X bps in Q3. With the pre‑approved actions (parcel re‑bid, returns triage, reserved coverage) we keep ≥H bps; the cash cost is $Y. Let me flip to ‘managed response’ and the headroom path.”
“I want to see the customer‑level pricing pre‑close.”
“We can’t share named customer pricing under clean‑team rules. We can show anonymized invoice samples and the aggregate waterfall, and we’ve loaded an evidence pack in the data room. If needed, counsel can expand clean‑team scope.”
“Why not more synergy?”
“The integration gate is billing/entitlement ≥99.5% accuracy and certification X. Dollars beyond that are upside‑only until gates clear. We’d rather bank what lands in the hold period.”
“Please change the model to 15% growth.”
“Happy to show the scenario band. For any new assumption outside our evidenced range, we’ll log it and return with a labeled “what‑if so we don’t anchor on unproven edits.”

Legal and policy boundaries to enforce in the room

Clean‑team and antitrust: no pre‑close joint pricing, customer allocation, or vendor negotiation; use aggregated/anonymized data only.
Platform and marketplace policies: do not discuss tactics that could trigger penalties or violate parity rules.
Privacy and sector rules (e.g., HIPAA/PCI): no PII or PHI; reference SOC/ISO, DPIAs, and RoPAs instead.
When a boundary risk appears, pause and invite legal to confirm the permitted scope.

Virtual and hybrid delivery tips

Keep one shared deck and one designated screen‑sharer; disable participant annotation.
Use a chat monitor to catch questions without interrupting flow; answer in voice at section breaks.
Call on silent decision‑makers by name; avoid letting the loudest voice set the agenda.
Record decisions live in a visible “Decision & Actions” pane to reduce ambiguity.
Have a fallback channel (dial‑in or phone bridge) in case conferencing fails.

Back‑pocket exhibits you should always have loaded

Pricing waterfall to realized price (with invoice and settlement audit references).
CM1→CM2 bridge by segment/channel.
Scenario fan (base, recession, stagflation) and quarterly headroom path.
Sensitivity tornado with the top five drivers and break‑even thresholds.
Risk heat‑map with Cash‑VaR, residuals, and reserve levels.
Integration feasibility gates and TSA exit milestones.
Term‑sheet translations mapped to residual risks.
90‑day value‑capture plan with owners and acceptance tests.

Decision capture and explicit close

Close with a clear, verbal commitment and read‑back. Then confirm owners and dates.

“To confirm: we’re proceeding at $X EV with [terms]; we accept the 90‑day plan; and we set [conditions precedent]. [Names] own [actions] by [dates]. We will issue the decision note and updated model after this meeting.”

Red flags in the room—and how to respond

Time hijack by a deep dive that won’t change the decision. Park it; return to the spine; offer a breakout.
Model mismatch with an exec’s mental math. Flip to the bridge or tornado; narrate drivers; avoid editing core assumptions live.
Definition fights (e.g., ARR vs. revenue, realized price vs. list). Flash your metric dictionary; reconcile quickly; move on.
Clean‑team creep. Pause and ask legal to restate permitted scope; revert to aggregated proof; note any expanded scope as a post‑meeting action.
Decision deferral with no conditions. Propose a dated decision plan with specific gates, owners, and the exact proof required.

After the read‑out: what must be in the wrap‑up pack

Decision note with price/terms, ΔCM2, ΔCash, headroom path, and conditions precedent.
Action log with owners, dates, acceptance tests, and dependencies.
Updated model and the deck with the model version stamp.
Q&A log with parked items and promised evidence (data‑room links).
Risk and reserve updates; term‑sheet draft changes and negotiation plan.

Day‑before and day‑of checklists

Day‑before

Pre‑wire deciders and skeptics; secure “no surprises” on the top two claims.
Freeze definitions, segmentation, and model version; reconcile last actuals and LTM.
Load back‑pocket exhibits; rehearse tough questions; validate legal boundaries.

Day‑of

Verify audio/video, screen share, and backup dial‑in; open read‑only model.
Print or pin your opening and closing scripts; confirm role assignments.
Start on time; state the decision and numbers in minute one; keep time checks.

Audience‑specific facilitation notes

PE Investment Committee: keep to 10–12 pages; emphasize ΔCM2/ΔCash, headroom, residual risks, and terms; limit synergy to hold‑period dollars.
Lenders/Credit Committee: spend more time on passive vs. managed downside, 13‑week cash, covenant math, borrowing‑base mechanics, and reserve policy.
Strategic buyers: add integration posture (Fuse/Federate/Interface), customer/brand risk, and option value; still anchor on the first 24 months of cash.

Opening, reset, and closing scripts (use verbatim if helpful)

Opening: “Our recommendation is [buy at $X with Y terms]. That drives ΔCM2 $A and ΔCash $B in Year‑1, with min headroom ≥ H bps across scenarios. We’ll prove it with unit economics, execution capacity, and risk protections.”
Mid‑meeting reset: “We’re 30 minutes in, two pages left before the decision. If we go deeper here, we will slip the decision. May I propose we park this and return to the headroom path?”
Closing: “Before we adjourn: are we aligned on [price/terms], the 90‑day actions, and these [conditions precedent]? [Name] will circulate the decision note and updated model.”

72‑hour facilitation sprint (from draft deck to decision)

T‑72 to T‑48: pre‑wire stakeholders; rehearse; finalize the ten‑page spine; align legal guardrails; ready back‑pocket exhibits.
T‑24: dry run with the exact team and roles; pressure‑test top five questions; freeze model version and definitions.
T‑0 to T+2 hours: deliver the read‑out; capture decisions and actions live; send the decision note, updated model, and Q&A log.
T+24: close parked items per the action log; update the value‑capture roadmap and term‑sheet drafts if needed.

Acceptance criteria for a high‑performing read‑out

The meeting opens with a clear buy/price/terms statement and quantified ΔCM2, ΔCash, and headroom, all tied to the current model version.
The story spine follows the Pyramid Principle; each page changes a decision and ties to named model drivers.
Time is controlled; deep dives that don’t change the decision are parked with owners and dates.
Live model navigation shows standard scenarios and sensitivities without free‑typing assumptions.
Legal and platform guardrails are observed; no PII or prohibited pre‑close coordination.
Decisions, conditions precedent, and 90‑day actions are captured with owners and dates and circulated the same day.

Run your read‑out with this discipline and you will replace debate with decisions: a crisp answer‑first narrative, model‑anchored proof, controlled Q&A, and a visible path from recommendation to cash.

18.4 Post-Mortem Review Template

A post‑mortem is where diligence becomes a learning system. Its goal is not to relitigate decisions but to convert what happened—good or bad—into tighter hypotheses, cleaner models, faster execution, and clearer terms on the next deal. Treat it as you would a safety investigation: blameless, fact‑rich, driver‑anchored, and relentlessly practical. The outputs are concrete: a dated action list, updates to this playbook, reusable assets, and a one‑page memo that improves your next IC outcome and your first 90‑day value capture.

Principles that keep the review honest

Blameless and specific. Focus on facts, drivers, decisions, and constraints. No personal attribution.
Cash‑first. Analyze ΔCM2, ΔCash, and quarterly headroom impacts, not just activity.
Model‑anchored. Every observation links to named driver cells in the forecast model and to evidence in the data room.
Comparable. Use a standard taxonomy, time windows, and metrics so results travel across deals.
Action‑biased. Each finding ends with a countermeasure: prevent, detect, or respond.

Scope and timing (use this cadence)

Rapid debrief (≤72 hours after read‑out or close): facts timeline, early wins/gaps, immediate fixes.
Structured post‑mortem (within 10 business days): full metrics, root‑cause analysis, preliminary actions.
30‑day deep dive (optional, for material gaps): complex root causes (data architecture, marketplace policy, billing/entitlement, integration gates), confirmed countermeasures, and playbook updates.

Who participates (and why)

Sponsor and Investment Lead: decision context and terms negotiation.
Engagement Lead and Model Owner: assumptions, sensitivities, and reconciliation.
Workstream leads: market, VoC/pricing, GTM, CTS/ops, tech/FinOps, regulatory/ESG, finance/WC.
Risk & Treasury: VaR, reserves, headroom.
Legal/Compliance: clean‑team, antitrust, privacy, platform policies.
Client counterpart or IMO lead (where appropriate): integration feasibility and Day‑1 realities.
Independent reviewer: challenges logic, confirms reproducibility.

Inputs to assemble before you begin

Final deck and appendix with model version stamp and perimeter notes.
Driver‑based model with scenario and sensitivity sheets, QA log, and change history.
Evidence registry mapping deck numbers to data‑room files.
Risk register, Cash‑VaR heat‑map, triggers, and mitigation playbooks.
Value‑capture roadmap and integration gates; TSA scope if relevant.
Term sheet and mark‑ups; covenant math; 13‑week cash view if produced.
Meeting decision log, Q&A log, red‑flag cards, and RAID items.

Post‑mortem agenda (copy this flow)

Outcomes vs. thesis
- What we recommended (buy/price/terms), the dollars underwritten, and the required conditions precedent.
- Where we landed: price and terms variation, headroom, reserves, and client/credit committee feedback.
Model accuracy and forecast quality
- Reconciliation of first forecast month to last actuals and LTM.
- Scenario weights vs. observed reality; sensitivity coverage vs. sources of variance.
- Break‑even thresholds and whether decisions respected them.
Evidence quality and data room hygiene
- Reproducibility checks (≤3 clicks from driver cell to data row).
- Missingness, duplicates, and referential integrity issues; impact on ranges/haircuts.
- Clean‑team boundaries and whether they slowed or distorted analysis.
Insight quality and story spine
- Which insights changed the decision; which were expensive but non‑decisive.
- Proof density per insight (triangulation) and falsification attempts.
- Read‑out control: time, Q&A drift, page utility.
Risk governance
- Early‑warning indicators that fired (or didn’t), trigger‑to‑action execution time, VaR actually removed.
- Residual risk accuracy and reserve sufficiency.
Execution and governance mechanics
- Cadence adherence; decision latency; critical path slips; hand‑offs; escalation paths.
- Tooling and version control issues (model, deck, VDR).
Client and counterparty experience
- NPS or qualitative feedback; trust markers (access, speed, clarity).
- Term‑sheet dynamics: protections won/lost and why.
Integration feasibility realism
- Gate acceptance tests (billing/entitlement accuracy, certifications, SLO headroom) vs. promises in the deck.
- TSA scope realism and exit plans.
People, capacity, and health
- Skill‑to‑task fit; coverage gaps; rework; burnout signals; learning needs.
Decisions and actions

Start/stop/continue list; owners; dates; acceptance tests; updates to the playbook.

Metrics library and formulas (compute these the same way every time)

Model & forecast quality

WAPE (weighted absolute percentage error) on Year‑1 ΔCash and ΔCM2: sum of absolute errors divided by sum of actuals.
Bias (mean error) for top five drivers: average of (forecast − actual) at the driver unit (e.g., bps, $/unit, pp).
Scenario hit rate: percent of cases where realized macro/channel conditions matched the chosen base/downside trigger rules.
Sensitivity coverage index: share of top‑five tornado drivers tested with ± standardized shocks before IC.

Evidence & reproducibility

Proof density: average independent sources per P0 insight (e.g., VoC + invoice audit + parcel bill).
Reproducibility rate: share of sampled numbers that a second person reproduces from model cells in ≤3 clicks.
Data readiness SLA: percent of evidence requests met within 48 hours; average days to reconcile last actuals to GL.

Story and decision efficiency

Page utility: share of spine pages that changed a decision (P0/P1 vs. P2).
Decision velocity: hours from red‑flag sighting to haircut in the model; hours from trigger to playbook launch.
Read‑out control: deviation from agenda time; count of parked topics resolved within 72 hours.

Risk & reserves

Cash‑VaR delta: pre‑ vs. post‑mitigation VaR; ROI of mitigations (VaR reduction divided by mitigation cost NPV).
Headroom‑at‑Risk (HaR): minimum quarterly headroom at p10 vs. buffer; breach probability.
Coverage index: share of portfolio Cash‑VaR protected by drilled playbooks with tested triggers.

Value capture & integration

Dollar realization ratio: underwritten dollars with gates that cleared inside the planned window divided by total underwritten dollars.
Gate pass rate: percent of cutovers meeting acceptance tests on first attempt (billing ≥99.5%, DR tested, SLO headroom).
TSA exit performance: exits on or before plan; cost variance.

Client & team health

Client NPS or proxy; decision maker satisfaction on clarity and speed.
Rework ratio: hours on redo divided by total hours; root cause tags (scope, data, model, story).
Capacity adherence: squads with ≤3 concurrent initiatives; overtime or burnout signals.

Root‑cause analysis—use this standard method

Facts timeline: reconstruct dated events, decisions, and artifacts; avoid retrospective assumptions.
Five Whys (bounded to 3–5): push beyond the first‑order cause to the process/assumption/tool level.
Ishikawa/Bow‑Tie: categorize causes under Data, Scope, Assumptions, Method, Governance, Tools, People, Client, Legal/Policy; pair preventive with responsive controls.
Countermeasure design: for each root cause, specify a control that (i) prevents recurrence, (ii) detects early, or (iii) reduces severity—with owner, budget, and acceptance test.

Taxonomy for tagging findings (pick one primary and one secondary)

Data/VDR, Definitions, Modeling, Scenarios, Pricing/VoC, GTM/Funnel, CTS/Ops, Tech/FinOps, Regulatory/ESG, Risk/Reserves, Integration/TSAs, Governance/Cadence, Story/Read‑out, Terms/Negotiation, Legal/Compliance, People/Capacity, Client/Stakeholder.

Copy‑ready templates (paste these into your workspace)

A) Post‑Mortem Agenda & Roles

Purpose and scope; date; attendees and roles (Sponsor, Engagement Lead, Model Owner, Workstream Leads, Risk/Treasury, Legal, Client/IMO, Independent Reviewer).
Decision log number and model version stamp.
Time blocks: Outcomes vs. thesis; Model & evidence; Risk; Execution; Client; Decisions & actions.

B) Facts Timeline Card

Event/date/time; artifact (deck/model/VDR/Q&A); decision taken; trigger/threshold crossed; owner; immediate effect on ΔCM2, ΔCash, or headroom.

C) Findings Card (one per issue or win)

What happened and why it matters (driver and dollar impact).
Root cause(s) tagged using the taxonomy.
Evidence links (model cells, VDR files, exhibits).
Countermeasure (prevent/detect/respond), owner, budget, acceptance test, due date.
Confidence label (H/M/L) and residual risk.

D) Metrics Summary Sheet

Populate the metric set above for this deal; list exceptions and data gaps; include a one‑paragraph interpretation.

E) Start/Stop/Continue List

Start (new practices), Stop (wasteful or risky behaviors), Continue (worked well).
Owners and dates for each Start/Stop item.

F) Playbook Update Ticket

Section and subsection (e.g., 9.1 Funnel Diagnostics).
Current guidance vs. proposed update.
Triggering finding and evidence.
Impact on future ΔCM2/ΔCash or risk.
Owner and due date; cross‑references to templates/checklists.

G) Knowledge Pack Index

Reusable assets to archive: survey guides, interview scripts, pricing waterfall SQL, parcel/cloud audit notebooks, scenario sheets, integration gate checklists, term‑sheet clause library.
Storage path and version tag; data privacy review completed; anonymization status.

Checklists by phase (use during the review)

Kick‑off and scope

Were initial hypotheses tied to model drivers and decision thresholds?
Did the scope align to the buyer’s mandates and legal guardrails from day one?

Workplan and governance

Did the cadence (stand‑ups, risk reviews, IC pre‑wires) run on time?
Did critical path items slip, and how early did we see it?

Data & VDR

Was the evidence registry complete and fresh?
Could a second person reproduce headline numbers in ≤3 clicks?
Clean‑team scope clear and followed?

Market & sizing

Were TAM/SAM/SOM definitions consistent with the go‑to‑market and model segmentation?
Did we reconcile bottom‑up and top‑down and publish a variance note?

VoC & pricing

Did we test elasticity bounds and realized price fences with invoice audits?
Was the interview/survey sample representative of the revenue mix?

GTM & channels

Were funnel definitions standard; did CAC payback meet guardrails in base and downside?
Marketplace policies and penalties fully costed?

CTS & operations

Did we quantify returns, freight, payment fees, support minutes/contact and tie them to CM2 bridges?
Capacity rungs booked; SLO floors respected?

Tech & digital

FinOps savings modeled as unit drivers; reliability/SLA credits reflected?
Security/privacy posture verified; no adjacent surprises (e.g., data residency)?

Financials, scenarios, and risk

First forecast month equals last actuals; LTM tied to GL; working‑capital logic consistent.
Scenario fans, tornado, and break‑even thresholds published; risk triggers and playbooks drilled.

Synergies & integration

Dollars contingent on gates labeled upside‑only until acceptance tests passed.
TSA scope priced with exits; stranded cost plan explicit.

Storylining & read‑out

One‑page executive summary answer‑first; page titles with numbers and verbs.
Decision capture and conditions precedent recorded live.

Red flags—and what to do when you find them

No GL tie‑out or ARR roll‑forward that doesn’t foot. Document, downgrade confidence, widen ranges, and add a mandatory reconciliation step to the template; create a SQL view or script and store it in the knowledge pack.
Dependency on unproven integration gates. Move dependent dollars to upside‑only; add gate acceptance tests to the integration template; update the “terms asks” library with conditions precedent.
Risk triggers without KRIs. Add the KRI to the dashboard, define persistence rules, and drill the playbook; update the risk template.
VDR full of PDFs and screenshots. Require machine‑readable extracts; update the seller‑side VDR checklist; add enforcement language to the NDA.
Overlong deck that doesn’t change decisions. Enforce the one‑page‑one‑message rule; add a page utility metric to the read‑out checklist.

72‑hour post‑mortem sprint plan

Day 0: Convene the rapid debrief; fix the facts timeline; lock model and deck version IDs; assign owners for metric computation and root‑cause threads.
Day 1: Populate the Metrics Summary Sheet; draft top five Findings Cards (wins and misses); list immediate countermeasures with owners and dates.
Day 2: Complete root‑cause analysis for the top issues; write Start/Stop/Continue; open Playbook Update Tickets; package the Knowledge Pack.
Day 3: Issue the one‑page post‑mortem memo, action log, and updated templates; schedule 30‑day deep dive if material risks remain.

One‑page post‑mortem memo (structure you can copy)

Headline: what changed cash/headroom, positively or negatively, in one sentence.
Three takeaways: each with a number (ΔCM2/ΔCash or VaR/HaR) and a countermeasure.
Two process fixes: governance/tooling or data improvements with owners and dates.
Terms implication: clauses to carry forward (indexation, reserve caps, certification CPs, earnouts).
Links: model version, evidence registry, action log, updated templates.

Acceptance criteria for a decision‑grade post‑mortem

Metrics computed and explained for model accuracy, evidence quality, story efficiency, risk coverage, and value capture; numbers traceable to driver cells and VDR files.
Root‑cause analysis completed for all material wins/misses with countermeasures (prevent/detect/respond), owners, budgets, and acceptance tests.
Action log issued with Start/Stop/Continue; playbook update tickets opened; knowledge assets archived and accessible.
One‑page memo circulated; client feedback captured; any term‑sheet learning documented.
Within 30 days (if invoked), deep dive closes out complex causes; templates and training updated.
A second person can reproduce any cited number in ≤3 clicks, and legal guardrails were observed throughout.

Use this template to make every diligence better than the last: the same drivers, the same math, the same disciplined storytelling—plus a tighter system of evidence, risk control, and execution that converts analysis into repeatable value.

Commercial Due Diligence Playbook >