Skip to content

Water balance and the spill register

After a run, the balance decomposes the whole volume into components, taken from the engine’s own continuity table rather than re-derived:

In: sanitary dry-weather flow, rainfall-runoff, groundwater, I&I / RDII, external inflow.

Out: discharge to receiving water, overflow spill, surface flooding, storage change, evaporation and exfiltration.

This is the view that answers the question utilities are most often asked: how much of what arrives at the works is actually sewage? In many networks the honest answer is surprisingly little.

Each overflow event is recorded with its structure, start and end time, duration, volume and a severity classification. Kept over time, that becomes the evidence base for compliance reporting, and it is far more defensible than reconstructing events afterwards from memory and telemetry.

Saved registers require a Utility plan; a single-run register is available on Pro.

The register and the water balance export as a formatted PDF, so what you send to a regulator is generated from the model run rather than transcribed. Transcription is where errors and disputes come from.

On the Utility plan, forecast runs are scheduled server-side and email alerts are sent when a spill is predicted. That turns the model from something an engineer consults into something that tells the operations team when to act.