How London's Planning System Got Buried Under Duplicate Images — And Why It's Finally Being Fixed

London's 33 borough councils are sitting on a collective archive of planning application documents that, by some internal estimates circulating among local government officers, contains duplication rates of between 30 and 40 percent — meaning that nearly two in every five uploaded files is a redundant copy of something already stored. The problem did not arrive suddenly. It accumulated over roughly fifteen years of rushed, under-resourced digitisation, and it is only in 2026 that a coordinated effort to address it is gaining traction.

The issue matters right now because Keir Starmer's government has made planning reform the centrepiece of its domestic agenda. The Planning and Infrastructure Bill, progressing through Parliament this year, demands faster, more transparent decisions. Councils that cannot locate the authoritative version of a site plan — because three near-identical copies exist under slightly different file names — are structurally incapable of meeting the new statutory timetables the Bill proposes. Duplicate image replacement, the technical process of identifying and retiring redundant document versions while preserving a single verified master file, has moved from a back-office nuisance to a political pressure point.

The Long Road to This Mess

The roots of the problem trace back to around 2009 and 2010, when councils began converting paper application files to digital formats under pressure from central government efficiency drives following the financial crisis. The work was done borough by borough, sometimes department by department, with no shared standard for file naming, image resolution, or version control. Southwark Council, which processes some of the highest volumes of planning applications in inner London due to its concentration of regeneration zones along the South Bank and around Elephant and Castle, ended up with multiple scanning contractors over successive years, each using different metadata conventions. Hackney, Tower Hamlets, and Lambeth faced comparable problems as major development programmes accelerated through the 2010s.

The Greater London Authority's Planning Datahub, established in 2021 to aggregate borough-level data across the capital, began flagging the duplication issue formally in its 2023 annual review. By that point, the cumulative file storage cost to London boroughs was a live budget concern, with cloud storage and legacy server maintenance consuming funds that planning departments — already hollowed out by years of cuts — could ill afford. A 2024 Local Government Association report found that English councils collectively spent an estimated £47 million annually maintaining redundant digital planning records, though London's share of that figure was not broken out separately.

What's Changing — and Where

The GLA and a consortium of eight boroughs, including Islington, Lewisham, and Greenwich, began piloting an automated duplicate-detection system in January 2026. The software, procured through the Crown Commercial Service framework, cross-references file hashes, pixel-similarity scores, and document metadata to flag likely duplicates for human review before deletion. Islington's planning department, based at 222 Upper Street, has been running the pilot on its post-2015 archive and expects to complete the first pass by September 2026.

The practical stakes are visible at street level. The Blackhorse Road regeneration corridor in Walthamstow, where Waltham Forest Council is managing dozens of live applications for new homes, has been cited internally as a case study in how document confusion slows decision-making. Officers there have reported spending time manually reconciling floor plans before committee dates — time that delays decisions on housing that the borough is under statutory pressure to approve quickly.

For residents and developers watching applications move through the system, the immediate advice from planning officers is consistent: when submitting documents to any London borough portal right now, use clear, unique file names with dates and version numbers embedded, and avoid resubmitting corrected drawings without explicitly withdrawing the earlier version. Councils currently have no automated safeguard against treating a superseded drawing as current.

The GLA consortium expects to publish findings from the January pilot by the end of 2026, with a view to rolling out the deduplication framework across all 33 boroughs through 2027. Whether that timeline holds depends partly on whether the boroughs can secure ringfenced resource from the Planning and Infrastructure Bill's proposed digital infrastructure fund — a detail still being negotiated between the Ministry of Housing and local government representatives.