Draft Comment Letter On Proposed Remedial Plan

Skill: Draft Comment Letter on Proposed Remedial Plan

1. Subject-matter triage

• Treat the assignment as a formal regulatory submission, not a general advocacy memo.
• Identify the reviewing authority, site name, docket or permit reference if present, comment deadline if present, and the commenter’s standing or interest.
• Determine whether the record presents one site or multiple operable units, media, or exposure pathways; if more than one, enumerate them before analysis.
• Pull the proposed remedy, investigation record, sampling data, community comments, and any applicable cleanup tables into a single review set before drafting.

2. Failure modes the skill is correcting

• Drafts object in general terms without tying each objection to the remedy-selection criteria or cleanup standards the plan must satisfy.
• Drafts ignore medium-specific and receptor-specific data, especially where residential exposure is the operative standard.
• Drafts fail to address vapor intrusion, groundwater, private wells, or other off-site pathways that matter for nearby residents.
• Drafts treat community concerns as background rather than as discrete comment issues that require a regulatory response.
• Drafts state that a remedy is inadequate without identifying the governing authority and the downstream consequence of the deficiency.
• Drafts read like a narrative summary instead of a structured comment letter with issue-by-issue objections and requested follow-up action.

3. Legal frameworks / domain conventions that apply

• CERCLA remedy-selection criteria and analogous state cleanup standards: overall protection of human health and the environment; compliance with applicable requirements; long-term effectiveness; reduction of toxicity, mobility, or volume; short-term effectiveness; implementability; cost; state acceptance; community acceptance.
• Residential land-use cleanup standards: where the receptor is a residential community, compare the proposal to residential, not industrial or commercial, exposure assumptions unless the governing program clearly allows otherwise.
• Vapor intrusion doctrine: assess whether the record adequately characterizes soil gas, sub-slab, and indoor air pathways and whether the proposed controls address current and future exposure.
• Groundwater and drinking water benchmarks: where private wells or potable aquifers are implicated, use the applicable drinking-water or groundwater protection standards as the benchmark.
• Institutional controls: deed notices, use restrictions, access restrictions, and monitoring obligations may support a remedy but rarely substitute for active cleanup where residents remain exposed.
• Public participation rules: comment-period procedures, response-to-comments obligations, and any right to a hearing or further explanation should be used to frame the requested relief.
• Remedial investigation and feasibility-study conventions: the proposed plan must be supported by the factual record, not by assumptions inconsistent with the site data.

4. Analytical scaffolds

• Start with the remedy-selection criteria and test the plan against each criterion in order.
• For each objection, use a three-part structure: the deficiency, the supporting evidence plus governing authority, and the specific action or additional analysis requested.
• Where data are available, compare the proposed cleanup level to the applicable standard for the relevant medium and receptor.
• Where multiple contaminants, media, or exposure pathways appear in the record, analyze each material item separately rather than folding them into one general critique.
• For protectiveness, focus on whether current and foreseeable residential exposure is addressed by the proposed remedy.
• For compliance, identify the specific cleanup requirement or screening level and explain how the proposed remedy falls short or how the record fails to show compliance.
• For long-term effectiveness, evaluate whether institutional controls, monitoring, and maintenance are adequate for an active residential setting.
• For implementability, identify any practical barrier shown by the record, including access limitations, utility conflicts, or sequencing issues.
• For community health and safety, convert resident concerns into formal comment points and tie each to a concrete pathway, dataset, or regulatory requirement.
• For each issue, include the consequence if the deficiency is not corrected, such as continued exposure, delayed attainment of cleanup goals, or an incomplete administrative record.
• If the record does not support a definitive conclusion, say so expressly and request the missing characterization, modeling, or sampling.

5. Vertical / structural / temporal relationships

• Residential versus non-residential standards: verify that the proposal uses the correct exposure scenario for the adjacent community.
• Investigation record versus proposed remedy: where the remedy assumes conditions not established by the site investigation, call out the mismatch and request additional data.
• Source area versus migration pathway: distinguish between on-site contamination, off-site migration, and resident exposure so the requested remedy reaches the relevant pathway.
• Short-term versus long-term effects: address both immediate construction or exposure risks and residual risks after implementation.
• Active remedy versus monitored natural attenuation or containment: explain whether the plan relies on passive measures without showing they are adequate for this site and receptor.

6. Output structure conventions

• Draft as a formal comment letter with standard business-letter elements, a clear subject line, and site identification.
• Include an introduction that identifies the commenter’s interest and the basis for submitting comments.
• Use numbered comment sections for technical and legal objections.
• Label each objection with an explicit severity designation using one consistent ordinal scale defined once near the top of the letter.
• In each numbered comment, state the deficiency, cite the governing authority, summarize the supporting data, explain the consequence, and request a specific correction, alternative, or additional study.
• Separate community health and safety concerns into their own section if they are not already embedded in the technical objections.
• End with a concise requested-action section that lists the precise changes, analyses, or responses sought from the agency.
• Where the source materials identify the controlling authority, cite it by name and section; do not state a legal conclusion without naming the rule or standard supporting it.
• Use a professional regulatory tone throughout and avoid advocacy rhetoric that is not anchored to the record.