
Most of the PFAS coverage since May has been about deadlines moving. EPA proposed letting drinking water systems request two additional years, to 2031, to meet the PFOA and PFOS limits, and proposed rescinding the regulations for four other PFAS entirely. Both proposals are still proposals. Neither one touches the date that matters first.
Initial monitoring results are still due to the state by April 26, 2027. Compliance monitoring still begins no later than that date. For a groundwater system that has not started, the sampling window is already narrow, and for the labs running the analysis, the sample volume arrives before the deadline does, not on it.
This article covers what initial monitoring requires under the rule as it stands today, what the 2026 proposals do and do not change, and where these deadlines actually get missed.
What is the April 26, 2027 PFAS monitoring deadline?
Under the 2024 PFAS National Primary Drinking Water Regulation, every community water system (CWS) and non-transient non-community water system (NTNCWS) must complete initial monitoring for the regulated PFAS at each entry point to the distribution system, and report those results, by April 26, 2027. Compliance monitoring begins on that same date.
Three separate obligations land in that window:
- Initial monitoring at every entry point, on a schedule set by system size and source water type
- Reporting of all laboratory results to the state, which uses them to set the system’s ongoing monitoring frequency
- Public information on PFAS levels in drinking water, beginning April 26, 2027
The limits being monitored against
The 2024 rule set maximum contaminant levels (MCLs) for six PFAS. Four of them are the subject of a 2026 rescission proposal, marked below and covered in the next section.
- PFOA: 4.0 nanograms per liter (parts per trillion)
- PFOS: 4.0 nanograms per liter
- PFHxS: 10 nanograms per liter (proposed for rescission)
- PFNA: 10 nanograms per liter (proposed for rescission)
- HFPO-DA, commonly called GenX chemicals: 10 nanograms per liter (proposed for rescission)
- Hazard Index of 1.0 for mixtures containing two or more of PFHxS, PFNA, HFPO-DA, and PFBS (proposed for rescission)
Two dates sit behind those numbers. Initial monitoring is due by April 26, 2027. Under the 2024 rule as finalized, a system whose results exceed an MCL then has until April 26, 2029 to install treatment, switch sources, or otherwise bring levels into compliance. The 2026 proposals address that second date and the four MCLs marked above. Neither one reaches the first date.
The initial monitoring results are not just a compliance record. They determine how often the system samples for the next several years, which makes them an operating cost decision as much as a regulatory one.
Did the 2026 proposed rules change the monitoring deadline?
No. EPA’s own guidance on the proposed compliance extension is explicit on this point: for systems that request and receive the federal exemption for the PFOA and PFOS limits, all monitoring and reporting of sample results must still be met according to the timeframes in the final April 2024 regulation.
What the two May 2026 proposals would do:
- The compliance extension proposal keeps the PFOA and PFOS maximum contaminant levels at 4.0 parts per trillion each and gives eligible systems the option to request up to two more years, to 2031, to complete treatment. EPA chose a request-based mechanism rather than an automatic extension so systems already on track for 2029 are not slowed down.
- The rescission proposal would remove the regulatory determinations and regulations for PFHxS, PFNA, HFPO-DA (GenX chemicals), and the Hazard Index covering mixtures of those three plus PFBS. EPA frames this as a procedural correction under the Safe Drinking Water Act rather than a reassessment of the health or occurrence data.
The comment period closed on July 20, 2026, and EPA has said it intends to finalize both rules before the end of the year. Until then, the six regulated PFAS in the 2024 rule remain the ones a system monitors for. Labs building analyte lists and reporting templates for the next nine months should plan on the current list and watch for the final rules rather than anticipating them.
How much sampling does initial monitoring actually require?
The schedule depends on source water and population served, applied at each entry point rather than to the system as a whole.
| System type | Initial monitoring required |
|---|---|
| All surface water CWS and NTNCWS | Four consecutive samples, 2 to 4 months apart, within a 12-month period |
| Groundwater CWS and NTNCWS serving more than 10,000 people | Four consecutive samples, 2 to 4 months apart, within a 12-month period |
| Groundwater CWS and NTNCWS serving 10,000 or fewer people | Two samples, 5 to 7 months apart, within a 12-month period |
| Groundwater under the direct influence of surface water (GWUDI) | Follows the surface water schedule |
Systems drawing on both surface water and groundwater apply the requirement that matches the source at each individual entry point, which means one system can be running two different sampling schedules at once. The full text sits at 40 CFR 141.902.
The spacing requirement is the part that closes the window early. A small groundwater system needs two samples five to seven months apart. Counting backward from April 26, 2027, and allowing for laboratory turnaround and state reporting, the first of those two samples needs to be collected well before the end of 2026.
Can UCMR 5 or older data count toward initial monitoring?
Yes, in many cases. Previously collected data may satisfy some or all of the initial monitoring requirement when it was generated on or after January 1, 2019 using an approved method and meets the rule’s conditions. That includes data collected under the Fifth Unregulated Contaminant Monitoring Rule (UCMR 5), state monitoring programs, and other appropriate campaigns.
Systems can also combine old and new data. Supplemental samples collected now can be paired with earlier monitoring so that the combined set meets the rule’s timing and spacing requirements, which often means a system needs two more samples rather than four.
Two practical points for anyone assembling this:
- Method matters. EPA Methods 533 and 537.1 are the approved drinking water compliance methods, and both are validated for the PFAS covered by UCMR 5. A newer method, currently designated EPA 534, is in development. Data generated outside an approved method will not carry the load.
- The seasonal spacing is evaluated by calendar month, not by year. A system with results from February and August of 2024 needs two additional samples in the corresponding windows, which can be collected in a later year as long as the month spacing works out.
Pulling this together is a records exercise before it is a sampling exercise. Systems that ran UCMR 5 already have results sitting in a lab’s data system, a state portal, or a PDF in someone’s email. Finding out which of those results qualify is the cheapest sampling any system will do this year.
What happens when initial monitoring ends?
The results set the ongoing frequency. Where a regulated PFAS is detected at or above its trigger level at a sampling point, the system moves to quarterly monitoring for all regulated PFAS beginning April 26, 2027. Trigger levels are set at one half of the corresponding MCLs, which puts them at 2.0 nanograms per liter for PFOA or PFOS, 5 nanograms per liter for HFPO-DA, PFHxS, or PFNA, and a Hazard Index of 0.5.
Systems below the trigger levels can qualify for reduced frequency. Compliance itself is determined at each sampling point, and for systems monitoring quarterly it is calculated as a running annual average rather than on any single result.
One reporting requirement deserves specific attention because it is easy to get wrong at the data-handling layer. All results a laboratory provides must be reported to the state and used in determining sampling frequency, including values below the practical quantitation level. Zero must not be substituted for a reported value. A reporting pipeline that quietly converts non-detects or sub-PQL results to zeros is generating a compliance problem, not cleaning up a data set.
What does this mean for the labs running the analysis?
Between now and April 2027, a finite number of accredited labs will absorb PFAS compliance samples from tens of thousands of water systems, many of which have not started. For labs offering drinking water PFAS analysis, the operational pressure shows up in a few predictable places.
- Intake volume against a fixed date. Samples do not arrive evenly. They arrive in the last two quarters before a deadline, from clients who each need results in time to report.
- Entry-point identity. Compliance is determined per sampling point. A result that cannot be tied back to the correct entry point with confidence is a result the client cannot use.
- Holding times and preservation. PFAS drinking water methods carry their own handling requirements, and a holding time exceedance discovered at data review is a resample the schedule may not absorb.
- Sub-PQL reporting. Labs need to report actual values, with the qualifiers the rule and the state expect, rather than a simplified non-detect flag.
- Method-specific QC. Each analytical batch carries its QC set, and the data package the state reviews has to show it.
- Reporting destination. Results go to the client and, depending on the state, into a state reporting pathway. Several states have filed primacy extension agreements with EPA, so the agency collecting the data and the agency enforcing the rule are not always the same one. Confirm the pathway per state rather than per client.
For labs pursuing or maintaining accreditation, this is also a scope conversation. Adding or expanding drinking water PFAS analysis means method validation records, demonstrations of capability, and a scope amendment, all of which take time that the April 2027 date does not extend. Our overview of TNI and NELAP accreditation covers how that documentary burden is structured, and the ISO 17025 requirements behind it apply here as they do to any accredited method.
Where these deadlines actually get missed
Failing to collect the required number of samples is a monitoring violation in its own right, separate from any exceedance, and compliance is then calculated on the samples that were collected. In practice, the failures cluster in four places, and none of them are analytical.
- Nobody owns the calendar per entry point. A system with eight entry points on mixed sources has multiple overlapping schedules. Tracked in a spreadsheet, one entry point gets skipped, and the gap surfaces after the window has closed.
- Existing data is never checked. Systems resample from scratch because no one determined whether their UCMR 5 results already satisfied part of the requirement. That is avoidable cost and avoidable sample volume in an already busy period.
- Turnaround was not counted backward. The rule requires results reported by the deadline, not samples collected by the deadline. Collection, analysis, review, and state submission all have to fit inside the window.
- The data package is incomplete at review. A result without its QC, its custody record, or its correct sampling point identity is a result that gets questioned. Reconstructing that after the fact is the most expensive way to do it.
What a LIMS carries in this work
None of the above is solved by software alone. What informatics changes is whether the tracking is a person’s responsibility or the system’s.
In a configured deployment, a LIMS built for environmental testing holds the pieces of this that are easy to lose: the sampling point and entry-point identity carried on every sample, chain of custody from field to report, holding time alerts before the exceedance rather than after, EPA method definitions with their QC requirements attached, and result qualifiers that survive the trip to a state submission. A client portal lets a water system pull its own results and data packages rather than emailing the lab for them, which matters more in the quarter before a deadline than at any other time. Several of the tasks involved here are the same ones we covered in five manual lab tasks a LIMS handles.
A LIMS supports the documentary side of this rule. The lab still earns the accreditation, validates the methods, and meets the date.
Frequently asked questions
Is the April 26, 2027 PFAS deadline still in effect?
Yes. Initial monitoring results are due to the state by April 26, 2027, and compliance monitoring begins no later than that date. EPA’s 2026 proposals address treatment compliance timing and the regulation of four PFAS, not the monitoring and reporting schedule.
What are the PFAS maximum contaminant levels?
Under the 2024 regulation, PFOA and PFOS are each set at 4.0 nanograms per liter, also expressed as parts per trillion. PFHxS, PFNA, and HFPO-DA (GenX chemicals) are each set at 10 nanograms per liter. Mixtures containing two or more of PFHxS, PFNA, HFPO-DA, and PFBS are regulated by a Hazard Index of 1.0. A 2026 proposed rule would rescind the regulations for the last four.
What is the difference between the 2027 and 2029 PFAS deadlines?
April 26, 2027 is the deadline to complete and report initial monitoring, which measures what is in the water. April 26, 2029 is the deadline under the 2024 rule for systems exceeding a maximum contaminant level to complete treatment or switch sources. A 2026 proposal would let eligible systems request two additional years, to 2031, for the PFOA and PFOS limits. The monitoring deadline is unaffected by that proposal.
Did EPA extend the PFAS compliance deadline to 2031?
EPA has proposed allowing eligible drinking water systems to request up to two additional years, to 2031, to meet the PFOA and PFOS limits. As of publication the rule is proposed, not final, and EPA has said it intends to finalize before the end of 2026. The maximum contaminant levels themselves remain 4.0 parts per trillion each under the proposal.
Can UCMR 5 results satisfy PFAS initial monitoring?
In many cases yes. Previously collected data from January 1, 2019 onward may satisfy some or all of the initial monitoring requirement when it was produced using an approved method and meets the rule’s timing and spacing conditions. Systems can also combine earlier results with new samples to complete the requirement.
Which methods are approved for PFAS drinking water compliance analysis?
EPA Methods 533 and 537.1 are the approved drinking water methods and are validated for the PFAS covered by UCMR 5. EPA 534, a direct injection LC-MS/MS method, is in development.
How many samples does a small groundwater system need?
A groundwater community or non-transient non-community water system serving 10,000 or fewer people takes two samples per entry point, spaced 5 to 7 months apart, within a 12-month period. Surface water systems and larger groundwater systems take four samples spaced 2 to 4 months apart.
Next step
If your lab is taking on drinking water PFAS compliance work ahead of April 2027 and wants to know what the tracking looks like inside a configured system, schedule a 30-minute scoping call. We will ask about your method scope, sample volume, accreditation status, and state reporting pathways, and tell you what a deployment would look like for your operation.
Accelerate Your Lab's Success & Experience LabLynx
"*" indicates required fields
Explore the LabLynx Suites

LIMS Suite
Seamless Sample and Workflow Management
The LabLynx LIMS Suite empowers laboratories with the tools needed to manage samples, workflows, compliance, and more in one centralized system. It’s the backbone for labs seeking efficient, reliable, and scalable management solutions.

ELN Suite
The LabLynx ELN Suite offers a modern approach to managing lab data and experiments. With its secure, intuitive platform, your team can record, store, and collaborate effortlessly, supporting innovation every step of the way.

Lab Automation
Automate for Efficiency and Growth
Streamline operations and boost productivity with the LabLynx Lab Automation Suite. Designed for labs ready to embrace advanced automation, this suite integrates systems, instruments, and workflows to deliver efficiency at scale.
