Drainage and SuDS: proving it was inspected

After heavy rain, the difference between a well-run Newcastle site and a neglected one shows up in minutes. On one, the water moves where it was designed to move, through the channels and basins and permeable surfaces that were put in to manage it. On the other, it pools at the wrong doors, backs up at a blocked gully, and finds the low point nobody planned for. The drainage was probably designed correctly on both. The difference is maintenance, and behind maintenance, evidence that the maintenance happened.

Sustainable drainage systems, the swales, basins, permeable paving and attenuation features that increasingly sit alongside conventional drainage on modern sites, are designed to slow and manage surface water rather than rush it into the sewer. They work brilliantly when maintained and fail quietly when not. A silted basin or a clogged permeable surface does not announce its decline; it simply stops doing its job, and the first anyone hears of it is a flood. That makes drainage a textbook case for a proven inspection routine rather than reactive call-outs.

Why drainage is an evidence problem as much as a maintenance one

It is not enough to maintain drainage. On many sites you have to be able to show you did. Planning conditions, adoption agreements, management company obligations and insurer expectations all increasingly assume that surface water features are being inspected and maintained on a schedule, and the assumption only holds if there is a record to point to. When a downstream property floods and asks whether your attenuation was kept clear, "we think so" is not an answer; a dated inspection log is.

The honest position to take in writing is that the precise statutory and planning regime for sustainable drainage varies across the UK and is evolving, so a Newcastle site should confirm its specific obligations under its planning consent, any adoption arrangement and the current English position rather than assume a fixed national rule. What does not vary is the logic: a feature you are obliged to maintain is a feature you should be able to prove you maintained.

A maintenance regime that produces a record

Good drainage maintenance is unglamorous and rhythmic. The components below recur across most sites with sustainable drainage, and each one generates a record if you let it.

The exact frequencies should follow the site's drainage management plan, which is the document that should have come with the development and which too often goes missing at the first change of manager. The rhythms above are a starting frame; the management plan is the authority.

The record is the deliverable

Treat each inspection as producing a small, dated deliverable: what was checked, what was found, what was done, and who did it. Photographs of a basin before and after desilting are worth more than a tick in a box, because they show condition rather than assert it. Over a year, those entries become a continuous story that the silt was kept under control and the flow paths stayed clear. That story is what you hand an insurer, an adopting authority or a regulator without having to reconstruct anything.

A practical inspection entry holds:

• The feature and its location on the site.
• The date and the person who inspected.
• The condition found and any blockage or damage.
• The action taken, or raised for follow-up.
• Supporting photographs where condition is the point.

This is the same evidence discipline we apply to building compliance, pointed at the ground. A drainage inspection is not different in kind from a fire equipment check; it is a recurring task that has to be done, dated and shown. We made the broader case for treating the ground as managed risk in managing the land a building sits on.

Tie it to the site and the calendar

Two things keep a drainage regime alive past the enthusiasm of the first year. The first is location: each feature held against the site boundary so inspections attach to a real thing rather than a vague "the drainage". The second is cadence: the recurring inspections chained on a calendar so the next one announces itself rather than waiting to be remembered after a flood. A compliance calendar that treats drainage checks like any other recurring duty is what stops the routine slipping in a quiet, dry spell and being missed when the weather turns. It also pairs naturally with knowing what is underground in the first place, which we covered in know what is buried before you dig.

Dry-weather work, wet-weather payoff

Drainage maintenance is done in the dry and paid back in the wet. The whole point is to keep the system clear and proven while nothing is going wrong, so that when the rain comes the water behaves and the records show why. Inspect on a schedule, capture what you find with dates and photographs, hold it against the site, and the question "was the drainage maintained" answers itself. In SAMRISK, drainage features and their inspection history can sit on the site record and on the compliance calendar, so the proof builds itself one routine visit at a time.