BARTLETT, IL · Cook County
BARTLETT Water System
Consumer Confidence Report status
BARTLETT must publish a Consumer Confidence Report — the annual drinking water quality report covering calendar year 2026 — by July 1, 2027.
As of August 1, 2026, EPA's federal records show no open violations for BARTLETT.
Data sourced from the EPA ECHO database (SDWA bulk download), last refreshed August 1, 2026. This is a record-keeping and public-information tool — it does not replace Illinois’s official records. Always confirm current status with Illinois before making decisions based on this information.
System facts
- System ID (PWSID)
- IL0314120
- System type
- Community Water System
- Population served
- 41,500
- Service connections
- 14,545
- Ownership
- local government
- Water source
- surface water (rivers, lakes, or reservoirs)
BARTLETT is one of 225 community water systems in Illinois in the 10,001 to 100,000 people size category, serving 41,500 people from surface water.
As of August 1, 2026, its federal record holds 37 entries between 1992 and 2011, all of which EPA lists as closed. Nothing has been added since 2011.
Of the 37, 4 are monitoring and reporting requirements — the category that accounts for about four in five of all violations in EPA's national dataset — rather than findings about the water itself. The record involves the Radionuclides and Revised Rad Rule, inorganic chemicals, and the Lead and Copper Rule.
Violation history
Maximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2011 – September 30, 2011
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2011 – June 30, 2011
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2011 – March 31, 2011
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2010 – December 31, 2010
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2010 – September 30, 2010
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2010 – June 30, 2010
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2010 – March 31, 2010
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2009 – December 31, 2009
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2009 – September 30, 2009
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2009 – June 30, 2009
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2009 – March 31, 2009
ResolvedMaximum Contaminant Level Violation, Average
Health-basedBarium
January 1, 2009 – March 31, 2009
ResolvedMaximum Contaminant Level Violation, Average
Health-basedBarium
October 1, 2008 – December 31, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2008 – December 31, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedBarium
July 1, 2008 – September 30, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2008 – June 30, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedBarium
April 1, 2008 – June 30, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2008 – March 31, 2008
ResolvedMonitoring, Regular
—Combined Radium (-226 and -228)
April 1, 2007 – June 30, 2007
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2006 – March 31, 2006
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2004 – June 30, 2004
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2004 – March 31, 2004
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2003 – September 30, 2003
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2003 – June 30, 2003
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2003 – March 31, 2003
ResolvedMonitoring, Repeat Minor (TCR)
—Coliform (TCR)
July 1, 2001 – July 31, 2001
ArchivedMaximum Contaminant Level Violation, Average
Health-basedBarium
October 1, 1998 – December 31, 1998
ResolvedMaximum Contaminant Level Violation, Average
Health-basedBarium
July 1, 1998 – September 30, 1998
ResolvedMaximum Contaminant Level Violation, Average
Health-basedBarium
April 1, 1998 – June 30, 1998
ResolvedMaximum Contaminant Level Violation, Average
Health-basedBarium
January 1, 1998 – March 31, 1998
ResolvedOCCT/SOWT Study/Recommendation
Health-basedLead and Copper Rule
August 1, 1995 – August 26, 1996
ResolvedOCCT/SOWT Study/Recommendation
Health-basedLead and Copper Rule
January 12, 1995 – August 26, 1996
ResolvedPublic Education
Health-basedLead and Copper Rule
January 1, 1995 – February 21, 1997
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
September 1, 1994 – September 30, 1994
ArchivedMonitoring, Repeat Minor (TCR)
—Coliform (TCR)
September 1, 1994 – September 30, 1994
ArchivedWater Quality Parameter M/R
—Lead and Copper Rule
January 1, 1994 – June 30, 1994
ResolvedOCCT/SOWT Study/Recommendation
Health-basedLead and Copper Rule
December 7, 1992 – July 15, 1994
Resolved
Resolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| July 1, 2011 – September 30, 2011 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2011 – June 30, 2011 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2011 – March 31, 2011 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2010 – December 31, 2010 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2010 – September 30, 2010 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2010 – June 30, 2010 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2010 – March 31, 2010 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2009 – December 31, 2009 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2009 – September 30, 2009 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2009 – June 30, 2009 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2009 – March 31, 2009 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2009 – March 31, 2009 | Maximum Contaminant Level Violation, Average | Barium | Health-based | Resolved |
| October 1, 2008 – December 31, 2008 | Maximum Contaminant Level Violation, Average | Barium | Health-based | Resolved |
| October 1, 2008 – December 31, 2008 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2008 – September 30, 2008 | Maximum Contaminant Level Violation, Average | Barium | Health-based | Resolved |
| April 1, 2008 – June 30, 2008 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2008 – June 30, 2008 | Maximum Contaminant Level Violation, Average | Barium | Health-based | Resolved |
| January 1, 2008 – March 31, 2008 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2007 – June 30, 2007 | Monitoring, Regular | Combined Radium (-226 and -228) | — | Resolved |
| January 1, 2006 – March 31, 2006 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2004 – June 30, 2004 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2004 – March 31, 2004 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2003 – September 30, 2003 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2003 – June 30, 2003 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2003 – March 31, 2003 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2001 – July 31, 2001 | Monitoring, Repeat Minor (TCR) | Coliform (TCR) | — | Archived |
| October 1, 1998 – December 31, 1998 | Maximum Contaminant Level Violation, Average | Barium | Health-based | Resolved |
| July 1, 1998 – September 30, 1998 | Maximum Contaminant Level Violation, Average | Barium | Health-based | Resolved |
| April 1, 1998 – June 30, 1998 | Maximum Contaminant Level Violation, Average | Barium | Health-based | Resolved |
| January 1, 1998 – March 31, 1998 | Maximum Contaminant Level Violation, Average | Barium | Health-based | Resolved |
| August 1, 1995 – August 26, 1996 | OCCT/SOWT Study/Recommendation | Lead and Copper Rule | Health-based | Resolved |
| January 12, 1995 – August 26, 1996 | OCCT/SOWT Study/Recommendation | Lead and Copper Rule | Health-based | Resolved |
| January 1, 1995 – February 21, 1997 | Public Education | Lead and Copper Rule | Health-based | Resolved |
| September 1, 1994 – September 30, 1994 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Archived |
| September 1, 1994 – September 30, 1994 | Monitoring, Repeat Minor (TCR) | Coliform (TCR) | — | Archived |
| January 1, 1994 – June 30, 1994 | Water Quality Parameter M/R | Lead and Copper Rule | — | Resolved |
| December 7, 1992 – July 15, 1994 | OCCT/SOWT Study/Recommendation | Lead and Copper Rule | Health-based | Resolved |
Resolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)
Enforcement actions
- December 6, 2011State Public Notification received1 linked violation
- October 20, 2011State Public Notification requested1 linked violation
- October 20, 2011State Violation/Reminder Notice1 linked violation
- October 11, 2011State Public Notification received1 linked violation
- September 30, 2011State Compliance achieved4 linked violations
- July 29, 2011State Violation/Reminder Notice1 linked violation
- July 29, 2011State Public Notification requested1 linked violation
- June 3, 2011State Public Notification received1 linked violation
- April 19, 2011State Public Notification requested1 linked violation
- April 19, 2011State Violation/Reminder Notice1 linked violation
- April 6, 2011State Public Notification received1 linked violation
- January 21, 2011State Violation/Reminder Notice1 linked violation
- January 21, 2011State Bilateral Compliance Agreement signed4 linked violations
- January 21, 2011State Public Notification requested1 linked violation
- December 9, 2010State Public Notification received1 linked violation
- November 24, 2010State Compliance achieved8 linked violations
- November 10, 2010State Formal Notice of Violation issued4 linked violations
- October 19, 2010State Violation/Reminder Notice1 linked violation
- October 19, 2010State Public Notification requested1 linked violation
- October 5, 2010State Public Notification received1 linked violation
- July 15, 2010State Violation/Reminder Notice1 linked violation
- July 15, 2010State Public Notification requested1 linked violation
- June 30, 2010State Public Notification received1 linked violation
- April 20, 2010State Violation/Reminder Notice1 linked violation
- April 20, 2010State Public Notification requested1 linked violation
- April 15, 2010State Public Notification received1 linked violation
- March 2, 2010State Violation/Reminder Notice1 linked violation
- March 2, 2010State Public Notification requested1 linked violation
- December 7, 2009State Public Notification received1 linked violation
- October 20, 2009State Violation/Reminder Notice1 linked violation
- October 20, 2009State Public Notification requested1 linked violation
- October 14, 2009State Public Notification received1 linked violation
- July 15, 2009State Public Notification requested1 linked violation
- July 15, 2009State Violation/Reminder Notice1 linked violation
- July 6, 2009State Public Notification received1 linked violation
- April 21, 2009State Public Notification requested1 linked violation
- April 21, 2009State Public Notification requested1 linked violation
- April 21, 2009State Violation/Reminder Notice1 linked violation
- April 21, 2009State Violation/Reminder Notice1 linked violation
- April 7, 2009State Compliance achieved6 linked violations
- February 18, 2009State Public Notification received2 linked violations
- January 16, 2009State Bilateral Compliance Agreement signed4 linked violations
- January 16, 2009State Bilateral Compliance Agreement signed3 linked violations
- January 15, 2009State Public Notification requested1 linked violation
- January 15, 2009State Violation/Reminder Notice1 linked violation
- January 14, 2009State Violation/Reminder Notice1 linked violation
- January 14, 2009State Public Notification requested1 linked violation
- November 6, 2008State Violation/Reminder Notice1 linked violation
- November 6, 2008State Public Notification requested1 linked violation
- September 11, 2008State Formal Notice of Violation issued4 linked violations
- September 9, 2008State Compliance achieved2 linked violations
- August 15, 2008State Public Notification received2 linked violations
- July 17, 2008State Violation/Reminder Notice1 linked violation
- July 17, 2008State Public Notification requested1 linked violation
- July 17, 2008State Violation/Reminder Notice1 linked violation
- July 17, 2008State Public Notification requested1 linked violation
- June 25, 2008State Bilateral Compliance Agreement signed10 linked violations
- May 28, 2008State Public Notification received1 linked violation
- May 28, 2008State Public Notification received1 linked violation
- April 25, 2008State Formal Notice of Violation issued10 linked violations
- April 16, 2008State Violation/Reminder Notice1 linked violation
- April 16, 2008State Public Notification requested1 linked violation
- August 13, 2007State Compliance achieved1 linked violation
- July 13, 2007State Violation/Reminder Notice1 linked violation
- July 13, 2007State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- July 13, 2007State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- July 13, 2007State Public Notification requested1 linked violation
- June 28, 2007State Public Notification received4 linked violations
- June 19, 2007State Compliance achieved4 linked violations
- June 1, 2007State Compliance achieved1 linked violation
- April 24, 2007State Public Notification requested1 linked violation
- April 24, 2007State Violation/Reminder Notice1 linked violation
- April 18, 2007State Bilateral Compliance Agreement signed2 linked violations
- April 17, 2007State Public Notification requested1 linked violation
- April 17, 2007State Violation/Reminder Notice1 linked violation
- March 13, 2007State Violation/Reminder Notice1 linked violation
- March 5, 2007State Public Notification received1 linked violation
- February 27, 2007State Compliance achieved1 linked violation
- February 7, 2007State Formal Notice of Violation issued2 linked violations
- February 6, 2007State Public Notification received1 linked violation
- January 17, 2007State Public Notification requested1 linked violation
- January 17, 2007State Violation/Reminder Notice2 linked violations
- January 16, 2007State Public Notification requested1 linked violation
- January 16, 2007State Violation/Reminder Notice1 linked violation
- December 27, 2006State Compliance achieved1 linked violation
- December 14, 2006State Violation/Reminder Notice1 linked violation
- December 14, 2006State Public Notification requested1 linked violation
- December 14, 2006State Violation/Reminder Notice1 linked violation
- December 14, 2006State Public Notification requested1 linked violation
- December 6, 2006State Compliance achieved1 linked violation
- November 30, 2006State Compliance achieved16 linked violations
- October 24, 2006State Public Notification received2 linked violations
- October 12, 2006State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- October 12, 2006State Public Notification requested2 linked violations
- October 12, 2006State Violation/Reminder Notice1 linked violation
- October 12, 2006State Violation/Reminder Notice1 linked violation
- August 7, 2006State Public Notification received1 linked violation
- July 10, 2006State Violation/Reminder Notice1 linked violation
- July 10, 2006State Public Notification requested1 linked violation
- June 12, 2006State Public Notification received1 linked violation
- April 11, 2006State Violation/Reminder Notice1 linked violation
- April 11, 2006State Public Notification requested1 linked violation
- January 19, 2006State Public Notification received1 linked violation
- January 10, 2006State Violation/Reminder Notice1 linked violation
- January 10, 2006State Public Notification requested1 linked violation
- October 25, 2005State Public Notification received1 linked violation
- October 7, 2005State Public Notification requested1 linked violation
- October 7, 2005State Violation/Reminder Notice1 linked violation
- July 8, 2005State Violation/Reminder Notice1 linked violation
- June 26, 2005State Public Notification received2 linked violations
- April 20, 2005State Public Notification received2 linked violations
- April 8, 2005State Violation/Reminder Notice1 linked violation
- April 8, 2005State Public Notification requested1 linked violation
- February 7, 2005State Public Notification received1 linked violation
- January 7, 2005State Public Notification requested1 linked violation
- January 7, 2005State Violation/Reminder Notice1 linked violation
- October 19, 2004State Violation/Reminder Notice1 linked violation
- October 19, 2004State Public Notification requested1 linked violation
- October 12, 2004State Public Notification received1 linked violation
- August 26, 2004State Public Notification received1 linked violation
- July 10, 2004State Public Notification requested1 linked violation
- July 10, 2004State Violation/Reminder Notice1 linked violation
- April 10, 2004State Public Notification requested1 linked violation
- March 4, 2004State Bilateral Compliance Agreement signed17 linked violations
- February 11, 2004State Public Notification received1 linked violation
- January 10, 2004State Public Notification requested1 linked violation
- January 10, 2004State Violation/Reminder Notice1 linked violation
- December 17, 2003State Formal Notice of Violation issued17 linked violations
- August 6, 2003State Public Notification received1 linked violation
- May 14, 2003State Public Notification requested2 linked violations
- May 14, 2003State Violation/Reminder Notice1 linked violation
- January 1, 1999State Compliance achieved4 linked violations
- April 1, 1998State Violation/Reminder Notice1 linked violation
- April 1, 1998State Public Notification requested1 linked violation
- April 1, 1998State Public Notification received1 linked violation
- March 9, 1998State Public Notification requested1 linked violation
- March 9, 1998State Violation/Reminder Notice1 linked violation
- February 21, 1997State Compliance achieved1 linked violation
- August 26, 1996State Compliance achieved2 linked violations
- March 12, 1996State Public Notification requested1 linked violation
- March 12, 1996State Violation/Reminder Notice1 linked violation
- December 31, 1994State Compliance achieved1 linked violation
- November 19, 1994State Public Notification requested2 linked violations
- November 19, 1994State Violation/Reminder Notice2 linked violations
- September 19, 1994State Public Notification received1 linked violation
- September 19, 1994State Public Notification received1 linked violation
- August 20, 1994State Violation/Reminder Notice1 linked violation
- August 20, 1994State Violation/Reminder Notice1 linked violation
- August 20, 1994State Public Notification requested1 linked violation
- August 20, 1994State Public Notification requested1 linked violation
- July 15, 1994State Compliance achieved1 linked violation
- July 15, 1994State Compliance achieved1 linked violation
- July 15, 1994State Compliance achieved2 linked violations
- November 27, 1993State Violation/Reminder Notice2 linked violations
- November 27, 1993State Public Notification requested1 linked violation
- November 27, 1993State Violation/Reminder Notice1 linked violation
- November 27, 1993State Violation/Reminder Notice1 linked violation
- November 27, 1993State Public Notification requested1 linked violation
- November 27, 1993State Public Notification requested2 linked violations
- September 1, 1990State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- September 1, 1990State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- January 1, 1989State Violation/Reminder Notice1 linked violation
Common questions
Is BARTLETT required to publish a Consumer Confidence Report?
- Yes. BARTLETT is a community water system, and federal rules (40 CFR 141 Subpart O) require every community water system to publish a Consumer Confidence Report each year.
When is BARTLETT’s next Consumer Confidence Report due?
- BARTLETT’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does BARTLETT have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for BARTLETT.
What is a Consumer Confidence Report?
- A Consumer Confidence Report (CCR) is the annual drinking water quality report that community water systems must provide to the people they serve. It lists the contaminants detected in the system’s water during the year, where the water comes from, and how the results compare with federal limits. EPA’s revised CCR rule takes effect January 1, 2027, and the first reports in the new format are due July 1, 2027.
Contact
DINGES, DAN
630-837-0811
BARTLETT, IL 60103