Extract Environmental Liabilities From Target Disclosure Schedules

---
name: extract-environmental-liabilities-from-target-disclosure-schedules
task_id: environmental-esg/extract-environmental-liabilities-from-target-disclosure-schedules
description: Guides preparation of an environmental liability summary memorandum for an acquisition target by extracting and synthesizing disclosed liabilities from disclosure schedules, environmental site assessments, regulatory correspondence, and financial accruals.
activates_for: [planner, solver, checker]
---

# Skill: Extract Environmental Liabilities from Target Disclosure Schedules — Environmental Liability Summary Memo

## 1. Subject-matter triage

When the source set spans disclosure schedules, site assessments, agency correspondence, accrual support, and insurance materials, separate target-owned matters from third-party background materials before analysis. If multiple sites, entities, programs, or periods appear, enumerate them first and analyze each on its own terms; do not collapse distinct liabilities into one blended description. Treat any item not tied to the acquisition target as reference only unless the documents show a direct exposure link.

## 2. Failure modes the skill is correcting

- The memo restates schedule disclosures without testing them against site findings, notices, orders, accrual support, or insurance terms
- The memo treats the disclosure schedule as complete even where independent records indicate additional sites, programs, or obligations
- The memo describes environmental exposure qualitatively but does not anchor the issue to the size of the site, the status of the matter, or the cost range reflected in the record
- The memo ignores how one matter can interact with another document set, such as an indemnity, cleanup program, or regulatory deadline
- The memo lists issues without stating why they matter to price, closing risk, post-closing operations, or residual liability allocation
- The memo omits a concrete next step for counsel or the business team

## 3. Legal frameworks / domain conventions that apply

- Acquisition due diligence conventions governing environmental disclosures, schedule completeness, and the relationship between representations, exceptions, and indemnification
- Environmental site assessment practice, including recognized environmental conditions, historic uses, sampling limits, and the difference between observed condition and legal liability
- Regulatory enforcement conventions, including notices of violation, consent orders, cleanup directives, and voluntary program participation
- Contingent liability and accrual analysis, including the distinction between recorded accruals and the broader reasonable exposure range
- Environmental indemnity practice, including scope, survival, cap, basket, exclusions, and collectability
- Insurance coverage conventions, including whether existing policies may offset or exclude the identified matter
- Transactional risk allocation conventions, including escrow, special indemnity, closing condition, covenant, and purchase price adjustment tools

## 4. Analytical scaffolds

- Identify each disclosed environmental liability by site, entity, program, or project, then capture the disclosed status, stated cost, and stated driver
- Cross-check each disclosed item against other source documents for consistency in location, timing, responsible party, regulatory posture, and cost support
- Flag omissions where site assessments, correspondence, or financial records show a matter not reflected on the schedule
- For each matter, compare the recorded accrual or reserve to the underlying facts and the broader likely exposure range
- Test whether the matter is confined to the described site or whether the records suggest broader corridor, watershed, facility, or portfolio exposure
- Test whether existing indemnity or insurance actually reaches the matter, considering exclusions, caps, survival periods, notice requirements, and counterparty capacity
- For each identified issue, state the scale of the exposure, the source conflict or corroboration, and the practical consequence for the transaction

## 5. Vertical / structural / temporal relationships

- Disclosure schedule vs. independent record: a mismatch is not merely a drafting point; it can indicate incomplete disclosure or hidden exposure
- Assessment findings vs. enforcement posture: a site condition becomes more serious when paired with agency action, deadlines, or mandated cleanup
- Accrual vs. exposure range: a booked reserve is not a ceiling; assess whether the factual record supports a wider liability band
- Pre-closing vs. post-closing allocation: identify which liabilities are intended to transfer, remain with seller, or be carved out
- Current obligation vs. future trigger: some matters are dormant until a permit event, redevelopment plan, or agency review activates them
- Coverage or indemnity vs. collectability: a contractual right is only as useful as its scope and the counterparty’s ability to perform

## 6. Output structure conventions

- Draft a concise memorandum in industry-conventional form, using sections such as Executive Summary, Matter-by-Matter Analysis, Disclosure Gaps, Financial Adequacy, Risk Allocation, and Recommended Actions
- Define an ordinal severity scale once at the top and apply it consistently to each matter or issue entry
- For each matter, include: identification, source basis, consistency check, exposure scale, transaction consequence, and severity
- Where the source documents supply legal or regulatory authority, cite that authority by name and section or order identifier in the discussion of the matter
- Do not use a generic narrative where a row-based or bullet-based matter list would better preserve distinctions among sites, entities, or periods
- End with a Recommended Actions block that assigns each action to counsel, finance, operations, or another responsible role and ties it to a transaction or regulatory timing anchor
- If the task instructions require a named output file, ensure the final document is prepared under that filename exactly