Is BRADFORD required to publish a Consumer Confidence Report?

Yes. BRADFORD 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 BRADFORD’s next Consumer Confidence Report due?

BRADFORD’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.

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.

BRADFORD, IL · Stark County

BRADFORD Water System

Consumer Confidence Report status

BRADFORD 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 1 item for BRADFORD that is open and awaiting resolution. None are health-based violations — open items of this kind are most often monitoring or reporting requirements, not water-safety findings.

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): IL1750050
System type: Community Water System
Population served: 676
Service connections: 341
Ownership: local government
Water source: groundwater (wells)

BRADFORD is one of 773 community water systems in Illinois in the 501 to 3,300 people size category, serving 676 people from groundwater.

As of August 1, 2026, its federal record holds 18 entries between 1977 and 2026, of which 1 remains open; none are health-based.

Of the 18, 3 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, the Total Coliform Rules, and the Lead and Copper Rule.

Violation history

Follow-up Or Routine LCR Tap M/R
—
Lead and Copper Rule
January 1, 2026
Unaddressed
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
April 1, 2004 – June 30, 2004
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
April 1, 2003 – June 30, 2003
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 1, 2003 – March 31, 2003
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
October 1, 2002 – December 31, 2002
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Gross Alpha, Excl. Radon and U
January 1, 2002 – September 30, 2002
Resolved
Maximum Contaminant Level Violation, Monthly (TCR)
Health-based
Coliform (TCR)
September 1, 1998 – September 30, 1998
Archived
Maximum Contaminant Level Violation, Average
Health-based
Gross Alpha, Excl. Radon and U
January 1, 1998 – December 31, 2001
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 1, 1996 – December 31, 1999
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Gross Alpha, Excl. Radon and U
March 21, 1995 – April 2, 1997
Resolved
Monitoring, Routine Major (TCR)
—
Coliform (TCR)
March 1, 1994 – March 31, 1994
Archived
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 1, 1992 – December 31, 1995
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Gross Alpha, Excl. Radon and U
October 1, 1988 – June 25, 1990
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
February 1, 1988 – December 31, 1991
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 1, 1988 – December 31, 1991
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 25, 1984 – January 24, 1988
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Gross Alpha, Excl. Radon and U
October 17, 1980 – October 16, 1984
Resolved
Monitoring, Regular
—
Gross Alpha, Excl. Radon and U
June 30, 1977 – June 29, 1981
Archived

Unaddressed no corrective action on record yetResolved 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
January 1, 2026	Follow-up Or Routine LCR Tap M/R	Lead and Copper Rule	—	Unaddressed
April 1, 2004 – June 30, 2004	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
October 1, 2002 – December 31, 2002	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
January 1, 2002 – September 30, 2002	Maximum Contaminant Level Violation, Average	Gross Alpha, Excl. Radon and U	Health-based	Resolved
September 1, 1998 – September 30, 1998	Maximum Contaminant Level Violation, Monthly (TCR)	Coliform (TCR)	Health-based	Archived
January 1, 1998 – December 31, 2001	Maximum Contaminant Level Violation, Average	Gross Alpha, Excl. Radon and U	Health-based	Resolved
January 1, 1996 – December 31, 1999	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
March 21, 1995 – April 2, 1997	Maximum Contaminant Level Violation, Average	Gross Alpha, Excl. Radon and U	Health-based	Resolved
March 1, 1994 – March 31, 1994	Monitoring, Routine Major (TCR)	Coliform (TCR)	—	Archived
January 1, 1992 – December 31, 1995	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
October 1, 1988 – June 25, 1990	Maximum Contaminant Level Violation, Average	Gross Alpha, Excl. Radon and U	Health-based	Resolved
February 1, 1988 – December 31, 1991	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
January 1, 1988 – December 31, 1991	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
January 25, 1984 – January 24, 1988	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
October 17, 1980 – October 16, 1984	Maximum Contaminant Level Violation, Average	Gross Alpha, Excl. Radon and U	Health-based	Resolved
June 30, 1977 – June 29, 1981	Monitoring, Regular	Gross Alpha, Excl. Radon and U	—	Archived

Unaddressed no corrective action on record yetResolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)

Enforcement actions

January 27, 2026State Public Notification requested1 linked violation
January 27, 2026State Violation/Reminder Notice1 linked violation
March 17, 2006State Public Notification received1 linked violation
February 22, 2005State Compliance achieved1 linked violation
February 9, 2005State Violation/Reminder Notice1 linked violation
February 9, 2005State Public Notification requested1 linked violation
October 19, 2004State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
October 19, 2004State Violation/Reminder Notice1 linked violation
October 19, 2004State Public Notification requested1 linked violation
October 19, 2004State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
September 30, 2004State Public Notification received1 linked violation
September 30, 2004State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
September 29, 2004State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
September 29, 2004State Public Notification received1 linked violation
September 2, 2004State Compliance achieved16 linked violations
July 10, 2004State Public Notification requested1 linked violation
July 10, 2004State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
July 10, 2004State Violation/Reminder Notice1 linked violation
April 10, 2004State Public Notification requested1 linked violation
April 10, 2004State Violation/Reminder Notice1 linked violation
April 10, 2004State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
April 10, 2004State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
March 17, 2004State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
March 17, 2004State Public Notification received1 linked violation
March 9, 2004State Bilateral Compliance Agreement signed15 linked violations
January 21, 2004State Formal Notice of Violation issued15 linked violations
January 15, 2004State Public Notification received1 linked violation
January 15, 2004State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
January 10, 2004State Public Notification requested1 linked violation
January 10, 2004State Violation/Reminder Notice1 linked violation
January 10, 2004State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
January 10, 2004State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
October 15, 2003State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
October 15, 2003State Public Notification received1 linked violation
September 11, 2003State Public Notification received1 linked violation
September 11, 2003State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
July 10, 2003State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
July 10, 2003State Public Notification requested1 linked violation
July 10, 2003State Violation/Reminder Notice1 linked violation
July 10, 2003State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
April 10, 2003State Violation/Reminder Notice1 linked violation
April 10, 2003State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
April 10, 2003State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
April 10, 2003State Public Notification requested1 linked violation
April 9, 2003State Public Notification received1 linked violation
April 9, 2003State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
January 10, 2003State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
January 10, 2003State Public Notification requested1 linked violation
January 10, 2003State Violation/Reminder Notice1 linked violation
January 10, 2003State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
December 3, 2001State Bilateral Compliance Agreement signed12 linked violations
November 15, 1998State Public Notification requested1 linked violation
November 15, 1998State Violation/Reminder Notice1 linked violation
March 25, 1998State Public Notification received1 linked violation
September 17, 1997State Public Notification received1 linked violation
April 2, 1997State Compliance achieved1 linked violation
March 26, 1997State Public Notification received2 linked violations
December 11, 1996State Public Notification received1 linked violation
September 25, 1996State Public Notification received2 linked violations
June 26, 1996State Public Notification received2 linked violations
March 20, 1996State Public Notification received2 linked violations
December 13, 1995State Public Notification received2 linked violations
September 20, 1995State Public Notification received2 linked violations
June 21, 1995State Public Notification received2 linked violations
April 29, 1995State Public Notification received1 linked violation
March 29, 1995State Public Notification received1 linked violation
December 14, 1994State Public Notification received1 linked violation
June 15, 1994State Public Notification received1 linked violation
May 28, 1994State Public Notification requested1 linked violation
May 28, 1994State Violation/Reminder Notice1 linked violation
May 16, 1994State Public Notification received3 linked violations
May 16, 1994State Public Notification received1 linked violation
December 22, 1993State Public Notification received1 linked violation
September 22, 1993State Public Notification received1 linked violation
June 30, 1993State Public Notification received1 linked violation
March 10, 1993State Public Notification received1 linked violation
October 28, 1992State Public Notification received1 linked violation
August 5, 1992State Public Notification received1 linked violation
April 6, 1992State Public Notification received1 linked violation
December 18, 1991State Public Notification received2 linked violations
June 26, 1991State Public Notification received2 linked violations
March 20, 1991State Public Notification received2 linked violations
December 24, 1990State Public Notification received2 linked violations
September 28, 1990State Public Notification received2 linked violations
July 5, 1990State Public Notification received2 linked violations
June 25, 1990State Compliance achieved3 linked violations
March 21, 1990State Public Notification received3 linked violations
July 13, 1989State Public Notification received3 linked violations
January 9, 1989State Public Notification received3 linked violations
January 6, 1989State Public Notification requested5 linked violations

Common questions

Is BRADFORD required to publish a Consumer Confidence Report?: Yes. BRADFORD 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 BRADFORD’s next Consumer Confidence Report due?: BRADFORD’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does BRADFORD have any open drinking water violations on record?: As of August 1, 2026, EPA's federal records show 1 item for BRADFORD that is open and awaiting resolution. None are health-based violations — open items of this kind are most often monitoring or reporting requirements, not water-safety findings.
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

CHADWICK, JIM

Phone not on record

BRADFORD, IL 61421