Flood Risk and Drainage for Data Centre Planning Applications

A data centre flood risk assessment has to clear a higher bar than the industrial-shed template most schemes were still using a year ago. Since 17 August 2026 the National Planning Policy Framework has listed data centres as essential infrastructure. That one line changes the climate change allowance you design to, whether the Environment Agency has to be consulted, and whether an Exception Test applies at all. This guide sets out what an application in England has to submit, in the order a planning authority looks for it.

The reclassification is not a relaxation. A data centre in Flood Zone 3a that needed no Exception Test in July 2026 needs one now.

What a data centre planning application has to submit

Flood risk and drainage reach a data centre application through four documents. They are prepared in sequence, because each one depends on the last, and getting the order wrong means the work gets done twice.

1. A screening position. Whether Policy F4 requires a site-specific flood risk assessment at all, and which flood risk vulnerability class each part of the campus falls into.
2. A Sequential Test, where one is engaged. The argument that no reasonably available site sits in a lower risk area, tested against an area of search you have to justify.
3. The flood risk assessment itself, carrying the Exception Test where Annex F requires one, the climate change allowances, the design levels and the continuity position.
4. A drainage strategy showing compliance with the National Standards for Sustainable Drainage Systems, with a validation statement to match.

The difficulty is front-loaded. That first classification decision sets the allowance, the consultation route and the test regime for everything downstream, and it is the step the industry has been getting wrong: most of the data centre assessments we have seen this summer still classify the use as less vulnerable. In June that was defensible. It no longer is. A flood risk assessment for planning built on the right class from the start costs a fraction of one rewritten after an Environment Agency holding objection.

The four documents are not interchangeable, and a data centre almost always needs both the assessment and the strategy. Our guide to whether a scheme needs an FRA and a drainage strategy sets out where the line falls.

Which vulnerability class does a data centre fall into?

A data centre in England is essential infrastructure. Annex F, Table 2 of the Framework lists "Data Centres." as a standalone bullet in that class, alongside wind turbines, solar farms, hydrogen production, carbon capture, heat networks and electric vehicle charging stations. Before 17 August 2026 no classification named data centres at all. The sector defaulted to less vulnerable, reading across from the less vulnerable class's "general industry, storage and distribution".

Two features of the wording matter. The bullet carries no qualifier. The two entries above it are limited to transport infrastructure "which has to cross the area at risk" and utility infrastructure "which has to be located in a flood risk area for operational reasons", but the data centre entry has no locational-necessity test on its face. The Framework also nowhere defines a data centre, so edge facilities, telecoms exchanges with server halls and enterprise server rooms inside a B2 or B8 building all sit in uncertain territory. Both points are arguable, and neither has been tested.

What follows from the class is more demanding than the old default, in three specific ways. In Flood Zone 2 the Environment Agency now has to be consulted, where standing advice used to be enough. Across Flood Zones 2, 3a and 3b the climate change allowance steps up from the central to the higher central peak river flow figure. That higher figure applies to the assessment, to the design of safe access and escape routes, and to any compensatory floodplain storage. And in Flood Zone 3a an Exception Test is now required where less vulnerable development needed none.

The change bites hardest on work already in the system. Annex A of the Framework makes its policies material to decisions from the day of publication, so a scheme sitting with a planning authority on a "less vulnerable" assessment written in the spring is now, on its face, being assessed against the wrong class. We have covered the wider restructure in our breakdown of the August 2026 NPPF changes, and the classes themselves in our guide to the flood risk vulnerability classification.

One red line, several classes

A campus is rarely one land use. The notes to Annex F, Table 3 say that where a development contains different elements of vulnerability, the highest category applies "unless the development is considered in its component parts". That is the route most large schemes will want, because a visitor centre and a car park do not need designing to the standard the halls do.

The splitting is already happening. The flood risk assessment for the East Havering Data Centre Campus, prepared by Ramboll for the London Borough of Havering as local planning authority, divides the site three ways: general industry buildings as less vulnerable, the visitor centre and campus management as more vulnerable, and the electrical infrastructure as essential infrastructure. On-site substations answer to their network operator's own standards as well as to planning policy, and we have set that interaction out in our guide to flood risk assessments for electrical substations. The same component-splitting logic runs through our guide to flood risk and drainage for EV charging infrastructure.

A split has to be genuine, though. Independent access, independent escape and independent flood management are what make component parts separable. A shared service yard behind a single security perimeter does not.

Does the site need a flood risk assessment at all?

Policy F4 requires a site-specific assessment with every proposal in Flood Zones 2, 3a and 3b. In Flood Zone 1 it requires one where the site is a hectare or more, where the Environment Agency has identified critical drainage problems, or where a strategic flood risk assessment or the Flood Map for Planning shows the land at risk from any source, now or in future.

A hyperscale campus clears the first trigger on the second page of the site plan: the Foundry at Teesworks runs to 78.09 hectares and the East Havering campus to 218.8, and even modest urban infill schemes get there. Flood Zone 1 is not an exemption; it is a threshold question. Our guide to when a flood risk assessment is needed covers the triggers in full, and critical drainage areas explains the designation that catches sites the flood zones miss.

The third trigger is the one that surprises people. It reaches any site identified as at risk from any source, having lost the old qualifier about more vulnerable uses. In practice that means surface water and groundwater have to be assessed on a Flood Zone 1 site, and the published mapping will not do it for you, because the Flood Map for Planning covers rivers and the sea and carries no groundwater layer at all.

There is independent evidence that surface water is the binding constraint for this sector rather than a secondary worry. XDI's 2025 Global Data Centre Physical Climate Risk and Adaptation Report assessed 8,868 operational, under-construction and planned facilities worldwide, including 369 in England, the highest national total after the United States and China.

In Berkshire, the densest cluster outside London, XDI found 8.33 per cent of the 48 sites analysed already at high risk, with surface water flooding the driving hazard, and projected the risk of damage to more than double by the end of the century.

How large is a data centre's area of search?

The Sequential Test asks whether a reasonably available site exists in a lower risk area. Policy F5 caps the area it is applied to at "the anticipated catchment of the development in terms of its likely occupiers or users". For a data centre that catchment is the whole argument, because the technical envelope is far narrower than any settlement boundary.

• Grid capacity. A contracted connection at the right capacity is the binding constraint, and connection queues make the set of viable sites very small. The East Havering campus is built around 600 MVA contracted with UK Power Networks.
• Fibre and latency. Distance from an interconnection point is a real functional constraint for latency-sensitive workloads, and it is what produced the West London and Docklands clusters.
• Land assembly. A contiguous, flat, developable parcel of the right shape and ground conditions, at a scale very few sites can offer.
• Power and water availability. Locations where the grid and the water network can both take the load are treated as strategically important in their own right under the Framework's economic policies.

The constrained-search argument has been run and accepted in England, but not for flood risk.

At the Abbots Langley inquiry in 2024 (appeal reference APP/P1940/W/24/3346061) the appellant's data centre evidence argued that availability zone architecture limits sibling sites to a 7 to 10 kilometre fibre distance and a round-trip latency under 2 milliseconds. The Inspector accepted an 8 kilometre search radius as "robust for the purposes of identifying an area of search", but that was a Green Belt alternative-sites exercise on a Flood Zone 1 site, and it was not a Sequential Test.

The distinction matters, and so does how fragile the underlying proposition is. The council contested the figure at inquiry, and the Inspector noted the point had never been put to the appellant's witness. Amazon's own published guidance describes availability zones as sited "up to 60 miles (~100 km)" apart to prevent correlated failures. Treat the 8 kilometre radius as a useful planning precedent rather than a law of physics. An area-of-search case for a data centre in a flood zone is arguable and untested, and it will not carry itself. It needs the grid, fibre and land evidence assembled properly, which is what a Sequential and Exception Test report is for. Our explainer on the Sequential and Exception Tests covers how the test works generally, and the surface water sequential test exemption sets out the narrow route around it.

Where the Exception Test now bites

The Exception Test applies to essential infrastructure in Flood Zones 3a and 3b, and it runs to three limbs: wider sustainability benefits to the community that outweigh the flood risk, safety for the development's anticipated lifetime, and no increase in flood risk elsewhere, with a reduction where possible.

The first limb is the awkward one for a privately operated commercial building. Planning practice guidance leaves authorities to set their own criteria against their sustainability appraisal framework. It offers two examples: re-using brownfield land as part of a regeneration scheme, and an overall reduction in flood risk to the wider community. A data centre on a former power station or steelworks has a real case on the first, and a scheme funding flood risk management infrastructure has one on the second. Economic benefit alone is not the test, although the Framework's economic policies now direct substantial weight to commercial development reflecting AI Growth Zone proposals. Five zones are designated: Culham, the North East, North Wales, South Wales and Lanarkshire.

In Flood Zone 3b the position inverts. Less vulnerable development is refused outright in the functional floodplain. Essential infrastructure that passes the Exception Test can proceed, provided it is designed to remain operational and safe for users in a flood, results in no net loss of floodplain storage, and does not impede flows or increase flood risk elsewhere. That is a demanding specification for a building with the footprint of a hyperscale hall, but it is no longer a refusal in principle, which is the genuinely new part.

What a data centre flood risk assessment has to show

Beyond the contents of any competent assessment, six things are specific to this building type. A generic template will not produce them.

• A component-by-component vulnerability position, stating which parts of the campus sit in which Annex F class, and why any split is genuinely separable.
• One reconciled levels drawing across the halls, the substations, the generator and transformer compounds and the chiller yard, showing every design level against a single datum in metres above Ordnance Datum.
• An exceedance route that takes water away from electrical plant and cable entry pits, rather than simply off the site.
• The higher central climate change allowance, applied consistently to the assessment, the access and escape design and any compensatory storage.
• A stated development lifetime. Guidance gives non-residential development a starting point of at least 75 years and contemplates longer for major infrastructure. A data centre's real service life, and the practical impossibility of moving one, are the argument for the longer horizon. Make it explicitly, rather than defaulting to 75 years in silence.
• A continuity position, not an evacuation plan on its own.

Real schemes show what those numbers look like on paper. The outline parameters for the Foundry at Teesworks fix a minimum finished floor level of 5.03 metres above Ordnance Datum against a maximum development height of 46.2 metres. The Thurrock scheme at Purfleet-on-Thames sets a maximum finished floor level of 17.5 metres for most of a 52-hectare site, with 13.4 metres at the security entrance, and keeps its on-site lake as stormwater attenuation, that lake sitting in Flood Zone 3 while most of the site sits in Flood Zone 1.

Where published mapping is too coarse to support levels at that precision, flood modelling produces site-specific levels, and a topographical survey pins existing ground to the same datum. Our guide to Environment Agency flood data products covers what modelled data the Agency will release, and when.

Staying operational, not evacuating

Policy F7 is written for buildings full of people. It asks for safe access and escape routes as part of an agreed emergency plan, and for development flood resistant and resilient enough to be "quickly brought back into use without significant refurbishment". A data centre inverts the first half of that and sharpens the second.

The building is lightly staffed and cannot be evacuated in the sense the policy imagines, because what has to survive the flood is the service rather than simply the occupants. Annex F is explicit for this class.

Continuity of operation is the test, and an evacuation plan on its own does not answer it. That reframes what the assessment has to demonstrate. Access matters for fuel deliveries and engineers during an event, as well as for getting people out. Loss of grid supply, telecommunications, water or road access can stop the facility while the building itself stays dry, so those dependencies belong in the assessment. The resilience limb is the hard one, because electrical plant that has been inundated is generally replaced rather than dried out and restarted, and "quickly brought back into use" is a high bar for a flooded switchroom.

Uptime Institute's annual outage analysis for 2026 records that 57 per cent of surveyed operators said their most recent major outage cost more than 100,000 US dollars, and for the second year running one in five put it above a million.

That is why authorities take the point seriously. Our explainer on residual flood risk covers how the hazard bands and the design event are set, and property flood resilience covers the measures themselves. Where a facility is already built and the question is operational rather than a matter of consent, a flood risk assessment for business continuity answers it directly.

Drainage on a site that is almost entirely impermeable

Policy F8 requires sustainable drainage on any proposal that could affect drainage on or around the site. It has to be designed in accordance with the National Standards for Sustainable Drainage Systems published in June 2025, with maintenance arrangements for the development's anticipated lifetime and regard to the lead local flood authority's advice on major development. Annex C adds a validation requirement: a statement setting out how the national standards have been achieved.

That lands awkwardly on a building type that covers most of its plot. A combined flood risk and drainage document for Plot 3 Maylands Avenue in Hemel Hempstead, prepared for Amazon Data Services UK in February 2026, records the proposed impervious area as 4,670 square metres of a 6,044 square metre site, or 77 per cent against 11.2 per cent existing. The parameters for the Foundry at Teesworks allow 464,515 square metres of floorspace on 78.09 hectares. Roof, service yard, perimeter road, generator compound, transformer compound, chiller yard, parking and the security standoff between them account for nearly everything.

A hyperscale scheme takes a site from roughly one-tenth impermeable to roughly three-quarters impermeable, and the drainage strategy has to absorb the whole of that difference.

The awkward part is that the obvious answer is being ruled out. Roof level is where the area is, but on a data centre that roof is claimed by chillers, generators, exhaust flues and the screening that hides them. A site-specific SuDS suitability appraisal for the Linmere Island scheme in Houghton Regis records, for each technique in turn, that "due to plant operations, blue roof options have not been considered feasible" and that "due to plant operations, green roof options have not been considered feasible". Plant operations is the entire stated reason offered in both cases, and we would expect a lead local flood authority to test that assertion rather than accept it, particularly where local policy pushes for roof-level storage.

What is left has to work harder. Discharge rates are set tightly: the Linmere scheme restricts surface water to 3 l/s/ha of impermeable surface, giving 15 l/s in total. Below-ground attenuation, permeable surfacing on yards and parking where loading allows, and basin or pond storage in the landscape margin carry the volume. The discharge hierarchy still has to be worked through in order: rainwater re-use first, then infiltration, then a surface water body, then a surface water sewer, and a combined sewer only as a last resort. Our guide to the 2025 national SuDS standards sets out the seven standards in full, and permeable paving covers where it works and where it does not.

Water quality is the strand most often under-scoped, and it is where we would expect the sharpest questions. A data centre yard is a heavy goods vehicle service area with a bulk fuel installation attached. The environmental permit application for the Didcot North campus describes roughly 2,400 cubic metres of diesel or HVO stored at any one time, across 129 generators. Bunding, full-retention separators on the yard and generator compound, containment for fire-fighting water, and an impermeable lining where a SuDS feature sits over a sensitive aquifer all follow from that, and the CIRIA SuDS Manual simple index approach is how the resulting treatment train gets justified. Our explainers on the four pillars of SuDS and first flush cover the water quality reasoning.

Cooling water belongs in the same conversation. Where evaporative cooling is proposed, the potable demand, the blowdown discharge and any trade effluent consent need resolving with the water company early, and in a water neutrality or seriously water-stressed catchment that conversation can shape the whole scheme. Both strands run through a surface water drainage strategy and, for the welfare and process flows, a foul drainage strategy.

The consents planning permission does not give you

A resolution to grant is not the end of it. Several consents run alongside or after the permission, and they get missed at programme stage more often than anything else on this list.

Drainage is also where the conditions land. At Manor Farm in Slough, where the Secretary of State allowed an appeal for a data centre and battery storage scheme in June 2026, the lead local flood authority raised no objection to the drainage strategy subject to a suitably worded condition, which is both the normal outcome and the normal sequel. Our guides to discharging drainage conditions, the role of the lead local flood authority and internal drainage boards cover who you are dealing with at each stage, and what drainage information planning permission requires covers the submission itself.

One route deserves a mention, because it changes the forum rather than the tests. Since 8 January 2026 data centres have been a prescribed category under the Planning Act 2008, so a developer may request a direction from the Secretary of State bringing a project into the nationally significant infrastructure regime. It is an opt-in with no capacity threshold, not an automatic classification, and no national policy statement for data centres has been published yet.

What goes wrong

The failure modes are consistent, and every one of them is avoidable at scoping.

1. The classification is carried over from an older report. A "less vulnerable" position written before 17 August 2026 is now wrong on its face, and in Flood Zone 3a it means an Exception Test is missing entirely.
2. The central climate change allowance is used instead of the higher central figure, so the modelled levels, the access design and any compensatory storage are all set too low.
3. Flood Zone 1 is treated as an exemption. Over a hectare, or with any identified surface water or groundwater risk, Policy F4 still requires a site-specific assessment.
4. The area of search is asserted rather than evidenced. Grid, fibre and land constraints have to be documented before an Inspector will narrow a Sequential Test around them.
5. Blue and green roofs are ruled out in a single sentence. Where roof-level storage is discounted on operational grounds, the reasoning has to survive a lead local flood authority reading it closely.
6. Safe access is designed for evacuation only, when the policy for this class asks the development to stay operational.

Two of those end in an objection rather than a refusal, which is worth knowing. Our guides to resolving an Environment Agency objection and an LLFA objection set out how each one gets lifted. And because new evidence is largely shut out at appeal, the assessment has to be right at submission.

Getting it right at the first attempt

A data centre flood risk assessment is a policy problem before it is a hydraulic one. The class the scheme sits in decides the allowance, the consultation route and the tests, and every level and volume downstream follows from it. Sites in the established clusters bring their own local constraints: surface water dominance in Hillingdon, water scarcity and internal drainage board consents across Cambridgeshire, tidal levels and climate uplift on the River Tees.

Unda prepares flood risk assessments, Sequential and Exception Test reports and drainage strategies for commercial and infrastructure schemes across England and Wales. If you are scoping a data centre application, or holding one that was assessed on the old classification, talk to us about a flood risk assessment for planning. Call +44 (0) 1293 214444, email enquiries@unda.co.uk, and we will send a tailored, no-obligation quote within 60 minutes on a working day.

Frequently asked questions