
A recent interview from Circle of Blue, written by Brett Walton and headlined The Troubling Rise in Water Violence - An Interview with Peter Gleick, takes up a question that utility records rarely answer well: what happens to people when water becomes a target. The published summary describes daily life in active conflict zones as more dangerous than in past conflicts, and it names water supply disruption among the risks. "Your water supply could be cut." The line is short, but it points to a failure mode that most municipal filings handle only by implication.
This article is not about the interview's claims. It is about the record a utility keeps, and whether that record could show a deliberate interruption if one ever occurred.
The Cause Code Is the Trend Line
Most water systems sort service interruptions by an initiating cause, such as power loss, main break, pump failure, storm damage, contamination response, or planned shutdown. The code decides how an event is counted, how its cost is tracked, and what a board or regulator sees when it reviews the trend. If no code describes a deliberate act, the event tends to land in other, or it is filed under equipment failure because that is what the operator first observed. In both cases the trend line shows nothing, and an empty category can be read as an absence of exposure.
The fix is not simple. A dedicated hostile-act code makes the risk visible inside the organization, which is useful. A detailed public log of such events, however, can also reveal how a system responds, and some utilities will reasonably decide that public disclosure should be narrower than internal tracking. This article does not settle that tradeoff. It argues only that the internal record should exist, whatever the public version looks like.
Separate the Cause From the Consequence
A single outage carries at least three facts: what started it, what it did to service, and how long it lasted. A pump station that stops after a utility power loss and a pump station that stops after deliberate damage can produce the same low-pressure event at a customer's tap. Their restoration steps may overlap, but the follow-up differs. Evidence handling, notification duties, and the scope of any investigation may all depend on that first distinction. A record that merges the cause into the consequence cannot separate the two cases later.
Keep unknown as its own state. Many early classifications are provisional, and a field that forces a choice between natural and equipment will be filled in with the most likely answer rather than the verified one. Date each reclassification so the change history stays visible. A revision that moves an event from unknown to deliberate, or back again, should show who made the change and on what basis.
Where Outside Reporting Belongs
A regional interview can justify asking a question. It cannot answer that question for a specific asset. The summary of the Circle of Blue piece says nothing about any particular utility, pump, or dam, and a board packet should not treat conflict reporting as evidence about its own system's condition. Read such sources as a prompt for internal review, not as a finding. Use them to set the list of hazards worth examining, then use the operating log to decide whether a given asset has a hazard-specific gap.
What to Write Down Now
A short set of changes can be made without a new program. Add an event field for initiating cause that includes a hostile-act option and an unknown option. Require that the consequence, the duration, and the affected service area be recorded separately from the cause. Put a revision date on every reclassification. Finally, have someone outside daily operations read a sample of the log each year, so that a decision to file an event under equipment failure can be questioned before it becomes the permanent record. None of these steps requires a decision about public disclosure, and each one makes the internal picture more complete.