How to Interpret ECHO Violation Data

ECHO violation data is useful, but the raw numbers require interpretation. A violation doesn't always indicate serious environmental risk, and a clean record doesn't always mean clean conditions. Getting this wrong leads to either over-reacting to minor compliance issues or missing meaningful red flags.

What counts as a violation

A violation in ECHO means a facility exceeded a permit limit or failed to meet a regulatory requirement. That category covers a very wide range:

• Effluent violations — discharged more than the permit allows into a waterway
• Emissions violations — exceeded air permit limits
• Monitoring and reporting violations — didn't submit required reports on time
• Schedule violations — missed a compliance schedule deadline
• Treatment standard violations — didn't treat waste to the required standard before disposal

Missing a monthly discharge monitoring report is technically a violation. So is releasing 10 times the permitted level of a toxic pollutant. ECHO records both the same way unless you look at the severity flags.

Significant Noncompliance (SNC)

The most important flag in ECHO is Significant Noncompliance status. SNC is assigned when violations meet certain severity thresholds — typically when effluent or emission violations exceed permit limits by a significant margin, or when a pattern of violations suggests ongoing noncompliance rather than one-off failures.

A facility with only minor violations — late reports, minor schedule delays — is a different risk profile than one with SNC designations. When reviewing ECHO data, look at SNC history first before tallying up total violations.

The enforcement gap

Not every violation leads to enforcement action. EPA and state agencies have limited resources and prioritize by severity and facility type. A facility may have violations on record that were never formally penalized, cited, or even followed up on with an inspection.

This doesn't make those violations less real. It means the regulatory response was limited. For due diligence, look at both the violation record and the enforcement record. Unresolved violations without enforcement action sometimes warrant more scrutiny than violations that were formally resolved — at least the enforcement process creates a documented resolution.

What no violations means

A clean compliance record in ECHO means the facility met its permit requirements during the period covered by ECHO records. It does not mean:

• The site is uncontaminated
• The facility had no environmental impact
• There are no state-level compliance issues not in ECHO
• Historical contamination from before EPA programs doesn't exist
• Neighboring sites haven't affected this property

A dry cleaning facility from the 1970s with a perfectly clean ECHO record can still have significant PCE contamination in the soil and groundwater. The contamination predates or falls outside of what ECHO tracks.

Reading the pattern, not just the count

The most useful analysis of ECHO data looks at patterns rather than raw violation counts:

• Repeated violations in the same program (CWA, CAA, RCRA) suggest systemic issues, not one-time failures
• Violations that coincide with ownership changes may indicate deferred maintenance or a change in operational discipline
• Recent violations (past 2–3 years) are more significant than old, resolved ones
• Facilities with violations but no inspections in several years may have unreported issues — inspections reveal violations, so no inspections means less data, not clean conditions
• A sudden increase in violation frequency is a red flag regardless of absolute counts

Contextualizing in reports

When including ECHO violation data in a due diligence memo or ESA report, raw counts without context aren't useful to most clients. "Three monitoring and reporting violations in 2019" reads very differently from "two Significant Noncompliance designations under the Clean Water Act in the past 18 months, with no enforcement resolution documented."

Good practice: identify the violations, note whether they're SNC or minor, describe whether enforcement action was taken, note whether issues appear resolved, and give your professional judgment on what this means for risk. That's more useful than an ECHO printout.

Industry context matters

Violation rates vary significantly by industry. Some heavily regulated sectors (large CAFOs, chemical manufacturers, certain industrial processes) have higher baseline violation rates because the permit requirements are more numerous and the monitoring is more frequent. A refinery with 5 violations over 10 years may be a better compliance performer than a smaller facility with 2 violations if the refinery's permit has far more requirements.

EnvScore's risk scoring accounts for this by weighting violations relative to industry benchmarks, not just counting them. If you're doing comparisons across different facility types, this kind of normalization matters.