Five Permeable Paving Mistakes That Fail on Site (and How to Avoid Them)

I’ll be honest from the start. I’m tired of hearing that permeable paving “doesn’t work.”

I hear it all the time. A site manager shrugs at a car park that’s turned into a paddling pool. A developer tells me they “tried it once” and won’t touch it again. A homeowner swears the new block drive is worse than the tarmac it replaced. Every time I go and look or ask a few awkward questions, it turns out the same way. The paving was fine. The problem was something somebody did, or didn’t do, between the drawing and the handover.

Permeable paving is one of the most forgiving and well-proven bits of drainage equipment we have in this country. There are decades of UK monitoring behind it. It isn’t fragile, and it isn’t experimental. It is, however, unforgiving of a handful of specific mistakes. Those mistakes keep turning up because they’re cheap, quick, and invisible once the blocks are down.

So this isn’t a sales pitch for permeable paving. It’s a list of the five things I see go wrong most often, why they go wrong, and what you should do instead. If you’re a contractor, a site manager, a developer, or a client trying to work out why your shiny SuDS-compliant surface is holding water like a bath, this guide is for you.

Why permeable paving fails (spoiler: it usually doesn’t)

Before the list, it’s worth being clear about what a permeable pavement actually is, because most of the mistakes come from forgetting it.

It’s not a paving product. It’s a drainage structure that happens to have paving on top.

The blocks, resin, or porous asphalt you see are the least important part. What matters is underneath: the laying course, the open-graded sub-base storing the water, the geotextiles or membranes controlling where the water goes, and the ground (or outfall) through which it eventually leaves. Treat the job as “laying a nice drive,” and you’ll make every mistake below. Treat it as building a below-ground attenuation tank that people can park on, and you’ll avoid most of them.

If you want the full technical picture—system types, the standards, design principles, and the evidence base – MAC Group Ltd.’s definitive guide to permeable paving is the most thorough single resource I’ve come across, and I’d point anyone new to permeable paving at it first. What follows is the site-level stuff, the things that go wrong once the design leaves the office.

Mistake 1: The wrong sub-base (or the right one, ruined)

If I could get one message onto every site cabin wall in the country, it would be this:

Type 1 is not a permeable sub-base.

I’ve lost count of the jobs where the drawing called for a clean, open-graded aggregate, typically something like a 4/20 crushed rock with all the fines taken out, and what turned up was standard MOT Type 1. Sometimes it’s a supplier substitution nobody questioned. Occasionally the material just isn’t easy to get locally, and someone decides, “Stone is stone.” Sometimes, and this situation is the one that irritates me most, someone on site thinks they know better and wants a “firmer base.”

Type 1 is designed to compact into a dense, tight layer. That’s precisely what you want under a normal road and exactly what you don’t want under a permeable one. All those fines fill the voids, and the voids are where your water is supposed to be stored. Lay permeable blocks on Type 1, and you’ve built an expensive, slightly leaky version of a conventional pavement. Water goes through the joints, hits a dense layer, and sits there.

The second version of this mistake is subtler. You get the right material, but you contaminate it.

An open-graded sub-base is basically a giant sieve. If it’s left exposed while plant tracks mud across it, or a muck-away wagon reverses over it in the wet, or someone stockpiles topsoil on the edge where the rain washes it in, the fines go straight into the voids. You can’t see it afterwards. It looks like clean stone on top. But you’ve cut its storage and infiltration capacity before a single block is down.

What to do instead:

  • Verify delivery tickets against the spec. Every load. It takes two minutes.
  • Know what the right material looks like and what it doesn’t look like. Open-graded aggregate has visible voids. If it looks like it’d make a lovely compacted haul road, it’s probably wrong.
  • Protect the sub-base from the moment it’s placed. Keep the plant off where you can, keep it covered if work is paused, and keep soil and spoil well away from the edges.
  • If contamination occurs, please remove and replace the affected area. Don’t kid yourself that a bit of mud doesn’t matter. It matters a lot.

Mistake 2: Letting the site wreck it before handover

Mistake 2 is the one that makes me genuinely angry, because it’s entirely a programming problem and almost always avoidable.

On housing sites especially, there’s a strong temptation to lay the permeable estate roads and private drives early. They look finished, they give everyone clean access, and the sales team loves them. Then you spend the next eighteen months building houses on either side. Brick cutting, plastering waste, cement slurry, mud off boots and tires, skips being dragged about, and landscaping contractors dumping topsoil – all of it ends up on, and in, the paving.

By the time the last plot is sold, the joints are packed with fines, and the surface has the infiltration rate of a car park in a supermarket. Then everyone stands around wondering why the “new SuDS” doesn’t work.

I’ve also seen the opposite. Heavy construction traffic runs over a finished permeable surface that was never designed for those loads during construction, and the blocks rut, or the laying course gets pumped full of muck.

What to do instead:

  • Sequence it properly. The best approach on most sites is to build up to sub-base level, protect it, use a temporary running surface where needed, and lay the final surface course as late as possible.
  • If you must lay it early, protect it – sheeting, temporary boarding on key routes, and a clear rule that cutting, mixing, and washing out happen nowhere near it.
  • Put a wheel wash or at least a proper hardstanding at the site access so you’re not carrying half of the site onto your finished surface.
  • Build a proper clean-down into the handover. Sweep, vacuum-sweep if needed, and re-joint where the joints have been contaminated. Then test it. Don’t just eyeball it.

The cost of protecting the surface is trivial. The cost of digging up and relaying the entire estate’s worth of contaminated paving, or engaging in disputes with the adopting authority, is significant.

Mistake 3: Getting the geotextiles and membranes wrong

This one causes more confusion than anything else on the list. I think that’s because the decision is made in the design office and the people on site don’t always understand why a particular layer is where it is.

Broadly, permeable pavements come in three flavors:

  • Full infiltration: water passes through the pavement and soaks into the ground beneath.
  • Partial infiltration: some soaks away, the rest is let out slowly through a pipe.
  • No infiltration (tanked): the whole thing is wrapped in an impermeable membrane, and the water is stored and released through a controlled outlet.

Each of those needs different layers in different locations. A full infiltration system needs a permeable geotextile between the sub-base and the subgrade so that water passes through but the fine soil doesn’t migrate up into the stone. A tanked system needs a properly lapped, sealed, puncture-protected impermeable membrane. Some designs also use a geotextile higher up, under the laying course, to help trap pollutants.

Where it goes wrong:

  • Someone puts an impermeable membrane in an infiltration design because “we always put a membrane down.” Congratulations, you’ve built a pond.
  • Someone omits the geotextile from an infiltration system, believing it to be a waste of time. Over the years, the subgrade fines work their way into the sub-base, and the storage slowly vanishes.
  • A tanked system’s membrane gets punctured by a sharp stone or plant, or the laps aren’t sealed, and water ends up exactly where the designer was trying to keep it out of. Often that’s next to foundations or into contaminated ground.
  • The layers may be installed at the incorrect level, or an inappropriate product may be used simply because it was available on the van.

What to do instead:

  • Please ensure the site team understands which kind of system they’re building and why. A two-minute toolbox talk does more than a stack of drawings.
  • Use exactly the specified geotextile or membrane. These aren’t interchangeable, and the product data matters.
  • For tanked systems, treat the membrane like waterproofing, because that’s what it is. Protect it, lap it properly, seal penetrations properly, and inspect it before it is buried.
  • Photograph each layer before it’s covered. If there’s ever a question about what went in, you’ll be overjoyed you did.

Mistake 4: Assuming the ground will take the water

This mistake gets made long before anyone picks up a shovel, but it fails on site, so it’s on the list.

There’s an awful lot of wishful speculation regarding infiltration. Someone looks at a site, decides it’s “probably sandy,” and designs a full infiltration system. Alternatively, a desk study may indicate that the geology is favorable, leading to a decision not to conduct any testing. Or there’s one soakage test from the far corner of the site, and it’s assumed to apply everywhere.

Then the scheme is built on ground that turns out to be clay, made ground, or has a perched water table sitting a meter down in winter. Water goes into the sub-base and simply stays there. The pavement fills up from the bottom, and the surface floods.

I’ll say it plainly: you can’t design an infiltration system without testing infiltration. In the UK, proper soakaway testing to BRE 365 typically involves conducting tests at the appropriate depth, in sufficient locations, and ideally during a sensible time of year. A test done in the middle of a dry August tells you very little about how the ground behaves in a wet February.

The positive aspect is that poor ground conditions do not necessarily prevent the use of permeable paving. That’s one of the best things about permeable paving. If the ground won’t take water, you design a partial infiltration or tanked system and let it out at a controlled rate. It still gives you storage, attenuation, and water quality improvement. What you can’t do is pretend.

What to do instead:

  • Test early, ideally at the feasibility stage, so the drainage strategy is designed around real ground rather than hope.
  • Test at the depth the water will actually be discharged at, not just whatever’s convenient.
  • Look at groundwater levels, especially seasonal highs, and at any contamination that could be mobilized by sending water into it.
  • If the results are not satisfactory, please consider revising the design. Don’t simply remain passive and hope for a positive outcome.

Mistake 5: Forgetting the edges

Edge restraint isn’t glamorous, and nobody puts it in the brochure photos, but it’s where a surprising number of permeable pavements start to fail.

Block paving of any kind relies on interlock. The blocks lock together because they’re held tightly between fixed edges. Take away a solid edge and the blocks start to creep, the joints open, the laying course migrates, and you get rutting and loose blocks, especially where vehicles turn or brake. With permeable paving, the wider joints and the open-graded laying course make the situation even more of an issue.

I observe that edges are often compromised in several ways:

  • No proper kerb or edging at all along a soft verge or planting bed, with someone assuming the grass will “hold it.”
  • The edging is set on a weak base and is not properly haunched, causing it to rotate outwards under load.
  • The edges may be suitable for pedestrians, but they are inadequate for the traffic that actually uses the surface, such as delivery vans on a “footpath” or bin lorries on a private drive.
  • Badly detailed junctions where permeable paving meets conventional paving can cause water to accumulate in unintended areas.

What to do instead:

  • Treat the edge restraint as a structural element, because it serves that purpose. Specify and build it for the loads the surface will actually see, not the loads on the drawing.
  • Set kerbs and edgings properly on concrete with proper haunching, and give them time to cure before compacting against them.
  • Consider the transitions between permeable and impermeable surfaces and the direction of any run-off.

Here are a couple of additional mistakes I want to address while I’m on my soapbox.

Since I’ve started, I might as well finish.

Sand in the joints. Permeable block paving needs clean, angular, grit-sized jointing aggregate, not building sand. Fill the joints with sand and you’ve sealed the very gaps the water is supposed to go through. It seems obvious. It still happens.

No maintenance plan. Permeable paving does need maintaining. Not much, but some. A regular sweep, an occasional deeper clean, keeping leaf litter and soil off it, and dealing with weeds before they take hold. If the client or the management company doesn’t know that, it won’t happen, and in ten years someone will be telling me that permeable paving “doesn’t work.” Hand over a simple written maintenance plan with every job. It costs nothing and protects everyone.

The real lesson

Look back over that list and you’ll notice something. None of these failures are failures of permeable paving as a technology. Every single one is a failure of specification, of sequencing, of supervision, or of understanding.

That matters, because permeable paving is about to become much more important in this country. As SDUs move from a planning nice-to-have to something closer to a national standard, more people will be building these systems, many of them for the first time. If the industry misinterprets the poorly constructed examples, we risk losing one of the most cost-effective and efficient tools for managing surface water.

So my plea is simple. Treat permeable paving as a drainage structure, not a surface finish. Respect the sub-base. Protect it while the site is live. Understand the layers. Test the ground. Build proper edges. And hand it over with a plan for looking after it.

Do those things and it’ll quietly do its job for decades. Skip them and you’ll join the long list of people blaming the product for a problem they built themselves.

 

Latest news

Related news