Introduction: how this rainwater harvesting reliability planner works
A rainwater harvesting system is judged as much by timing as by annual volume. A roof can collect plenty of water over twelve months and still leave the tank empty when irrigation, flushing, or other non-potable uses peak. This planner focuses on that timing problem by stepping through the year one month at a time and showing how storage responds to rainfall, losses, and demand.
The model stays intentionally transparent. For each month, the calculator converts rainfall depth into captured gallons using roof area and runoff efficiency, adds that water to the tank, applies a simple monthly storage-loss percentage, limits storage to the usable tank capacity, and then subtracts demand. The output is a planning-level reliability estimate, not a detailed hydraulic design, but it is straightforward to compare across scenarios.
That makes the tool useful in early design, budgeting, and education. You can test whether more storage would reduce dry-season shortages, whether a larger roof connection would meaningfully improve supply, or whether demand management would help more than adding capacity. Because the assumptions are visible, the results are also easier to explain to homeowners, clients, students, or reviewers.
Monthly rainwater balance and formula
The monthly rainwater balance begins with the portion of roof runoff that the system can actually capture. Monthly rainfall is entered in inches, while roof area is handled in square feet internally. If you choose square meters, the calculator converts that area before running the simulation. Runoff efficiency is entered as a decimal between 0 and 1 so it can represent wetting losses, splash-out, gutter overflow, debris screens, and similar real-world effects.
Captured volume (gallons) is estimated with the following relationship:
The constant 0.623 converts one inch of rain falling on one square foot into gallons. After capture is calculated, the model adds that water to the current storage, applies the monthly loss percentage, caps the result at the tank capacity, and records any overflow. Demand is then removed. If demand is larger than the available water, the tank is set to zero and the difference is counted as a shortage.
Monthly demand is based on your average daily demand multiplied by the number of days in each month. If you enter seasonal adjustments, each month is scaled by that percentage so you can reflect irrigation seasons, occupancy changes, or other predictable shifts in use. A value of 120 means that month uses 20% more than the baseline daily demand, while 90 means 10% less. February is treated as 28 days to keep the model lightweight and consistent.
Rainwater harvesting inputs: what each input means
Roof catchment area should represent the roof area that actually drains to the rainwater collection system. In many cases this is the horizontal projected area connected to gutters feeding the tank, not every roof surface on the building. If only part of the roof is connected, use only that portion.
Area unit lets you enter the roof size in square feet or square meters. The rainwater simulation converts square meters to square feet automatically, so you do not need to do that conversion yourself.
Runoff efficiency is a decimal from 0 to 1. A value such as 0.85 means the system captures about 85% of the theoretical roof runoff. This is one of the most important rainwater harvesting inputs because it bundles several collection losses into a single planning factor.
Storage capacity is the usable tank volume in gallons. If part of the tank is not practically usable because of outlet placement, sediment, or operating constraints, use the usable volume rather than the nominal tank label.
Initial stored water is the amount of water in the tank at the start of the simulation year. This matters because a full tank entering a wet season behaves very differently from an empty tank entering the same season in a rainwater harvesting plan.
Monthly storage loss is a simple percentage that represents evaporation, leaks, and other standing losses. It is not a detailed physical evaporation model, but it gives you a practical way to test how sensitive the rainwater system is to ongoing losses.
Average daily demand should include only the uses you expect the rainwater system to serve. Many users model irrigation, toilet flushing, laundry, or other non-potable uses rather than total household demand.
Monthly demand adjustments are optional. They let you reflect seasonal irrigation, occupancy changes, or other predictable shifts in rainwater use. Enter exactly 12 comma-separated percentages from January through December.
Rainfall profile can be one of the built-in city examples or a custom set of 12 monthly rainfall values in inches. The built-in profiles are useful for quick rainwater comparisons, while custom rainfall is better when you have local climate normals or site records.
How to use this rainwater harvesting planner
To run the rainwater harvesting planner, start by entering the catchment and storage information. Then add your expected daily demand and, if needed, seasonal demand adjustments. Next, choose a rainfall profile. If you select a built-in city, the calculator uses the stored monthly rainfall values automatically. If you choose custom rainfall, paste 12 monthly totals in inches from January through December.
After you click Simulate Reliability, the results area shows a summary and a month-by-month table. The summary tells you how much water was captured over the year, how much demand was met, how often the system fully supplied a month, how much water overflowed, and how much shortage occurred. The monthly table then shows the detailed balance for each month so you can see the seasonal pattern rather than relying on a single annual number.
If you want to compare scenarios, change one variable at a time. For example, keep rainfall and demand fixed while increasing storage capacity, or keep storage fixed while testing a lower and higher runoff efficiency. That approach makes it much easier to see which rainwater harvesting choice actually improves reliability.
Worked rainwater harvesting example
Suppose you have a 2,000 square foot roof, a runoff efficiency of 0.85, a 5,000-gallon tank, 1,000 gallons of initial storage, a 3% monthly storage loss, and a daily demand of 120 gallons. If you pair those inputs with the Seattle rainfall profile, the tank will start with a useful reserve, refill in the wetter part of the year, and then draw down as rainfall drops through the drier months.
In that rainwater harvesting example, the annual captured volume may look comfortable on paper, but the more important question is whether the tank can bridge the dry months. If the table shows shortages late in the year, the system may be limited by storage carryover or by demand timing rather than by annual rainfall alone. If the table shows repeated overflow in wet months while shortages still appear later, that is usually a sign that additional storage could be more valuable than additional roof area.
This is why the calculator reports both monthly reliability and demand coverage. Monthly reliability is strict: a month counts as fully supplied only if the entire modeled demand is met. Demand coverage is broader: it measures the share of total annual demand that the system supplies. A rainwater harvesting system can have high annual coverage but still miss a few critical months, so both metrics matter.
Interpreting rainwater harvesting results
Annual rainfall captured is the total water collected from the roof after applying runoff efficiency. This tells you the scale of the rainwater resource, but not whether the timing works in your favor.
Total demand is the modeled annual water need based on daily demand and any seasonal adjustments. The percentage shown beside it is the share of that annual demand that the rainwater system actually supplied.
Monthly reliability is the percentage of months with no shortage at all. This is useful when you care about dependable rainwater service month by month.
Total overflow is water that could not be stored because the tank was already full. High overflow often suggests that the rainwater system has more collection potential than storage capacity during wet periods.
Total shortage is unmet demand. If shortage remains high even with a large tank, the system may be rainfall-limited or the demand may simply be too large for the available catchment.
Worst shortage month identifies the month with the largest unmet demand. That can help you focus on the season where design changes or backup supply matter most in the rainwater harvesting plan.
Rainwater harvesting assumptions and limitations
This rainwater harvesting planner is designed for planning-level analysis, not final engineering design. It treats each month as a single time step, so it does not model the exact timing of storms within a month. In reality, a month with the same total rainfall can behave very differently depending on whether rain arrives in one large event or several smaller events spread across the month.
The model also does not explicitly represent first-flush diversion, filtration losses, pump controls, treatment requirements, water quality constraints, or emergency reserve rules. Those details can matter in a real rainwater installation, especially for potable systems or regulated projects. The storage-loss input is likewise simplified; it is a practical planning factor rather than a full evaporation or leakage model.
Even with those limitations, the calculator is valuable because it highlights the main tradeoffs clearly. It helps answer whether your concept is broadly feasible, whether storage is likely to be undersized, whether demand is too ambitious for the local climate, and which assumptions deserve better field data before final design.
Rainwater harvesting planning background and practical guidance
For rainwater harvesting projects, the most useful planning question is not simply how much rain falls on the roof over a year. The better question is whether the system can store enough water at the right times to support the uses you care about. That is why reliability planning matters.
In many climates, rainfall and demand move in opposite directions. Wet months may arrive when outdoor demand is low, while dry months coincide with irrigation or higher occupancy. A tank that looks generous on paper may still empty during the season that matters most. Conversely, a site with modest annual rainfall can perform surprisingly well if demand is low and well matched to the rainy season. The calculator helps reveal those rainwater patterns quickly.
When choosing inputs, it is usually better to start with realistic, slightly conservative assumptions than with best-case values. If you are unsure about runoff efficiency, test a lower and higher case. If your demand is uncertain, model a core demand that must be served and a larger stretch demand that would be nice to serve. If you have local rainfall normals, compare them with the built-in profiles to see how sensitive the rainwater result is to climate assumptions.
The monthly table is especially useful for decision-making. It shows whether shortages are isolated or persistent, whether overflow is concentrated in a few wet months, and whether the tank ever truly cycles through a healthy refill-and-drawdown pattern. Those details can guide whether you should prioritize more storage, more catchment area, lower demand, or a supplemental supply connection.
For reporting or stakeholder discussions, it can help to summarize the rainwater system in plain language: how large the roof is, what efficiency was assumed, how much water the tank can hold, what demand was modeled, and which rainfall record was used. Because this calculator uses a transparent monthly balance, those assumptions are easy to document and easy for others to review.
Finally, remember that quantity is only one part of system design. If the project involves potable use, code compliance, treatment, backflow prevention, and maintenance planning become essential. This tool does not replace those steps. It gives you a clear first look at whether the water budget is plausible and where the main constraints are likely to appear.
