Review Data Room Red Flag Review

---
name: review-data-room-red-flag
task_id: corporate-ma/review-data-room-red-flag-review
description: Guides preparation of a data room red flag memorandum for an acquisition where a large, heterogeneous data room requires systematic review to identify material risks requiring deal team attention.
activates_for: [planner, solver, checker]
---

# Skill: Data Room Red Flag Review

## 1. Subject-matter triage

- Treat the assignment as a buyer-side red flag review, not a full diligence report.
- Triage the data room into deal-relevant buckets before drafting: corporate, financial, tax, regulatory, environmental, customer/commercial, litigation, employment, IP/technology, debt/security, and governance.
- If the data room is broad, first enumerate the distinct risk-bearing workstreams you will review, then analyze each workstream once and only once.
- Prioritize documents that can change price, closing conditions, indemnity scope, reverse termination exposure, post-closing integration burden, or operating licenses.

## 2. Failure modes the skill is correcting

- The review describes documents one by one without synthesizing how separate documents interact to create a material risk pattern.
- Financial materials are accepted at face value without checking whether related operational, tax, debt, or covenant materials tell a different story.
- Regulatory, permit, and environmental materials are treated as background rather than as potential sources of closing conditions, remediation cost, or post-closing restrictions.
- Employment and workforce materials are reviewed generically without identifying dispute signals, misclassification risk, co-employment exposure, benefits issues, or key-person dependency.
- Debt and lien materials are reviewed in isolation without checking whether collateral packages, releases, consents, or payoff mechanics affect closing deliverability.
- Customer and contract materials are summarized without identifying concentration, termination, assignment, change-of-control, service-level, or pricing reset risk.
- The memorandum states problems but does not tie them to scale, cross-document support, and transaction consequences.
- The output lists concerns without a consistent severity ladder or concrete next steps.

## 3. Legal frameworks / domain conventions that apply

- A red flag memorandum is a risk-identification product: it should surface material buyer issues, not catalogue every diligence fact.
- Use a uniform ordinal severity scale and apply it consistently to each issue.
- For each issue, connect the risk to the governing legal or commercial rule implicated by the source set, such as permit requirements, environmental liability regimes, labor and employment doctrines, secured lending release mechanics, assignment/consent provisions, tax exposure rules, or corporate authority constraints.
- When a proposition depends on a legal rule, cite the controlling authority or doctrinal source by name and section, regulation, rule, or recognized authority as appropriate.
- Treat document hierarchy and specificity as important: signed agreements, schedules, certificates, notices, filings, and audit materials generally outrank summaries or oral explanations.
- In an acquisition context, the most important consequences are closing delay, purchase price adjustment, indemnity exposure, financing risk, post-closing remediation, and operational interruption.

## 4. Analytical scaffolds

- Start by listing the discrete issue areas you will evaluate; if only one category is in scope, say so explicitly.
- For each issue area, identify:
  - the triggering fact or disclosure,
  - the governing contractual, regulatory, or legal rule,
  - the magnitude or operational scale reflected in the source materials,
  - the cross-document corroboration or inconsistency,
  - the downstream buyer consequence,
  - the severity rating, and
  - the recommended action.
- Cross-check every financial, covenant, or compliance statement against related schedules, models, certificates, debt documents, and operational data.
- Cross-check environmental and regulatory disclosures against notices, agency correspondence, permits, audits, incident reports, remediation plans, and reserve or accrual information.
- Cross-check employment disclosures against offer letters, separation materials, staffing arrangements, benefits plans, and contractor classifications.
- Cross-check IP and technology materials against financing documents, liens, assignments, escrow arrangements, and change-of-control restrictions.
- Cross-check customer and commercial contracts against renewal terms, termination rights, consent requirements, concentration data, pricing obligations, and service commitments.
- Cross-check corporate authority and governance materials against charter documents, board/stockholder approvals, and cap table or ownership records.
- Synthesize patterns that emerge only when multiple documents are read together, such as a compliance issue paired with inadequate reserves, or a contract risk paired with revenue concentration.
- Keep the analysis buyer-oriented: ask whether the issue affects valuation, closing, deliverability, or integration, not whether the file is merely imperfect.

## 5. Vertical / structural / temporal relationships

- When multiple periods appear in the source set, compare them explicitly rather than blending them into a single narrative.
- When multiple counterparties, facilities, sites, permits, or material contracts appear, evaluate each separately before aggregating themes.
- Track whether a risk is historical, current, or forward-looking; state whether it is a one-time remediation item or an ongoing compliance obligation.
- Where chronology matters, identify whether a problem predates signing, arises at closing, or becomes a post-closing operational burden.
- If the data room reflects a sequence of notices, violations, amendments, waivers, or waivers-to-waivers, treat that sequence as evidence of trajectory, not isolated events.

## 6. Output structure conventions

- Produce a single red flag memorandum.
- Use a conventional memorandum shape: short executive summary, followed by issue sections grouped by topic, then a synthesis of cross-document patterns, then a concise Recommended Actions section.
- Open with a brief overall risk characterization and the most important buyer concerns.
- Define the severity scale once at the top, then apply it uniformly to each issue.
- For each issue entry, include: severity, issue title, source support, legal or commercial significance, scale or magnitude, cross-reference, consequence, and recommended action.
- Keep issue descriptions concise but complete; every issue should close the loop from facts to rule to consequence.
- Include citations to the source documents where useful, but do not quote internal text verbatim unless necessary to preserve meaning.
- End with a Recommended Actions block using imperative verbs, assigning each action to the relevant role or function, and anchoring timing to signing, closing, or another transaction milestone.
- If the record is sparse on a point, say that the point cannot be confirmed from the available materials and specify what document or clarification is needed.