The Cistern as a Planning Unit

The contributing surface establishes the first boundary of a rainwater system. On buildings this is commonly a roof, but courtyards, paved surfaces, terraces, and other designed surfaces may also collect runoff where appropriate.

Potential harvest depends fundamentally on rainfall depth and contributing area, adjusted for losses associated with the collection surface and system. Increasing storage volume cannot compensate for a catchment that rarely supplies enough water to fill it.

The catchment should also be read qualitatively. Material, slope, accumulated dust, vegetation, animals, nearby activities, maintenance, and atmospheric deposition can influence the water reaching storage. This becomes especially important when the harvested water is intended for uses involving greater human exposure.

A useful site survey therefore maps both catchment area and catchment condition. The roof is not simply the background above the tank. It is the first component of the infrastructure.

Follow water in the sequence it would actually travel. Begin at the collection surface and trace gutters, channels, downpipes, screens, first-flush or diversion components where present, filters, junctions, tank inlets, storage, outlets, pumps, distribution lines, drainage, and overflow.

This simple exercise often exposes gaps between a drawing and a functioning system. A downpipe may disappear underground without a clear destination. Several roofs may feed one tank despite being represented separately on architectural plans. An overflow may terminate at a wall even though water ultimately crosses neighboring land.

Drawing the entire path converts a collection of plumbing components into a spatial system. It also reveals where water can be lost, contaminated, redirected, or become difficult to maintain.

Cistern capacity is usually expressed as a volume, but storage performance is a relationship through time. Water enters during rainfall events and leaves according to demand. The timing of both matters.

A system may receive enough annual rainfall in total while still running empty during a long dry interval. A large cistern may remain underused if its contributing catchment is too small. Another may overflow frequently because storage is small relative to episodic inflow or because demand is low.

Early planning should therefore ask what period the storage is intended to bridge and what demand it is expected to serve. Detailed sizing can later use rainfall records, runoff assumptions, storage behavior, and demand profiles, but the conceptual water balance should be understood before a tank volume becomes fixed.

Rainwater should not be treated as having one universal quality requirement. The controls needed depend on how the collected water will be used. Irrigation, toilet flushing, cleaning, process uses, and drinking can involve very different exposure pathways and regulatory requirements.

For drinking-water applications, preventive risk management begins before the tank. Catchment condition, screens, protected storage, sanitary access, contamination pathways, treatment, and ongoing inspection all matter. First-flush or diversion devices may reduce the amount of accumulated debris and contamination entering storage, but they do not replace a complete risk-management approach.

For planning review, the important discipline is to make intended use explicit. A plan labelled only rainwater tank leaves a critical question unanswered: stored for what?

Define the contributing catchment and its surface condition Trace gutters, channels, and downpipes without assuming where they terminate Identify screens, filters, diversion devices, bypasses, and disconnected components Record the tank location, type, approximate capacity, accessibility, and visible condition Identify the intended uses of stored water Trace distribution from the tank toward those uses Follow the overflow to its actual receiving surface or drainage system Look for leakage, sediment, staining, erosion, blocked inlets, and uncontrolled discharge Record how the system can be inspected, cleaned, repaired, and operated Return to the site plan and draw the complete water path as one connected system

One cistern is a small intervention. Many cisterns distributed across roofs, courtyards, institutions, housing, commercial buildings, and public landscapes become a planning layer.

At that scale, different questions emerge. How much roof area contributes to storage? Where is stored water used? Which buildings have useful non-potable demands? Where do overflows converge? Which systems depend on pumps? Where can excess rainfall enter soil or vegetation? Who is responsible for maintenance?

GIS can help make this distributed infrastructure visible by linking building footprints, catchment areas, storage, demand, drainage, land cover, and ownership. The objective is not to pretend that decentralized storage replaces centralized water supply or stormwater infrastructure. It is to understand it as one additional layer within the wider urban water system.

The planning opportunity lies in making these layers work together rather than treating each tank as an isolated sustainability feature.