Retrospective Applications

What a retrospective application actually is

Anyone can apply for planning permission for development that’s already been carried out, whether because it was built without permission at all or because it departed from an approved scheme. This is a genuine route within the planning system, not a special loophole exclusive to bad-faith applicants — genuine mistakes happen alongside deliberate ones.

Why “it’s already built” isn’t itself a reason for refusal

This is the single most important thing to understand: the council must assess a retrospective application on exactly the same planning merits as if it hadn’t been built yet. The fact construction has already happened, however frustrating, doesn’t change the test being applied — an objection based purely on “they shouldn’t be allowed to get away with it” carries no formal weight, however understandable the frustration.

What actually can be raised

• The same material considerations that would apply to any application for the same development — amenity, design, character, and so on
• Whether enforcement action was or should have been taken before an application was made — a separate process from the planning decision, best raised directly with the council’s enforcement team alongside, not instead of, objecting to the application
• Whether the development as built actually matches what’s described in the retrospective application, since these sometimes only partially reflect what was actually constructed

What strengthens this objection

• Focusing entirely on the same substantive planning grounds — light, privacy, character — that would apply to any application, not on the process itself
• Checking the application drawings against what’s actually on the ground, and flagging any discrepancy directly to the case officer
• Separately contacting the council’s planning enforcement team if you believe enforcement action should also be considered

Where it tends to fail

Objections built entirely around the unfairness of the retrospective process rather than the substance of the development — however justified the frustration, it doesn’t change the officer’s assessment.

A worked example of a weak objection versus a strong one

Weak: “This was built without permission and it’s completely unfair that they get to apply for it after the fact.”

Strong: “As built, the extension’s ridge height appears to differ from what’s shown on the submitted drawings — the structure on site appears taller than stated. Separately, on the planning merits, the structure as built removes the only rear-facing window’s direct light for most of the afternoon.”

Common mistakes to avoid

• Focusing solely on the unfairness of the process rather than the planning merits the decision is actually based on
• Not separately contacting the council’s enforcement team, which handles a genuinely different question from the application’s own merits
• Assuming a retrospective application is automatically approved because it’s “already there” — it can genuinely be refused, with enforcement action potentially following