Home / Blog / Weybridge

Weybridge · Leak detection guidance

Leak detection in Weybridge: what belongs in a communal meter evidence pack?

Exact Source · 5 November 2026 · 2 min read

A communal meter may cover flats, common facilities, plant or commercial users with different operating patterns. Leak detection in Weybridge should begin with verified meter identity and an affected-user schedule before interpreting flow as leakage. The evidence pack must also limit unrelated personal and account information.

Confirm meter identity and boundary

Photograph chamber, serial, units and surrounding apparatus, matching the serial to a reliable supplier or management record. Map visible branches and meters. Do not assume the nearest meter serves the named block.

List categories of users and any known shared supply without publishing individual consumption unnecessarily. Ofwat guidance on meter control and supply pipes can inform the record, while the actual managed arrangement may require supplier or site information.

Build a controlled-use schedule

Record normal automatic and manual uses, occupancy, cleaning, plant and irrigation. Identify a feasible quiet window and the site contact who can confirm readiness. Do not isolate safety or critical equipment simply to obtain a cleaner graph.

Capture start and finish readings, times, logger interval and interruptions. A moving meter supports unexplained flow on the boundary; it does not locate the defect or assign cost.

Narrow by authorised branches

Use competent isolation and coordination, recording valve positions and affected outlets. If a valve passes or another user resumes consumption, qualify the result. Preserve each attempt rather than selecting only the clearest one.

Any proposed access should cite the branch evidence, permissions and site risks. Communal plant rooms or other flats need their own authorised arrangements.

Share and close proportionately

Provide managers, repairers and insurers the sections needed for their decisions. Remove unrelated names, bills and security details, and log recipients. ICO data minimisation remains relevant to technical packs.

After repair, repeat a comparable whole-boundary observation and document the confirmed pipe. Keep unresolved usage anomalies visible. The pack should support management decisions without claiming that every shared branch was tested. Add a data-quality note covering missing users, clock offsets, passing valves and estimated readings. Management can then decide whether another branch test is justified. Close the case only when the technical loss and operational anomalies are either resolved or assigned to named actions with review dates.

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