Is ARLAM CONCORD WSC required to publish a Consumer Confidence Report?

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

ARLAM CONCORD WSC’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.

GARRISON, TX · Rusk County

ARLAM CONCORD WSC Water System

Consumer Confidence Report status

ARLAM CONCORD WSC 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 ARLAM CONCORD WSC.

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 Texas’s official records. Always confirm current status with Texas before making decisions based on this information.

System facts

System ID (PWSID): TX2010004
System type: Community Water System
Population served: 990
Service connections: 330
Ownership: local government
Water source: groundwater (wells)

ARLAM CONCORD WSC is one of 1,859 community water systems in Texas in the 501 to 3,300 people size category, serving 990 people from groundwater.

As of August 1, 2026, its federal record holds 5 entries between 2007 and 2022, all of which EPA lists as closed. Nothing has been added since 2022.

Of the 5, 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 synthetic organic chemicals, the Lead and Copper Rule, and the Stage 1 Disinfectants and Disinfection Byproducts Rule.

Violation history

Monitoring, Regular
—
Aldicarb sulfone
January 1, 2022 – December 31, 2024
Archived
Monitoring, Regular
—
Carbofuran
January 1, 2022 – December 31, 2024
Archived
Follow-up Or Routine LCR Tap M/R
—
Lead and Copper Rule
October 1, 2012 – November 7, 2013
Resolved
Monitoring and Reporting (DBP)
—
Chlorine
October 1, 2008 – December 31, 2008
Resolved
Consumer Confidence Report Complete Failure to Report
—
Consumer Confidence Rule
July 1, 2007 – January 3, 2011
Resolved

Archived closed in EPA's records (typically due to age or a data correction)Resolved addressed and confirmed by the state

Period	Violation	Contaminant / rule	Health-based	Status
January 1, 2022 – December 31, 2024	Monitoring, Regular	Aldicarb sulfone	—	Archived
January 1, 2022 – December 31, 2024	Monitoring, Regular	Carbofuran	—	Archived
October 1, 2012 – November 7, 2013	Follow-up Or Routine LCR Tap M/R	Lead and Copper Rule	—	Resolved
October 1, 2008 – December 31, 2008	Monitoring and Reporting (DBP)	Chlorine	—	Resolved
July 1, 2007 – January 3, 2011	Consumer Confidence Report Complete Failure to Report	Consumer Confidence Rule	—	Resolved

Archived closed in EPA's records (typically due to age or a data correction)Resolved addressed and confirmed by the state

Enforcement actions

December 29, 2022State Public Notification requested118 linked violations
March 27, 2009State Violation/Reminder Notice1 linked violation
September 1, 1984State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
August 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
July 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
June 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
May 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
April 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
February 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
January 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
December 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
November 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
October 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
September 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
August 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
July 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
June 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
May 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
April 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
March 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
February 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
January 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
December 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
November 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
October 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
September 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
August 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
July 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
May 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
March 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
February 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
January 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
December 1, 1980State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
November 1, 1980State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
October 1, 1980State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
September 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
August 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
July 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
June 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
May 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
April 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
February 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
January 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
December 1, 1979Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
November 1, 1979Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
October 1, 1979Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record

Common questions

Is ARLAM CONCORD WSC required to publish a Consumer Confidence Report?: Yes. ARLAM CONCORD WSC 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 ARLAM CONCORD WSC’s next Consumer Confidence Report due?: ARLAM CONCORD WSC’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does ARLAM CONCORD WSC have any open drinking water violations on record?: As of August 1, 2026, EPA's federal records show no open violations for ARLAM CONCORD WSC.
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

CHATMAN, L, D

936-254-2108

GARRISON, TX 75946-0324