Compare Site Assessment Reports Against Applicable Regulatory Cleanup Standards

Skill: Compliance Gap Analysis Memorandum — Compare Site Assessment Reports Against Applicable Regulatory Cleanup Standards

1. Subject-matter triage

Group all investigation, regulatory, and transaction documents by site, parcel, medium, and reporting phase before analysis. Separate the acquisition target from background or comparator properties. State whether one site is in scope or multiple sites must be analyzed, then run the comparison site by site and medium by medium. Flag out-of-scope materials early so they do not contaminate the gap analysis.

If the source set includes more than one applicable program, cleanup regime, land-use category, or media-specific standard, identify each separately before evaluating adequacy. Do not collapse distinct regulatory pathways into a single blended standard.

2. Failure modes the skill is correcting

• Site assessment findings are summarized without measuring detected conditions against the applicable cleanup standard for the relevant medium and land use
• The remedial plan is described without testing whether it is sufficient to reach the governing cleanup endpoint or satisfy program conditions
• Contract protections are reviewed in the abstract without tying them to the actual environmental risk profile disclosed by the reports
• Sampling gaps, incomplete delineation, or uncertain plume boundaries are not carried through to the remediation cost and closing-risk analysis
• The analysis states that a condition is problematic but does not identify the governing authority that makes it so
• Issues are listed without severity, cross-document interaction, or downstream transaction consequence

3. Legal frameworks / domain conventions that apply

• Phase I ESA concepts: recognized environmental conditions, controlled recognized environmental conditions, historical recognized environmental conditions, and data gap significance
• Phase II ESA concepts: sampling design adequacy, delineation completeness, exceedances above applicable standards, and contaminant-of-concern identification
• Cleanup standards framework: generic numerical standards, media-specific thresholds, land-use-based standards, groundwater classification, and site-specific risk-based alternatives
• Regulatory programs: voluntary cleanup, brownfields, corrective action, and similar cleanup regimes; institutional controls and activity/use limitations
• Remedial planning conventions: source control, excavation, cap-and-contain, monitored natural attenuation, treatment, and long-term operation/maintenance assumptions
• Transactional protections: environmental representations, disclosure schedules, indemnities, escrows, special closing conditions, covenant packages, and survival periods
• If the source documents identify the controlling statute, regulation, permit, or program guidance, cite that authority by name and section in the memo; if not, cite the generally recognized governing authority used in the analysis

4. Analytical scaffolds

• Enumerate the applicable standards first: by contaminant, medium, and regulatory pathway
• For each site and medium, extract the reported condition and compare it to the applicable standard
• For each exceedance or suspected exceedance, assess whether the condition is fully delineated, partially delineated, or still uncertain
• For each uncertainty, identify the missing sampling, characterization, or historical-use information that drives the gap
• For each remedial proposal, test whether the selected remedy and cleanup level align with the governing program, expected land use, and any required institutional controls
• For each contract provision, test whether the representation, indemnity, escrow, closing condition, or disclosure schedule matches the actual risk and uncertainty profile
• For each issue, state: the condition, the governing authority, the comparison result, the practical consequence, and the recommended follow-up

When the source set contains multiple sites, media, or regulatory tracks, analyze each one separately and do not rely on a representative sample. If only one is relevant, say so expressly and explain why the other materials are non-operative.

5. Vertical / structural / temporal relationships

• Earlier investigative findings constrain later remediation design; later delineation results can confirm or expand the cleanup burden
• Media interact vertically: soil contamination can drive groundwater obligations, and groundwater standards can in turn affect institutional control requirements
• Regulatory sequence matters: cleanup endpoints and land-use assumptions should be tested before finalizing closing conditions or indemnity scope
• Transaction timing matters: pre-closing diligence items address uncertainty; post-closing obligations address ongoing compliance, monitoring, and long-term controls
• If the remedial approach depends on future land-use restrictions, identify who will own, monitor, and enforce those restrictions over time

6. Output structure conventions

• Draft a compliance gap analysis memorandum in conventional memo form with a brief executive summary, a standards-and-findings section, a remedial adequacy section, a contract protections section, and a recommendations section
• Use an explicit ordinal severity scale defined once at the top, and apply it consistently to each issue
• Present findings issue-by-issue or by site/medium table, but each entry must include the governing authority, the comparison result, the severity, the downstream consequence, and the follow-up action
• For any quantitative comparison, include the reported condition and the applicable threshold in the same entry; do not provide arithmetic derivations unless the source documents require them
• Recommendations must be concrete, imperative, and tied to a responsible role and a timing anchor relative to signing, closing, or the regulatory milestone
• Distinguish pre-closing due diligence items from negotiated contractual protections and post-closing compliance obligations
• Use only conventional memo section shapes; do not mirror any hidden checklist or rubric structure
• Deliverable filename must match the task instructions exactly