Flood Evacuation Plan Planning: UK Developer's Guide

Flood Evacuation Plan Planning: UK Developer’s Guide

Flood evacuation plan on table with safety gear

If your development sits in Flood Zone 2, 3, or 3b, or involves a vulnerable use on a surface-water-risk site, you almost certainly need a Flood Evacuation Plan (FEP) alongside your planning application. The Gov is clear: failing to submit a satisfactory plan can result in outright refusal.

A draft FEP submitted with your application needs to include, at minimum:

A site plan showing evacuation routes and safe refuge locations
Identified flood triggers tied to Environment Agency warning levels, with realistic lead times
Named roles and responsibilities for site management
A designated place of safety, either an internal upper-floor refuge or an off-site safe location

Pro Tip: Request EA Flood Map for Planning products early. Product 1 is free and gives you the flood zone boundary. Product 4 gives you modelled flood levels and is the data source most LPAs expect to see referenced in both the FRA and the FEP. Start your application at the EA flood map for planning portal, then adapt the Bristol City Council FEP template as your working draft.

Key Takeaways

A flood evacuation plan submitted with a UK planning application must be site-specific, tied to FRA outputs, and name a responsible person — a generic template without modelled flood levels and confirmed lead times will not satisfy an LPA.

Point	Details
FEP triggers	Major development, vulnerable uses, ground-floor sleeping accommodation, and caravan/camping sites in Flood Zone 2 or 3 typically require an FEP.
Core FEP contents	Include named triggers linked to EA warning levels, confirmed lead times, evacuation routes above design flood level, and a named Flood Plan Manager.
FRA and FEP alignment	Every flood level, lead time, and residual risk scenario in the FEP must cross-reference the FRA using the same datum and EA product data.
LPA review focus	Emergency planners check for specific trigger wording, evidenced lead times, safe access/egress for the design and extreme flood, and a named management owner.
Fortress Associates	Provides combined FRA and FEP packages with EA data product handling, map production, and an amend-or-refund guarantee for UK planning submissions.

When does your development trigger a flood evacuation plan requirement?
What does a planning-ready flood evacuation plan need to contain?
How to prepare your FEP: a step-by-step workflow
Which maps and EA data products should you attach to the FEP?
How LPAs and emergency planners assess FEPs — and how to secure the plan
Practical pitfalls and expert tips from Fortress Associates’ planning submissions
Why integrating the FRA and FEP speeds up your approval
Fortress Associates can prepare your FEP and FRA together
Sources

When does your development trigger a flood evacuation plan requirement?

Local Planning Authorities (LPAs) do not apply a single universal rule, but the triggers are consistent enough across England that you can screen your project quickly. The NPPF and Planning Practice Guidance require that all development be safe for its lifetime, with safe access, escape, and management of residual risks, and an FEP is the primary mechanism for demonstrating that for at-risk sites.

Common triggers include:

Major development in Flood Zone 2 or 3 (typically 10 or more dwellings, or commercial floorspace above 1,000 m²)
Vulnerable residential uses such as care homes, sheltered housing, or extra-care schemes in any flood zone with a residual risk
New dwellings or flats with no internal access to upper floors, where occupants cannot shelter in place above the design flood level
Extensions that add ground-floor sleeping accommodation on sites with a flood risk
Caravan and camping sites, which carry a high vulnerability classification and often require detailed emergency planning regardless of flood zone
Hotels and hostels where guests may be unfamiliar with the site and unable to self-evacuate without assistance

The link to your Flood Risk Assessment (FRA) matters here. The GOV.UK FRA guidance states this explicitly.

Sequential and Exception Tests

If the Sequential Test has not already steered the development away from higher-risk land, and the Exception Test applies (as it does for certain vulnerable uses in Flood Zone 3a, or any use in Flood Zone 3b), the FEP becomes part of the evidence that the development will be safe. A weak or absent FEP undermines the Exception Test case.

LPAs retain discretion. A site in Flood Zone 2 with a surface water risk flagged in the Strategic Flood Risk Assessment (SFRA) may still attract an FEP requirement even if the standard triggers do not apply. Pre-application consultation with the LPA’s emergency planning officer is the only reliable way to confirm what is expected before you commit to a design.

Development Type	Typical FEP Trigger	Notes
Major residential (10+ units)	Flood Zone 2 or 3	FRA required; FEP normally conditioned
Care home / sheltered housing	Any zone with residual risk	High vulnerability; detailed FEP expected
Dwellings with no upper-floor access	Flood Zone 2 or 3	Refuge or off-site evacuation must be evidenced
Caravan / camping site	Flood Zone 2 or 3	High vulnerability; EA product 4 usually required
Hotel / hostel	Flood Zone 2 or 3	Guest unfamiliarity increases complexity
Ground-floor sleeping extension	Site with identified flood risk	LPA discretion; check SFRA and surface water maps

What does a planning-ready flood evacuation plan need to contain?

The structure below is drawn from the Bristol City Council FEP template and the North Somerset Council guidance, both of which reflect what LPAs across England commonly expect. Adapt rather than start from scratch.

Title and document control — site name, address, version number, date, and named author with contact details.
Scope and purpose — one paragraph stating what the plan covers, who it applies to, and which flood sources it addresses.
Site description — brief description of the site layout, number and type of occupants, ground levels relative to the design flood level, and access points.
Flood sources and risk profile — identify all relevant flood sources (fluvial, tidal, surface water, groundwater, sewer). Reference the FRA and the EA product used.
Vulnerability profile — describe the occupant profile, including any residents or visitors who may need assistance to evacuate (mobility-impaired, elderly, children, non-English speakers).
Warning sources and lead times — identify the EA Flood Warning service area covering the site, the quick-dial code for that area, and the realistic lead time between an EA warning and flood water arriving at the site. This is the section LPAs scrutinize most.
Triggers and decision logic — set out the specific EA warning level (Flood Alert, Flood Warning, Severe Flood Warning) that activates each stage of the response. Tie each trigger to a named action and a responsible person.
Evacuation procedure — step-by-step actions from initial warning through to all-clear, including who does what, in what order, and how they communicate.
Evacuation routes and maps — attach the annotated site plan (see Section 5 for map requirements). Describe primary and secondary routes, and confirm that both are above the estimated flood level for the design event.
Place of safety — specify whether the plan relies on off-site evacuation, internal refuge above the design flood level, or both. Distinguish clearly between the two: evacuation means moving people off-site; safe refuge means sheltering above the flood level within the building. LPAs expect evidence for whichever approach is chosen and justification for why it is appropriate.
People at risk and assistance needs — list categories of occupants who may need help, the assistance available, and who is responsible for providing it.
Roles and responsibilities — a named management table showing the Flood Plan Manager, deputies, and any contracted third parties, with 24-hour contact numbers.
Communications and contact list — emergency services numbers, EA Floodline (0345 988 1188), the LPA emergency planning team, utility contacts, and internal communication cascade.
Equipment and resources — flood boards, pumps, sandbags, first aid, and where they are stored.
Testing and training — schedule for tabletop exercises and live drills, with a record of who attended and what was learned.
Maintenance and review schedule — commit to a minimum review cycle. Isle of Wight Council’s Flood Warning & Evacuation Plan guidance recommends reviewing at least every three years or whenever site circumstances change materially.

Pro Tip: Create a one-page “site management table” at the front of the FEP listing the Flood Plan Manager, their deputy, and the review date. LPAs and emergency planners look for this immediately. A plan with no named owner is the single fastest route to a “needs changes” response.

How to prepare your FEP: a step-by-step workflow

The process below applies to most triggered developments. For complex sites, specialist input is needed at Steps 2 and 3.

Screen the site using the EA Flood Map for Planning (Product 1). Confirm flood zone, surface water risk, and whether the site falls within an area covered by an EA flood warning. Check the SFRA for any additional local constraints.
Classify vulnerability using the NPPF flood risk vulnerability classification. This determines which flood zones are acceptable for the use and whether the Exception Test applies.
Commission the FRA if one is required. For sites in Flood Zone 2 or 3, or surface-water-risk sites above the standing advice threshold, a site-specific FRA is mandatory. The FRA outputs — estimated flood levels, residual risk mapping, modelled lead times — feed directly into the FEP. See what a site-specific FRA involves before briefing a consultant.
Map access, egress, and refuge against the FRA’s estimated flood levels. Any route that falls below the design flood level cannot be the primary evacuation route. If the design constrains routes, resolve this now — not after planning permission is granted.
Draft triggers and decision logic tied to EA warning levels. Confirm the lead time between the earliest relevant EA warning and flood arrival at the site using FRA modelling or EA product data. Plans that assume occupants can evacuate during active flooding are routinely rejected.
Engage stakeholders. The ADEPT/EA joint guidance advises early liaison with the LPA’s emergency planning team and, where relevant, the Local Resilience Forum (LRF). Do this at pre-application stage, not after the FEP is drafted.
Internal sign-off and training. Before submission, the named Flood Plan Manager should confirm they understand their responsibilities. Record this in the document.
Submit with the planning application. The FEP should be listed as a supporting document. Agree with the LPA whether it will be secured by planning condition (submitted and approved prior to occupation) or by a planning obligation under Section 106.

For riverine sites where EA product 4 does not provide sufficient detail, you may need to request Products 5, 6, or 7 directly from the EA, which involves a formal data request and a fee. Budget four to eight weeks for this. Guidance on FRA work for sites near rivers covers when this level of detail is needed.

Common pitfalls:

Designing the building layout before checking evacuation route levels — retrofitting routes after design is a leading cause of delays, as the ADEPT/EA guidance explicitly warns against.
Assuming long lead times without modelled evidence. If the FRA shows flood water can arrive within two hours of an EA warning, the plan must reflect that.
Vague trigger language such as “when flooding is imminent” — LPAs want specific EA warning levels named.
No named management owner, or a management table that lists a company rather than a person.

Pro Tip: Pay for EA Product 4 early. It gives you modelled flood levels and extents that are far more defensible in an FEP than the indicative Flood Map for Planning boundaries. LPAs notice the difference, and emergency planners notice it even more.

Which maps and EA data products should you attach to the FEP?

The maps attached to an FEP are not optional extras. They are the primary evidence that evacuation routes are viable. The GOV.UK FRA guidance sets out the EA product suite; the table below shows which products to request and what each delivers.

EA Product	What it provides	When to request it
Product 1	Flood zone boundary (indicative)	Always — free, used for initial screening
Product 4	Modelled flood levels and extents	Standard for most FRA/FEP work in Flood Zone 2/3
Products 5/6/7	Detailed model outputs, breach/overtopping scenarios	Complex sites, defended areas, or where Product 4 is insufficient

Map checklist for the FEP

Every map attached to the FEP should include:

Site boundary clearly delineated
Estimated flood level contours or depth bands from the FRA, referenced to Ordnance Datum (mAOD)
Primary and secondary evacuation routes, annotated to show that route levels are above the design flood level
Refuge locations within the building (if internal refuge is the chosen approach), with floor levels confirmed above the design flood level
Off-site safe place with a grid reference and a description of the route to reach it
Scale bar and north arrow — LPAs typically expect site-level maps at 1:2,500 or larger
Legend explaining all symbols and color coding

The FRA should also provide residual risk mapping covering defence failure and overtopping scenarios. Where pedestrian or vehicular routes are affected in those scenarios, the GOV.UK guidance states that an emergency plan will normally be required. Include this mapping as an annex to the FEP so the LPA can see the worst-case picture.

For surface-water-risk sites, include the relevant outputs from the Lead Local Flood Authority’s (LLFA) surface water flood map and any SuDS strategy outputs. Surface water flooding is the risk most planning applicants underestimate, and LPAs are increasingly asking for it to be addressed explicitly in the FEP.

The CIRIA Property Flood Resilience Code of Practice is worth referencing in the FEP where flood resilience measures (flood doors, non-return valves, raised thresholds) are proposed as part of the design. The GOV.UK standing advice recommends it for specifying resistance and resilience measures that do not create structural problems.

How LPAs and emergency planners assess FEPs — and how to secure the plan

LPAs are increasingly delegating FEP review to their emergency planning teams, as the ADEPT/EA guidance notes. That means the person reading your FEP may not be a planner at all — they may be an emergency management professional who will apply a different lens to the document.

Standard LPA checks include:

Triggers are specific and realistic — named EA warning levels, not vague language
Lead times are evidenced — modelled or confirmed by EA data, not assumed
Safe access and egress exist for the design flood and the extreme flood (0.1% annual probability plus climate change allowance)
Management responsibilities are named — a person, not an organization
Vulnerable occupants are identified and a specific assistance plan is in place
Testing and training are scheduled with a realistic frequency
The FEP links to the FRA — the same flood levels, the same sources, the same residual risk scenarios

LPAs secure FEPs in two main ways. A planning condition requires the FEP to be submitted and approved prior to occupation — this is the most common approach and gives the LPA a clear enforcement mechanism. A Section 106 obligation may be used where the FEP involves off-site infrastructure or contributions to emergency services capacity. In some cases, both are used.

Red flags that trigger refusal or heavy conditioning:

Reliance on EA Flood Warning lead times without confirming those warnings cover the site
No safe access or egress route above the design flood level
No named management owner or review schedule
A plan that would materially increase demand on emergency services without mitigation
Trigger language that does not correspond to any EA warning product

Practical pitfalls and expert tips from Fortress Associates’ planning submissions

The gap between a plan that gets approved and one that generates three rounds of LPA queries is almost always in the details, not the structure.

Common submission problems and how to fix them:

Trigger wording that doesn’t match EA warning areas. If the site is not covered by an EA Flood Warning area, the plan cannot rely on EA warnings as triggers. The fix is to identify the nearest upstream gauge and agree a site-specific trigger level with the EA and LPA emergency planning team during pre-application.
Maps at the wrong scale. A site plan at 1:10,000 does not show enough detail for an LPA to assess whether evacuation routes are viable. Use 1:2,500 for the site-level evacuation map, with key nodes (refuge entry points, route decision points, off-site safe place) labeled.
No EA quick-dial code in the communications section. Every EA Flood Warning area has a quick-dial code. Include it. Emergency planners check for it.
Responsibility table listing a company name. The management table must list a named individual with a direct phone number. A company name is not enforceable.
Refuge floor levels not confirmed against FRA flood levels. If the plan proposes internal refuge, the floor level of the refuge must be stated in mAOD and confirmed to be above the design flood level in the FRA. Without that cross-reference, the LPA cannot verify the refuge is safe.

A technical peer review before submission checks all of these. Specifically, it verifies that trigger wording aligns with EA warning levels, that map scales and annotations meet LPA expectations, that the vulnerability profile covers all occupant categories, and that the management table is complete and enforceable.

Pro Tip: When drafting trigger wording, copy the exact language from the EA Flood Warning service description for the relevant warning area, then add the site-specific action that follows. For example: “On receipt of a Flood Warning for [EA warning area name, quick-dial code], the Flood Plan Manager will [specific action] within [time period].” This phrasing is immediately recognizable to emergency planners and removes any ambiguity about what activates the response.

Why integrating the FRA and FEP speeds up your approval

The FEP that gets through LPA review fastest is not the longest one. It is the one where every flood level in the FEP matches the FRA, every trigger corresponds to a documented lead time, and every map uses the same datum and the same source data as the technical assessment.

Decision-makers — planners and emergency planning officers alike — spend less time raising queries when the FEP and FRA are clearly cross-referenced. A plan that forces the reviewer to flip between two documents to check whether the refuge floor level matches the modelled flood level will generate a query. A plan that states “the refuge floor level of 12.4 mAOD is above the 1-in-100-year plus climate change flood level of 11.8 mAOD as modelled in Section 4 of the FRA” does not.

The practical implication: if the FRA shows limited lead times between EA warning and flood arrival, the design needs to respond to that finding. Finished floor levels, access road levels, and refuge locations should all be set with the FRA outputs in hand, not after the FEP is drafted. Coordinating these early means fewer pre-commencement conditions and a lower risk of the LPA requiring a redesign before occupation.

Fewer conditions also means faster pre-commencement sign-offs. Every condition that requires a document to be approved before work starts is a potential delay. A well-integrated FRA and FEP, submitted at application stage, reduces the number of those conditions to the minimum.

Fortress Associates can prepare your FEP and FRA together

Producing a flood evacuation plan that satisfies an LPA and its emergency planning team requires more than filling in a council template. It requires modelled flood levels, confirmed lead times, defensible trigger wording, and maps that hold up to technical scrutiny.

Fortress Associates

Fortress Associates prepares technical FRAs and FEPs for planning applications across the UK, handling EA data product requests, map production, trigger drafting, and liaison with LPA emergency planning teams. Clients provide a site plan, a brief, and any LPA pre-application correspondence — Fortress Associates handles the rest, cross-referencing the FRA and FEP so the two documents speak the same technical language.

Every report is validated against current standards before delivery, and the amend-or-refund guarantee means that if an LPA requests changes, Fortress Associates addresses them at no additional cost. No advance payment is required. To commission a technical FEP review or a combined FRA and FEP package, visit the Fortress Associates planning reports service and submit your project details.

Sources

These are the primary references for flood evacuation plan planning in the UK. Each one serves a specific purpose in the drafting process.

Flood Evacuation Plan Planning: UK Developer's Guide