When a water system exceeds a PFAS limit, telling customers is not optional, and it is not left to the utility’s judgment. Public notification requirements prescribe who must be told, how quickly, through which channels, and in what words. Getting these wrong creates a violation on top of the original one. This article sets out what the requirements actually are, how PFAS fits within the existing notification framework, and how to communicate well within it.
These requirements sit alongside broader regulatory and liability developments covered in our discussion of PFAS legal challenges.
EPA finalized its PFAS drinking water regulation in April 2024, setting enforceable maximum contaminant levels of 4.0 parts per trillion each for PFOA and PFOS, with limits for PFHxS, PFNA, HFPO-DA, and a hazard index for mixtures. Compliance was required by 2029. In May 2026, EPA proposed retaining the PFOA and PFOS limits with an optional extension to 2031 and rescinding the others; as of September 2026 these remain proposals.
Because PFAS are now regulated contaminants with MCLs, they fall under the existing Public Notification Rule rather than a separate PFAS-specific notification scheme. That framework is well established, and understanding how PFAS maps onto it is the key point.
Separately from violation notification, systems must include PFAS monitoring results in their annual Consumer Confidence Reports once that requirement takes effect under the rule. This is routine reporting of results, not violation notification, and applies whether or not results exceed the limits.
The Public Notification Rule establishes three tiers based on the severity and immediacy of the health risk. Misapplying them is the most common error:
Reserved for violations with the potential for acute health effects — E. coli contamination, nitrate exceedances, and similar immediate risks. Requires broadcast media, hand delivery, or posting, and consultation with the primacy agency within 24 hours.
PFAS MCL violations are not Tier 1. PFAS health effects are associated with chronic exposure rather than acute risk.
Applies to MCL violations for contaminants with chronic health effects, which is where PFAS MCL violations fall. Notification must reach all persons served within 30 days of the violation, typically by mail or direct delivery, with repeat notification every three months while the violation continues.
Applies to monitoring and testing procedure violations — failing to sample on schedule, for example. Notification may be included in the annual Consumer Confidence Report.
A second common misunderstanding: notification is triggered by a violation, not by detection. Because compliance with the PFAS MCLs is determined on a running annual average, a single sample above 4 parts per trillion is not itself a violation and does not by itself trigger public notification.
This distinction matters practically. A system with one elevated result has time to conduct additional monitoring and, if appropriate, adjust source use before a violation occurs. It does not, however, prevent the utility from communicating voluntarily — and many choose to, on the reasonable view that customers would rather hear it from the utility than discover it later.
Notifications must contain prescribed elements:
Notices must be in plain language, avoid technical jargon, and include translation or assistance where a substantial proportion of the population served speaks another language.
For Tier 2, notification is typically by mail or direct delivery to customers. Systems should remember the people who are served but not billed — residents of multi-unit buildings, employees at commercial premises, and users of schools and institutions — which is why notices include the request to post and share. Consecutive systems purchasing water must be notified so they can inform their own customers.
States implement the federal rule and may impose additional requirements. Several states set PFAS drinking water standards before federal action, and their notification triggers may differ from the federal ones. Some states also require notification at levels below the MCL, or have their own advisory frameworks. Confirming requirements with the state primacy agency is essential, since the state determines what actually applies.
Meeting the legal minimum and communicating well are not the same thing. PFAS is a subject where public concern frequently runs ahead of the technical picture, and where a notice that is technically compliant but opaque can do real damage to trust.
Public notification sits within a broader regulatory picture. The designation of PFOA and PFOS as hazardous substances carries liability implications discussed in our coverage of the PFAS hazardous substance designation, and discharge-side obligations are increasingly appearing in permits, as examined in our guide to NPDES permits and PFAS.
PFAS public notification operates under the existing Public Notification Rule rather than a separate scheme. The essential points are that PFAS MCL violations are Tier 2, requiring notification within 30 days rather than 24 hours; that notification is triggered by a violation based on a running annual average, not by a single detection; and that mandatory health effects language must be used as written.
Beyond compliance, the systems that come through PFAS detections with public trust intact are those that prepared their communications in advance, explained the numbers in terms people can use, and were specific about what they were doing. The regulatory minimum is a floor, not a strategy.