- 07961839260
Commercial roofs can provide a large catchment area for rainwater harvesting, but roof size alone does not make a building suitable. The project also needs enough non-potable demand, suitable drainage connections, manageable contamination risk, reliable overflow routes and a maintenance plan that keeps the roof and collection system working together.
This guide is for facilities managers, building owners, developers and project teams considering roof-fed rainwater harvesting on commercial or industrial buildings. It focuses on the roof and drainage interface rather than on detailed plumbing-system design. The aim is to help the client decide whether the roof is a suitable collection surface and what should be resolved before it is connected to a tank or non-potable water system.
The key principle is simple: a rainwater harvesting system should not be designed as a tank added at the bottom of an existing downpipe. The catchment, roof condition, drainage, water quality, storage, overflow and maintenance strategy need to work as one system.
This guide does not design the internal rainwater plumbing system, size tanks, specify pumps, certify water quality or determine whether harvested water is suitable for drinking. Those decisions require project-specific design and, where potable use is proposed, a much more stringent treatment and regulatory approach.
It also does not replace drainage calculations. A harvesting tank can contribute to surface-water management, but only where storage, demand and overflow have been designed so that the system performs as intended during rainfall events.
The national SuDS standards refer designers to BS EN 16941 for rainwater harvesting system design. This guide uses that as the design benchmark but does not reproduce the standard.
Pause if the roof has active leaks, deteriorated outlets, suspected structural problems, significant contamination from industrial processes, uncertain roof materials or drainage that already struggles during heavy rainfall.
Escalate where collected rainwater is proposed for uses involving higher human contact, where potable and non-potable systems could be confused, where industrial emissions may contaminate runoff or where the harvesting design materially changes the site’s existing drainage strategy.
The roof should be suitable as a collection surface before the project invests in storage and distribution equipment.
The national SuDS standards say rainwater harvesting is most useful where there is a demand for non-potable water and enough contributing catchment area to deliver worthwhile water savings. Industrial and commercial buildings are specifically identified as examples.
This means a very large roof is not automatically a good project. The site also needs regular demand that can use the harvested water.
Potential commercial non-potable uses can include:
The design should match expected collection with actual demand rather than assuming every litre that falls on the roof can usefully be stored.
A harvesting system relies on the roof to collect and convey water consistently. Before connection, check whether the roof is structurally and physically suitable to remain in service for the intended project life.
Inspect:
A commercial roof and drainage condition survey can establish whether defects should be corrected before harvesting infrastructure is added.
Rainwater is not automatically clean simply because it falls from the sky. The roof surface can add contamination before water reaches the gutter.
The Drinking Water Inspectorate highlights risks from overhanging trees, birds and roof-mounted features. On commercial buildings, the assessment should also consider industrial dust, exhausts, cooling-tower drift, chemical emissions, flues, rooftop maintenance activity and other local contamination sources.
Ask:
The intended use of the harvested water should determine how conservative the collection and treatment strategy needs to be.
Most commercial rainwater harvesting projects target non-potable uses. Local-authority guidance commonly identifies toilet flushing and irrigation as typical applications.
This guide assumes a non-potable system. Water intended for drinking or other human-consumption uses creates a different level of treatment, monitoring and regulatory control and should not be treated as a simple extension of a standard commercial harvesting system.
Clear system identification and separation from mains drinking-water supplies are therefore important project issues even though the detailed plumbing design sits outside this roof guide.
Before harvesting, map how water currently leaves the roof. Identify gutters, sumps, outlets, downpipes, siphonic drainage where present, overflows and emergency drainage routes.
The existing industrial flat roof drainage systems guide provides the wider context for understanding how primary and emergency drainage should work.
Do not change outlet connections without understanding whether the current system is gravity-based, siphonic, combined or split across several roof zones. A harvesting connection that interferes with the intended hydraulic behaviour can create a roof problem instead of a water-saving benefit.
Rainwater harvesting should not rely on the storage tank always having spare capacity. During prolonged rainfall, the tank may already be full.
The system therefore needs a defined overflow path that safely carries excess water when storage is unavailable. That overflow should integrate with the wider surface-water strategy rather than creating uncontrolled discharge around the building.
From a roofing perspective, the critical question is: if the tank is full or the harvesting system is isolated, can the roof still drain safely?
The answer should be yes.
The first rainfall after a dry period can wash accumulated dust, bird droppings and other debris from the roof. DWI guidance says first-flush diversion can be considered as a risk-control measure.
A first-flush device diverts an initial portion of runoff away from storage before cleaner subsequent water is collected. Whether this is suitable depends on the system and intended use.
First flush is not a substitute for keeping the roof and drainage system clean. If gutters, outlets and roofs are heavily contaminated, diverting only the first flow may not address the wider maintenance problem.
Filters are important because roof runoff can carry leaves, grit, moss, fragments of coating and other debris. But every filter adds a maintenance requirement.
Specify filters that can be reached safely, inspected and cleaned without dismantling difficult roof details or entering hazardous spaces.
Ask who will:
A system that works only while a difficult-to-access filter remains perfectly clean is not a robust FM solution.
Rainwater harvesting equipment should not make normal roof maintenance harder. Downpipe modifications, screens, collection boxes and filters should leave gutters and outlets accessible.
The site’s planned commercial roof maintenance support can provide the ongoing service route for roof and drainage inspection after the harvesting system is installed.
The facilities team should be able to inspect:
A large commercial roof may not be one uniform catchment. Different zones can have different contamination risks, roof materials or drainage arrangements.
It may be sensible to exclude some roof zones from harvesting, for example where:
The remaining lower-risk zones may still provide enough catchment area to make the project worthwhile.
If the roof is due for refurbishment, this can be a good time to plan harvesting because outlets, gutters and collection routes can be considered alongside the new roof design.
The project can then confirm:
Retrofitting harvesting after a drainage refurbishment is complete can be more difficult if the system was not designed with future collection in mind.
Rainwater harvesting can contribute to sustainable drainage because water stored and used on site reduces runoff leaving the development.
However, the national SuDS standards make an important distinction: storage has to be available when rainfall arrives. A tank used only occasionally may remain full and offer little stormwater benefit.
Where harvesting is being relied upon as part of the formal surface-water strategy, the system should be designed and modelled accordingly rather than assuming that any storage tank automatically counts as drainage attenuation.
A practical commercial assessment can score each roof zone against four questions:
Check condition, drainage, access and remaining service life.
Assess birds, trees, exhausts, industrial contamination and roof materials.
Protect primary drainage, emergency overflow and hydraulic function.
Filters, gutters, first-flush devices and storage interfaces all need accessible maintenance.
If a zone fails one of these tests, exclude it or investigate further rather than automatically connecting every available downpipe.
A commercial roof rarely stays unchanged for the full life of a rainwater harvesting system. New plant, vents, solar PV, coatings, penetrations, replacement rooflights or local repairs can all change the catchment condition or water-quality risk.
Whenever the roof changes, review whether the affected area should remain connected to the harvesting system. A new exhaust discharge near a collection zone may change contamination risk. A new coating may alter the runoff characteristics. A drainage alteration may move water from one zone into another.
Keep a simple change record showing the roof zone, date, work completed and whether the harvesting layout or maintenance plan was reviewed. This turns the system into a managed asset rather than a one-off sustainability installation.
Good maintenance planning asks what happens when a component fails. For each roof-side harvesting element, identify the likely failure and the safe fallback.
This failure-mode approach is especially valuable on large commercial roofs because a water-saving feature should never become a single point of failure for the roof drainage system.
Sizing the project from roof area alone. Water demand matters as much as collection potential.
Connecting every roof zone. Some areas may carry higher contamination risk.
Ignoring emergency overflow. The roof still needs to drain safely when storage is full.
Assuming harvested rainwater is clean. Roof surfaces introduce debris and contamination.
Making filters difficult to access. Poor maintainability eventually becomes poor performance.
Treating the tank as automatic SuDS attenuation. Stormwater benefit depends on available storage and system design.
Installing on a roof near the end of its service life. Future refurbishment can force collection pipework and equipment to be altered again.
The facilities plan should connect roof maintenance with harvesting-system maintenance. Cleaning gutters but ignoring the filter, or servicing the tank while outlets remain blocked, treats one system as two unrelated assets.
Record inspections of roof zones, gutters, outlets, first-flush devices, filters and overflow routes. Where water-quality monitoring is required for the intended use, keep those records with the system maintenance history.
Review the catchment after roof repairs, new plant, new flues, coatings or other changes that could alter runoff quality.
Start by confirming the building has a useful non-potable water demand. Then survey the roof and drainage system to identify suitable collection zones, contamination risks and existing maintenance issues.
Ask the rainwater-harvesting designer to coordinate with the roofing and drainage information rather than designing only from total roof area. The design should show collection zones, exclusions, filtration, first-flush strategy where used, storage, overflow and how the original roof drainage remains safe.
Before installation, agree who will inspect the roof-side components and how often they will be maintained. Make sure all collection and overflow components remain accessible.
If you need to assess whether a commercial roof is suitable for rainwater harvesting, send the roof and drainage details to Industrial Roofing Services to discuss the appropriate survey or maintenance route.
Commercial roofs can provide valuable catchment area for rainwater harvesting, but the project should begin with demand, roof condition and drainage rather than tank size.
The strongest scheme selects appropriate roof zones, controls contamination, protects primary and emergency drainage, provides maintainable filtration and keeps overflow performance clear when the storage tank is full.
Rainwater harvesting works best when the roof, drainage and water system are designed and maintained as one connected asset.
Yes. Commercial and industrial buildings are specifically recognised in national SuDS guidance as potential settings where roof catchment and non-potable demand can support rainwater harvesting.
Typical non-potable uses include toilet flushing and irrigation. Other commercial uses may be possible where the required water quality and system design support them.
No. Some roof zones may be unsuitable because of contamination risk, poor drainage or difficult maintenance access.
No. The roof still needs a safe drainage route when the tank is full, unavailable or isolated.
It is a method of diverting an initial portion of rainfall away from storage so some of the debris and contamination accumulated on the roof is not collected.
No. Its drainage benefit depends on whether storage capacity is available when rainfall occurs and whether the system is designed and modelled for that purpose.
If the roof is near the end of its service life or has drainage defects, coordinating refurbishment first can avoid later disruption to the harvesting system.
