Opportunity Areas and their planning frameworks

An Opportunity Area planning framework is guidance, not development plan policy, and that distinction decides how much weight it carries when your application is determined. London Plan policy SD1 designates the Opportunity Areas and Annex 1 of the Plan gives each one an indicative capacity for homes and jobs. The framework that follows, prepared by the Greater London Authority and often with the borough, sits underneath that as a material consideration. Treat the capacity figure as a floor to aim at and the framework as the evidence base you argue from.

What the designation does and does not do

An Opportunity Area is a growth location with capacity for substantial new homes and jobs, usually where public transport accessibility is already good or is about to improve. The designation is strategic. It does not allocate individual sites, it does not grant any form of consent, and it does not displace the borough's own local plan policies.

What it does is set the policy context in which intensification is expected rather than resisted. On a site inside an Opportunity Area, the starting presumption in the strategic plan is that higher density is appropriate if the design and infrastructure cases are made. That shifts the burden in a way that matters at committee.

The boundaries are drawn generously and often include land that will not change at all. Being inside the boundary is the beginning of an argument, not the end of one.

Check which Opportunity Area you are actually in, and whether the site also falls within a town centre boundary, a Strategic Industrial Location or a conservation area. Those overlapping designations usually have more to say about what can be built than the Opportunity Area status does, and they are the ones a case officer will raise first.

Indicative capacity figures and the weight they carry

Annex 1 figures are indicative minimums for the area as a whole, expressed as new homes and new jobs. They are not site-level targets and they are not ceilings.

Two mistakes follow from misreading them. The first is dividing the area figure by the number of developable sites and presenting the result as the capacity your site must deliver. The second is treating the area figure as satisfied once consents add up to it, so that later applications face a capacity argument against them. Neither reading survives contact with policy SD1, which frames the numbers as capacity to be realised rather than quotas to be rationed.

The useful way to use the figures is as context for a density case. If the area is expected to accommodate thousands of homes and your scheme proposes a density above the surrounding grain, the Annex 1 figure explains why. Pair it with the design-led approach in London Plan policy D3, which asks for capacity to be established through design testing rather than a density matrix, and which our note on optimising site capacity under policy D3 covers in detail.

Where a framework sits in the decision

A framework published by the Mayor is not part of the development plan. Under section 38(6) of the Planning and Compulsory Purchase Act 2004 the decision must be made in accordance with the development plan unless material considerations indicate otherwise, and the framework is one of those considerations.

Its weight depends on three things.

• Whether it was adopted by the borough as a supplementary planning document or merely published by the Mayor as guidance.
• How recent it is, and whether the London Plan or the local plan has moved on since.
• Whether it was consulted on, and what the consultation produced.

An older framework prepared against the 2016 London Plan and never refreshed is the weakest of these, and officers know it. Say so yourself rather than pretending otherwise, then explain why the parts you rely on remain sound.

Infrastructure phasing and the conditions that follow

Frameworks usually set out infrastructure that the area needs before its capacity can be delivered, such as a station upgrade, a new bridge, a school or a district heat network. For an individual applicant this is where the commercial risk sits.

The question an officer will ask is whether your scheme can be occupied before the infrastructure arrives. Expect Grampian conditions tying occupation to the delivery of off-site works, phasing conditions tying later blocks to earlier ones, and section 106 contributions calculated against the framework's infrastructure schedule.

Those contributions have to meet the statutory tests of necessity, direct relation and fair and reasonable scale. A framework schedule is evidence of need. It is not a tariff, and a contribution sought purely because the framework lists a project can be resisted where the connection to your development is weak.

Design codes, masterplans and the detail that binds

Many frameworks now carry a design code or a spatial masterplan showing building heights, street alignments, active frontages and public spaces. These are the parts that most often become conditions.

Height is the usual flashpoint, and the one most often tested at appeal. A code indicating a maximum of eight storeys on your block, where your scheme proposes twelve, puts you in conflict with guidance that the borough will treat as settled. The argument for departing from it has to be site specific, which means daylight and sunlight modelling, townscape analysis and a clear statement of what the extra homes buy. Where tall buildings are proposed, the London Plan fire safety and energy requirements bring their own documents, and a Fire Statement and an Energy Statement will be validation requirements rather than optional extras.

Codes also fix things that cost less to accept than to fight, such as frontage treatment and servicing arrangements. Pick the one or two departures that matter commercially and comply with the rest.

Read the code's status page before you plan the argument. Some codes are expressed as parameters that must be met, others as illustrative, and the drafting is often looser than the officer's summary of it. Where a figure appears only on a plan and nowhere in the text, that is worth pointing out.

Where the framework conflicts with local policy

Conflict happens most often on employment land and on affordable housing tenure. A framework may show residential-led intensification on land the local plan protects as industrial, in which case the local plan prevails unless the framework was adopted by the borough or the London Plan's own industrial policy provides a route. Our note on industrial land in London and no net loss sets out how that tension is usually resolved.

Where the framework and the local plan point different ways, say which you are relying on and why, in the Planning Statement rather than leaving the officer to work it out. A statement that quotes both, acknowledges the conflict and explains the balance is far harder to refuse than one that quotes only the convenient document. For the wider effect of an allocation on a site, see our note on what a London Opportunity Area allocation changes.

PlanScope drafts planning statements against the London Plan and the borough's adopted policies and marks the site facts it does not hold rather than guessing them. Reports should be reviewed before submission, and PlanScope does not guarantee planning approval.