PFAS money tends to arrive with a sampling requirement attached, which makes the laboratory report the first document an operator reads. On Oct. 22, Congresswoman Laura Gillen (D-N.Y.), along with Rep. Brian Fitzpatrick (R-Pa.), introduced the bipartisan Protect Clean Water Act. Water Finance and Management reported the introduction, describing the bill as legislation "to help fund the removal of toxic per- and polyfluoroalkyl substances" from drinking water supplies. Introduction is not enactment. The report does not establish the bill's final text, funding levels, or path through Congress. Whatever the outcome, the arithmetic inside a sample will be the figure any project under such a program cites.
A Nondetect Is a Bound
A laboratory result for a PFAS compound is reported against at least two limits. The method detection limit is the lowest concentration the procedure can distinguish from zero under defined conditions. The reporting limit is the lowest value the lab will report as a quantified number, and it is usually set above the detection limit so that reported values carry acceptable uncertainty. Below the reporting limit, a result is typically reported as not detected, or with a qualifier indicating that the compound was seen but not quantified. Either way, the report says the concentration fell below a bound. It does not say the compound is absent.
That distinction matters because limits vary. They depend on the method, the instrument, the sample matrix, and the day's calibration, so a limit printed on one report describes that analysis, not the water itself. Two utilities sampling the same source can receive different reporting limits from different laboratories. Both results can be correct as reported and still be poorly comparable.
Three Checks Before Anyone Reads a Trend
The first check is whether the reporting limit sits below the level being compared. If a target falls under the reporting limit, a nondetect cannot demonstrate compliance or exceedance. It shows only that the concentration lies somewhere between zero and the bound, which may or may not be enough to decide anything.
The second check is blank performance. Field blanks, equipment blanks, and laboratory method blanks show whether contamination entered the sample path. PFAS work is sensitive to sampling equipment, containers, and some materials that do not look like sources, so a detection in a blank is a signal to examine the handling chain before trusting the sample it accompanies. A sample with a contaminated blank carries a different meaning than the same sample with a clean one.
The third check is the substitution convention. Spreadsheets and trend tools often replace nondetects with zero, with half the reporting limit, or with the reporting limit itself. Each choice yields a different mean and a different direction of change over time. In a dataset dominated by nondetects, the convention can determine the apparent trend more than the water does. Choose the convention before results arrive, record it in the data file, and report it alongside any average.
What to Request From the Lab
Ask for the method name and version, the method detection and reporting limits for each analyte in each sample, the laboratory's definition of every qualifier code, the blank results that accompany the batch, and the chain-of-custody record showing how and when the sample was handled. Where the method provides recovery data for labeled internal standards or surrogates, request those as well, because low recovery can change how a reported value should be read. Most of these records are already generated by the laboratory. The utility's task is to ask for them and keep them with the data they describe.
Why the Funding Question Starts Here
A removal project is designed around a target, and that target is measured in the same units as the laboratory result. If the reporting limit sits above the target, the project cannot be verified against it using the data available. If nondetects are read as zero, a source may appear cleaner than it is. If a single detection is treated as a trend, a sampling problem may be funded as a contamination problem. Each error runs in a direction, and each eventually appears as a scope change or a dispute over whether the money performed.
The bill named above is at the introduction stage, so its eventual sampling, reporting, or eligibility rules are not known here. Operators can still prepare. Before a funding request is written, confirm which limits the proposed analyses will carry, which target the project will be measured against, and how nondetects will be handled in the baseline. A funding case built on a documented reporting record is easier to defend than one built on a tidy average.