Retrospective Planning Applications: Flood Risk and Drainage Explained

A retrospective planning application is a normal application made after building work has already started or finished. Where that development sits in a flood risk area, or changes how surface water drains from the site, the retrospective planning application flood risk and drainage evidence still has to be produced. Producing a policy-compliant version after the fact is far harder than doing it before a spade goes in the ground.

A flood risk assessment for a completed development cannot simply describe the site. It has to justify what has already been built, and where it cannot, the fix is physical work rather than a redraft.

This article explains what a retrospective application is, when flood risk and drainage evidence is required, why that evidence is so difficult to assemble once works are complete, how the sequential test and the enforcement rules bear on it, and why choosing the retrospective route can commit you to substantial and invasive remediation.

What is a retrospective planning application?

A retrospective planning application regularises development that has already been carried out without the required permission. It is made under Section 73A of the Town and Country Planning Act 1990. It covers a completed building, an extension built differently from the approved plans, an unauthorised change of use, or works that began before a pre-commencement condition was discharged.

The decisive point is that it is determined in exactly the same way as any other application. The local planning authority assesses it against the same national and local policies and the same material considerations. The fact that the development already exists is not, in itself, a reason to grant it. As the Planning Portal sets out, a retrospective application is not a formality or a rubber stamp. It has to succeed on its planning merits, flood risk and drainage among them.

There is only one chance to regularise unauthorised work: a Section 73A application, or an appeal against an enforcement notice. You cannot keep trying.

That single shot is what raises the stakes on the flood risk and drainage evidence. The government's enforcement guidance is explicit that permission after the event comes through those two routes and no more. So the assessment has to be right first time, rather than revisited if it fails.

Do you need a flood risk assessment or drainage strategy for a retrospective application?

Yes, on exactly the same basis as any application. Nothing about the triggers for a flood risk assessment or a surface water drainage strategy is waived because the work is already done. If anything, the scrutiny is tighter, because the consultee is now testing whether a real, standing thing is safe rather than whether a proposal could be made safe.

The thresholds are the ones that apply to any site. Our guide on when you need a flood risk assessment sets out the full list. The Environment Agency's flood risk assessment guidance requires an applicant to show that development is safe for its lifetime and does not increase flood risk elsewhere. A completed building has to meet that test just as a proposed one would.

Since the September 2025 Planning Practice Guidance update, the sequential test and the risk-based approach apply to all sources of flooding, surface water and groundwater included.

So a retrospective assessment now screens more sources than the same site would have a few years ago. Where drainage is involved, the strategy is judged against the 2025 national standards for sustainable drainage, not the standards that were current when the ground was first broken. The way flood risk and drainage fit into the planning process is the same for a retrospective case. Only the timing has moved.

Why is a policy-compliant flood risk assessment so much harder after the build?

Because a flood risk assessment is designed to shape a development, not to defend one. Done at the right time, it influences where the building sits, how high the floor levels are, and how surface water is managed. Done retrospectively, all of those decisions are already fixed, and the assessment has to work backwards from what exists. Five problems follow.

The difficulties compound on one another, and the drainage case tends to suffer first.

• The pre-development baseline is gone. A drainage strategy has to show that post-development runoff is no worse than the greenfield or pre-existing rate. Once a site is built out and surfaced, the original ground conditions, permeability and runoff behaviour can no longer be measured directly; they are reconstructed from historic mapping, records and assumption, which is weaker evidence and easier for a Lead Local Flood Authority to challenge.
• Finished levels constrain the mitigation. Raising finished floor levels, setting the building back, or grading the ground to fall away from it are the most reliable fixes, and each depends on being decided before construction. Retrospectively, floor and site levels are set, so the tools that would normally solve the problem have gone.
• Ground investigation is compromised. Infiltration testing for soakaways, and the winter groundwater monitoring many sites need, assume undisturbed ground and access. On a completed site the ground is disturbed, covered or built over, and a missed monitoring window, which typically runs November to May, can add a full season to the programme.
• Below-ground features cannot be inspected. Where attenuation, pipework or a soakaway should exist, a retrospective assessment often cannot confirm what is in the ground without excavation. What was built, and whether it works, becomes a question rather than a record.
• The goalposts may have moved. The application is judged against current policy, not the policy in force when the work was done. A development built a few years ago may now have to meet the 2025 national standards for sustainable drainage and updated climate change allowances. Compliance is measured today.

An AI-drafted or box-ticking assessment is even less likely to survive here than usual. The consultee is often a Lead Local Flood Authority whose objection can hold up the whole application, and what it is testing is whether an existing thing is genuinely safe and compliant. That is an evidence problem, and no amount of drafting fixes it.

How does the sequential test apply to a development that already exists?

The sequential test is the sharpest example of the mismatch. Its purpose is to steer new development towards land at the lowest risk of flooding, by comparing the site with reasonably available alternatives. Applied to something already built, that logic strains. The applicant is effectively being asked whether the development should have gone somewhere else, when it is already here.

Planning guidance recognises a pragmatic approach for genuinely minor works. A small extension relative to an existing building is one example, where relocating the floorspace elsewhere would be unrealistic. For anything more substantial, the local planning authority and the Environment Agency will still expect the test to be addressed properly, and an unauthorised development in a higher flood zone can fail it. As the Yatton appeal showed, the sequential and exception tests turn on evidence and the planning balance, not on how the case is worded. Passing the sequential test was never a drafting exercise. Retrospectively, it can become the point on which the whole application turns.

The real danger with retrospective flood risk: remediation, not paperwork

Here is the part that catches people out. Suppose the flood risk assessment or drainage strategy for a completed development shows that it increases flood risk, or that surface water is not managed to standard. The remedy is not a better-worded report. It is physical remediation of what has been built, and on a finished, occupied site that work is substantial and invasive.

On a completed site the fix for a flood risk failure is construction, and a constrained plot sometimes cannot accommodate compliant drainage at all.

Depending on what the assessment finds, compliance can mean real construction after the fact.

• Excavation. Digging out finished ground to install the attenuation tanks, crates or soakaway that should have been built in from the start.
• Floor levels. Lifting or rebuilding finished floors to achieve a safe freeboard above the flood level.
• Surfacing. Replacing impermeable surfaces with permeable construction, or re-grading so water falls away from the buildings.
• Flood resilience. Retrofitting resilient construction into a structure that is already complete.
• Footprint. In the worst cases, reducing or removing part of what has been built, because the site cannot accommodate compliant drainage as-built.

Each of these is disruptive, expensive, and slower than it would have been as part of the original build. Worse, a constrained finished site sometimes cannot achieve full compliance at all, because there may be no room for the storage the runoff calculations demand. At that point the application is at risk of refusal, and refusal can lead to an enforcement notice requiring the development to be altered or removed. This is why the decision to "choose" the retrospective route is rarely as low-risk as it looks. The flood and drainage dimension is where the gamble tends to fail, because the evidence is the hardest to produce and the fixes are the hardest to build after the fact.

How long can a council take enforcement action? The four- and ten-year rules

Some people rely on time limits to avoid regularising unauthorised work at all. That calculation changed in 2024. Under the Levelling Up and Regeneration Act 2023, from 25 April 2024 England moved to a single ten-year enforcement time limit for all breaches of planning control.

Before that, building and engineering operations and changes of use to a single dwelling were immune after four years. Now the longer period applies to almost everything completed on or after that date. Works substantially completed before 25 April 2024 keep the old four-year limit, and Wales has retained four years. In practice, a council now has a full decade to act in England. Unauthorised development in a flood risk area therefore stays exposed to challenge far longer, and waiting it out is a weaker strategy than it used to be. A robust retrospective flood risk assessment or drainage strategy is more often the sensible route.

Can a flood risk activity permit be granted retrospectively?

No, and this is the one situation where "regularise it later" is not even an option. Where works involve a main river, a flood defence or the land next to one, such as building, excavating or placing a structure within a watercourse or its byway, they may have needed a Flood Risk Activity Permit from the Environment Agency before anything started.

A Flood Risk Activity Permit cannot be issued retrospectively, and carrying out a regulated activity without one is an offence. Planning permission does not remove the need for it.

The permit and the planning permission are assessed separately. A Flood Risk Activity Permit that should have been obtained first cannot be repaired by a later planning consent. It is a reminder that the flood risk consequences of building first and asking later are not always fixable at any price.

How Unda approaches retrospective flood risk and drainage work

Unda regularly prepares flood risk assessments and drainage strategies for retrospective planning applications. The approach is deliberately different from a standard, pre-construction commission. Rather than describing a proposal, the work reverse-engineers the evidence for something that already exists.

1. Start with an honest as-built appraisal: what has actually been constructed, what its levels and surfaces are, and how surface water behaves now compared with before.
2. Reconstruct the pre-development baseline as robustly as the evidence allows, from historic mapping, records and site investigation.
3. Model the site as it stands, screening every source of flooding the current guidance requires.
4. Identify the mitigation that is genuinely achievable on a finished site, rather than the mitigation a blank plot would have used.
5. Set out any remediation clearly and proportionately, so the applicant can weigh the cost before committing.

Where remediation is unavoidable, we set it out plainly: what needs to change, why, and how it satisfies the local planning authority, the Lead Local Flood Authority and the Environment Agency. That way an applicant can weigh the cost with the facts in front of them. And where a development can be shown to be safe and compliant as built, we make that case with the site-specific evidence the consultees actually test. In one recent case we justified a retrospective new dwelling in a River Ems floodplain:

The goal in both cases is the same. It is to give a retrospective application the strongest, most defensible flood risk and drainage position it can have, rather than a document that unravels at consultation.

If you are facing a retrospective planning application, whether by choice, a condition breach, or an enforcement notice, the flood risk and drainage evidence is usually the hardest part to get right, and the part most likely to require physical works. Unda's consultants prepare policy-compliant flood risk assessments and surface water drainage strategies for retrospective applications across England and Wales. We can tell you early whether a development stands up as built, or what remediation it will need. Get in touch for a no-obligation quote, and one of our flood risk consultants will respond within 60 minutes.

Frequently asked questions