How to Analyse London Planning Applications: A Data-Driven Guide

Every week, London’s 32 boroughs and the City of Corporation publish hundreds of planning applications. For residents, community groups, researchers and data analysts, the challenge is not just finding these applications, but extracting the information that matters. This guide shows you how to use the key data sources—the Planning Data portal, the London Datastore, and borough registers—to track, compare and analyse applications in a systematic way.

The approach is data‑driven: you will learn to identify the relevant fields, filter by date and type, export records, and cross‑reference documents with local and London‑wide policies. The goal is to move from passive reading to active analysis, so you can quantify development trends, assess compliance, and prepare evidence‑based responses.

—

Where to Find Machine‑Readable Planning Data

The most powerful starting point is the Planning Data portal (https://www.planning.data.gov.uk), a national open dataset maintained by the Ministry of Housing, Communities and Local Government. It aggregates application records from all English local authorities, including every London borough. You can search by address, postcode, or application reference, and then download the metadata in CSV or GeoJSON format. This allows you to import records into a spreadsheet or GIS tool.

For historic or aggregated data, the London Datastore (https://data.london.gov.uk/dataset/planning-applications) provides quarterly extracts of planning applications across London, with fields such as application type, decision date, floor area, and number of units. These datasets are ideal for trend analysis—for example, comparing the number of major applications in Hackney versus Croydon over the past five years.

Finally, each borough’s own planning portal (e.g., Westminster’s, Croydon’s, Lewisham’s) remains the authoritative source for individual application documents. The portal is where you will find the PDFs of plans, statements, and reports.

Action: Open the Planning Data portal, enter your postcode, and filter by “Full planning permission” within the last 30 days. Download the result as CSV. This gives you a list of reference numbers, application types, and statuses to work with.

—

Decoding the Application Reference Number

Every London planning application has a unique reference that encodes the borough, year, and type. The format is typically `Borough code / Year / Sequential number / Type suffix`. For example, `23/01234/FULL` is a 2023 application in that borough, number 1234, for full planning permission. The type suffix is critical for filtering and analysis.

When you export data from the Planning Data portal, the `application_type` column will contain these suffixes. Use them to filter out minor applications (e.g., `CON` or `TPO`) when you want to focus on substantive developments.

—

Key Documents and What to Extract from Each

Once you have a list of application references, open each one on the borough’s portal. The documents are usually listed as PDFs. Do not read every page; instead, extract specific data points.

Application Form – Contains the applicant’s name, site address, description of development, and the exact use class. Record the use class (e.g., C3 for dwellinghouses, B1 for offices) because it determines the policy framework.

Site Location Plan – A scaled map with the site boundary outlined in red. Use this to verify the site area (in hectares) and to check if the site falls within a conservation area, flood zone, or other designated area. The London Datastore provides a flood zone map layer you can overlay.

Existing and Proposed Plans – Floor plans, elevations, and sections. Compare the proposed gross floor area (GFA) with the existing. The change in GFA is a key metric for density calculations. Also note the number of storeys.

Design and Access Statement – Required for most major applications. It explains the design rationale, how the proposal responds to the site context, and how it meets accessibility standards. Look for the section on “policy compliance” – it will list the specific policies from the London Plan and the local plan that the applicant claims to satisfy.

Planning Statement – A more detailed policy justification. It often includes a table that maps each policy to the proposal’s response. This is a goldmine for analysis: you can compare the applicant’s claims against the actual policy wording.

Transport Statement – Contains trip generation numbers, parking provision, and cycling/walking infrastructure. Compare the proposed parking ratio (spaces per unit) with the borough’s maximum parking standards. The London Plan sets maximum parking standards for new developments.

Flood Risk Assessment – For sites in flood zones 2 or 3 (common along the Thames and canals). Check the flood risk vulnerability classification (e.g., “more vulnerable” for residential) and whether the sequential test is passed.

Heritage Statement – If the site is in or near a conservation area or a listed building. Look for the assessment of impact on the significance of the heritage asset.

Tip: Use Ctrl+F in each PDF to search for keywords: “affordable housing”, “daylight”, “overshadowing”, “parking”, “cycle parking”, “policy [number]”. This saves time and ensures you don’t miss critical sections.

—

Cross‑Checking Against the Development Plan

A planning application is decided against the development plan for that area. In London, the plan has three tiers:

The London Plan – the spatial development strategy for Greater London, produced by the GLA. It sets borough‑wide policies on housing, transport, environment, and design. The current version is the London Plan 2021, available at https://www.london.gov.uk/programmes-strategies/planning/london-plan.

The Local Plan – each borough has its own plan (e.g., Newham Local Plan, Camden Local Plan). These are more detailed, with site‑specific allocations, building height limits, and local design guidelines.

Neighbourhood Plans – if your area has one, it adds further policies.

When analysing an application, create a simple comparison table:

You can find the local plan policies on the borough’s website. The London Datastore also provides a planning policy layer in some boroughs.

—

Limitations and Pitfalls

Analysing planning applications is not straightforward. Here are three common limitations:

• Missing documents. Not all applications upload every document. If the Design and Access Statement is missing, check the comments section or contact the planning officer. The Planning Data portal may have a link to the full application, but the documents are hosted by the borough.

• Viability assessments. A developer may claim that full affordable housing is not viable. The viability assessment is often redacted. You can request a summary under the Freedom of Information Act, but the council may withhold it.

• Data quality. The Planning Data portal relies on data submitted by boroughs. Some records have missing fields (e.g., floor area, number of units). Always cross‑check with the borough’s own register.

A further limitation: major applications (over 150 homes or buildings taller than 30 metres) are referred to the GLA for a Stage 1 and Stage 2 assessment. The GLA’s decisions are published on the London Assembly website. If you are tracking a major application, you need to monitor both the borough and the GLA timeline.

—

Next Steps: From Analysis to Action

Once you have extracted the data, you can use it to:

• Write an evidence‑based comment on the borough’s portal. Reference the specific policy numbers and the document page numbers. For example: “Page 12 of the Design and Access Statement states the proposal will provide 40% affordable housing, but London Plan Policy H4 requires 50% on public land. The Viability Summary (page 3) does not justify the reduction.”

• Track trends over time by downloading the London Datastore dataset and filtering by application type, borough, and decision date. You can calculate the approval rate for major applications in your borough over the past year.

• Share your analysis with a community group or local councillor. A simple spreadsheet with policy comparisons is more persuasive than a personal opinion.

Start today: open the Planning Data portal, search for your postcode, and download the last 30 days of applications. Pick one with a FULL suffix, open the PDFs, and fill in the comparison table above. This repeated practice will turn you into a confident analyst of London’s planning system.