MetandumFREE TOOLS. NO SUBSCRIPTION.Find a calculator My projects
COMPARE THE SUPPLIED SCENARIOS

Rainfall event volume does not size a gutter or overflow.

Publication and review

Author
Metandum Team

14 years of experience in digital web projects.

Reviewer
Metandum Team

14 years of experience in digital web projects.

Published
Last reviewed
Last updated

An event total is a volume budget

Rainwater collected during an event can be estimated as a volume from the horizontal catchment area and rainfall depth. A capture share and diversion quantity then reduce the modeled amount before it is compared with available storage. This helps answer how much water a supplied scenario could retain in a tank with known current contents and capacity. The result describes an event total. It does not give the peak rate of flow through a gutter, downpipe, overflow or drain, which depends on timing and hydraulic conditions. Keep the volume budget separate from any design question about how quickly water must move through a system. The calculation starts after the relevant event depth has been supplied for planning.

Enter the supplied catchment facts

Use the plan area that drains to the collection point, the rainfall depth selected for the scenario, the capture percentage, any event diversion volume, the usable tank capacity and its current stored volume. Rainfall depth must use a length unit compatible with the area so their product forms a volume. The calculator treats the entered values as scenario inputs; it does not fetch a forecast or estimate a site’s capture efficiency. If the area is sloped, the tool’s stated assumption uses horizontal catchment area. Roof projections, connected sections and disconnected drains should be represented according to the actual collection plan rather than combined just because they occupy the same property. Mark which surfaces connect to the tank before adding their plan areas.

Trace the guide’s storage example

The example uses a 100 m² catchment with an entered 10 mm event depth, giving 1 m³ of rain over the plan area. At an 80 percent capture share, then subtracting a 0.1 m³ diversion, the modeled water after diversion is 0.7 m³. The tank has 1 m³ usable capacity and already contains 0.5 m³, leaving 0.5 m³ of available space. The calculator therefore reports 0.5 m³ retained and 0.2 m³ beyond available storage. Each of those values appears in the engine result lines, so the check records the gross rain, post-diversion amount and excess alongside the main retained output. The guide values illustrate the sequence rather than define a design storm.

Distinguish capacity from free space

Tank capacity is the usable total volume entered for the scenario. Current volume already occupies part of that amount, so only the remaining capacity can accept additional water. If current contents equal capacity, no additional water is retained. An entry above capacity is rejected. The result is bounded by free space after capture and diversion are applied. In a second illustrative scenario with the same event inputs but an empty 1 m³ tank, all 0.7 m³ after diversion fits, leaving no modeled overflow. A tank’s labeled volume may differ from usable operating capacity because of a reserve, air gap, internal fittings or installation constraints. Enter the relevant capacity and record its source; the calculator does not select safe freeboard.

Keep rainfall depth and flow separate

Multiplying catchment area by event depth estimates a total water volume over the event. A flow rate describes volume per unit of time and requires information about how quickly runoff arrives, along with the drainage path and its restrictions. The rainwater budget has no duration or time series input, so it cannot size a gutter or overflow. Two storms with the same total depth can deliver water at different rates. Any capacity assessment needs the applicable rainfall and site design method, plus the actual product and installation data. Do not convert the retained volume into a pipe size by assuming the event arrives uniformly unless a separate method supplies that assumption. A separate hydraulic review must address peak inflow and discharge capacity.

Interpret diversion as an entered amount

The diversion field represents a volume removed from the modeled event before storage is considered. It can represent a scenario quantity that has already been specified, such as a planned first-flush diversion, but the tool does not decide what diversion is suitable or model how a device behaves. If the diversion exceeds the water captured in the event, the amount after diversion cannot fall below zero. This lower bound prevents a negative retained result. Record how the diversion value was chosen, its units and whether it applies once per event. Do not enter a flow rate in that field, since a rate needs a time interval before it can be compared with a volume. Keep device operation details with the supplier specification.

Use the overflow line carefully

The volume beyond available storage is a geometric scenario result. It indicates that the modeled event amount is larger than the empty space entered in the tank. It does not identify where that water goes or whether an overflow route can carry it without damage. The vertical-tank companion estimates cylindrical liquid height and geometric spare volume from internal dimensions and known liquid volumes. That model also does not certify safe fill levels or hydraulic performance. Keep drainage routing, overflow discharge, foundation loads and water quality within the appropriate project review. A numeric exceedance can support a planning conversation, but it is not a substitute for checking the actual storage and drainage arrangement. Follow the selected tank maker’s limits when setting operating levels.

Save the event assumptions together

Retain the catchment plan area, rainfall depth, capture share, diversion, usable capacity and current volume with the estimate. If any assumption changes, create a new scenario instead of overwriting the only record. A different tank fill level changes available space, while a change in catchment connections changes gross event volume. Keep the result labeled as event storage arithmetic, and note any overflow amount separately. Product instructions and local drainage requirements may apply beyond these calculations. The tool uses user-supplied geometry and storage values; it does not predict weather, verify a roof connection, assess water quality or approve a drainage design. Those limits define what the result can tell you. Retain the date and source of rainfall data with any scenario comparison.

Questions about this guide

What does the example predict for a half-full 1 m³ tank?

The 100 m² catchment and 10 mm event produce 1 m³ gross rain; 80% capture less a 0.1 m³ diversion leaves 0.7 m³. With 0.5 m³ already stored, only 0.5 m³ fits, so the engine reports 0.5 m³ retained and 0.2 m³ beyond the available space.

Why is the empty-tank result different with the same event inputs?

An empty 1 m³ tank has more free space than the half-full one. The same 0.7 m³ after capture and diversion fits entirely, leaving 0.3 m³ capacity and no modeled excess.

Can event volume determine a gutter or overflow flow rate?

No. The tool has no event duration or runoff time series, so it estimates a total volume rather than peak volume per unit time. Hydraulic sizing needs a separate method and site-specific drainage inputs.

What does the overflow result say about where water will go?

It reports modeled volume beyond the entered free storage; it does not identify a route or establish whether that route can carry the water safely. Keep tank capacity assumptions separate from overflow and drainage review.

Use the matching calculator

Updated . Reviewed . Methods and scope.

Related decisions

Connected work guides and comparisons

Browse all work types

Collect your material inputs

Browse material preparation sheets

Evaluate your own supplied alternatives

Browse quantity scenarios