PFAS Testing Readiness Starts with the Method and Matrix

PFAS testing readiness is not a single instrument purchase, software configuration, or generic checklist. The first decision is the intended work: which matrix, analytes, method revision, program, and report will the laboratory support?

EPA's drinking-water Methods 533 and 537.1 can measure 29 unique PFAS in drinking water.[1] EPA Method 1633A addresses 40 PFAS across wastewater, surface water, groundwater, soil, biosolids, sediment, landfill leachate, and fish tissue.[2] Those scopes are not interchangeable, and the information workflow should not flatten them into one undifferentiated “PFAS” service.

A useful readiness review begins by fixing the method boundary, then tracing one representative batch from intake through authorized output.

Define the service before configuring the system

Write a specific service definition for each intended offering. Include:

• accepted matrices and sample types;
• required method and revision;
• target analytes and naming conventions;
• container, preservation, shipping, and holding conditions;
• expected concentration range and reporting units;
• field and laboratory quality-control samples;
• preparation and analytical batch model;
• review, qualification, and reanalysis rules; and
• the required report or electronic deliverable.

Method 533 is specifically a solid-phase-extraction LC-MS/MS method for selected PFAS in drinking water.[3] Method 1633A covers aqueous, solid, biosolids, and tissue samples and states that the December 2024 revision supersedes previous versions.[4] Method identity and revision therefore belong on controlled records, not only in a report narrative.

The governing program may narrow or add requirements. Keep that program decision attached to the service definition so staff can distinguish a laboratory workflow from a permit, contract, state, or client-specific obligation.

Treat contamination control as connected evidence

PFAS contamination control crosses sampling, shipping, storage, preparation, consumables, equipment, and the laboratory environment. Method 533 defines a field reagent blank as reagent water treated like a sample through shipment, field exposure, storage, and analysis so it can reveal analytes or interferences introduced along that path.[3]

Method 1633A directs laboratories to clean equipment to avoid cross-contamination, verify residual PFAS in disposable plasticware and filters by batch or lot, and run method blanks at the beginning and with each sample batch.[4]

The system design implication is traceability. A reviewer should be able to move from a reported result to:

• the received containers and observed condition;
• field blank and field reagent blank identities where applicable;
• preparation and extraction batch;
• analytical sequence and instrument;
• standards, reagents, cartridges, filters, and relevant lot records;
• method blanks and other batch QC;
• any contamination investigation, affected-sample assessment, and corrective action; and
• the final disposition of the result.

Free text may explain an exception, but it should not be the only place these relationships exist.

Model QC as a batch network

PFAS review is rarely confined to one result row. The reviewer needs the sample's relationships to blanks, spikes, duplicates, labeled compounds, calibration records, and batch acceptance decisions.

Build the review view around those relationships. For each result, make the following visible without switching to an unrelated spreadsheet:

1. the applicable method, revision, analyte, and units;
2. the preparation and analytical batches;
3. the QC records that govern the result;
4. the effective acceptance criteria;
5. the original observation and any dilution, reinjection, re-extraction, or reanalysis;
6. the qualifier and its reason; and
7. the approved value selected for reporting.

Do not hard-code one universal blank rule or batch structure under a PFAS label. The selected method and the laboratory's controlled procedures should supply the rules for that service.

Control analyte identity and report vocabulary

Long analyte lists create naming risk. Native analytes, labeled analogues, abbreviations, isomers, external program codes, and client-facing names may not match one-for-one.

Use a controlled analyte identity with method-specific membership and effective dates. Maintain report labels, external codes, units, limits, and qualifiers as governed mappings rather than ad hoc text substitutions. When a method revision changes an analyte list or criterion, create a new effective version instead of silently changing historical work.

Then test the full output. The approved result, analyte identity, method, units, limit, qualifier, and narrative should remain consistent in the reviewer screen, certificate or report, data export, and amendment history.

Test an exception, not just the happy path

A polished demonstration can show sample login and a clean final report while missing the decisions that make PFAS work difficult. Use a sanitized scenario with one routine batch and one meaningful exception—for example, a blank concern that leads to an investigation and reanalysis.

Ask the team to show:

• intake and custody through batch assignment;
• every relevant blank and QC relationship;
• consumable or reagent lot traceability;
• the initial result and the reason it was not selected;
• reanalysis and reviewer authorization;
• the final report and an amended-report path; and
• an export containing the underlying identities and revision history.

The acceptance record should identify the tested method revision, scenario, expected output, actual output, reviewer, and unresolved gaps. That is more useful than a statement that the laboratory is “PFAS ready.”

Software can preserve the workflow evidence; it cannot establish method suitability, analyst competence, or permission to report.

Make a lane-by-lane readiness decision

Score readiness separately across four lanes:

• Scientific: the method, matrix, analyte scope, and performance work are established for the intended use.
• Operational: facilities, supplies, contamination controls, staffing, and custody practices support routine work.
• Quality: controlled procedures, training, QC review, investigations, and approvals are in place.
• Information: identities, relationships, decisions, revisions, and outputs remain traceable from receipt to report.

A gap should stay assigned to its real lane. Software configuration should not hide an unresolved scientific or operational decision.

Evaluate the workflow you intend to run

If your current decision is whether a LIMS workflow can represent your selected PFAS method, QC network, exception handling, and report boundary, evaluate the workflow with Clearline LIMS using a sanitized batch scenario.

Sources

1. U.S. EPA — Comparing EPA Analytical Methods for PFAS in Drinking Water
2. U.S. EPA — CWA Analytical Methods for PFAS
3. U.S. EPA — Method 533
4. U.S. EPA — Method 1633A