BRIGGSDALE, CO · Weld County
BRIGGSDALE WC Water System
Consumer Confidence Report status
BRIGGSDALE WC 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 BRIGGSDALE WC.
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 Colorado’s official records. Always confirm current status with Colorado before making decisions based on this information.
System facts
- System ID (PWSID)
- CO0162155
- System type
- Community Water System
- Population served
- 303
- Service connections
- 63
- Ownership
- privately owned
- Water source
- groundwater (wells)
BRIGGSDALE WC is one of 1,060 community water systems in Colorado in the 500 or fewer people size category, serving 303 people from groundwater.
As of August 1, 2026, its federal record holds 9 entries between 1996 and 2025, all of which EPA lists as closed.
All 9 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 inorganic chemicals and the Lead and Copper Rule.
Violation history
Notification, Known or Potential LSL
—LEAD AND COPPER RULE REVISIONS
July 2, 2025 – July 28, 2025
ResolvedMonitoring, Regular
—Fluoride
January 1, 2005 – December 31, 2007
ResolvedMonitoring, Regular
—Nitrate
January 1, 2003 – December 31, 2003
ResolvedMonitoring, Regular
—Nitrate
January 1, 2001 – December 31, 2001
ResolvedMonitoring, Regular
—Fluoride
January 1, 1996 – December 31, 1998
ResolvedMonitoring, Regular
—Nickel
January 1, 1996 – December 31, 1998
ResolvedMonitoring, Regular
—Cadmium
January 1, 1996 – December 31, 1998
ResolvedMonitoring, Regular
—Barium
January 1, 1996 – December 31, 1998
ResolvedMonitoring, Regular
—Arsenic
January 1, 1996 – December 31, 1998
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| July 2, 2025 – July 28, 2025 | Notification, Known or Potential LSL | LEAD AND COPPER RULE REVISIONS | — | Resolved |
| January 1, 2005 – December 31, 2007 | Monitoring, Regular | Fluoride | — | Resolved |
| January 1, 2003 – December 31, 2003 | Monitoring, Regular | Nitrate | — | Resolved |
| January 1, 2001 – December 31, 2001 | Monitoring, Regular | Nitrate | — | Resolved |
| January 1, 1996 – December 31, 1998 | Monitoring, Regular | Fluoride | — | Resolved |
| January 1, 1996 – December 31, 1998 | Monitoring, Regular | Nickel | — | Resolved |
| January 1, 1996 – December 31, 1998 | Monitoring, Regular | Cadmium | — | Resolved |
| January 1, 1996 – December 31, 1998 | Monitoring, Regular | Barium | — | Resolved |
| January 1, 1996 – December 31, 1998 | Monitoring, Regular | Arsenic | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- July 29, 2025State Public Notification received1 linked violation
- July 28, 2025State Compliance achieved1 linked violation
- July 16, 2025State Violation/Reminder Notice1 linked violation
- July 16, 2025State Public Notification requested1 linked violation
- June 15, 2021State Public Notification requested1 linked violation
- April 30, 2010State Compliance achieved2 linked violations
- April 10, 2008State Compliance achieved2 linked violations
- February 8, 2008State Public Notification requested1 linked violation
- October 27, 2004State Compliance achieved1 linked violation
- February 6, 2004State Violation/Reminder Notice1 linked violation
- February 6, 2004State Public Notification requested1 linked violation
- March 27, 2002State Compliance achieved1 linked violation
- March 4, 2002State Formal Notice of Violation issued1 linked violation
- March 4, 2002State Public Notification requested1 linked violation
- November 20, 2001State Compliance achieved2 linked violations
- November 20, 2001State Compliance achieved1 linked violation
- November 20, 2001State Compliance achieved1 linked violation
- November 20, 2001State Compliance achieved1 linked violation
- November 20, 2001State Compliance achieved1 linked violation
- November 20, 2001State Compliance achieved1 linked violation
- November 20, 2001State Compliance achieved1 linked violation
- November 20, 2001State Compliance achieved3 linked violations
- November 20, 2001State Compliance achieved1 linked violation
- July 3, 2000State Public Notification requested9 linked violations
- July 3, 2000State Formal Notice of Violation issued1 linked violation
- March 3, 1999State Public Notification requested1 linked violation
- March 3, 1999State Public Notification requested1 linked violation
- March 3, 1999State Public Notification requested1 linked violation
- March 3, 1999State Public Notification requested1 linked violation
- March 3, 1999State Public Notification requested1 linked violation
- March 3, 1999State Public Notification requested1 linked violation
- March 3, 1999State Public Notification requested1 linked violation
- March 3, 1999State Public Notification requested1 linked violation
- March 3, 1999State Public Notification requested1 linked violation
- March 3, 1999State Public Notification requested1 linked violation
- March 3, 1999State Formal Notice of Violation issued1 linked violation
- March 3, 1999State Formal Notice of Violation issued1 linked violation
- March 3, 1999State Formal Notice of Violation issued1 linked violation
- March 3, 1999State Formal Notice of Violation issued1 linked violation
- March 3, 1999State Formal Notice of Violation issued1 linked violation
- March 3, 1999State Formal Notice of Violation issued1 linked violation
- March 3, 1999State Formal Notice of Violation issued1 linked violation
- March 3, 1999State Formal Notice of Violation issued1 linked violation
- March 3, 1999State Formal Notice of Violation issued1 linked violation
- March 3, 1999State Formal Notice of Violation issued1 linked violation
- March 3, 1999State Formal Notice of Violation issued1 linked violation
- March 3, 1999State Public Notification requested1 linked violation
Common questions
Is BRIGGSDALE WC required to publish a Consumer Confidence Report?
- Yes. BRIGGSDALE WC 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 BRIGGSDALE WC’s next Consumer Confidence Report due?
- BRIGGSDALE WC’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does BRIGGSDALE WC have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for BRIGGSDALE WC.
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
WARNER, JERRY
970-302-7388
BRIGGSDALE, CO 80611