A planning application can fail on flood risk evidence even where the proposed building is outside the mapped floodplain. A credible flood risk assessment example shows how the development changes flood pathways, surface-water runoff, finished levels, safe access and the resilience of the completed asset. It is not simply a map extract with a drainage drawing attached.
For construction, infrastructure and property teams, the assessment must provide a clear, technically defensible case for the Local Planning Authority, Lead Local Flood Authority and, where applicable, the Environment Agency. The level of detail should be proportionate to the site and proposal, but it must identify residual risk as well as the headline flood zone.
A flood risk assessment example: an employment development
Consider a proposed 3,200 m² light-industrial unit with associated parking, access roads and service yard on a previously developed site in England. The site sits in Flood Zone 1 for fluvial and tidal flooding, but the Environment Agency surface-water mapping identifies an overland flow route along the eastern boundary. Historic records also indicate that the adjoining highway has ponded during intense rainfall.
The initial assumption that the site is “low risk” would be incomplete. The development introduces new impermeable area, potentially displaces shallow surface-water flow and could direct runoff towards neighbouring premises unless its drainage strategy is properly designed.
The assessment would first define the proposal, its vulnerability classification and the planning context. For this type of commercial development, the report would normally address the National Planning Policy Framework flood-risk requirements, planning practice guidance, local policy, the authority’s strategic flood risk assessment, and the LLFA’s published drainage standards. Site-specific policy requirements can vary considerably, particularly around climate-change allowances, discharge rates and SuDS adoption.
Evidence reviewed
A proportionate desktop review would cover Flood Map for Planning, surface-water flood mapping, reservoir inundation mapping, historic flood records, ordinary watercourse and main-river data, topographical survey information, geology, groundwater susceptibility and sewer records where available. A utilities search and drainage survey may also be needed to establish the capacity, ownership and condition of existing assets.
For this example, a detailed topographical survey confirms that levels fall from west to east, towards the mapped flow route. The existing site drains via gullies connected to a public surface-water sewer. CCTV findings identify localised defects in the private drainage, while infiltration testing records slow percolation in the made ground. This means infiltration-led SuDS are unlikely to be the primary drainage solution, although limited landscaped infiltration may still be feasible if testing supports it.
The key finding is that flood risk is predominantly from intense rainfall and overland flow, rather than river flooding. That finding directly informs the layout, finished floor levels and drainage design.
How the risk is assessed
A useful flood risk assessment separates the source of flooding from the consequence for people, property and operations. It should not treat every mapped area as an automatic development constraint, nor dismiss mapping without site evidence.
In the worked example, the assessment considers four connected questions: can water reach the development; what depth, velocity and duration could occur; would the proposal increase risk elsewhere; and can occupants access and leave the site safely during an event?
The project team commissions hydraulic modelling or obtains model outputs where the available mapping is too coarse to answer those questions. For a modest site, a carefully interpreted topographical survey and drainage catchment analysis may be sufficient. For sites near watercourses, in functional floodplain, or affected by substantial surface-water flow routes, more detailed modelling is commonly required.
| Assessment area | Example finding | Design response | |—|—|—| | Fluvial and tidal flooding | Flood Zone 1, with no direct river pathway | Record low probability and retain evidence base | | Surface-water flooding | Shallow flow crosses the eastern edge in extreme rainfall | Keep built development outside the flow route | | Sewer flooding | Existing network capacity uncertain | Restrict discharge and provide on-site attenuation | | Groundwater | Low to moderate susceptibility | Confirm through ground investigation where relevant | | Off-site effects | Raised levels could divert water towards a neighbour | Maintain exceedance route and avoid obstruction |
Climate change must be incorporated into the drainage and flood-risk analysis using the applicable current allowances and guidance. The correct allowance depends on the flood source, development type, vulnerability and design life. Applying a generic percentage without explaining its basis is a common weakness in planning submissions.
Mitigation measures in the worked example
The preferred layout places the industrial unit and electrical plant outside the identified overland flow corridor. Rather than filling the entire eastern edge to create a level platform, the design retains a landscaped conveyance route that carries exceedance flows through the site and away from buildings.
Finished floor levels are set above the modelled or mapped flood level with an appropriate freeboard, subject to the agreed evidence and planning authority requirements. External levels are graded so that runoff does not pond against roller shutters, personnel doors or substations. Thresholds, loading areas and ramp details require coordination with the architect and civil engineer: a high floor level alone does not manage risk if the access route creates a low point at the building entrance.
The drainage strategy follows the SuDS hierarchy. Because infiltration is constrained, runoff is controlled through permeable paving in parking areas, rain gardens where ground conditions permit, oversized pipes or cellular attenuation, flow control and a restricted discharge to the surface-water sewer. The proposed discharge rate is agreed against the receiving network constraints and LLFA expectations, rather than selected solely because it is convenient for the design.
An exceedance plan is essential. It identifies where water will travel when the drainage system is overwhelmed or blocked, ensuring flows are directed away from buildings and do not create a new hazard at site entrances, neighbouring land or the public highway. This is particularly relevant for commercial sites with frequent vehicle movements, stored materials and electrical infrastructure.
Where residual risk remains, the assessment may specify flood-resilient measures. These could include locating switchgear above predicted flood levels, using water-resistant finishes at lower levels, installing non-return valves where justified, and preparing an operational flood response procedure. Such measures support resilience, but they do not compensate for poor site layout or inadequate drainage capacity.
What the report should demonstrate to planning authorities
A planning-stage flood risk assessment is not a drainage calculation package, and a drainage strategy is not a substitute for flood-risk analysis. They must, however, be consistent. If the drainage drawing shows a discharge point, attenuation volume or finished level that differs from the FRA, consultees will reasonably question the reliability of both documents.
For this example, the report should demonstrate that the development is appropriate in its flood-risk setting; it will remain safe for its intended lifetime; it does not increase flood risk elsewhere; and, where possible, it provides a betterment over the existing hardstanding condition. It should also state the limits of the assessment, including any outstanding surveys, third-party asset information or modelling assumptions.
The sequential approach should be addressed at the correct level. In many cases, site selection is considered through the local plan allocation or application site-selection process, while the site-specific FRA explains how risk is managed within the proposed red line boundary. Where the Sequential Test or Exception Test is required, it needs clear evidence and cannot be resolved through drainage mitigation alone.
Common gaps that delay approval
Planning delays often arise because the assessment has relied only on national mapping, ignored drainage exceedance, or assumed that a Flood Zone 1 location removes the need for surface-water analysis. Other frequent issues include unsupported finished floor levels, absent infiltration testing, no maintenance responsibility for SuDS, and a drainage outfall that has not been evidenced as deliverable.
For operational sites, another gap is the lack of consideration for business continuity. A distribution depot may tolerate shallow flooding in part of a car park but not at a transformer compound, fuel store, control room or emergency access route. The risk assessment should reflect the actual operational consequences, including pollution pathways where stored substances, oils or chemicals are present.
Turning assessment findings into buildable controls
The most effective FRA is carried into detailed design, construction planning and handover. Its controls should appear in the civil drawings, specification, drainage calculations, construction environmental management arrangements and maintenance documentation. If levels or drainage routes change during value engineering, the flood-risk implications should be reassessed before works proceed.
For the employment scheme in this example, the practical outcome is a development that preserves a surface-water route, stores runoff on site, restricts discharge, protects critical equipment and identifies how the drainage features will be inspected and maintained. That is the standard of evidence that supports planning compliance while also reducing avoidable disruption after occupation.
A flood risk assessment should give the project team decisions they can build, operate and defend – not merely a document submitted to obtain consent.

