Rainwater harvesting and whether it counts as attenuation

A rainwater harvesting tank holds water. An attenuation tank holds space. That difference is why lead local flood authorities usually decline to count harvesting storage towards the attenuation volume a scheme has to provide, and why a drainage strategy that quietly subtracts the tank volume from the required storage comes back with a holding objection.

The reasoning is simple once stated. Attenuation works only if the void exists at the moment the storm arrives. A harvesting tank is designed to be full, because full is what makes it useful.

What a harvesting system does in drainage terms

A conventional system takes roof runoff through a filter into a below-ground or internal tank, from which a pump supplies non-potable uses: cistern flushing, washing machines, external taps and irrigation. Mains top-up maintains supply in dry periods, protected by an air gap to prevent backflow into the supply under the water fittings regulations.

The drainage effect is real but small and unreliable. Over a year, a system sized to the building's demand will divert a meaningful volume of roof runoff away from the network. During the single critical storm event that the drainage design is checked against, it may divert nothing at all, because the tank was already full from the rain three days earlier.

Sizing under the rainwater harvesting code of practice is driven by the relationship between yield and demand, with the tank sized to ride through dry spells. That objective works directly against having spare volume for a storm.

Why regulators discount it

Three questions decide whether a drainage engineer will accept a storage credit, and a standard harvesting tank fails all three.

1. Can the void be guaranteed at the start of the design event? Not without a control system.
2. Does the system fail safe? A pump failure in a harvesting system leaves the tank full and the void gone, and nothing about that failure is visible from outside the building.
3. Will it still be working in 30 years? That is a maintenance and ownership question rather than an engineering one.

Approving authorities apply the same logic to any storage whose availability depends on an active system or on an occupant's behaviour. It is not scepticism about harvesting in particular, and the same objection is raised against storage that relies on a pumped outlet with no gravity fallback. Understanding what a consultee checks in drainage model output makes the reasoning easier to anticipate.

Designs that do earn a credit

The way to make harvesting count is to stop asking for a credit on the harvesting volume and provide a separate, dedicated one instead.

A dual-purpose tank splits the vessel. The lower portion is retention volume for reuse, always full. The upper portion is attenuation volume, normally empty, discharging through a flow control to the outfall. The two are separated by the outlet arrangement rather than by a valve, so the attenuation void is passive and cannot be lost through equipment failure. Only the upper portion is claimed in the calculation, and it is claimed on exactly the same basis as any other attenuation tank.

Real time control systems go further, using a weather forecast feed to release stored water ahead of a predicted storm, and they can be modelled to give a larger effective void. They also add a communications link, a control cabinet and a dependency on a service contract. Some authorities will accept them on a managed site with a facilities management team. Few will accept them on a housing scheme sold to individual owners, and that reluctance is reasonable.

The passive split tank is the answer that survives contact with a planning condition. It is less clever and more likely to be built as drawn.

Peak flow and volume are different requirements

The technical standards for sustainable drainage set separate requirements for peak flow control and for runoff volume, and harvesting sits differently against each.

Peak flow control asks for discharge during the design event to be limited to a stated rate. Harvesting contributes nothing dependable here, for the reasons above.

Volume control asks for the total runoff volume from a large event to be constrained, with the excess over the greenfield volume dealt with by infiltration, by long term storage or by reuse. Reuse is named in that list. Where infiltration is not possible, evidence that a proportion of the annual roof volume is used within the building is a legitimate part of the volume argument, and it is routinely left out of drainage strategies that could have used it.

Set out the two requirements separately in the Drainage Strategy and show which measure answers which. Strategies that blur them invite the objection that the applicant is double counting.

Water neutrality and demand reduction

The stronger case for harvesting is usually about water supply rather than drainage. In catchments subject to water neutrality requirements, a scheme has to show that it does not increase demand on the resource, and harvesting reduces potable demand directly.

It also counts in the water efficiency calculation under Part G of the Building Regulations, where an authority has applied the tighter optional requirement through a planning condition. Where both apply, a system that was marginal on cost for drainage reasons becomes easier to justify.

Where a Water Supply Assessment is required, present the harvesting yield as part of the demand case with the calculation method stated, and keep it out of the attenuation figures entirely. Separating the two arguments makes both stronger.

Maintenance and the abandonment problem

Systems fail quietly. A clogged filter, a failed pump, a disconnected control panel after an electrical fault: any of these leaves the building on mains top-up with nobody aware that the system has stopped contributing anything.

Where a drainage credit has been granted on the basis of the system working, that failure is a compliance issue as well as a waste. It is the reason authorities ask for a maintenance schedule, a named responsible party and a funding mechanism, and the reason conditions increasingly require a verification report on completion.

Answer it in the submission. Name who owns the system, how it is funded, what the inspection interval is, and what happens on failure. A management company with a sinking fund is an acceptable answer. "The homeowner" is not.

What to submit if you want the credit

• Continuous simulation modelling covering a long rainfall series, not a single design storm, showing tank behaviour with a realistic demand profile.
• The demand profile itself, with occupancy assumptions and the fittings served, stated as assumptions rather than as facts.
• A section through the tank showing the split between retention and attenuation volumes and the position of the flow control.
• The failure mode analysis: what the void is with the pump not running.
• The maintenance schedule, ownership and funding arrangement.
• A Sustainability Statement tying the water efficiency and drainage arguments together where local policy asks for both.

If that package looks disproportionate for the volume being claimed, it probably is. On most schemes the storage is better provided in permeable paving, in a below-ground crate under parking, or in a swale, with harvesting justified on water demand instead. That is not an argument against harvesting. It is an argument for claiming it under the right heading.

Enter your postcode on PlanScope to see which drainage and water documents a scheme is likely to need.

This is general guidance, not legal advice; check the position with your local planning authority or a qualified professional before relying on it. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.