If I had to summarize what I learned designing drainage works in one sentence, it would be this: almost no structure fails because the material was bad, it fails because water found a path nobody designed for it. Drainage works are not an accessory to a road or urban project, they’re the infrastructure that decides whether a road, a slope, or a foundation reaches its design lifespan or deteriorates in half the time.

Surface Drainage vs. Subsurface Drainage

Surface drainage handles water running over the terrain: ditches, canals, catch basins, and culverts that intercept runoff before it erodes slopes or saturates a road’s subgrade. Subsurface drainage, on the other hand, deals with water that has already infiltrated: gravel subdrains wrapped in geotextile, placed to lower the water table or intercept flow within the soil mass before it generates pore pressures that reduce shear strength.

The most common confusion in the field is treating these two systems as interchangeable. A well-sized ditch is useless if the real problem is groundwater surfacing halfway up a slope, and a subdrain doesn’t solve poorly channeled surface runoff. Getting the diagnosis right — which water is actually causing the problem — is the first step in any drainage design, before you even calculate a discharge.

Design Criteria: Discharge, Return Period, and Runoff Coefficient

Sizing a drainage work starts with the design discharge, which in practice is estimated with the rational method for small catchments:

  1. Define the return period based on the structure’s importance (typically 10-25 years for ditches and minor culverts, up to 50-100 years for critical works).
  2. Obtain the design rainfall intensity from the region’s IDF (intensity-duration-frequency) curves.
  3. Estimate the runoff coefficient based on land use and catchment cover (impervious surfaces like pavement contribute nearly 100% of rainfall, well-vegetated green areas much less).
  4. With those three parameters and the catchment area, the rational method returns the peak discharge the structure needs to evacuate.

That discharge is then used to size the hydraulic cross-section — a circular or box culvert, a triangular or trapezoidal ditch — using uniform flow equations (Manning is the de facto standard), while checking that velocity stays in a range that neither erodes the channel material nor allows excessive sedimentation.

Drainage as Failure Prevention, Not a Secondary Work

This is what almost never gets explained with enough emphasis: uncontrolled water is, by far, the most common root cause behind slope instability and premature deterioration of pavements and structures. A poorly designed or absent subdrain raises pore pressures inside a hillside, reduces the soil’s effective strength, and is precisely the mechanism that triggers a large share of the mass movements documented after rainy seasons. In the same way, when runoff erodes the toe of a slope or saturates the subgrade under a road, deficient drainage ends up being the root cause that erosion control works have to compensate for years later, at a much higher cost than solving it in the original design.

That’s why, on any geotechnical or road project, drainage shouldn’t be designed at the end, as an afterthought — it should start with the initial soil study: understanding where the water comes from, how it moves through the ground, and where it will be conducted in a controlled way.

Closing the Loop: Water, Terrain, and Data

Designing drainage well requires thinking in complete systems — contributing catchments, conveyance networks, discharge points — rather than isolated structures, and that same systems logic is what later led me to work with geospatial data and risk models: understanding a territory, whether to conduct its water or to predict its behavior under a hazard, always starts by modeling how flows — of water, sediment, or information — move through it.