Scenario 02

---
name: analyze-responses-to-ddrl-s02
task_id: corporate-ma/analyze-responses-to-ddrl/scenario-02
description: Guides cross-verification of seller responses to DDRL requests against the underlying diligence materials to identify inaccurate or incomplete characterizations, contradictions, and information gaps.
activates_for: [planner, solver, checker]
---

# Skill: Analyze Responses to DDRL (Scenario 02)

## 1. Subject-matter triage

- Treat the assignment as a response-by-response reconciliation exercise, not a narrative diligence summary.
- Start by identifying every DDRL request, every seller response, and every source document actually provided.
- If multiple facilities, customers, agreements, or periods are in play, enumerate them first and analyze each separately before drawing cross-cutting conclusions.
- Distinguish between a document that is responsive in form and a document that substantively answers the request.

## 2. Failure modes the skill is correcting

- Cataloguing which DDRL items received a response without verifying whether the response is accurate against the underlying diligence materials.
- Treating a cited attachment as dispositive when it does not actually satisfy the request.
- Missing the compounding effect of overlapping regulatory issues at the same site, especially where compliance, enforcement, and litigation concerns interact.
- Failing to test major customer relationships for change-of-control, expiration, and renewal risk where revenue concentration makes the issue material.
- Accepting associate status notes as conclusions rather than using them as starting points for independent verification.
- Overlooking that a partial response, delayed response, or “no issues identified” response can itself be a gap if the source set shows otherwise.

## 3. Legal frameworks / domain conventions that apply

- DDRL gap analysis requires cross-checking each response against the underlying record; a response that points to a document that does not answer the request is itself a gap.
- Materiality in diligence is driven by transaction context, concentration, and downstream effect, not by whether the seller provided some document.
- Financial statement characterization can matter where reviewed, compiled, and audited statements are conflated; verify the stated level of assurance against the actual report.
- Environmental and regulatory diligence should test notices, permits, orders, and correspondence for contradictions, expirations, or unresolved conditions.
- Customer concentration and contract diligence should examine governing terms that affect assignment, change of control, renewal, termination, and continuity of revenue.
- Where a regulatory issue and a litigation matter involve the same site, facility, or conduct, analyze them together because they may be interdependent.
- Labor diligence should confirm the existence or absence of collective bargaining obligations and test any cited enforcement history against source documentation.
- Insurance diligence should verify claims history, coverage limitations, and notice issues, not merely declarations pages.
- Related-party diligence should compare financial schedules, ownership disclosures, and operational materials for undisclosed arrangements.
- Where a legal proposition is invoked, identify the governing authority from the source materials or the standard authority ordinarily used for that topic.

## 4. Analytical scaffolds

1. Identify the request precisely.
   - Restate the DDRL item in functional terms.
   - Determine what type of proof would actually satisfy it.
   - Note whether the response is complete, partial, nonresponsive, or contradicted by the source set.

2. Cross-check the response against the source documents.
   - Compare seller characterization to the actual text, dates, signatures, exhibits, schedules, and attachments.
   - Verify whether quoted or summarized terms are complete and accurate.
   - Test whether the document covers the right entity, asset, period, or counterparty.
   - Flag internal inconsistencies, missing exhibits, stale copies, and mismatched dates.

3. Apply issue-specific diligence lenses.
   - Financial statements: verify assurance level, reporting period, and consistency across documents.
   - Environmental/regulatory: identify permit expirations, notices, citations, orders, and unresolved agency communications.
   - Major customers: test concentration, termination rights, assignment and change-of-control terms, renewal mechanics, and expiration.
   - Labor/employment: confirm collective bargaining status, wages, claims, and enforcement documentation.
   - Insurance: check whether the claims history and material exclusions were actually produced.
   - IP/licenses: test anti-assignment and change-of-control restrictions.
   - Related-party matters: compare disclosures across schedules, financial statements, and operational records.

4. Close each issue analytically.
   - State the scale of the issue using a source-document figure, term, period, exposure, or other concrete metric.
   - Cross-reference the interacting clause, schedule, or other document that changes the analysis.
   - Explain the downstream consequence for the transaction, including operational, regulatory, litigation, or closing risk.

5. Resolve overlap intelligently.
   - If the same fact pattern appears in more than one DD item, do not duplicate analysis mechanically; explain the interrelationship once and point to the affected requests.
   - If only one facility, contract, or counterparty is relevant, say so expressly and explain why.

## 5. Vertical / structural / temporal relationships

- Track whether the issue sits at the parent, subsidiary, facility, contract, or claim level.
- Track whether the relevant event is historical, ongoing, expiring, pending, or contingent.
- Track whether a response is stale as of signing, closing, or the document date.
- Where multiple documents address the same matter across time, reconcile the chronology rather than treating them as independent facts.
- When one issue affects another, state the direction of dependence and whether the secondary issue worsens, mitigates, or confirms the primary one.

## 6. Output structure conventions

- Produce a gap analysis memo organized by qualitative risk level using a defined ordinal scale stated once at the top.
- Include an explicit risk rating for every issue and apply the same scale consistently.
- For each issue, use a compact row or bullet that captures:
  - DDRL item reference
  - seller response characterization
  - actual underlying content
  - gap, contradiction, or incompleteness
  - risk rating
  - specific follow-up request
- Draft follow-up requests with enough specificity for formal diligence inquiry, including the precise record, period, or document sought.
- When multiple issues exist, present them in a numbered sequence and do not collapse distinct gaps into one umbrella point.
- End with a Recommended Actions block that assigns each action to a role and ties timing to the transaction or regulatory milestone.
- Use ordinary legal citations where a legal proposition is necessary; do not state a legal conclusion without naming the governing authority or standard.