The Natural Water Cycle

The water cycle is powered by the sun and gravity, and it runs in a loop with no beginning or end. Follow one drop. Evaporation: the sun warms the ocean (which holds the vast majority of the planet's water) and turns liquid water into invisible vapour that rises into the air; the same happens from lakes, rivers, wet soil and - importantly on land - from plants, which draw water up through their roots and release it from their leaves, a process called transpiration. Together, evaporation and transpiration (often bundled as 'evapotranspiration') load the atmosphere with moisture. Condensation: as the moist air rises and cools, the vapour condenses onto tiny particles into the droplets that make clouds. Precipitation: when those droplets grow heavy enough, they fall as rain, snow or hail - the moment the cycle delivers fresh water back to the land and sea.

What happens to rain when it lands is the part designers most need to understand, because it is exactly what a building changes. Some rain is intercepted by leaves and surfaces and evaporates straight back. Of the rest, some soaks into the soil - infiltration - and, if there is enough, percolates down past the root zone to refill the groundwater, the vast underground store held in the pores and cracks of soil and rock (an aquifer), whose upper surface is the water table. Water that the ground cannot absorb becomes surface runoff, sheeting across the land into rills, streams and rivers that eventually carry it back to the sea - where the sun lifts it once more and the loop closes.

Two features of this cycle matter enormously later in the course. First, the cycle cleans water: evaporation is nature's distillation, leaving salt and most contaminants behind, so precipitation is naturally soft and clean - which is why captured rainwater is such a prize. Second, the cycle stores and delays water underground: infiltration is a slow deposit into a groundwater savings account that sustains springs, wells and rivers through dry spells. Fast, clean rain becomes slow, stored groundwater only if it can soak in. Hold on to those two ideas - clean-by-evaporation and stored-by-infiltration - because the modern city sabotages both.

Zoom in from the planet to a single patch of land - a plot, a rooftop's footprint, a city block - and the cycle becomes a simple, powerful bookkeeping idea: the water balance. Over a year, the rain that falls on that patch has to go somewhere, and it splits three ways. A share evaporates and transpires back to the air. A share infiltrates into the soil and recharges groundwater. And a share leaves as surface runoff. Roughly, precipitation in equals evapotranspiration plus infiltration plus runoff (with soil moisture storage buffering the timing). This is not an abstraction; it is the single most useful mental model in this whole module, because regenerative design is largely about deliberately changing these shares in a building's favour.

The split is not fixed - it depends on the surface and the situation. On a healthy meadow or forest soil, most rain soaks in: the ground is porous, roots open channels, leaf litter slows the water, so infiltration is high and runoff is low - the land behaves like a sponge. On bare, compacted or sloping ground, less soaks in and more runs off. And on a sealed surface - a roof, a road, a paved yard - almost nothing infiltrates, so nearly all the rain becomes runoff, fast. The same rainstorm can produce a trickle of runoff from a garden and a flash flood from a car park. Intensity matters too: gentle rain has time to soak in, while a cloudburst overwhelms the soil's intake and runs off regardless - which is why India's concentrated monsoon, delivering much of the year's rain in a few intense weeks, is so hard to capture and so easy to lose.

Seeing water as a balance reframes the designer's job. You are not a passive recipient of 'the water supply'; you are managing the water balance of your site. Every design choice - how much you pave, whether roofs drain to a soakaway or a gutter to the street, whether you plant or seal, whether you store rain or let it rush off - shifts the shares between evaporation, infiltration and runoff. The regenerative aim, in one line, is to keep a developed site's water balance as close as possible to its natural, pre-built state: soak in what used to soak in, and do not dump on the neighbours and the drains what the meadow used to quietly absorb.

A conventional building and the city around it disrupt the water cycle at three points, and naming them explains most of our modern water troubles. First, sealing the ground. Roofs, roads, car parks, paved plazas and compacted construction sites are impervious - water cannot pass through them. Where a natural surface let most rain infiltrate, a sealed one converts almost all of it into runoff. As a landscape urbanises, the sponge is paved over: infiltration collapses, groundwater stops being recharged even as the city pumps it harder, and runoff multiplies - arriving at the drains all at once, faster and in greater volume, which is why paved cities flash-flood in downpours that a green catchment would have absorbed. That runoff also scours up oil, litter and pollutants and carries them straight to rivers, so sealing the ground worsens both flooding and water pollution at the same time.

Second, abstraction from afar. Rather than living on the water that falls locally, cities reach out - damming distant rivers, piping water hundreds of kilometres, and drilling ever-deeper borewells into groundwater. When abstraction outruns the recharge that sealing has already crippled, the water table falls year on year - overdraft - wells dry up, land can subside, and coastal aquifers turn salty. India is the world's largest user of groundwater and a stark example: falling water tables across many regions, and cities like Chennai pushed toward 'day zero'. Third, distant discharge. Used water is not returned to the local cycle; it is flushed into sewers and carried far away, discharged - too often barely treated - into a river or the sea downstream. The building takes clean water from one distant place and dumps dirty water in another.

Put the three together and the pattern is unmistakable: the city takes water from far away, refuses to let rain refill what it takes, and exports its used water downstream. It has replaced the cycle's loop with a one-way line - the same linear, take-use-discard model this course exists to challenge, now seen at the scale of the whole water cycle. Every one of these breaks is a design decision, which means every one can be designed differently.

If the three breaks are design decisions, so is repairing them - and the whole of regenerative water can be read as putting each break back together. The organising aim is simple to state: keep the site's water behaving as close to its natural cycle as you can. Where nature let rain soak in, help it soak in; where nature stored and slowed water, store and slow it; where nature returned water clean, return it clean. Against the three breaks stand three moves. Against sealing: reduce impervious area, use permeable paving, green roofs and planting, and route what runoff remains into rain gardens, swales and soakaways so it infiltrates on site instead of rushing to the drain - later modules call this water-sensitive design and the 'sponge city'. Against abstraction: live more on the water that arrives locally by harvesting rainwater and recharging groundwater, so the site leans less on distant, overdrawn sources. Against discharge: reuse water on site and return what leaves as clean as possible - treated, and ideally recharging the aquifer rather than polluting a river.

Notice what this reframing does to the designer's mindset. Rainwater stops being a nuisance to be shed as fast as possible and becomes a resource to be caught. Stormwater stops being 'somebody else's drain problem' and becomes site water to infiltrate. Sewage stops being waste to export and becomes a resource to treat and, one day, reuse. The building stops being a straw stuck into a distant reservoir and a pipe to a distant sea, and becomes a participant that catches, slows, cleans and returns - a small, well-behaved piece of the water cycle.

Two honest cautions, carried from lesson 0.1 and running through the course. Working with the cycle still comes after reducing demand - the cleanest way to take less from the cycle is to need less water in the first place. And infiltration, storage and reuse must never compromise health: recharging an aquifer with polluted runoff, or reusing water without proper treatment and separation, harms the very cycle and people you meant to protect. The binding decisions - what may be infiltrated, what water is safe for what use - belong to qualified specialists and the codes. Work with the cycle, yes; but demand-first, and safely.