A PFAS result on a laboratory report looks like a fixed fact. It is actually an output of a specific method, run by a specific laboratory, inside a defined scope of accreditation. A recent Circle of Blue report on PFAS contamination in drinking water carries an October 23, 2026 date in its summary and addresses a situation that every PFAS reader eventually meets: concentrations that "fall below laboratory reporting limits." The summary is brief, so this article does not describe that study's methods or conclusions. It takes the narrower question that the report raises for anyone who files, compares, or acts on a PFAS value: which record supports the number, and does that record cover the compound and matrix in question?
Nothing here assumes the underlying study is right or wrong. The point concerns paperwork, because paperwork decides what a number can bear.
What the scope actually lists
Laboratory accreditation for drinking water analysis is generally granted against named methods. The scope document lists the analytes covered, sometimes the matrices, and the method version in force. A laboratory accredited for one PFAS method does not thereby hold accreditation for another, and a scope that covered a given compound list last year may have changed since. The scope carries an issue date and, in many cases, an expiry. The record that matters is the one in force on the day the sample was analyzed, not the certificate forwarded from a website or a sales packet.
Dealers selling treatment equipment and engineers writing specifications both face this problem from different sides. A dealer quoting a media change may rely on a lab report to justify a change-out. An engineer may write a performance requirement that names compounds the lab is not accredited to report. Either way, the mismatch appears later, usually at the point when a decision has already been made.
Match the analyte list to the decision
Before a value is used, compare the analytes on the scope with the analytes the decision depends on. A permit, a treatment specification, or a bid may name a specific list of compounds, or it may name a sum. If a required compound is absent from the scope, the lab may still report a value for it, but that value belongs to a different kind of record. It should be labeled as such in any file that carries it forward.
Sums need the same care. Where a requirement uses a total of individual compounds, confirm whether the scope covers the summed result or only the individual analytes. The arithmetic of summing is only as reliable as the inputs, and a reader should be able to trace each input to a line on the scope.
Ask how below-limit values are reported
The reporting limit is a property of the method and of the laboratory's validated performance. It is not a fixed feature of the compound. Ask the laboratory how it reports results between its detection limit and its reporting limit, whether those values are flagged as estimated, and whether the reporting limit printed on the report matches the limit in its validation file. A non-detect written as "less than" a number tells a reader something different from a zero, and a dataset that drops the qualifier has changed the meaning of the record.
When a study or a dataset says that concentrations fall below reporting limits, the scope and the report are the places to check how those values were carried forward. Substitution rules, censoring, and qualifier codes are all decisions made somewhere in the chain. The reader should know where.
Keep the scope with the result
File the accreditation scope, the method version, and the laboratory report together, dated to the sample. Researchers merging data from several laboratories should record which scope covered each batch, since a combined table hides differences that a careful reader would want to see. Utilities preparing annual summaries and consultants compiling site files should follow the same practice.
The aim is not to distrust every result. It is to make each result traceable to the record that supports it, so that a later reader can see what was measured, by which method, under what authority, and with what limit. A value without that trail may still be correct. It is simply harder to defend, and harder to compare with the next value that arrives from a different laboratory.