Review Environmental Site Assessment

---
name: review-environmental-site-assessment
task_id: environmental-esg/review-environmental-site-assessment
description: Guides preparation of an environmental issues memorandum for a portfolio acquisition by integrating Phase I and Phase II findings across multiple properties and assessing the adequacy of transaction environmental protections for each site.
activates_for: [planner, solver, checker]
---

# Skill: Environmental Site Assessment Review — Issue Identification Memorandum for a Compressor Station Portfolio Acquisition

## 1. Subject-matter triage

When reviewing environmental diligence for a compressor-station acquisition, sort materials by site first, then by document type within each site. Treat each property as a separate factual record unless the source materials expressly connect them.

Enumerate the full site set before analysis. If only one site is in scope, state that expressly and explain why no portfolio comparison is needed.

Identify which sites have Phase I only, which have Phase II follow-on work, and which have both. Preserve the chain from Phase I condition to Phase II characterization so unresolved conditions remain visible as data gaps rather than being flattened into a generic risk summary.

## 2. Failure modes the skill is correcting

- Reviews each report in isolation and misses the portfolio-level risk picture, including which sites drive the transaction risk profile
- States Phase I recognized environmental conditions without testing whether Phase II work adequately characterizes them or whether further delineation is needed
- Fails to tie site findings to the compliance record for underground storage tanks and similar regulated systems commonly present at compressor stations
- Treats transaction protections as generic boilerplate instead of testing them against the actual site-by-site risk profile
- Describes an issue without naming the governing authority, the applicable standard, the severity, the cross-document interaction, and the practical consequence
- Omits an affirmative recommendation set, leaving the memo diagnostic only

## 3. Legal frameworks / domain conventions that apply

- ASTM Phase I ESA practice: recognized environmental conditions, historical use review, data gaps, and all appropriate inquiry concepts under 40 C.F.R. Part 312
- Phase II ESA practice: sampling scope, delineation, pathway analysis, and whether the investigation is sufficient to characterize the condition against the relevant cleanup benchmark
- Underground storage tank regulation: 40 C.F.R. Part 280 and applicable state tank rules for registration, release detection, integrity testing, closure, and financial responsibility
- Compressor-station contaminant profile: petroleum hydrocarbons, glycols, produced water constituents, and other operational chemicals that may be implicated by the source materials
- State cleanup and voluntary remediation regimes: applicable numeric standards, land-use assumptions, institutional controls, and reporting or cleanup triggers
- Transaction protection concepts: environmental representations and warranties, disclosure schedules, indemnity scope, conditions precedent, special escrows or reserves, and known-condition carveouts

## 4. Analytical scaffolds

- For each site, identify the investigation package, date, scope, and whether the record is Phase I, Phase II, or both
- For each Phase I condition, ask whether the follow-up work actually characterizes the issue; if not, label the remaining uncertainty as a live diligence gap
- For each Phase II result, compare the reported findings to the applicable cleanup standard or risk benchmark referenced in the materials, and note whether the source documents show exceedance, partial delineation, or closure
- For regulated tank systems, assess whether the record shows registration, leak detection, integrity testing, closure documentation, or other compliance markers required by the cited rules
- Cross-check internal or deal documents for statements that confirm prior knowledge, carvebacks, disclosure, insurance, escrow, or negotiated remediation responsibility
- For every issue, close the loop with: the site and source document, the governing authority or standard, the severity rating, the interaction with another document or site record, and the transaction or regulatory consequence
- Distinguish site-specific issues from portfolio-wide themes, such as repeated tank compliance weaknesses or repeated gaps in characterization
- If the source set provides no numeric threshold, concentration, date, or term for an issue, say so and treat the missing information itself as part of the risk

## 5. Vertical / structural / temporal relationships

- Portfolio-level vs. site-level: summarize common themes across the acquisition, but keep each site’s condition and consequence separate
- Phase I to Phase II progression: unresolved Phase I items should remain open until the follow-on work fully answers the question; otherwise the issue is incomplete
- Compliance history as a risk signal: repeated tank or release-control deficiencies can indicate broader management problems and raise the likelihood of hidden contamination
- Timing matters: note whether the source materials show pre-signing, pre-closing, post-closing, or ongoing remediation obligations, because that changes the appropriate recommendation
- If multiple sites share a similar issue, present the repeated pattern once at the portfolio level and then note the site-by-site instances that support it

## 6. Output structure conventions

- Write the memo as an environmental issues memorandum with a concise executive summary, a site-by-site analysis, a portfolio-level synthesis, a transaction-protections review, and a recommendations section
- Open with a short severity legend using a uniform ordinal scale: Critical, Significant, Moderate, Informational
- In the site-by-site section, give each site its own subheading and include: investigation scope, Phase I findings, Phase II status, regulated-system compliance observations, issue list, severity, and recommended action
- For each issue, use a compact issue format that states the issue, the controlling authority or standard, the cross-reference to the interacting document, the consequence, and the severity
- Where a legal conclusion is drawn, identify the controlling authority by name and section or part rather than relying on conclusory language alone
- In the transaction-protections review, test whether the current representations, indemnities, conditions, and disclosure structure actually address the issues identified in the diligence record
- End with a distinct Recommended Actions block that uses imperative verbs, names the responsible role or function, and ties each action to the signing, closing, or remediation timetable reflected in the source materials
- Use the exact filename requested in the task instructions for the deliverable output