Rainwater Harvesting Yield Calculator

How to Use

Start with the roof area that actually drains into your collection system. For many homes that means the plan area of the roof feeding the gutters, not necessarily every roof surface on the building. If only one wing of the roof is connected to the storage tank, enter only that contributing area. Then enter your annual rainfall in millimeters. A local weather service, climate normal, or municipal planning document is usually the best source. Using a long-term average is helpful for baseline planning, while using a dry-year value is more conservative.

Next, choose a runoff coefficient between 0 and 1. A value near 0.9 is common for smooth metal roofs with efficient gutters. Rougher or more absorbent surfaces tend to shed less water, so they use lower values. The coefficient folds several losses into one design shortcut, which is why it matters so much. After that, enter the total tank capacity in liters and your expected daily household use for the non-potable uses you plan to supply from the system. If you only want water for irrigation, enter that average daily irrigation demand instead of the whole household demand.

When you press Estimate Harvest, the calculator reports four planning metrics. First is the annual harvestable volume, which is the main supply estimate. Second is approximate full tank turnover, which tells you how many times the storage volume fits into the yearly harvest. Third is a simplified annual overflow indicator, useful for spotting a mismatch between supply and storage, though it is not a storm-by-storm spill simulation. Last is the number of days the annual harvest could cover at the daily use you entered. Together those outputs show whether your project is primarily limited by rainfall, by storage, or by demand.

If you are comparing design ideas, try a few deliberate scenarios. Increase the tank size and see whether the annual spill indicator drops. Lower daily demand and note how many more days of supply you gain. Change the runoff coefficient to compare roof materials. These simple sensitivity checks often reveal more than a single point estimate because they show which variable most strongly controls your outcome on your site.

Formula

Designing a rainwater harvesting system begins with a direct physical relationship between rainfall depth and catchment area. The formula below captures that first-order behavior:

Here V is the annual volume in liters, A is the roof area in square meters, R is the annual rainfall in millimeters, and C is the runoff coefficient. Because 1 millimeter of rain on 1 square meter corresponds to about 1 liter, the units work out cleanly without a separate conversion factor when you stay in metric units. This is why the calculator asks for square meters and millimeters rather than feet and inches.

Once the gross harvestable amount is known, storage becomes the next design question. A tank or cistern captures runoff during storms, but any real tank has finite capacity. The calculator uses the annual harvest and the storage volume to estimate how often the tank volume would be cycled over the year. That relationship is expressed as:

Where F is the number of full-tank equivalents and T is tank capacity. This is useful because it reveals whether a very small tank is likely to turn over often or whether a large tank may sit underused relative to the annual water available. The overflow line in the calculator should be read as a simplified annual storage-spill indicator based on that turnover idea. It helps identify cases where more storage could potentially capture more water, but it does not resolve the exact timing of every storm.

Demand is the final planning layer. If you know the average amount of non-potable water your household uses per day, you can compare the annual harvest to that demand:

In this expression, D is days of supply and U is daily usage. It is a rough annual coverage metric rather than a guarantee of uninterrupted service. In seasonal climates, a home could technically have enough annual rainfall for many months of use and still run dry during an extended summer dry spell. Even so, this number is easy to interpret and gives a fast sense of how meaningful the harvested volume is relative to everyday demand.

The following reference values are common starting points for preliminary design. Local practice, roof age, slope, gutter layout, and maintenance can justify moving these values up or down.

Those coefficients are not just abstract numbers. A higher coefficient means more of the rain that lands on the roof makes it into the tank. A lower coefficient means more of it is lost before storage. That is why a system with the same roof area and rainfall can perform quite differently depending on surface finish, gutter design, and maintenance quality.

Example

Consider a home with a 120 square meter roof in a place that receives 650 millimeters of rain each year. If the roof is smooth metal, a runoff coefficient of 0.9 is a reasonable first estimate. Plugging those numbers into the equation gives an annual harvestable volume of 70,200 liters. That is a surprisingly large amount for many households and immediately shows why rooftop collection can be useful even when the rainfall does not seem dramatic.

Now suppose that home has a 5,000 liter tank and uses 250 liters per day for irrigation, toilet flushing, and laundry. Dividing 70,200 liters by 5,000 liters gives about 14.0 full-tank equivalents per year. Dividing 70,200 liters by 250 liters per day gives about 281 days of annual supply. The interpretation is important: the roof can provide a meaningful fraction of yearly non-potable demand, but a single 5,000 liter tank may be too small to fully capitalize on heavy storms unless water is being drawn down regularly between events. In other words, the site has a healthy supply potential, while storage strategy may be the tighter constraint.

A different example shows the opposite pattern. Imagine a smaller roof, only 60 square meters, in a climate with 450 millimeters of rain and a tile roof coefficient of 0.75. The annual harvest becomes 20,250 liters. If the owner installs a large 10,000 liter cistern but still uses 200 liters per day, the system now has generous storage relative to supply, yet limited rainfall relative to demand. That configuration may still be valuable for smoothing dry periods, but the limiting factor is the roof-water resource itself rather than the tank.

These examples highlight why the calculator is best used as a decision aid instead of a single verdict. It helps answer questions such as: should I invest in more roof collection area, a larger tank, or lower daily use? Often the most cost-effective improvement is not the biggest tank but better matching of storage, supply, and intended use.

Limitations and Assumptions

This calculator uses annual averages, so it intentionally smooths out the real rhythm of weather. Actual systems live through wet weeks, dry months, intense cloudbursts, and long calm periods. A home may receive enough rain annually to cover much of its demand, yet still need backup water during seasonal dry spells. Conversely, a site with short intense storms might need more storage than the annual average alone suggests, because large volumes arrive in brief bursts. Monthly or daily rainfall data gives a better answer when final sizing matters.

Water quality is another important limit. The runoff coefficient addresses quantity losses, not treatment needs. Roof debris, bird droppings, dust, and pollutants can affect what the water is suitable for. Many systems use a first-flush diverter so the dirtiest initial runoff does not enter the tank. Potable use typically requires filtration, disinfection, and compliance with local rules. For many households the safest first target is non-potable demand, because it offers real savings while avoiding unnecessary treatment complexity.

There are also practical assumptions hidden in the numbers. Roof area should represent the portion connected to the collection system. Tank capacity should mean usable storage, not only the nominal volume written on a manufacturer sheet. Daily use should reflect the water applications you actually intend to offset. A family that only uses harvested water for irrigation has a very different daily demand profile from a home that also serves toilets and laundry. Even behavior matters: if you irrigate heavily right before a storm, you create tank space and capture more runoff than a household that leaves the tank nearly full.

Finally, the calculator's overflow line is intentionally simplified. It is best read as a signal that storage may be small compared with annual harvest, not as a precise forecast of liters spilling from the overflow pipe during real storms. If you are designing a system for permitting, detailed budgeting, or potable use, pair this tool with local rainfall records, roof and gutter details, first-flush design, filtration requirements, and maintenance planning. For an early feasibility check, though, this annual method is fast, transparent, and surprisingly informative.

Use the calculator to explore scenarios, then validate promising options with local climate data and practical operating assumptions. That approach keeps the math simple at first, without losing sight of the real engineering questions that determine whether a rainwater harvesting system feels generous, frustrating, or just right for the property.