Drainage that has to be proven, not assumed

Seen from above, Rotterdam is a city built in open conversation with water. The grid of harbours, channels and basins that defines its plan is not a backdrop to the city but the structure of it, and the relationship between built ground and managed water is visible at almost every scale. It is a useful place to think about drainage, because here the question of where water goes is never assumed. It is engineered, monitored and maintained, because the consequences of getting it wrong are immediate and severe.

Most sites are not Rotterdam, and most of the time water behaves itself. That is precisely the problem. Drainage is the kind of system that works invisibly until the day it does not, and because it works invisibly, it tends to be assumed rather than proven. The gullies are presumed clear, the soakaways presumed functioning, the attenuation presumed sized for the rain that actually falls. None of those presumptions survives a heavy storm, and by then the evidence of whether the system was ever inspected is exactly what is missing.

Drainage is a system, not a feature

The instinct is to treat drainage as something that was designed once, installed, and then forgotten. But a drainage system on a site is a working asset with moving parts and failure modes, and it degrades like any other. Gullies silt up. Pipes block or collapse. Soakaways clog as the surrounding ground changes. Interceptors fill and stop intercepting. Attenuation tanks and controls fail quietly, so that capacity you are relying on is not there when the rain arrives.

The components that need proving on a typical site usually include:

• Surface gullies, channels and their connections.
• Below-ground pipework, manholes and inspection chambers.
• Soakaways and any infiltration features.
• Attenuation storage and flow-control devices.
• Oil and silt interceptors where the site has them.
• Pumping stations, where the ground forces water to be lifted.

Each of these is a thing that can be inspected, and each is therefore a thing that should be recorded as inspected, with a date and a finding. The alternative is to discover the state of your drainage during the event it was meant to handle.

Why "it has always coped" is not evidence

The most dangerous phrase in site management is that something has always been fine. A drainage system that has coped for years may have done so only because the rain has not yet tested its true capacity, or because a slow deterioration has not yet crossed the threshold where it shows. The absence of a flood is not proof that the system works. It is the absence of a test.

Proving drainage means generating evidence on purpose, on a cadence, rather than waiting for the system to declare its own condition. That is a discipline Rotterdam takes for granted because it has to, and it is one that any site benefits from adopting whatever its climate, simply because the cost of a buried failure is so much higher than the cost of looking.

What proving it actually requires

Proving drainage is not complicated, but it does require deliberate effort and a place to keep the result. A site needs a record of what drainage assets exist and where they are, a schedule of inspection and clearance appropriate to their type and risk, and a trail showing that each scheduled check was carried out and what it found. When something is cleared or repaired, that too becomes part of the record, so that the next person can see not just the current state but the history of how it has behaved.

This is where many sites fall down. The drainage exists, and it may even be inspected, but the evidence lives in a contractor's job sheet, an email, or nowhere at all. When a question arises, whether from an insurer, a regulator, a neighbour downstream, or simply a manager trying to understand a flood, there is no consolidated answer. Holding drainage assets, their inspection cadence and their findings against the site itself turns a set of scattered job sheets into a record you can actually rely on, and pairs naturally with the wider discipline of managing the land a building sits on.

Tie the schedule to the calendar, not to memory

The reason drainage inspections get skipped is almost always that they are seasonal, infrequent and easy to forget. A clearance due before the wet season is exactly the kind of task that slips when nobody is reminding anyone it is due. Putting drainage onto a compliance calendar alongside the building's other recurring obligations means the seasonal clearance and the periodic inspection arrive as prompts rather than afterthoughts, and the resulting evidence accumulates as a continuous record rather than a few isolated visits.

The principle travels

Rotterdam is an extreme case, and the specific obligations and standards that apply to drainage and surface water differ from place to place; nothing here should be read as a statement of the rules in any particular jurisdiction, and the live position should always be checked locally. But the underlying principle is universal and does not depend on any one country's law. A drainage system that has been proven, on a schedule, with a record, is one you can stand behind. One that has merely been assumed is a risk you are carrying without knowing its size. The work of turning the second into the first is mostly the work of looking, on purpose, and writing down what you saw.