A small drip on Friday is a closed school on Monday.
“a leak shut a school for a week last term”
Water leaks are the cheapest hazard to catch and the most expensive one to miss. Pulse-counter meters running 24/7 spot out-of-hours flow the moment it starts — and humidity sensors catch what a meter can't, flagging a room that runs damper than its neighbours, often the first sign of water getting in after heavy rain. From there the loop closes: a task goes to the right person and is chased until it's signed off, and where automated isolation valves are installed the system can shut the flow itself.
Three capabilities, one feed.
Continuous pulse metering
Litres per hour, per site, per zone. Daily totals reconciled with billing. Sudden spike triggers a same-day anomaly task.
Out-of-hours alerts
Flow at 03:00 on a Sunday is never normal. Real-time push to the FM on-call, regardless of the metric's usual cadence.
Optional valve-closure integration
Where isolation valves are wired in, the system can close them automatically on confirmed leak — capping damage at minutes, not days.
Out-of-hours flow as the canary. Escalation runs in minutes — the difference between a wet floor and a closed building.
It doesn’t stop at the screen.
The reading is checked against the rulebook on an orchestration engine. When it’s out of band the job is created, sent to the right person and chased until it’s signed off — and every step is logged. Here’s a real flow for leak detection.
Rules & flows on an orchestration engine · every action traceable to a line of config
The audit trail it builds.
One sensor stream. Multiple rulebooks. Each row links to the full entry in the Standards matrix.
Where it lives in real estates.
Carry this on your estate?
Short call. We’ll scope what a v1 deployment looks like and walk through the standards we can prove the day it goes live.