The Environmental Protection Agency has put four nouns into the name of its PFAS work, and a utility, laboratory, or dealer that plans around the effort will get more use from it by treating each noun as a separate line of work with its own records. Water Finance and Management reported that Administrator Lee Zeldin launched the “first ever agency-wide PFAS Technology, Evaluation, Coordination, and Harmonization (PFAS TECH) strategy” at an event in Commerce City, Colorado, and that EPA said the effort will help springboard technology innovation on PFAS. The summary available for that report does not describe individual deliverables, so the reading below is an organizing exercise, not a summary of commitments.
Technology and evaluation produce different files
Technology points to the hardware, media, and processes that remove or destroy PFAS. Evaluation points to the test of how those options perform. The two generate different records. A technology file holds vendor descriptions, design basis, and the operating conditions under which any performance claim was made. An evaluation file holds the sample plan, the analytical method, the reporting limit in force on each sampling date, and the quality control results that show whether a non-detect means absence or only a result below a floor. A pilot that keeps only the first file cannot be compared with another pilot, because the comparison depends on the second.
Coordination decides who holds the file
Coordination is the least physical of the four words and the easiest to skip. In practice it means someone decides which office, agency, or utility owns each dataset when several parties test the same technology in different places. Nothing in the launch coverage says how that will work, and a utility should not assume an answer in advance. The practical step is internal. Name the staff member who will receive federal or vendor pilot results, and record where the original laboratory reports are stored, with the chain of custody and the sample identifiers that link each report to a physical bottle. This is the same question as who keeps pilot data when staff change, and it does not wait for a federal document to settle.
Harmonization depends on the floor
Harmonization is the word that most depends on measurement detail. Circle of Blue published a study account by Alissa de Chassey dated October 23, 2026, originally carried by Inside Climate News, which addresses PFAS concentrations that fall below laboratory reporting limits. That is the central problem for any cross-laboratory comparison. Harmonizing results requires that each reported value carry its reporting limit, its method, and a qualifier that marks values between the detection limit and the reporting limit. A non-detect at one laboratory and a non-detect at another are not the same statement if their floors differ. A combined table that drops the floors will look more consistent than the underlying data is, and a reader who sees a clean column of zeros has no way to recover what the labs actually measured.
What to write into the file now
Three entries do most of the work: the reporting limit for each sampling date, the method identifier, and the qualifier used for values near the floor. Write them beside every result before any strategy document is cited in a board packet, a customer notice, or a vendor bid. The federal program may change which laboratories report what and how, and the federal framework may shift over time. Records written now will stay correct for their own dates whatever comes next, which is the practical reason to keep the floor and the method attached to the number rather than in a separate memo.