Requesting modelled flood level data and reading it

A flood zone tells you how likely flooding is. It does not tell you how deep the water would be, how fast it would arrive, or what level to build your floor at. For that you need modelled output, and an Environment Agency modelled flood level request is how most self-builders get it. The request is free, it is made through the Environment Agency's flood risk data service, and it takes long enough that it should be the first thing you do rather than the last.

Probability, not depth

The Flood Map for Planning puts a site in Flood Zone 1, 2 or 3 based on annual probability of flooding from rivers and the sea, ignoring the presence of defences. Zone 1 is land with less than a 1 in 1,000 annual probability. Zone 2 is between 1 in 100 and 1 in 1,000 for rivers. Zone 3 is 1 in 100 or greater for rivers, with the functional floodplain, Zone 3b, defined by the local planning authority.

Those categories drive the policy questions. They decide whether the sequential test applies, whether the exception test is engaged, and which uses are compatible with the zone. None of them tell you anything about depth or level.

So an assessment built only on the published map can state the zone and then has nothing to say about safety of occupants, floor levels or residual risk. That is the gap the modelled data fills, and it is the gap a case officer or the Environment Agency will find.

What a detailed data request returns

The content varies with what has been modelled in your catchment, which is the first thing to understand. Where a detailed hydraulic model exists, a request will usually produce modelled flood levels for a range of annual exceedance probabilities, often including the 1 in 100 and the 1 in 1,000 events and the corresponding levels with climate change allowances applied. You should also receive flood extents as spatial data, information on any defences and their standard of protection, historic flood outlines where they exist, and metadata describing the model.

Where no detailed model covers the reach, you may receive national generalised modelling only, or nothing beyond the published extents. That answer is itself useful, because it tells you a site specific hydraulic assessment will be needed and that a consultant will have to build or obtain a model.

Ask for the metadata explicitly. A level without the model name, the model date and the node or cross-section it relates to is close to useless when a reviewer queries it.

Reading levels in metres above Ordnance Datum

Modelled levels come in metres above Ordnance Datum, written mAOD, referenced to the Newlyn datum. A level of 12.46 mAOD means nothing on its own. It means something once you know the ground level at your plot in the same datum.

That is the step people skip. A GPS reading from a phone, a spot height scaled off a drawing, or a level taken from a site benchmark of unknown origin cannot be compared with a modelled level. The comparison needs a topographic survey tied to Ordnance Datum, which is ordinary surveying work and not expensive relative to the cost of getting the floor level wrong.

Watch the node location too. Modelled levels are reported at model cross-sections or grid cells, and the nearest node may be 80 metres upstream of your plot on a reach with a falling water surface. Interpolating between nodes is legitimate and should be shown, not assumed.

Model confidence, extents and the limits of the output

Every data pack comes with caveats, and they are there for a reason. Models are built for a purpose, usually strategic flood mapping rather than the design of a single plot, and their resolution, structure representation and boundary conditions reflect that purpose.

Three limitations recur. Defence breach and overtopping scenarios are often not included, so a defended site can appear dry in the output while carrying real residual risk. Culverts and bridges may be represented simply, which matters on small urban watercourses where a blockage changes everything, a point developed in modelling a partially blocked flow control. And surface water flooding, which causes a great deal of property damage, is mapped separately and is not part of a river modelling pack at all.

Read the confidence statement before you quote a number. Where it says the model is unsuitable for property level assessment, saying so in your Flood Risk Assessment is far better than quoting the level as though it were survey data.

Matching the data to your site

The sequence that works is short.

1. Confirm the flood zone and the source of risk from the published map, and record the date you checked it.
2. Request detailed flood risk data from the Environment Agency, giving a site plan with a red line boundary and a grid reference.
3. Commission a topographic survey tied to Ordnance Datum, covering the plot and the ground between the plot and the watercourse.
4. Plot the modelled levels against surveyed ground levels on a section as well as on a plan.
5. Identify the depth and the hazard at the building footprint and on the access route.
6. Only then decide on levels, resistance measures and the access strategy.

Step four is where most of the thinking happens. A plan shows you whether you are in the extent. A section shows you by how much, which is the question the Environment Agency actually asks.

Lead times and the programme

Treat the request as a long lead item. Responses are not immediate, the service standard changes, and a request that comes back needing clarification can add weeks. Check the current turnaround published by the Environment Agency and build it into the programme before you fix a planning submission date.

There is a sequencing point that costs people money. The sequential test is a policy test about whether the development should be in that location at all, and it sits logically before the detailed level work, as the sequential test for flood risk sets out. Commissioning hydraulic modelling for a site that cannot pass the sequential test is wasted expenditure. Do the policy test first on the published zones, then spend money on levels.

Drainage design runs on a separate track and needs rainfall rather than river data, which is a different dataset and a different request, covered in which rainfall dataset to cite in a drainage calculation. On sloping ground the overland flow question arrives alongside it, as managing run-off on a steeply sloping site describes.

Setting a finished floor level from the output

The design level is normally derived from the 1 in 100 annual probability river level with the appropriate climate change allowance applied over the lifetime of the development, plus a freeboard allowance. The freeboard figure is not set nationally. Authorities and the Environment Agency commonly look for 300 mm, and some ask for more where the modelling is uncertain or the hazard is high, so agree the figure in writing at pre-application stage rather than discovering it on a consultation response.

Then show the arithmetic. State the modelled level, the node, the allowance applied and the resulting design level, each on its own line, with the surveyed existing ground level alongside. A reviewer who can follow four numbers will not ask for the model.

Where levels cannot be raised, because of access, drainage outfall or the character of the street, the assessment moves to flood resistant construction, safe refuge and an evacuation route, and the case becomes harder. Say so plainly rather than presenting a raised threshold that nobody can reach from the pavement.

This is general guidance, not legal advice. Flood risk assessment for anything beyond a straightforward site is specialist work and councils normally expect a suitably qualified author. 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. For specialist technical reports, qualified professional input may be required. Enter your postcode on PlanScope to see whether your site needs a flood risk assessment.