How EPA's ECHO Database Is Updated and What Its Lag Time Means
EPA\'s Enforcement and Compliance History Online (ECHO) system is updated regularly, but not in real time — and understanding the various update schedules for different components of ECHO is essential for correctly interpreting the data. A facility that shows a clean compliance record in ECHO today may have recent violations that simply haven\'t been entered yet. Conversely, a facility may have resolved violations that still appear in ECHO because the resolution hasn\'t been processed.
ECHO Component Update Schedules
Different ECHO data elements are updated on different schedules. Discharge Monitoring Reports (DMRs) for NPDES water permits are typically processed weekly as states submit data from facilities. RCRA inspection and violation data has a longer lag — state-submitted RCRA data may take 30–90 days to appear. TRI release data is updated annually after the July 1 reporting deadline, with a lag of several months for data processing. Facility basic information (name, address, permit status) is updated continuously. EmissionsLookup loads fresh ECHO and TRI data as it becomes available.
The TRI Annual Cycle
TRI reporting is annual — facilities report releases from the prior calendar year by July 1. EPA then processes, verifies, and publishes the data over the following months. The TRI dataset on EmissionsLookup represents the most recently published reporting year, which may be 18–24 months behind current operations. A facility that installed major pollution controls in the past year may not yet show that improvement in the available TRI data.
Inspection Frequency and Data Completeness
The completeness of ECHO compliance data depends heavily on inspection frequency. States vary significantly in how frequently they inspect permitted facilities — some conduct annual inspections of major sources; others inspect major sources every 3–5 years. A facility that has never been inspected may show a clean compliance record in ECHO simply because violations were never documented, not because the facility is actually compliant. This is a real limitation of administrative compliance data that users should bear in mind.
Using Date Context
When citing EmissionsLookup data, always note the data vintage: the ECHO data download date and the TRI reporting year. For recent regulatory actions and permit modifications, check EPA\'s public notice systems and state agency portals, which may be more current than ECHO. Browse our facility database with these limitations in mind, and cross-reference with enforcement records for recent formal actions.