NPDES Exceedance Reporting: Timelines, Required Content, and Enforcement Context

Your DMR shows a daily maximum exceedance on total suspended solids. The permit limit is 45 mg/L and your grab sample came back at 52 mg/L. What happens next depends entirely on how quickly you act, what you report, and how you document it. Exceedance reporting under NPDES permits follows specific federal timelines codified in 40 CFR 122.41, but state programs frequently layer additional requirements on top. Getting the sequence wrong—or missing a deadline—can escalate a single exceedance into a formal enforcement action.

NPDES Exceedance Reporting: The Three Reporting Tiers

Federal regulations establish three distinct reporting tiers for NPDES permit noncompliance. Each tier has its own timeline, content requirements, and triggering conditions. Understanding which tier applies to your exceedance is the first decision you make after identifying a limit violation.

Tier 1: 24-Hour Oral Notification

Under 40 CFR 122.41(l)(6), certain exceedances require oral notification to the permitting authority within 24 hours of becoming aware of the noncompliance. This applies to:

Any unanticipated bypass that exceeds an effluent limit
Any upset that exceeds an effluent limit
Violation of a maximum daily discharge limitation for any pollutant specifically listed in the permit for 24-hour reporting (typically toxic pollutants and hazardous substances)

Common Mistake The 24-hour clock starts when you “become aware” of the noncompliance—not when the lab delivers results. If your operator observes an equipment malfunction that causes an unauthorized discharge at 2 PM on Tuesday, the oral report is due by 2 PM Wednesday, even if lab confirmation comes later.

Tier 2: 5-Day Written Follow-Up

Every 24-hour oral notification must be followed by a written report within 5 days. Per 40 CFR 122.41(l)(6)(i), the written report must contain:

A description of the noncompliance, including exact dates and times
The duration of the noncompliance period
The estimated volume and concentration of the discharge
The cause of the noncompliance
Steps taken or planned to reduce, eliminate, and prevent recurrence

Tip Document everything contemporaneously. Enforcement cases often hinge on whether the permittee can demonstrate they identified the exceedance promptly and took reasonable corrective action. A timestamped operator log entry carries more weight than a reconstructed narrative written days later.

Tier 3: DMR Reporting (Monthly/Quarterly)

All exceedances—whether or not they trigger 24-hour reporting—must appear on the Discharge Monitoring Report submitted through EPA’s NetDMR system. DMRs are typically due by the 28th of the month following the monitoring period, though individual permits may specify the 15th or another date. The DMR captures the actual measured value, the permit limit, and the number of exceedances for each parameter during the reporting period.

If you have already submitted a DMR for a period and later discover an exceedance (for example, when late lab results arrive), you must file an amended DMR. NetDMR tracks amendment history, and regulators review amendments during compliance evaluations. For a walkthrough of the DMR submission process itself, see our guide on submitting NPDES DMRs through NetDMR.

Exceedance Severity and Enforcement Consequences

Not all exceedances carry the same enforcement risk. EPA and state agencies classify violations using severity tiers that determine whether you receive an informal notice, a formal enforcement action, or a penalty.

Significant Noncompliance (SNC) Criteria

EPA defines Significant Noncompliance using specific quantitative thresholds. An effluent limit violation qualifies as SNC if it meets any of these criteria during a review period (typically 6 months):

Technical Review Criteria (TRC) exceedance: A single monthly average violation exceeding the permit limit by 40% or more for Group I pollutants (conventional: BOD, TSS, fecal coliform, oil & grease, pH) or 20% or more for Group II pollutants (all others including toxics and metals)
Chronic violations: Monthly average exceedances in 4 or more months during any 6-month review period, regardless of magnitude
Non-monthly average violations: Two or more daily maximum or weekly average violations of the same parameter in a 6-month period, where any single violation exceeds the TRC threshold

Worked Example Your permit sets a monthly average TSS limit of 30 mg/L. In January you report 35 mg/L, February 28 mg/L, March 33 mg/L, April 31 mg/L, May 42 mg/L, June 29 mg/L. You had exceedances in January, March, April, and May—four months in a 6-month period. Even though January and March were only marginally above the limit, the chronic violation criterion triggers SNC. The May result (42 mg/L) is 40% above the 30 mg/L limit, which independently triggers TRC for Group I pollutants.

What SNC Triggers

Facilities in SNC are listed in EPA’s ECHO database (Enforcement and Compliance History Online), which is publicly searchable. SNC status typically triggers:

Formal enforcement action (administrative order or consent decree)
Potential civil penalties (up to $64,618 per day per violation under the 2024 penalty adjustment)
Increased inspection frequency
Public listing in EPA’s Quarterly Noncompliance Report (QNCR)

State-Specific Exceedance Reporting Requirements

Federal requirements are the floor, not the ceiling. Most state NPDES programs add their own notification requirements that consultants and operators must track separately.

Common State Additions

Expanded 24-hour reporting triggers: Some states require 24-hour oral notification for any effluent limit exceedance, not just the federal subset of toxic/hazardous pollutants
Shorter written follow-up deadlines: Some states require written reports within 3 days instead of the federal 5 days
Additional notification recipients: State programs may require notification to local health departments or downstream water intakes in addition to the permitting authority
Spill reporting integration: Some states combine NPDES exceedance reporting with spill/release notification requirements under a single hotline

Tip Build a permit-specific notification matrix for each client. Extract the reporting requirements from the permit’s standard conditions (usually Section C or D of the permit), the state’s general NPDES regulations, and any special conditions. A single reference table showing “if X happens, notify Y within Z hours” prevents missed deadlines during the stress of an actual exceedance event.

The Consultant’s Role in Exceedance Response

Environmental consultants supporting NPDES permittees often serve as the technical backbone of exceedance response, even though the reporting obligation rests with the permittee. Here is how the workflow typically plays out for consultants managing compliance data.

Step 1: Identify the Exceedance

When lab results arrive (via EDD or PDF report), the consultant compares each parameter against the permit limits for that outfall and monitoring period. This is the screening level comparison step—the same VLOOKUP-and-conditional-formatting process used for MCL and RSL comparisons, applied to permit-specific limits. Automated exceedance detection tools eliminate the manual comparison step and reduce the risk of a missed exceedance buried in a large dataset.

Step 2: Classify the Exceedance

Determine which reporting tier applies by checking:

Is the exceeded parameter listed for 24-hour reporting in the permit?
Was the exceedance caused by a bypass or upset?
Does the state require 24-hour notification for all exceedances?

Step 3: Notify the Permittee

The consultant is not the permittee. The reporting obligation belongs to the permit holder (the facility). The consultant’s job is to alert the client immediately and provide the information needed for the notification. Delay at this step is the single most common cause of missed 24-hour deadlines.

Step 4: Prepare the Written Report

Draft the 5-day written follow-up or the noncompliance narrative for the DMR. Include all five required elements (description, duration, volume/concentration, cause, corrective actions). The corrective action section is particularly important—regulators evaluate whether the permittee took reasonable steps to prevent recurrence.

Step 5: Document in the DMR

Ensure the exceedance appears on the next DMR submission. For facilities already using NetDMR for electronic reporting, this means entering the actual measured value even when it exceeds the permit limit. Entering a value at exactly the permit limit to hide an exceedance is falsification of a federal document.

Avoiding Common Exceedance Reporting Errors

After reviewing hundreds of NPDES compliance files, certain errors recur consistently:

Applying the wrong permit limit: Using an expired permit limit when the permit has been renewed with new limits. Always confirm you are comparing against the current effective permit.
Confusing daily maximum with monthly average: A single grab sample result of 52 mg/L against a 45 mg/L daily maximum is an exceedance. The same result against a 45 mg/L monthly average is not necessarily an exceedance until the monthly average is calculated from all samples in the period.
Missing the “aware” trigger: The 24-hour clock starts when any person associated with the facility becomes aware of the noncompliance. If the lab calls with preliminary results on Thursday but the formal EDD arrives Monday, Thursday starts the clock.
Incomplete corrective action documentation: Stating “will investigate” without specific actions. Regulators want to see: what caused it, what was done immediately, what will prevent recurrence.
Failing to amend prior DMRs: If late-arriving data reveals an exceedance in a period already reported, the DMR must be amended. Leaving an inaccurate DMR in the system is a separate violation.

The consultants who handle exceedances well share one trait: they have a documented response procedure prepared before the exceedance happens. A pre-built notification matrix, a template for the 5-day written report, and a checklist for DMR amendment make the difference between a clean compliance record and an enforcement escalation. For related guidance on managing compliance data across multiple permits, see our coverage of why firms are re-evaluating their environmental data management tools.