Water Quality Wire

When The Guardian's report on Indigenous students retracing the Lewis and Clark route reached readers, the most useful line for water professionals sat in the headline: "We can't protect what we cannot see." The story, by Ashley Stimpson, describes a new wildlife survey along the route, two centuries after the expedition. It is a conservation story first, but the logic applies to any file a utility, dealer, or laboratory keeps.

The Question Chooses the Columns

The summary of the story describes Thomas Jefferson's aim in dispatching Meriwether Lewis and William Clark in 1804 as primarily political, concerned with the newly acquired land west of the Mississippi. The journals that resulted are a substantial record, but they were shaped by the questions of the people who commissioned them. Every record carries its origin, and the origin determines which observations were made, which were skipped, and how they were framed.

A monitoring file works the same way. Sampling points, parameters, detection limits, and sampling frequency are chosen to answer a question someone was paying to ask, whether that is permit compliance, a rate case, a source assessment, or a grant report. Those choices are sensible for the original question. They become a problem when the file is later used to answer a different one. A parameter that was never requested does not appear in the table, and a missing column reads as a clean result unless someone checks what the table was designed to show.

Reporting limits add a second layer. A result listed as below the reporting limit answers a narrower question than many readers assume. It says the analyte was not quantified at that method's sensitivity on that date. It does not say the analyte was absent from the water, and a file that mixes older and newer methods may carry reporting limits that are not directly comparable.

Tradeoffs of a Purpose-Built Program

Purpose-built records have real advantages. A narrowly designed program produces comparable data at a known cost, with method continuity that lets trends be read over years. Staff know the procedures, the sampling points stay fixed, and the quality checks match the questions being asked.

The cost is coverage. Expanding scope usually means changing methods, detection limits, or locations, and each change can break comparability with older results. Reusing a file for a new decision therefore requires a reconciliation step: identifying what changed, what was added, and what was dropped. That step is often skipped because the old file looks complete, and a complete-looking table is the most persuasive kind of false reassurance.

Absence Is a Claim About Scope

Treat an absence as a statement about scope, not about the world. A clean finished-water report says something about the sampled points and the listed analytes. It says little about dead ends in distribution, unlisted contaminants, or conditions between scheduled events unless the program was built to watch them. The Guardian story points at the same gap in a different setting. The new survey exists in part because the older record did not capture what lived along the route. The reporting does not establish what the survey will find, and nothing in this analysis should be read as a prediction about it.

Before using an older file for a new decision, a professional should be able to answer four questions in writing. Who commissioned the work? What question did it answer? Which parameters, species, or locations were in scope? What changed in the method over time? These answers take little effort to assemble, and they prevent the common error of treating a silent column as a zero. Where the answers cannot be found, that gap is itself a finding, and it belongs in the decision memo.

Households Keep Records Too

Purpose applies at home as well. A household that logs filter change dates, a softener's service visits, or home test kit results is building a file for a specific question, such as whether a cartridge is due or whether a service call corrected a problem. Those logs are useful only if the question is written at the top of the page. Without it, a note that a test was run last spring cannot tell a future reader whether the test was meant to check taste, hardness, or a suspected contaminant. For more on how this publication approaches home systems and appliances, see coverage for home systems and appliances.

The lesson from the 1804 journals and from the new survey matches what a utility faces when it inherits a monitoring file. Write the purpose line first, then the data. A record without a stated question is one whose silences nobody can read, and the gaps in it will be filled by whoever uses it next, often without knowing they are doing so.