How London's Planning System Ended Up Drowning in Duplicate Images — and Why It Matters Now

Thousands of planning applications lodged with London's 33 borough councils carry duplicate images — the same site photograph, elevation drawing, or flood-risk map filed two, three, sometimes five times under different reference numbers. The result is bloated digital case files, slowed validation times, and, in some instances, decisions delayed by weeks while officers track down the authoritative version of a document.

The problem matters right now because the Labour government's Planning and Infrastructure Bill, progressing through Parliament in the summer of 2026, depends on a functioning digital evidence base. Ministers have argued that a reformed, data-driven planning system will help England build 1.5 million new homes by 2029. If the underlying document infrastructure is riddled with redundancy and mismatched metadata, that ambition starts on shaky foundations.

How the Duplication Built Up Over Decades

The roots go back to 2004, when the Planning Portal — a joint venture between central government and local authorities — became the standard electronic submission route for planning applications in England. Boroughs migrated legacy paper files into nascent back-office systems at different speeds and to different standards. Tower Hamlets, which was processing applications for the rapid Docklands expansion at the time, and Southwark, managing the Elephant and Castle regeneration corridor, both imported large volumes of scanned documents in bulk. Automated file-naming conventions were inconsistent, and nobody built a deduplication layer into the upload pipeline.

By 2016, the Greater London Authority's Digital Planning programme — a precursor to the national Open Digital Planning initiative — flagged the issue internally. Pilot work in Camden and Lambeth found that roughly one in eight uploaded image files was a duplicate of another document already sitting in the same case folder, according to a 2017 technical review circulated to borough chief planners. The GLA recommended standardised file-naming protocols and a mandatory hash-check on upload. Most boroughs acknowledged the recommendation. Few implemented it.

The pandemic accelerated the underlying problem. Between March 2020 and December 2021, application volumes across London boroughs rose sharply as homeowners pursued extensions and conversions during successive lockdowns. Officers working remotely uploaded documents through a patchwork of VPN connections and personal devices. Hackney's planning department, for example, saw its caseload rise by around 30 percent in the eighteen months to September 2021, stretching a team already managing the Dalston and King's Cross growth corridors. In that environment, robust file hygiene was not a priority.

What the Digital Planning Push Exposed

The Open Digital Planning project, jointly run by the Department for Levelling Up (now merged into the Ministry of Housing, Communities and Local Government) and the GLA, began its most intensive phase in 2023. It connected back-office systems across a dozen London boroughs to a shared data schema. That integration work acted like a torch shone into a cluttered attic: it revealed the scale of the duplication for the first time in aggregate rather than borough by borough.

Islington Council's planning team, working with the project's technical partners on the Upper Street and Angel development clusters, identified more than 4,000 duplicate image records in live case files during a data-cleaning sprint in late 2024. Across all participating boroughs, the total runs into tens of thousands of records. Each duplicate is a small drag — an extra click, an extra query, an extra minute — but multiplied across hundreds of officers and thousands of applications, the cumulative effect on validation times is measurable.

The Planning Portal announced in March 2026 that it would introduce server-side deduplication checking for new submissions from the autumn. That addresses the pipeline going forward. It does nothing about the existing backlog of legacy case files, which boroughs are now expected to clean up individually, under guidance from MHCLG, using tools that vary in capability from one back-office provider to another.

For applicants dealing with the system today, the practical advice is straightforward: label every document with a unique, descriptive filename before upload, include the application reference number in the filename, and keep a local log of exactly which file was submitted and when. It will not fix the system, but it reduces the chance that your planning officer spends time on the wrong version of your drawings — and in a city where a validated application can take six weeks just to reach a decision queue, every hour saved counts.