What Actually Happens When You Miss a DMR Deadline (and How to Recover)

Missing a DMR deadline feels like an administrative failure. What it actually triggers is an automated federal violation record — one that can escalate through multiple enforcement tiers without a human being making a deliberate decision to pursue you. Understanding how that system works is the first step to navigating it effectively.

This post explains the mechanics of how ICIS generates violations, the specific codes you will see in your compliance record, when a missed deadline crosses the threshold into Significant Noncompliance, what the Clean Water Act authorizes in terms of penalties, and exactly how to respond and recover.

How Violations Are Generated Automatically in ICIS

ICIS — the Integrated Compliance Information System — is EPA's centralized database for NPDES permit compliance tracking. It is not a passive record-keeping system. It actively compares submitted DMR data against permit limits and expected submission schedules, generating violation records automatically when discrepancies are found. No inspector needs to review your DMR for a violation to appear in the system.

The key violation codes to understand:

• D80 — DMR Not Received: Generated when a DMR is not submitted by the deadline. This is a reporting violation, not an effluent violation. Even if your plant was operating perfectly, a D80 appears if the paperwork was not filed. D80 violations are the most common compliance finding at small facilities.
• D90 — DMR Numeric Violation: Generated when a submitted DMR contains a value that exceeds a permit limit. This includes monthly average violations, daily maximum violations, and weekly average violations. The comparison is done automatically when data is entered in NetDMR.
• E90 — Effluent Violation: Similar to D90 but specifically flagged for single-day maximum exceedances reported on the DMR. In some state-delegated programs, E90 and D90 are used differently; the distinction matters for SNC calculations.
• M10 — Monitoring Violation: Generated when a required monitoring event was not conducted or a result is missing for a parameter that has a monitoring frequency requirement. This is distinct from the DMR itself not being submitted — M10 arises when the DMR is submitted but a required data point is blank or reported as "no data" without authorization.

All of these violations are visible in EPA's publicly accessible ECHO database (echo.epa.gov). Anyone can search your facility by name or permit number and see your compliance history including every violation code generated in the last several years. Lenders, insurers, environmental groups, local media, and your permitting agency all have access to this information.

The 31-Day Rule: When a Late DMR Becomes a Formal Violation

Under NPDES regulations and EPA's enforcement response policy, a DMR that is not received by its due date generates a D80 violation immediately — on day one of lateness. The violation record exists from the moment the deadline passes without a submission.

The 31-day threshold matters for a different and more serious calculation: Significant Noncompliance. Under EPA's SNC criteria for reporting violations, a facility is considered in SNC for reporting if it fails to submit required DMRs for two or more quarters within a 12-quarter (3-year) evaluation period, or if a single DMR is more than 30 days late — meaning the violation persists 31 or more days beyond the original due date without a submission being received.

This means there is a meaningful difference between a DMR that is submitted a week late and one that is not submitted for more than a month. Both are violations. But the latter can trigger SNC, which carries a separate set of consequences. If you realize you have missed a deadline, the priority is to get the DMR submitted as quickly as possible — not just to stop the lateness, but to ensure the violation does not accumulate into an SNC-triggering condition.

Significant Noncompliance: What It Means and What Follows

Significant Noncompliance is a formal classification within the NPDES compliance tracking framework. A facility in SNC status is not merely flagged internally — it is subject to mandatory escalation requirements under EPA's enforcement management system. State agencies that have received NPDES program delegation from EPA are required to take formal enforcement action against facilities in SNC within specific timeframes.

SNC is triggered by two categories of conditions: effluent violations and reporting violations. On the reporting side, the criteria include failing to submit 50% or more of required DMRs over a 12-quarter evaluation period, or having any DMR that is more than 30 days late. On the effluent side, SNC is triggered when a parameter exceeds its monthly average permit limit by a defined multiplier — typically 1.4x for most parameters, 1.2x for conventional pollutants like BOD and TSS, and any exceedance for certain toxics.

Once a facility is classified as SNC, the state agency's enforcement management system typically requires a response within defined timeframes. This can mean a Notice of Violation, an Administrative Order, or referral to a formal enforcement action. The specific trajectory depends on the state, the severity of the violations, and the facility's compliance history.

SNC status in ECHO is visible to the public and is actively used by environmental advocacy organizations to identify facilities for scrutiny. It can affect a community's relationship with its regulator, complicate permit renewals, and in some cases trigger third-party citizen suit provisions under the Clean Water Act. The reputational and regulatory consequences of extended SNC status substantially exceed those of a single, promptly-resolved missed deadline.

Civil and Criminal Penalties Under the Clean Water Act

Section 309 of the Clean Water Act establishes the penalty structure for NPDES permit violations. Understanding the statutory framework helps calibrate the actual risk.

Civil penalties are the most common enforcement tool. Under Section 309(d), civil penalties for violations of permit conditions can reach $25,000 per day per violation for violations occurring on or before November 2, 2015, and higher amounts for more recent violations after the Federal Civil Penalties Inflation Adjustment Act updates. When calculating civil penalties, regulators consider the economic benefit gained from noncompliance, the severity of the violation, the compliance history of the facility, any good faith efforts to comply, and the ability of the violator to pay.

In practice, civil penalties assessed against municipal wastewater facilities for reporting violations — as opposed to effluent exceedances or bypasses — are often negotiated downward from the statutory maximum, particularly for small municipalities with demonstrated good faith. However, facilities that have ignored multiple Notices of Violation, failed to respond to enforcement correspondence, or have extended compliance histories face significantly less favorable negotiations.

Criminal penalties under Section 309(c) apply to knowing violations. A person who knowingly violates a permit condition faces fines up to $10,000 per day of violation and up to two years imprisonment for a first offense — increasing to $20,000 per day and four years for subsequent violations. Knowingly falsifying a DMR — entering a value you know to be incorrect — is itself a separate criminal offense under 18 U.S.C. Section 1001 (false statements to the federal government). Criminal enforcement is rare for municipal reporting violations without aggravating circumstances, but it is not theoretical. It has been applied in cases involving deliberate falsification of monitoring records.

How to Respond to a Notice of Violation

A Notice of Violation (NOV) is a formal written communication from your state NPDES authority (or EPA in states without delegation) informing you that a violation has been identified and requiring a response. Receiving an NOV does not mean you are in litigation. It means the regulatory process has been formally initiated and that you are expected to engage.

The response process:

1. Read the NOV carefully and immediately. Note the response deadline — it is typically 30 days from receipt, but shorter deadlines exist in some state programs. Missing the NOV response deadline compounds the compliance problem.
2. Identify the specific violations listed. The NOV should reference permit numbers, violation dates, violation codes, and the specific permit conditions at issue. For each violation, you need to know whether it has been resolved (DMR since submitted, exceedance was a one-time event) or is ongoing.
3. Contact the issuing agency as soon as possible after receipt — by phone first, then confirm in writing. Introduce yourself, ask for the name and contact information of the staff person handling the case, and signal that you intend to respond in good faith. This call should happen within the first week, not at the response deadline.
4. Prepare a written response that addresses each violation specifically: what happened, what corrective action has been taken or is planned, and what you have done to prevent recurrence. Attach supporting documentation — lab reports, submission confirmations, calculation worksheets, equipment maintenance records, whatever is relevant to each specific violation.
5. Do not make commitments you cannot keep. If you say in your NOV response that you will implement a specific corrective action by a specific date, that commitment becomes part of the enforcement record. Missed voluntary commitments in NOV responses are taken seriously by regulators.

Submitting a Corrected or Amended DMR

If you discover an error in a previously submitted DMR — a calculation mistake, a transcription error, a wrong non-detect substitution — you can submit a corrected DMR through NetDMR. The process replaces the original submission in the system with the corrected values, though the original submission history remains in the audit trail.

In NetDMR, amended submissions are typically allowed for DMRs submitted within a defined window — generally up to 60 days after the original submission in most state programs, though some states allow amendments further back in time. Beyond the standard amendment window, you typically need to contact your state agency to request that an amendment be accepted. This request should be made in writing, explain the nature of the error, and include the corrected values and supporting calculation documentation.

What you can amend: calculation errors, unit errors, transcription errors, wrong non-detect substitution, missing parameter values that were inadvertently omitted.

What you cannot undo through amendment: a D80 for a DMR that was not submitted on time. Submitting a late DMR resolves the outstanding submission requirement, but the D80 violation for the late submission remains in the compliance record. The violation happened when the deadline passed without submission. The late filing updates the record to show it has been resolved, but does not remove the violation.

When submitting an amended DMR that corrects a value that previously appeared to be in compliance to one that is actually a violation — or vice versa — notify your state agency in writing at the same time as the amendment. Proactive self-disclosure of a compliance problem is a significant mitigating factor in any subsequent enforcement discussion and is explicitly recognized under EPA's self-disclosure policy (the Audit Policy) as a basis for penalty mitigation.

The 90-Day Compliance Schedule

When a facility has accumulated multiple violations or is dealing with an ongoing compliance problem that cannot be corrected immediately, a formal compliance schedule is the standard mechanism for demonstrating good faith while working toward resolution. A compliance schedule is a legally binding agreement between the facility and the regulatory agency that sets specific milestones for achieving compliance.

For reporting violations specifically — late or missing DMRs — a compliance schedule might include: a deadline for submitting all outstanding DMRs, a deadline for implementing a new internal compliance workflow, and a deadline for providing documentation that the process is functioning. For effluent violations caused by equipment failures or treatment deficiencies, the schedule is typically longer and includes capital improvement milestones.

The 90-day framework comes from EPA's enforcement management system, which defines the window within which a state agency is expected to respond to a SNC facility with either an enforcement action or a compliance schedule in place. Being on a compliance schedule — actively engaged with your regulator and meeting milestones — is categorically different from being in SNC with no engagement. The former demonstrates good faith and stops the escalation clock. The latter results in continued escalation.

To negotiate a compliance schedule, contact your state NPDES authority as soon as you recognize that you cannot achieve compliance quickly on your own. Propose specific, achievable milestones with realistic dates. Ask for the schedule to be memorialized in a compliance order or administrative agreement rather than an informal letter — a formal compliance schedule with milestones you are meeting is the most effective shield against penalty escalation during a period of active correction.

The single most important thing a facility can do after a violation occurs is to engage early, respond in writing, and demonstrate concrete corrective action. Regulators consistently differentiate between facilities that communicate proactively and those that go silent. Silence reads as indifference and accelerates escalation.