
Headline counts of harm to water systems are easy to find and hard to use. A utility planner, a state agency, or a consultant building a risk register needs to know what a count measures before it goes into a budget or a board memo. The useful question is not only whether harm to water supply is rising, but what a record must contain before anyone can say it has risen.
Three mechanisms under one word
A recent Circle of Blue interview with Peter Gleick, written by Brett Walton, takes up the rise in what it calls water violence. The published summary describes conditions for people in war zones, where, in its words, "Your water supply could be cut." It also points to exploded dams flooding rural homes and to civilians killed in drone attacks. Those examples involve three different mechanisms: deliberate interruption of supply, collateral damage from a structural failure, and direct harm to people. The summary does not provide a dataset or a classification scheme, so any count built from it inherits whatever scheme its compiler chose.
What a record has to hold
A planner who records all three under a single heading will get a total that cannot say which mechanism is growing. A record that separates them needs at least four fields: the mechanism, the location and the population whose service was affected, the duration of the loss, and the source of the report. The source field matters because early reports of an interruption often come from people without direct access to the utility, and the cause may be revised once a crew or an agency confirms it. A record that forces a cause at the time of logging will fill the field with a guess. A better design allows "unknown at logging" as a valid entry, paired with a separate amendment field that keeps the original entry intact.
Counts measure reports, not exposure
An event count is also a measure of what gets reported and where reporting capacity exists. Places with active local media, functioning utility communication, and well-funded monitoring will generate more entries than places where disruption goes unrecorded. A rising count can therefore reflect better documentation as easily as more events. Exposure is a different quantity. It depends on how many people rely on a single intake, whether an alternate source can be brought online, and how long the system can run on storage before service fails. Those are properties of the system, and a utility can measure them in its own asset records before any external event occurs.
Tradeoffs in the category scheme
Broad categories keep totals stable and comparable across years, but they hide the mechanism that planners need to act on. Narrow categories are diagnostic but fragile: they require agreement on definitions, and each new case type forces a revision that breaks comparison with older records. The workable compromise is to keep a fine-grained raw field and roll it up for reporting, with the roll-up rules written down and dated. A rule changed without a date makes the trend line unreadable, because no one can tell whether a shift reflects the world or the rulebook.
A practical starting point
Before the next incident, write the definition of each term the organization uses, the mechanisms it will recognize, the fields it will keep, and the role that may change a classification. Attach a dated note to each change. A count built on those rules can be compared across years. A count built without them will need an explanation every time someone reads it.