Scenario 01

---
name: review-agency-inspection-scenario-01
task_id: environmental-esg/review-agency-inspection/scenario-01
description: Guides preparation of a defense-oriented issues memorandum for a contested agency multi-media inspection by organizing findings by media and assessing each allegation against facility records, monitoring data, and procedural documentation.
activates_for: [planner, solver, checker]
---

# Skill: Issue Identification Memorandum for Contested EPA Multi-Media Inspection of Chemical Manufacturing Facility

## 2. Failure modes the skill is correcting

- The memo narrates the inspection findings without tying each allegation to the governing permit condition, reporting rule, or inspection requirement that actually controls it.
- It treats the inspection report as self-proving instead of testing each finding against facility records, monitoring data, logs, and contemporaneous correspondence.
- It collapses air, water, stormwater, and spill-prevention issues into one undifferentiated compliance narrative, which obscures distinct defenses and remedies.
- It ignores procedural defects in the inspection record, including access, sampling, documentation, and chain-of-custody issues, even where those defects may narrow or defeat a finding.
- It omits the client’s prior response materials, which may preserve admissions, objections, corrective actions, or a consistent defense theme.
- It stops at identifying problems and does not convert them into a prioritized defense posture with mitigation and follow-up actions.

## 3. Legal frameworks / domain conventions that apply

- Multi-media inspection authority: evaluate the applicable statutory and permit basis for inspection, including credentials, access, notice, and document-request procedures.
- Air compliance framework: apply permit terms, emission limit conditions, leak detection and repair requirements, monitoring obligations, deviation reporting, and recordkeeping duties under the applicable air rules and permit.
- Water compliance framework: apply discharge authorization conditions, effluent limits, discharge monitoring, certification requirements, and reporting accuracy obligations under the applicable water rules and permit.
- Stormwater framework: apply the facility’s stormwater permit conditions, inspection and corrective-action obligations, and benchmark or sample-reporting duties where applicable.
- Spill-prevention framework: apply the spill-prevention plan requirements, inspection cadence, containment standards, amendment triggers, and implementation obligations under the applicable oil-storage prevention rules.
- Sampling and evidence rules: test whether any samples, photos, field notes, or observations are supported by proper collection procedures, contemporaneous notes, and chain-of-custody documentation.
- Procedural integrity: assess whether the inspection report fairly reflects what was observed and whether the agency documentation supports the asserted facts.
- Penalty and enforcement factors: assess gravity, duration, recurrence, good-faith cooperation, corrective action, compliance history, and economic benefit in framing the enforcement response.

## 4. Analytical scaffolds

- Start by enumerating the full set of inspection findings and grouping them by medium, source, or program so each issue is analyzed once and only once.
- For each finding, identify the exact control point: permit term, reporting rule, inspection protocol, plan requirement, or recordkeeping obligation that the finding purports to implicate.
- Cross-check the allegation against the source set: operating logs, maintenance records, monitoring data, certifications, deviation reports, work orders, sampling materials, internal emails, and prior correspondence.
- For air issues, compare the cited condition to emissions records, LDAR logs, calibration records, and deviation notices; determine whether the record supports noncompliance, a timing mismatch, or a documentation gap.
- For water and stormwater issues, compare the cited condition to discharge logs, analytical results, benchmark data, certification pages, inspection logs, and corrective-action records; distinguish an actual exceedance from a reporting or transcription issue.
- For spill-prevention issues, compare the cited deficiency to the actual plan language, inspection worksheets, containment drawings, training records, and any amendment history; assess whether the report describes a true deficiency or an outdated condition.
- For procedural and evidentiary issues, test the inspection chronology, access notes, sample handling, photo support, and custody records for gaps that weaken a sample-based or observation-based finding.
- For the prior response letter, identify what the client already stated, what it conceded, what it disputed, and what corrective steps were represented as underway.
- Classify each issue as defensible, partially defensible, or conceded with mitigation, and state why the evidence supports that classification.
- Tie every issue to its practical consequence: enforcement exposure, corrective-action burden, permit/reporting risk, or litigation posture.
- Where the source documents supply a threshold, date, frequency, or limit, use it to anchor the analysis; do not rely on abstract descriptions alone.
- Where the source documents identify a governing authority, cite that authority by name and section in the analysis rather than asserting the proposition bare.

## 5. Vertical / structural / temporal relationships

- Treat the prior response letter as contemporaneous evidence of the client’s position; reconcile any mismatch between that letter and the present defense strategy before drafting.
- Distinguish historical conditions at the time of inspection from current conditions after corrective action; current compliance may reduce penalty exposure even if it does not erase the issue.
- Track cross-media interactions where one condition may implicate more than one program, such as housekeeping or containment issues affecting both spill-prevention and stormwater compliance.
- If the inspection report relies on a timeline, sequence the facts in the same order so the memo does not obscure causation, notice, response, or cure.
- If a finding turns on a sampled event, separate the sample result from the broader compliance narrative and test whether the collection process itself was sound.
- If the same defect appears in multiple documents, explain whether it is the same underlying issue, a repeated observation, or a documentation inconsistency.

## 6. Output structure conventions

- Write a defense-oriented issues memorandum, not a compliance summary.
- Use conventional memo architecture: Executive Summary; Findings Organized by Medium; Procedural and Evidentiary Issues; Penalty and Mitigation Assessment; Recommended Response Strategy.
- At the outset, define a simple ordinal severity scale and apply it consistently to each issue entry.
- For each issue, include: the inspection allegation, the controlling authority or document reference, the best defense or narrowing argument, the supporting record, the severity assessment, the downstream consequence, and the recommended response.
- Keep the analysis issue-specific; do not merge unrelated findings into a single paragraph.
- Where multiple findings depend on the same record set, make that relationship explicit so the reader can see the common defense theme.
- End with a Recommended Actions block that uses imperative verbs, assigns each action to a responsible role, and gives a timing anchor tied to the inspection response, corrective-action window, or enforcement milestone.
- Use the deliverable filename specified in the task instructions exactly: `issue-identification-memo.docx`.