Rainwater & Stormwater

The first shift is to see the whole site as a catchment. Rain falling on roofs, paving and ground is a volume you can calculate, and the numbers surprise people. The rule of thumb is simple: one millimetre of rain on one square metre of surface yields one litre of water. So 1 mm on a 100 m2 roof gives 100 litres; a year with 800 mm of rain on that roof delivers, in principle, 80,000 litres - before losses.

Real yield is lower because of a runoff coefficient: a hard roof captures perhaps 0.8-0.9 of what falls (the rest evaporates or wets the surface), sloped tiles a bit less, and permeable ground much less because it - helpfully - soaks in instead. Multiply catchment area x rainfall x runoff coefficient and you have a defensible annual yield. For a modest house in a monsoon climate this can be tens of thousands of litres a year - a serious fraction of demand, all of it free and needing only simple treatment.

The catch is timing. Rain is seasonal and lumpy - much of India's falls in a few monsoon months, and climate change is making downpours more intense and dry spells longer. So the design question is not just how much but when: store what you can use in the near term, and recharge the rest into the ground, which is by far the largest and cheapest 'tank' available. Sizing a store to bridge the dry season is possible but expensive; recharge is usually the smarter home for surplus.

A rooftop rainwater system is refreshingly simple, and every architect should be able to sketch one. Rain runs off the roof into gutters and downpipes; it passes a first-flush diverter that discards the dirty opening flow (which carries the dust, leaves and bird droppings that accumulated between rains); the cleaned water then either fills a storage tank for direct non-potable use (or potable, with proper filtration and disinfection) or is directed to a recharge structure - a pit, trench or recharge borewell - that lets it percolate down to the water table. The figure shows this path in section.

Good detailing is what separates a working system from a clogged one. Size gutters and downpipes for peak intensity; screen inlets to keep out leaves; make the first-flush volume proportional to roof area (a common rule is to divert the first 1-2 mm); provide an overflow that routes surplus to recharge rather than back to the roof; and make tanks light-proof and mosquito-proof (standing water is a dengue and malaria risk in Indian conditions - a real, not theoretical, concern). Filtration before storage keeps the tank clean; if the water will be drunk, add settling, filtration and disinfection sized to the risk.

Stored rainwater is excellent for exactly the non-potable uses Lesson 5.1 identified - flushing, laundry, irrigation, cooling - so rainwater and greywater reuse work as a pair, together displacing a large share of mains demand.

Where harvesting captures water for use, groundwater recharge returns it to the aquifer - the single most important thing a building can do for a region running its groundwater into the ground. Recharge structures range from simple soak pits and percolation trenches to recharge wells that inject filtered rainwater deeper. On a permeable site, well-designed recharge can put back a large fraction of annual rainfall, arresting or reversing the water-table decline that plagues Indian cities. Test the soil's infiltration rate first: sandy soils recharge fast, clay barely at all, which changes the whole strategy.

Recharge only works if water can reach soil, which brings us to the ground plane. Stormwater management on site is largely about keeping surfaces permeable. A sealed, paved plot behaves like an extra roof: 80-95% of rain runs off, fast, causing the very floods cities blame on 'too much rain' when the real culprit is too much concrete. Replace impermeable paving with permeable paving, gravel, or planted ground and most of that water infiltrates instead - cutting the flood peak, recharging the aquifer, and cooling the site (Lesson 5.3). The figure contrasts the two ground planes starkly.

The design principle, which Lesson 5.4 develops into full blue-green infrastructure, is to slow, spread and soak rather than collect and convey: keep rain high on the site, moving slowly across living surfaces, rather than rushing it into a pipe.

Rainwater harvesting has moved from optional to obligatory in much of India. Many states and cities - Tamil Nadu was a pioneer, with Chennai making rooftop harvesting mandatory for buildings; Bengaluru, Delhi and others followed - now require harvesting or recharge structures on plots above a threshold size as a condition of building approval or water connection. Green-rating systems (GRIHA, IGBC, LEED) award credits for it, and model building codes increasingly reference it. Knowing your local mandate is part of basic compliance, not a nice-to-have.

Be honest about the limits, though, so you neither over-promise nor dismiss it. Harvesting yield is only as good as the rainfall - it does little in a genuine drought year, so it supplements rather than replaces a resilient supply. Storage is bulky and can be costly if sized for long dry spells. First-flush and filtration must be maintained or quality degrades. Recharge needs permeable soil and a water table that can accept it, and must avoid contaminating groundwater with polluted runoff. And a token harvesting pit installed to tick a permit box, then left to silt up, is a classic piece of greenwashing (Module 10) - the structure exists but does nothing.

Done properly, though, rainwater is the clearest path to net-positive water: combine deep efficiency and reuse (Lesson 5.1) with real harvesting and recharge, and a building on a decent site can return more clean water to its watershed than it takes - genuinely regenerative.

Two further points turn a competent rainwater scheme into a robust one. The first is water quality, which is easy to overlook when you are excited about volume. Roof runoff is not automatically clean: it picks up dust, pollen, bird and animal droppings, and - depending on the roofing material - traces of metals or bitumen, while the atmosphere itself can deposit pollutants, especially in polluted cities where the first rains wash acidic, dusty air out of the sky. This is exactly why the first-flush diverter matters, and why the intended use dictates the treatment: garden and flushing water needs only screening and settling, whereas anything destined for washing or drinking needs proper filtration and disinfection. Recharge water must be clean too - injecting polluted runoff into an aquifer contaminates the very resource you are trying to protect, so recharge structures need a silt trap and filter, and should never take runoff from contaminated hardstanding such as fuel-stained yards.

The second is climate resilience, which is fast becoming the strongest argument for harvesting at all. Climate change is making rainfall more erratic - the same annual total arriving in fewer, fiercer downpours separated by longer dry spells. That double-edged pattern is precisely what a well-designed rainwater system buffers: harvesting and recharge absorb the intense bursts that would otherwise flood streets, and the stored and recharged water helps bridge the lengthening dry gaps. A building that harvests rain is more resilient to both flood and drought than one that simply flushes rain away and buys mains water - a resilience dividend that grows as the climate destabilises.

Finally, remember that rainwater rarely acts alone. It pairs naturally with the greywater reuse of Lesson 5.1: both feed the same non-potable loads (flushing, laundry, irrigation, cooling), so a shared storage-and-treatment strategy and a single dual-plumbing network can carry both, smoothing supply across seasons - greywater is steady year-round, rainwater peaks in the monsoon. Designed together, harvesting and reuse displace far more mains water than either alone, and set up the blue-green integration the module closes on. Treat rainwater not as a standalone gadget but as one flow in a connected water system.