# Identify Issues In Notice Of Violation > Guides preparation of a defense memorandum for an industrial facility's notice-of-violation response by assessing each alleged violation against available permit records, operational data, and monitoring results to identify defensible positions and mitigation arguments. - Skill: `finchipaiorg/identify-issues-in-notice-of-violation` (Agent Skill) - Install (CLI): `npx skillmds@latest add finchipaiorg/identify-issues-in-notice-of-violation` - Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/identify-issues-in-notice-of-violation/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/identify-issues-in-notice-of-violation --- # Skill: Identify Issues in Notice of Violation — Issue Memorandum for Industrial Recycling Facility ## 1. Subject-matter triage - Treat the NOV, permit excerpts, internal records, COMS data, and inspection memo as one integrated enforcement record. - Identify every alleged violation, then determine whether it is air, water, monitoring/reporting, inspection-procedure, or penalty-related. - If the NOV bundles multiple programs or time periods, separate them before analysis and keep each allegation tied to its own cited condition and evidence set. - If the source set contains only one allegation type, say so explicitly and explain why no broader program sweep is needed. ## 2. Failure modes the skill is correcting - Summarizing allegations without matching each one to the governing permit term, regulation, time period, and cited evidence. - Treating the memo as a narrative response instead of a count-by-count defense analysis. - Missing factual defenses available from operating data, validity windows, monitoring methodology, startup/shutdown/malfunction treatment, or reporting timing. - Failing to distinguish between a defensible allegation, a partially defensible allegation, and an allegation that should be conceded with mitigation. - Ignoring inspection-process defects, sample-handling problems, or documentation gaps that can weaken specific counts. - Overlooking how prior notices, post-inspection corrective actions, and cooperation affect penalty exposure. - Analyzing air and water issues in isolation when they arise from the same inspection or compliance episode. - Stating conclusions without tying them to a controlling permit term, regulation, rule, or enforcement procedure. ## 3. Legal frameworks / domain conventions that apply - Air permit enforcement commonly turns on permit emission limits, opacity or visible-emission standards, monitoring obligations, deviation reporting, and data validity rules under the applicable air permit and state implementing regulations. - Continuous monitoring issues must be evaluated against the governing averaging period, calibration and QA/QC requirements, downtime treatment, invalid-data rules, and any applicable startup, shutdown, or malfunction provisions in the air program. - Water permit issues commonly turn on effluent limits, discharge monitoring obligations, stormwater conditions, sampling requirements, and report-submission duties under the applicable water permit and implementing regulations. - Inspection-based allegations should be tested against inspection authority, notice requirements, recordkeeping duties, and sample chain-of-custody rules where samples were collected. - Enforcement defenses and mitigation should be framed under the applicable state environmental enforcement procedures, including response deadlines, informal conference rights, and penalty calculation factors. - Any legal proposition relied on should be anchored to the controlling authority named in the source set or the generally recognized governing statute, regulation, rule, or permit condition. - Do not assert a regulatory exemption, reporting excuse, or evidentiary defect without identifying the provision that supplies it. ## 4. Analytical scaffolds - Start by enumerating each allegation in order of appearance and mapping it to: - the alleged conduct, - the controlling permit term or regulation, - the cited evidence, - the relevant date range, - the program implicated. - For each allegation, ask three questions in sequence: - Does the source record support the factual premise? - Does the cited permit term or regulation actually cover the conduct as described? - If a violation remains, what is the best mitigation or corrective-action posture? - For air allegations, compare the NOV period to COMS or other monitoring data, then test data usability, averaging rules, outage periods, QA/QC status, and any shutdown or malfunction context. - For water allegations, compare reported or sampled values to permit limits and verify whether the alleged shortfall is a true exceedance, a reporting defect, a sampling anomaly, or a timing issue. - For inspection allegations, test whether the inspection memo, field notes, photographs, sample records, and chain-of-custody support the asserted violation. - For each allegation, classify the position using a uniform ordinal severity or strength scale defined once at the outset, then apply it consistently. - Every issue entry should close with three moves: a scale reference from the source record, a cross-reference to the interacting document or condition, and the practical consequence for liability, operations, or penalty exposure. - When more than one allegation, period, facility area, or monitoring event is in play, analyze each one separately rather than collapsing them into a representative example. - If a defense depends on an assumed fact not in the record, mark it as conditional and identify what additional proof would be needed. ## 5. Vertical / structural / temporal relationships - Track whether an allegation is derivative of another event, such as a monitoring failure following an equipment outage or a reporting issue following a substantive exceedance. - Distinguish one-off incidents from repeated conditions, since repetition can affect penalty posture and corrective-action credibility. - Treat post-inspection fixes, revised procedures, retraining, maintenance, and agency communications as temporally relevant to mitigation even when they do not erase historical liability. - If the NOV covers multiple compliance dates, analyze chronology carefully; a later corrective step cannot defeat an earlier violation unless the governing rule makes timing material. - If prior compliance history is mentioned, characterize it accurately as either mitigation or aggravation based on the record, not as a generic background fact. ## 6. Output structure conventions - Write as a defense memorandum in conventional legal memo form, using headings that cover: executive summary, allegation-by-allegation analysis, penalty and mitigation assessment, and recommended response strategy. - Use one entry per allegation, and within each entry state: - the allegation, - the governing authority, - the evidence reviewed, - the defense or mitigation position, - the strength or severity classification, - the recommended response. - Keep the analysis practical: identify whether the issue is defensible on the merits, partially defensible with mitigation, or should be conceded while preserving penalty arguments. - Close with an explicit Recommended Actions section that assigns each action to the appropriate role and ties it to a response deadline or regulatory milestone drawn from the record. - The memorandum should be suitable for conversion into the required `.docx` response file and should read as an operative legal work product, not a summary of documents.