Most community water systems publish an annual water quality report, often called a consumer confidence report, that summarizes the previous year's monitoring results. The document reads like a single snapshot. In practice it is a composite, drawn from samples collected on different days, analyzed by different laboratories, and sometimes reported under different method versions. The reporting year, the sampling dates, and the calendar year printed on the cover are three separate sets of dates, and careful staff keep them apart.
Three dates on one page
A reporting period is usually fixed by the regulator, and sampling events inside it may fall near the boundary. A sample taken in late December may appear in the same document as one taken in early January, while the lab reports for each arrive weeks apart. The analysis date on a lab report can trail the collection date by days, depending on shipping and holding times. Each date answers a different question: when the water was taken, when it was measured, and when the result was approved for inclusion. A table that uses only one of them will mislead, even when every individual number is correct.
The gap matters most for results near a reporting limit. A non-detect is stated against the limit in force for that analysis, and that limit can change between method versions or between years. Comparing a non-detect from one year with a detection from another, without checking the limit that produced each, compares two different measurements. Recent coverage of PFAS monitoring has pressed this point. Circle of Blue's report, dated October 23, 2026, states that "When PFAS concentrations in drinking water fall below laboratory reporting limits" the results depend on those limits. The summary does not describe how the underlying study handled such values, so this article does not assume how it did. The mechanism itself is well understood by laboratory staff: the limit is part of the result.
A reconciliation sequence
Start by writing the reporting period from the regulator's guidance at the top of the working file. Then list every sample event inside that period, with collection date, laboratory, method, and reporting limit for each analyte. Sort the lab reports by analysis date, and match each one back to a collection event. Flag any result whose analysis date falls outside the period while its collection date falls inside, or the reverse. Those flags are where annual reports usually go wrong.
For each contaminant, record the highest result, the number of samples, and the count of non-detects. Note any mid-year change in reporting limit or method. Then have a second person check the sums against the original lab files, not against the working table. The second check catches transcription errors that the first pass cannot see.
What the report can and cannot say
The report states what was measured on the sample dates. It does not describe water quality at every moment between those dates, and its wording should not imply continuous conditions. Where a limit changed during the year, the methods note should say so in plain terms. Where a late lab report arrives after the print deadline, the utility has to decide whether to issue a correction, hold the result for the following year, or add a supplemental notice. Whichever path it takes, the reasoning belongs in the file. Requirements for timing and content vary by state and by rule, so the governing rule for the system should be checked before any of these choices is made.
The file that outlasts the document
Keep the matching table with the lab reports it was built from. When a customer, a reporter, or an auditor asks why a figure differs from the prior year, the table answers the question without reconstruction. Staff who inherit the file can see which dates were used, which limits applied, and which results were held. That record is worth more than the cover page, because the cover page only states the conclusion, and the table shows how it was reached.