Skip to content
CLW
A commercial development where waterproofing risk is managed on site

Knowledge · Construction risk

What an Expert Witness Sees: the Recurring Patterns Behind Below-Ground Water Claims

Below-ground water disputes are not random. From the witness box, the same handful of root causes appear again and again, long before the contractor reached site.

Last updated 15 June 2026

Direct answer

Below-ground water disputes follow a small number of recurring patterns, and almost all of them originate before the contractor reaches site. From expert witness work, the patterns that appear again and again are: no competent party was ever formally appointed to design the waterproofing; a supplier’s specification document was mistaken for a design despite disclaiming that role; the risk assessment was generic or absent; the interfaces between trades fell into a scope gap; and the installation was never independently monitored before it was concealed. Workmanship defects feature, but they are usually the symptom that exposes an upstream design or procurement failure, not the root cause.

Full explanation

Expert witness work is a particular kind of education. You do not see the projects that went well; you see the ones that ended in a leaking basement, a claim and a bundle of documents, and your task is to work out, dispassionately and to the standard a tribunal will accept, what actually went wrong. After enough of those, a pattern becomes impossible to ignore: the failures are not exotic, and they are not random. The same root causes recur across schemes of every size and procurement route. CLW’s Founder and Technical Director, Ben Hickman (MEng PgDip MSt(Cantab) C.Build E CSRT CSSW APAEWE WDS AssocRICS MCIOB MCABE MAE), is a registered expert witness and a contributing member of the BS 8102:2022 committee, and the patterns below are the ones that surface most consistently in that work.

Pattern one: orphaned design responsibility

This is the dominant pattern, and it is almost always the first thing the documents reveal. There is a defect, but there is no designer. The architect assumed the structural engineer had the waterproofing; the engineer assumed it was a supplier’s product or a finish outside their scope; the contractor assumed it had been designed for them to build. Nobody formally accepted the role, and so nobody discharged it. This is the orphaned-risk problem of who should design the waterproofing made visible at the worst possible moment, and it is why the risks of not appointing an independent designer are not theoretical. The risk did not vanish because no one owned it. It waited.

Pattern two: the supplier document mistaken for a design

Close behind sits a specific and predictable artefact in the project file. A supplier specification, often forty pages or more, with detailed drawings, BBA certificates and extensive reference to BS 8102, treated by the entire team as the waterproofing design. The project manager put it in the contract documents, the contractor priced against it, the architect filed it as evidence the waterproofing was designed. And on its own first or last page, the document states that it does not constitute a waterproofing design and that a competent designer should be appointed. In a dispute that disclaimer is usually decisive, because it is true. As we set out in why supplier warranties and specifications do not replace independent design, the document everyone relied on was never a design at all.

Pattern three: the generic or absent risk assessment

BS 8102 requires a waterproofing-specific risk study - water pressure to the full height of the retained structure, construction-sequence risk, material compatibility, long-term degradation, maintenance access. In dispute bundles this is frequently either missing or substituted by a generic construction risk register that mentions water in passing. The consequence is a design that was never tested against the conditions that actually caused the failure. A system selected for the current water table, with no allowance for the rising table or burst main that later put it under pressure, is a recurring entry in the catalogue of why these defects occur.

Pattern four: the failure happens at the interface

The forensic detail is telling: water rarely enters through the middle of a membrane or slab. It enters at the junctions - where the waterproofing meets the structural frame, the drainage, a service penetration, the capping or capping beam, or the above-ground envelope. These are precisely the points that fall between trade packages when no one is coordinating the waterproofing as a whole. The scope gap at interfaces is not an abstraction in the witness box; it is the literal location of the leak.

Pattern five: nobody watched it go in

The final recurring feature is that the installation was concealed without independent verification. The defect - a membrane lapped the wrong way, an untreated construction joint, a penetration sealed with an incompatible material - was invisible the moment it was covered, and the only quality record was the contractor’s own. Investigation then reveals an error that competent construction monitoring at the hold points would have caught and corrected before it disappeared.

Why the patterns matter before there is a dispute

The reason to set these out is not to narrate failure but to design it out. Each pattern is preventable, and the prevention is the same in every case: a named, competent, independent owner of the waterproofing scope, appointed early, who produces the risk assessment and design philosophy, coordinates the interfaces, and verifies the build. The anatomy of one such failure, including how the claim found its way back down the supply chain, is set out in the anatomy of a £450,000 basement claim.

Wondering whether your scheme carries any of these patterns? Put your project and your responsibility matrix to the Waterproofing Wisdom agent - CLW’s specialist AI, trained on BS 8102:2022 and two decades of exactly this dispute work - and find out before water does.

Frequently asked questions

Are most basement water disputes caused by bad workmanship?

No. From expert witness work, the recurring causes are overwhelmingly upstream of the contractor: no one competent was appointed to design the waterproofing, a supplier document was mistaken for a design, the risk assessment was generic or absent, and the interfaces between trades were never coordinated. Workmanship defects exist, but they are usually the symptom that surfaces a design or procurement failure that was already present, not the original cause.

What is the single most common pattern in waterproofing claims?

Orphaned design responsibility. On scheme after scheme, the project file contains no evidence that any competent party formally accepted responsibility for the waterproofing design. The architect assumed the engineer had it, the engineer assumed it was a supplier's product or a finish, and the contractor assumed it had been designed for them. When water comes in, there is a defect but no designer, which is exactly the position that produces a dispute.

Does a supplier specification count as a waterproofing design in a dispute?

Not in the eyes of the standard or, typically, the tribunal. Supplier specifications almost always carry an explicit disclaimer stating that they do not constitute a waterproofing design and that a competent designer should be appointed. That disclaimer is usually decisive. The document the whole team relied on turns out, on its own terms, never to have been a design, leaving the project without the competent design BS 8102 expects.

Why does expert witness experience improve waterproofing design?

Because it shows you, in forensic detail, exactly how and where designs fail in service rather than on paper. Seeing the same root causes recur across many disputes builds a working map of the failure modes, which feeds directly back into designing them out: the risks worth pricing, the interfaces worth coordinating, the documentation worth producing. Design informed by dispute work is design that has seen the consequences of getting it wrong.

Related guidance

Working on a live scheme?

Put our AI agent to work. It'll reason through your specifics from BS 8102:2022 and land on a defensible recommendation.