BRIDPORT, VT · Addison County
TRI TOWN WATER DISTRICT Water System
Consumer Confidence Report status
TRI TOWN WATER DISTRICT 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 TRI TOWN WATER DISTRICT.
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 Vermont’s official records. Always confirm current status with Vermont before making decisions based on this information.
System facts
- System ID (PWSID)
- VT0005001
- System type
- Community Water System
- Population served
- 3,800
- Service connections
- 1,800
- Ownership
- local government
- Water source
- surface water (rivers, lakes, or reservoirs)
TRI TOWN WATER DISTRICT serves 3,800 people from surface water, placing it in the 3,301 to 10,000 people size category.
As of August 1, 2026, its federal record holds 7 entries between 2009 and 2019, all of which EPA lists as closed. Nothing has been added since 2019.
Of the 7, 1 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 Stage 1 Disinfectants and Disinfection Byproducts Rule and the Total Coliform Rules.
Violation history
Monitoring, Routine (RTCR)
—Revised Total Coliform Rule
August 1, 2019 – August 31, 2019
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTotal Haloacetic Acids (HAA5)
October 1, 2010 – December 31, 2010
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTotal Haloacetic Acids (HAA5)
July 1, 2010 – September 30, 2010
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTotal Haloacetic Acids (HAA5)
January 1, 2010 – March 31, 2010
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTotal Haloacetic Acids (HAA5)
October 1, 2009 – December 31, 2009
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTotal Haloacetic Acids (HAA5)
July 1, 2009 – September 30, 2009
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTotal Haloacetic Acids (HAA5)
April 1, 2009 – June 30, 2009
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| August 1, 2019 – August 31, 2019 | Monitoring, Routine (RTCR) | Revised Total Coliform Rule | — | Resolved |
| October 1, 2010 – December 31, 2010 | Maximum Contaminant Level Violation, Average | Total Haloacetic Acids (HAA5) | Health-based | Resolved |
| July 1, 2010 – September 30, 2010 | Maximum Contaminant Level Violation, Average | Total Haloacetic Acids (HAA5) | Health-based | Resolved |
| January 1, 2010 – March 31, 2010 | Maximum Contaminant Level Violation, Average | Total Haloacetic Acids (HAA5) | Health-based | Resolved |
| October 1, 2009 – December 31, 2009 | Maximum Contaminant Level Violation, Average | Total Haloacetic Acids (HAA5) | Health-based | Resolved |
| July 1, 2009 – September 30, 2009 | Maximum Contaminant Level Violation, Average | Total Haloacetic Acids (HAA5) | Health-based | Resolved |
| April 1, 2009 – June 30, 2009 | Maximum Contaminant Level Violation, Average | Total Haloacetic Acids (HAA5) | Health-based | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- June 15, 2020State Public Notification received1 linked violation
- June 15, 2020State Public Notification received1 linked violation
- May 12, 2020State Compliance achieved1 linked violation
- March 20, 2020State Public Notification requested1 linked violation
- March 20, 2020State Formal Notice of Violation issued1 linked violation
- November 18, 2019State Compliance achieved1 linked violation
- October 24, 2019State Public Notification requested1 linked violation
- October 24, 2019State Formal Notice of Violation issued1 linked violation
- May 17, 2013State Compliance achieved11 linked violations
- May 16, 2011State Public Notification received1 linked violation
- April 29, 2011State Technical Assistance Visit1 linked violation
- April 29, 2011State Formal Notice of Violation issued1 linked violation
- April 29, 2011State Public Notification requested1 linked violation
- February 7, 2011State Public Notification received1 linked violation
- January 25, 2011State Technical Assistance Visit1 linked violation
- January 25, 2011State Formal Notice of Violation issued1 linked violation
- January 25, 2011State Public Notification requested1 linked violation
- February 11, 2010State Public Notification received1 linked violation
- October 29, 2009State Public Notification received1 linked violation
- October 14, 2009State Public Notification requested1 linked violation
- October 14, 2009State Formal Notice of Violation issued1 linked violation
- October 14, 2009State Technical Assistance Visit1 linked violation
- May 7, 2009State Public Notification received1 linked violation
- April 22, 2009State Technical Assistance Visit1 linked violation
- April 22, 2009State Public Notification requested1 linked violation
- April 22, 2009State Formal Notice of Violation issued1 linked violation
- April 2, 2007State Public Notification received3 linked violations
- January 1, 2005State Violation/Reminder Notice1 linked violation
- January 1, 2005State Public Notification requested1 linked violation
- January 1, 2005State Violation/Reminder Notice1 linked violation
- January 1, 2005State Public Notification requested1 linked violation
- April 2, 2004State Public Notification received1 linked violation
- April 2, 2004State Public Notification received1 linked violation
- June 26, 2003State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- June 13, 2003State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- June 13, 2003State Public Notification requested1 linked violation
- June 13, 2003State Formal Notice of Violation issued1 linked violation
- June 13, 2003State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
Common questions
Is TRI TOWN WATER DISTRICT required to publish a Consumer Confidence Report?
- Yes. TRI TOWN WATER DISTRICT 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 TRI TOWN WATER DISTRICT’s next Consumer Confidence Report due?
- TRI TOWN WATER DISTRICT’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does TRI TOWN WATER DISTRICT have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for TRI TOWN WATER DISTRICT.
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
PRATT, DARWIN
802-758-2202
BRIDPORT, VT 05734