Home / Blog / Hampton

Hampton · Leak detection guidance

Leak detection in Hampton: how should logger alert thresholds be documented?

Exact Source · 5 November 2026 · 2 min read

A logger alert is useful only when its threshold, delay, recipients and response are understood. Leak detection in Hampton should not treat every spike as an emergency or every quiet period as proof of no leak. The schedule must connect an alert to a defined technical question.

Choose the threshold from a baseline

Record normal flow or pressure patterns, operating events and data quality before setting the trigger. Explain whether the alert concerns continuous flow, rate, pressure drop, duration or change from baseline.

Do not invent a universal threshold. The appropriate value depends on meter resolution, system, occupancy and intended decision. Record units and sampling interval.

Define filtering and delay

State whether brief peaks, known appliance cycles or maintenance are excluded and how. A delay may reduce false alerts but can hide short events. Preserve raw data and mark the rule applied.

Synchronise the logger clock with building controls and event notes. If a device resets or data gap occurs, suspend automated interpretation until the condition is reviewed.

Assign notification and response

List recipients, priority, contact route and expected action. A technical reviewer may assess data before the site isolates anything. Do not ask untrained occupants to operate valves or plant from an automated message.

Give urgent safety guidance separately for active water near electrics or unsafe fabric. A data alert is not a substitute for direct emergency observation.

Review and retire the alert

Record every alert, event found, action and false-positive reason. Adjust a threshold through a dated change, not silently. Set an end date and owner for ongoing monitoring.

After repair, compare alerts under equivalent operating conditions and close the rule when its purpose is complete. This prevents equipment remaining active without anyone responsible for the data or response. Add an alert register with timestamp, threshold crossed, raw value, known event, notification, acknowledgement and outcome. Review false positives for a specific cause before changing settings. If a threshold is lowered or raised, record the effective date and preserve earlier alerts under their original rule. At final handover, remove obsolete recipients and confirm whether the logger is retrieved, transferred or retained under a new monitoring instruction. Test the notification route once under controlled conditions and record the result without creating a false emergency response.

Further reading

Prepared with AI assistance using the sources listed above. General information cannot diagnose an individual property. Contact us to discuss your circumstances.

Would you like to talk it through?

Tell us what you have noticed and request a callback for further information.

Speak to a specialist