1---2name: identify-issues-in-draft-npdes-permit-conditions3task_id: environmental-esg/identify-issues-in-draft-npdes-permit-conditions4description: Guides preparation of an NPDES permit issues memorandum for an industrial discharge by evaluating draft conditions against applicable Clean Water Act requirements, current permit limits, applicable load allocations, and technical data to identify deficiencies for public comment.5activates_for: [planner, solver, checker]6metadata:7 source: https://skillmd.com/skills/finchipaiorg/identify-issues-in-draft-npdes-permit-conditions8---910# Skill: Identify Issues in Draft NPDES Permit Conditions for Pulp Mill Discharge1112## 2. Failure modes the skill is correcting1314- Baseline identifies permit deficiencies without grounding each issue in the applicable regulatory standard, data methodology, or receiving-water protection requirement that the draft permit must satisfy15- Baseline fails to compare the draft permit against the existing permit to identify anti-backsliding concerns and changes requiring regulatory justification16- Baseline does not integrate available discharge monitoring data and engineering assessment findings to substantiate claims that permit limits are inadequate17- Baseline omits consultation correspondence and third-party submissions as sources of legally relevant objections that may strengthen the issues memorandum18- Baseline stops at spotting a defect instead of tying it to the governing rule, the supporting record, and the practical consequence for permit coverage or compliance1920## 3. Legal frameworks / domain conventions that apply2122- Clean Water Act permitting: distinguish technology-based effluent limits from water-quality-based effluent limits, and test whether the more stringent applicable limit is reflected in the draft permit23- NPDES implementing regulations: evaluate permit limits, monitoring, reporting, special conditions, and fact-sheet rationale under the applicable federal and state permitting rules24- Anti-backsliding: renewal permits should not become less stringent than prior permit conditions absent an applicable exception25- Water quality standards: state numeric and narrative criteria, designated uses, antidegradation policy, and any implementation procedures for translating criteria into permit conditions26- TMDLs: waste load allocations from applicable TMDLs should be incorporated into permit conditions where the receiving water is impaired or otherwise subject to allocation-based controls27- Mixing zone analysis: where allowed, assess whether the authorized zone is supported by the governing state method and is adequate for pollutants of concern28- Effluent guideline framework: identify the applicable technology-based standard for the facility type and operational subcategory29- Monitoring adequacy: sampling, analytical methods, frequency, and reporting must be sufficient to demonstrate compliance and support enforcement30- Administrative record review: fact sheets, technical memos, consultation letters, and public submissions can reveal analytical gaps or independently support objections3132## 4. Analytical scaffolds3334- Start by enumerating the draft conditions to be tested: effluent limits, monitoring requirements, reporting duties, special conditions, and any compliance schedules or variances35- Then compare each draft condition against the current permit, the applicable technology-based standard, the water-quality standard, and any relevant TMDL or mixing-zone support36- Use discharge monitoring data to assess whether the proposed limits track facility performance, whether they are overbroad, and whether the data show recurring noncompliance or margin concerns37- Use engineering assessment findings to test the technical basis for the draft permit; identify where the record supports a more protective limit or a different monitoring approach38- Review the fact sheet for missing assumptions, inconsistent calculations, unsupported selections, or omitted alternatives that weaken the legal basis for the draft condition39- Review consultation correspondence and public submissions for objections that map onto identifiable permit defects; use them to reinforce, not replace, the core regulatory argument40- For each issue, include: the permit condition, the controlling authority, the defect, the supporting record, the cross-reference to another source in the file set, the downstream consequence, and a comment position41- Treat a condition as vulnerable if the record does not explain why the selected limit, frequency, or method satisfies the governing rule in light of the facility’s discharge and receiving-water constraints4243## 5. Vertical / structural / temporal relationships4445- Existing permit as baseline: assess whether each corresponding draft condition is more or less stringent than the prior permit and whether any relaxation is justified under the governing anti-backsliding rule46- TMDL hierarchy: where a TMDL applies, verify that the draft permit aligns with the waste load allocation and any implementation method used by the permitting authority47- Record hierarchy: source documents may include technical data, agency analysis, correspondence, and submissions; if they conflict, note the conflict and identify which source best supports the comment position48- Temporal sequence matters: distinguish historic performance, current permit compliance, draft changes, and future compliance obligations so the memo does not conflate past events with proposed permit terms49- If multiple discharge points, pollutants, or permit condition groups are in scope, analyze each separately rather than blending them into a single generalized critique5051## 6. Output structure conventions5253- Organize the memo as a conventional issues memorandum with an executive summary, a categorized issue analysis section, a concise issues table, and a recommended public-comment approach54- Define an ordinal severity scale once at the outset and apply it consistently to every issue identified55- State each issue in a self-contained format: condition at issue, governing authority, defect, record support, cross-reference to related material, consequence, severity, and recommended comment56- Support every legal proposition by naming the controlling authority or regulatory provision on which the point depends57- When citing the record, identify the document type and the relevant data or analysis it contains; do not rely on unsupported generalizations58- Conclude with a recommended actions section that assigns an action, a responsible role, and a timing anchor tied to the comment deadline or permit process milestone59- Use the deliverable filename exactly as instructed: `permit-issue-identification-memo.docx`