Small System PFAS Compliance

Small System PFAS Compliance: Navigating Regulatory Challenges and Implementing Effective Solutions

Introduction

Small water systems face the same PFAS limits as large utilities, with a fraction of the staff, budget, and technical support. A system serving 800 people must meet 4 parts per trillion exactly as a system serving 800,000 must, and must navigate the same monitoring schedules, compliance calculations, and notification requirements. This article focuses on those regulatory mechanics — what small systems must do, when, and what flexibilities exist — rather than on treatment technology.

The broader municipal compliance framework is covered in our guide to PFAS compliance for municipalities.

What Counts as a Small System

Under the Safe Drinking Water Act, a small system serves 3,300 people or fewer; a very small system serves 500 or fewer. These thresholds matter because several regulatory provisions — including monitoring frequency and certain compliance options — are tied to them. The great majority of U.S. public water systems fall into these categories.

The Regulatory Requirements

The Limits

EPA’s April 2024 rule set enforceable limits of 4.0 parts per trillion for PFOA and PFOS, plus limits for PFHxS, PFNA, HFPO-DA, and a hazard index for mixtures, with compliance 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; the 2024 rule is in force until final action.

Initial Monitoring

All public water systems must conduct initial monitoring for the regulated PFAS within the period the rule specifies, using EPA Method 533 or 537.1 at a certified laboratory. Monitoring frequency thereafter depends on system size and on the results of initial monitoring — systems with low or non-detect results qualify for reduced frequency, which matters considerably for small system budgets.

How Compliance Is Determined

This point is frequently misunderstood and is worth stating plainly: compliance is based on a running annual average, not a single sample. A single result above the limit is not automatically a violation. For systems monitoring quarterly, the average of four consecutive quarters determines compliance; for systems on annual monitoring, a result above the limit triggers quarterly monitoring to establish the average.

This gives systems near the limit some room to respond — to adjust source use, for example — before a violation occurs.

Public Notification

Exceeding an MCL triggers public notification requirements with prescribed timing and content. PFAS MCL violations fall into the tier requiring notification within 30 days, not the 24-hour tier reserved for acute risks. Systems must also report PFAS monitoring results in their annual Consumer Confidence Reports once that requirement takes effect.

Compliance Routes for Small Systems

Point-of-Use Treatment

Some states permit point-of-use devices as a compliance strategy for small systems, subject to strict conditions: the utility must own, install, maintain, and monitor the devices, and must cover every connection served. For very small systems this can be dramatically cheaper than centralized treatment, at the cost of an ongoing access and maintenance program across many properties. Whether it is available depends entirely on the state primacy agency.

Consolidation and Interconnection

Purchasing treated water from a neighboring utility, or consolidating with a larger system, eliminates the need to operate treatment — frequently the binding constraint for a small system, where operator capacity matters more than capital. Several states actively encourage consolidation and offer funding preferences for it.

Source Management and Blending

Where a system has multiple sources with differing PFAS levels, changing which sources are used, or blending them, can achieve compliance without construction. Because compliance is measured at the entry point to the distribution system, blending is a legitimate approach — subject to the state accepting it and to monitoring that demonstrates it holds under all operating conditions.

Exemptions and Extensions

The Safe Drinking Water Act provides for exemptions in defined circumstances, granting additional time where a system cannot comply for financial or technical reasons and no alternative source is available. These are granted by the state, are time-limited, and require a compliance schedule. They are not a way to avoid compliance, but they can provide realistic time to arrange funding and construction.

Working With the State

Most SDWA requirements are implemented by state primacy agencies, and state programs differ in monitoring schedules, whether point-of-use is permitted, how blending is treated, and what additional PFAS are regulated. Early engagement with the state is the single most useful step a small system can take — it establishes what is actually required and what flexibilities exist before money is spent.

Capacity and Support

Technical Assistance

Small systems are not expected to solve this alone. State drinking water programs, rural water associations, and technical assistance providers funded through federal programs offer free or low-cost help with sampling, compliance planning, funding applications, and alternatives analysis. These resources are consistently underused.

Operator Capacity

A treatment process that requires daily attention will not perform at a system with a part-time operator. Matching the compliance route to available staffing is not a compromise; it is what determines whether compliance is sustained after the first year.

Funding

Federal infrastructure legislation directed around $10 billion to emerging contaminants including PFAS, with a substantial share reserved for small and disadvantaged communities. State Revolving Fund programs offer low-interest loans and, for qualifying systems, principal forgiveness. Settlement funds from litigation against PFAS manufacturers are also available. Application cycles should be built into the compliance schedule from the start.

Treatment, Briefly

Where treatment is required, the established technologies are granular activated carbon, PFAS-selective anion exchange, and high-pressure membranes. Conventional treatment removes essentially no PFAS, and conventional advanced oxidation does not destroy it. For small systems, the practical considerations are usually operator attention and media replacement logistics rather than removal performance, since all three technologies work.

A Practical Sequence

  1. Complete initial monitoring and understand the results, including which sources are affected.
  2. Contact the state primacy agency to confirm requirements, timelines, and available flexibilities.
  3. Engage technical assistance, which is generally free.
  4. Evaluate all compliance routes, not treatment alone.
  5. Apply for funding early, allowing for application cycles.
  6. Communicate with customers before rumors outpace facts.

Conclusion

Small system PFAS compliance is as much an administrative and financial challenge as a technical one. The requirements are the same as for large utilities, but the routes to meeting them differ: point-of-use treatment, consolidation, interconnection, and source management are all more likely to be viable at small scale than at large.

Understanding that compliance rests on a running annual average, that state agencies hold meaningful discretion, and that free technical assistance exists puts a small system in a far better position than assuming an expensive treatment plant is the only option. The systems that struggle are generally those that wait, then face a deadline with no plan and no funding application in progress.