Water Quality Wire

A water risk register is a set of decisions written as a table. Each row names a hazard, a judgment about likelihood, a consequence, and an owner. Most utility registers were built around failures that arrive without intent, including main breaks, power loss, chemical feed errors, drought, and flooding. Some include cyber intrusion. Far fewer state plainly whether armed conflict, sabotage, or deliberate interruption of a supply is in scope. When the question goes unanswered, the omission becomes the answer.

What the interview raises

A Circle of Blue interview with Peter Gleick, conducted by Brett Walton, examines what water violence looks like in practice. The interview describes conditions for civilians in active war zones, where, in its words, "daily life is more dangerous than in conflicts past." Among the scenarios it raises are a cut water supply and a dam failure that floods the surrounding countryside. These are not abstract categories for the people living through them. They are also not the categories most utility registers were drafted to hold. The interview is useful for a water professional less as a forecast than as a reminder that the hazard list has edges, and that the edges are a choice.

Scope is a decision, not a default

A hazard left out of scope is not assessed for consequence. No capital line is written against it, no mutual aid clause is tested for it, and no operator is trained to recognize its early signs. Excluding deliberate threats keeps the register defensible on frequency data, since the utility can point to its own incident history. That defensibility has a cost. Frequency records for deliberate attacks on domestic utilities are often thin or absent in a single agency's file, and an empty history says little about the underlying hazard. Including them adds rows whose likelihood is hard to estimate, and a register full of speculative entries can lose credibility with a board that wants numbers it can audit.

Neither choice is free. The practical question is which cost the utility is willing to carry, and whether that choice is written down with its reasoning.

Separate the threat from the consequence

A workable approach is to split each conflict-related entry into two parts. The first is the threat scenario, which begins with an intentional act and states the assumed access or capability without elaboration. The second is the consequence chain, which uses the same language the register already applies to other hazards. For a water system, that chain usually runs through loss of source, loss of treatment capacity, loss of distribution pressure, and degradation of residual disinfection. Pressure loss, for example, raises the risk of backflow and intrusion, and a falling residual changes what operators can say about microbial control. Those consequences are familiar to the staff who already manage them. Writing the threat as a scenario lets the utility reuse that knowledge rather than building a parallel process.

This split also keeps likelihood judgments from crowding out consequence analysis. A low likelihood score does not reduce the consequence of a lost source. Scoring the two separately makes it harder for a single number to hide a severe outcome.

Who owns the row

Ownership matters more than most registers acknowledge. Operations can describe consequences, emergency management can describe response, and security staff can assess access and capability. Legal or records staff may need to limit what appears in a document that is public or subject to disclosure. A common arrangement is to keep the register entry at the level of scenario and consequence, and to point to a controlled file for any detail that would be sensitive if circulated. The trade-off is real. A board that sees only a summary row may find it harder to judge whether the entry is current, and a controlled file that nobody reviews is no better than no file. The review interval and the named reviewer should be written into the entry itself.

Record the decision before it is needed

The entry should record four things: the scope decision and its date, the sources consulted, the review interval, and what is excluded and why. Exclusions are the part most often lost. A later reader who sees no conflict row cannot tell whether the utility considered and rejected the hazard or never reached it. The minutes or memorandum that approved the scope should carry the reasoning, not only the result.

None of this predicts whether a particular utility will face deliberate interruption. It establishes whether the utility, when it reviews its own risks, has made a visible choice about a category that its own staff, neighbors, and mutual aid partners may someday need to plan around.