EA River Modelling Technical Standards (2026): What Flood Risk Assessments Must Demonstrate

What the EA's river modelling standards cover

The river modelling technical standards and assessment are guidance for the whole flood risk management industry on how to build and review hydraulic models, and how to provide evidence for flood risk management decisions. First published in 2021, they were last updated on 8 May 2026. They are built around a simple idea: model the flooding using the source, pathway and receptor concept, then document it well enough that someone else can trust the result.

In practice that means the standards span four things: how you estimate flood flows (the source), how you represent channels, floodplains and pipe networks (the pathway), how you represent buildings and infrastructure (the receptor), and how you record all of it. The EA also publishes an Excel-based fluvial model assessment tool that lets a reviewer gauge a model's quality without running a full technical review, so weak models are easier to spot than they used to be.

1D, 2D and linked models: choosing the right approach

Different sites need different approaches: 1D models for in-channel flow, 2D models for how water spreads across a floodplain, and linked 1D-2D models where both matter. Common industry packages include Flood Modeller, TUFLOW and HEC-RAS, and our guide to flood modelling tools and techniques covers how they differ. The important point is that the EA standards are deliberately package-agnostic: the EA removed software-specific guidance back in 2023, and now asks only that whatever you use is fit for the question and properly verified. The EA's own benchmarking of hydraulic modelling software tests packages against best practice, but it does not crown a winner. Choosing the wrong dimensionality for the site is a far more common failing than choosing the wrong brand.

What a detailed FRA has to demonstrate

For a Level 2 or Level 3 FRA, the practical implications are consistent. Justify the modelling approach against the site and the question. Calibrate and verify against observed data where any exists. Run and report sensitivity tests on roughness, inflows and climate-change allowances. And document all of it, in a Model User Report, so the EA reviewer can follow the logic rather than take it on trust. The EA's own guidance on using modelling for flood risk assessments makes the same point from the reviewer's side.

Input data is half the battle. A model is only as good as the ground it sits on, which is why LiDAR and terrain data, GIS and, on sensitive sites, a proper topographical survey matter so much. Thin or mismatched input data is one of the quickest ways to lose a reviewer's confidence, and it is usually cheaper to fix at the start than after a model has been built. This is one of the clearest places where expertise in an FRA earns its keep.

Where modelling meets planning policy

Modelling does not sit apart from policy. The outputs feed straight into how a site sits against the flood zones, whether it can pass the Sequential and Exception Tests, and how safe-for-its-lifetime is demonstrated. That link has tightened since the September 2025 PPG update and the May 2026 Flood Map for Planning changes, both of which lean harder on modelled surface-water and climate-change data. A model that is technically sound but presented without that policy thread tends to generate more questions, not fewer.

The parallel coastal modelling standards

Alongside the river standards, the EA now maintains separate coastal modelling standards for open-coast and tidal modelling, and the 8 May 2026 update to the river page added the link to them. Most of Unda's work is inland, but for estuarine or coastal-fringe sites the same principles carry over: a fit-for-purpose method, verification, and documented evidence.

Common reasons a model gets sent back

Across the FRAs we see, the modelling problems that draw EA questions are rarely exotic. The wrong dimensionality for the site is common, as is a model run without reported sensitivity testing, so the reviewer cannot tell how much weight the result can bear. A missing or thin Model User Report is another, because the reviewer cannot reconstruct what was done. And climate-change allowances that are out of date with current EA guidance will undo an otherwise good model. None of these are hard to avoid, but all of them cost time once an application has stalled.

How Unda can help

Unda's flood modelling team builds and reviews hydraulic models to the EA's standards, and presents the evidence in a form that holds up under EA scrutiny. If your scheme depends on a model result, whether that is a fresh model, a review of someone else's, or a defence of a result the EA has questioned, our flood modelling service is the place to start. Get in touch with the site details and what stage you are at, and we will tell you what the modelling needs to show.