How London's Planning System Got Tangled in Duplicate Images — and Why It Matters Now

London's planning apparatus is sitting on thousands of application files where the same photograph, site survey, or architectural drawing has been submitted multiple times — clogging case-management systems, slowing officer decisions, and quietly undermining the reliability of public records that residents and councillors depend on. The problem is not new, but the scale of housebuilding the Labour government is demanding of the capital has made it impossible to ignore.

The Starmer administration has set a mandatory target requiring London boroughs to collectively approve enough homes to hit a figure approaching 90,000 new dwellings per year across England's largest city-region. That pressure funnels directly into the planning portals of all 33 London boroughs, each of which runs its own document management infrastructure — most of it procured separately, many systems dating to the mid-2000s. When applicants upload supporting material, duplicate files pile up inside those systems because upload validation was never a priority when the pipelines were built.

Where the Problem Took Root

The issue traces back to a structural choice made around 2004 and 2005, when the Office of the Deputy Prime Minister encouraged local authorities to move planning applications online under what became the Planning Portal, a nationally shared submission gateway based in Leeds. Boroughs were required to accept digital documents but were left to manage storage and indexing themselves. Southwark Council, which handles some of the highest application volumes in inner London because of major regeneration zones along the Old Kent Road and around Canada Water, built its back-end systems in that era. Tower Hamlets, processing applications across the Whitechapel and Aldgate corridors, did the same.

The result, across most of inner London, was a patchwork. An agent submitting plans for a residential conversion in Bermondsey might upload a ground-floor plan, receive an error message, upload it again, and walk away unaware that both versions now lived in the council's document store. Officers working under caseload pressure — Southwark's planning team, for instance, has publicly reported handling upwards of 5,000 applications annually in recent years — rarely had time to audit file sets for redundancy before issuing decisions.

The Greater London Authority introduced its own development management system, called Acolaid and later migrated toward cloud-based platforms, to handle strategic applications above certain thresholds. But boroughs below those thresholds — which covers the overwhelming majority of residential planning — remained responsible for their own digital hygiene. By 2019, a cross-borough working group convened under the London Legacy Development Corporation flagged duplicate document storage as a factor contributing to delayed subject access requests under the Freedom of Information Act 2000, though no formal remediation programme followed.

Why 2026 Is the Pressure Point

Three things have converged to make the status quo untenable this year. First, the government's Planning and Infrastructure Bill, currently advancing through Parliament, imposes new transparency requirements on local planning registers, meaning document accuracy will face external scrutiny it previously avoided. Second, the GLA's London Plan Implementation Framework, updated in spring 2026, asks boroughs to demonstrate streamlined decision timelines as a condition for accessing certain affordable housing grant streams administered through Homes England. Third, artificial intelligence tools that planning departments are now piloting — including a document-classification system being tested by Hackney Council — flag duplicate files automatically, producing backlogs of remediation tasks that teams had not budgeted for.

Hackney's pilot, which began in January 2026 along the Dalston Lane and Shoreditch corridors where permitted development and change-of-use applications are dense, surfaced duplicate image rates in some case files running above 30 percent of uploaded assets, according to a summary the council published on its website in March 2026. That figure, drawn from a sample rather than the full archive, points to a systemic rather than incidental pattern.

For Londoners watching planning decisions that affect their streets, the practical consequence is that appeals and legal challenges can become entangled when the official record contains conflicting versions of the same document. Neighbourhood groups in Elephant and Castle have raised exactly this concern in written submissions to Southwark's planning committee during 2025 and early 2026, arguing that duplicate filings make it harder to track design revisions across application histories.

Boroughs piloting deduplication tools have generally given themselves a 12-to-18-month window to clear historic backlogs before the Planning and Infrastructure Bill's transparency provisions take effect. That clock is already running. Residents appealing decisions or lodging objections should download and timestamp the specific documents they rely on from the public planning register now, before remediation processes alter what is publicly visible.