Leak Detection in Potters Bar
Properties across Potters Bar's separate sewer areas suffer from invisible water loss due to pin-hole corrosion in copper pipework and scale deposits in cast-iron systems. Hard water from Anglian Water's supply creates microscopic leaks in EN6, EN7 and EN8 properties that only manifest as elevated water bills or damp patches. Detecting these leaks early prevents structural damage, mold growth and unnecessary water consumption charges.
Leak detection in Potters Bar uses acoustic sensors and thermal imaging to find hidden water loss in copper and cast-iron pipes. Hard water from Anglian Water (250+ mg/L) causes pin-hole corrosion in copper within 5–15 years. Early detection prevents structural damage and water bill inflation.
Drainage in Potters Bar — what local engineers know
Anglian Water supplies Potters Bar with water hardness levels of 250–280 mg/L calcium carbonate equivalent, classifying the area as 'very hard'. This mineral-rich water deposits limescale inside copper pipes, causing pin-hole corrosion within 5–15 years of installation in properties built after 1970. Older cast-iron pipes in Victorian and Edwardian Potters Bar homes (especially EN6 postcode) suffer from rust and scale buildup rather than corrosion, but the result is the same: slow internal seepage. Hertsmere building records show approximately 15% of properties require leak detection annually. Hard water also accelerates joint failures and micro-fractures in radiator pipework, creating slow drips inside walls that go unnoticed for months.
- Hard water supply causes limescale accumulation in boilers, radiators and soil pipe joints — powerflush and descaling demand is high across Potters Bar
- Separate sewer system across most of Potters Bar: misconnections (e.g. washing machines plumbed into surface water drains) are a known local issue and can result in environmental enforcement action
- Ageing infrastructure in parts of Potters Bar means drain blockages from grease, wipes and root ingress remain the most common call-out reasons
- With 32% of properties built before 1920, salt-glazed clay drainage and lead-solder copper pipework are common — pipe collapse, root ingress and joint failure are recurring call-out drivers.
What happens when you call us in Potters Bar
- 1 Immediate dispatch. We find the nearest available engineer covering EN6/EN7 and confirm the ETA before the call ends.
- 2 On-site diagnosis — no guessing. The engineer inspects using professional-grade equipment including CCTV where needed and quotes a fixed price before work starts.
- 3 Job complete, report issued. You receive a written completion report. All work is guaranteed — same fault returns within the guarantee period, we come back free.
Who's responsible for drains in Potters Bar?
In Potters Bar, responsibility for a blocked or damaged drain depends on where the fault sits. As a homeowner you are responsible for the drains within your property boundary that serve only your home. Since the 2011 private sewer transfer, Anglian Water is responsible for shared sewers and lateral drains beyond your boundary — even where they run under private land. Road gullies and highway drainage are maintained by Hertsmere.
This matters because it determines who pays. If our engineer's CCTV inspection shows the fault is in a shared sewer, we'll tell you — and you can report it to Anglian Water rather than paying for the repair yourself. The separate sewer layout that dominates Potters Bar affects where these boundaries typically fall, and our local engineers know the EN6, EN7, EN8 networks well enough to identify ownership quickly.
Leak Detection prices in Potters Bar
Every Potters Bar job is quoted as a fixed price before work starts — what we quote is what you pay, with no call-out fee for providing the quote. The final price depends on access (an external inspection chamber is quicker than internal-only access), the pipe material and condition , and how established the blockage or fault is. Request your free quote and we'll confirm the price and your engineer's ETA in the callback.
