# Draft Environmental Permit Application Narrative > Guides drafting of a permit renewal application narrative for a food processing facility by addressing each pre-application conference topic systematically with accurate technical data and proactively resolving compliance history issues. - Skill: `finchipaiorg/draft-environmental-permit-application-narrative` (Agent Skill) - Install (CLI): `npx skillmds@latest add finchipaiorg/draft-environmental-permit-application-narrative` - Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/draft-environmental-permit-application-narrative/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: FinchipAIOrg (https://skillmd.com/u/finchipaiorg) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/finchipaiorg/draft-environmental-permit-application-narrative --- # Skill: Draft Permit Renewal Application Narrative ## 1. Subject-matter triage - Treat the pre-application conference letter as the controlling roadmap for scope and ordering. - Identify the permit program, renewal form set, receiving-water context, and any facility changes that may affect renewal conditions. - Confirm whether the application is a straightforward renewal or a renewal with operational, treatment, discharge, or monitoring changes that require fuller explanation. - If the source set contains multiple studies, monitoring periods, or operational phases, enumerate them before drafting and keep each distinct. ## 2. Failure modes the skill is correcting - Baseline drafts a generic facility description without answering the agency’s specific pre-application topics. - Baseline omits compliance history, glosses over deviations, or fails to explain corrective actions and current status. - Baseline recites monitoring or study conclusions without reconciling them to the underlying data and facility operations. - Baseline ignores receiving-water, loading, mixing-zone, or toxicity issues that can drive renewal conditions. - Baseline fails to disclose operational changes, project status, or treatment updates that may affect the permit term. - Baseline produces a narrative that is descriptive but not supportable by the source documents or the governing permit framework. ## 3. Legal frameworks / domain conventions that apply - Apply the governing water-permit renewal framework for the relevant program, including the renewal application and any supplemental narrative requirements. - Follow the pre-application conference letter and any agency filing instructions as the primary scope-defining authority. - Address effluent characterization, compliance history, and permit-term changes as part of the renewal record, not as optional background. - Where the record includes receiving-water impairment, wasteload allocation, total maximum daily load, or other loading framework, explain the facility’s relationship to that framework and the compliance path. - Where dilution or mixing assumptions are used, summarize the technical basis for the claimed mixing-zone treatment of the discharge. - Where toxicity testing is relevant, summarize acute and chronic results, any failures, and the status of any toxicity reduction or investigation work. - Where stormwater, spill prevention, or process changes are implicated, summarize controls and any updates triggered by operations or projects. - Cite the controlling permit-program authority, state regulations, and any agency guidance or letter instructions relied on in the narrative. ## 4. Analytical scaffolds - Start from the letter topics and draft one section per topic; do not merge unrelated topics into a single generalized operations summary. - For each section, answer four questions in order: what exists now, what changed during the term, what the source documents show, and why the answer matters for renewal. - For facility description, identify current production processes, wastewater sources, treatment steps, discharge points, and any seasonal or episodic variation. - For effluent characterization, summarize the monitoring record over the permit term, explain excursions or deviations, and state the corrective measures taken. - For compliance history, disclose notices, violations, inspections, enforcement contacts, and current closure status with plain explanation. - For loading or allocation issues, describe the applicable framework, compare the facility’s discharge to that framework, and identify any operational or treatment adjustments needed for continued compliance. - For mixing-zone issues, explain the study method, assumptions, and how the discharge is expected to meet water-quality requirements under those assumptions. - For toxicity issues, summarize test methods and outcomes, identify any failures, and explain the current investigation or reduction status. - For stormwater and spill prevention, identify current controls, training, inspections, containment, response procedures, and any revisions tied to process changes. - For process changes, disclose capital projects, new equipment, production changes, or wastewater-routing changes and assess whether they affect limits or monitoring. - Cross-check every numeric, operational, and compliance statement against the source documents before including it. - If the source record contains more than one relevant period, study, or operational condition, list them first and then analyze each on its own terms. ## 5. Vertical / structural / temporal relationships - Keep the narrative aligned vertically with the letter’s topic hierarchy so reviewers can trace each response to a requested subject. - Reconcile the current narrative against discharge-monitoring data, study results, and operational descriptions; do not let one source implicitly override another without explanation. - Distinguish past compliance events from current conditions and future project impacts. - If a project is planned or underway, state its timing, present status, and expected impact on permit obligations. - If the record spans multiple monitoring periods, identify the period boundaries before drawing conclusions so trends are not collapsed into a single average story. ## 6. Output structure conventions - Draft the primary deliverable first as the required .docx narrative and ensure it is populated with operative text, not placeholders. - Organize the document using the same topic headings or numbering used in the pre-application conference letter when possible. - Under each heading, write a concise narrative supported by references to the attached documents and internal cross-references where helpful. - Include a certification or signature statement only if the permit program or filing instructions require it. - Use professional permit-application prose: factual, specific, and transparent; avoid advocacy that obscures the record. - End with any required action items, attachments, or certifications in the format the program expects.