Identify Environmental Issues In Preliminary Assessment Report

---
name: identify-environmental-issues-in-preliminary-assessment-report
task_id: environmental-esg/identify-environmental-issues-in-preliminary-assessment-report
description: Guides preparation of an environmental issues memorandum for a commercial acquisition by integrating preliminary assessment, Phase I, and Phase II findings with seller disclosure, purchase agreement provisions, and lender requirements to identify material issues and gaps.
activates_for: [planner, solver, checker]
---

# Skill: Identify Environmental Issues in Preliminary Assessment Report — Issue Memorandum

## 1. Subject-matter triage

Treat the document set as one transaction file unless the source set clearly splits assets, parcels, or closing escrows. Read the environmental reports in chronological order and treat the latest investigation as the current factual baseline, with earlier reports serving as context for persistence, escalation, or resolution.

If the record includes more than one parcel, phase, operating unit, or environmental topic, enumerate each discrete site condition before analysis and keep the assessment separate unless the documents expressly combine them. If only one condition is truly in scope, say so explicitly.

## 2. Failure modes the skill is correcting

- Reviews the preliminary assessment in isolation and misses later findings that change the risk profile or supersede earlier assumptions
- Treats a preliminary assessment as a complete substitute for later site investigation where the record shows a need for deeper characterization
- Fails to test seller disclosure against the independent environmental record for omissions, inconsistency, or understatement
- Reviews purchase-agreement environmental language without testing whether the protections match the actual condition of the site
- Omits lender due diligence requirements and financing conditions that may set the minimum acceptable investigation standard
- Lists conditions descriptively but does not translate them into severity, transactional consequence, and recommended action
- States environmental conclusions without tying them to the governing environmental standard, regulatory program, or contractual provision
- Compresses distinct issues into a single narrative and obscures which finding drives which recommendation

## 3. Legal frameworks / domain conventions that apply

- Environmental site assessment practice distinguishes recognized environmental conditions, controlled conditions, historical conditions, and data gaps; those labels matter because they frame diligence sufficiency and risk allocation
- A preliminary assessment is scope-limited; later Phase I or Phase II findings can reveal conditions that require a different diligence response
- Phase II data are used to characterize contaminants of concern in soil, groundwater, or other media, and the key questions are extent, pathway, and whether delineation is adequate
- State and federal environmental databases may indicate historic releases, enforcement activity, or regulatory attention; they are not mere background and should be treated as diligence inputs
- Voluntary cleanup or closure programs may reduce uncertainty, but any closure, comfort, or no-further-action letter should be tested for scope limits, conditions, and enforceability
- Purchase agreements typically allocate environmental risk through representations, warranties, disclosure schedules, indemnities, survival periods, caps, baskets, escrows, closing conditions, and material adverse effect language
- Lender diligence standards may require a broader or cleaner record than the buyer would accept on a standalone basis
- Where a legal proposition is stated, identify the controlling authority or program standard by name and citation as reflected in the source set or, if absent, by recognized environmental diligence practice

## 4. Analytical scaffolds

- Build a unified chronology: preliminary assessment, subsequent site investigations, seller disclosure, draft PSA provisions, and underwriting memo
- For each reported condition, ask four questions:
  1. What is the condition?
  2. What document establishes it?
  3. What environmental rule, program, or contractual provision governs it?
  4. What does it change for the buyer, lender, or closing?
- Translate each issue into a transaction consequence: investigation cost, remediation cost, closing risk, covenant pressure, financing risk, indemnity gap, or post-closing liability
- Cross-check seller disclosure against independent reports and note any mismatch, omission, or ambiguous qualifier
- Cross-check the PSA against actual site conditions and ask whether the seller’s reps, indemnity, bring-down mechanics, and closing conditions are adequate for the risk profile shown by the reports
- Cross-check the lender memo against the environmental record and flag any mismatch between required diligence and performed diligence
- Identify data gaps by asking whether the available record answers extent, pathway, source, and regulatory status; if not, the gap itself is an issue
- For every issue, close the loop with: a measured or scaled fact from the record, the interacting document or clause, and the downstream consequence for the client
- Use ordinal severity consistently across the memo and reserve the highest ratings for issues that materially affect closing, financing, or cleanup certainty

## 5. Vertical / structural / temporal relationships

- Later investigation findings control over earlier assumptions unless the later report expressly defers or leaves a question open
- A closure or no-further-action type letter may narrow agency exposure but usually does not eliminate all environmental, off-site migration, third-party, or contractual risk
- Unresolved delineation is itself a material risk because unknown scope means unknown cost and unknown timing
- If lender standards are stricter than buyer expectations, the lender floor governs financing feasibility even if the buyer would otherwise proceed
- If the agreement’s environmental allocation depends on a schedule or disclosure update, test whether the schedule actually captures the latest report findings
- Temporal gaps matter: an old report, stale database search, or outdated closure document should be treated as a risk until refreshed or reconciled

## 6. Output structure conventions

- Draft the deliverable as an environmental issues memorandum, not a raw notes dump
- Use an executive-summary style opening, followed by site-condition summary, issue-by-issue analysis, disclosure-completeness review, PSA analysis, lender-constraint review, and recommendations
- Define the severity scale once at the top and apply it uniformly to every issue, using an ordinal scale such as Critical / Significant / Moderate / Informational
- Each issue entry should include:
  - the condition or gap
  - the source document
  - the governing environmental standard, program rule, or contract provision
  - the severity rating
  - the transaction, financing, or compliance consequence
  - the recommended response
- Separate distinct issues rather than combining them into one generalized risk statement
- When the source record supports a quantified fact, use that fact to scale the issue; if the record does not provide a reliable number, say that the extent is not yet quantified rather than inventing one
- End with an explicit Recommended Actions section that assigns the next step to a role from the source set and ties the timing to the transaction milestone or regulatory deadline
- Keep the filename aligned to the task instruction: environmental-issues-memo.docx