How London's Planning System Got Tangled in Its Own Paperwork: The Duplicate Image Problem Explained

London's planning departments are grappling with a growing administrative crisis: duplicate and mismatched images attached to planning applications are clogging case files, triggering automatic rejections, and in some instances sending applicants back to square one after months of work. The problem is not new, but pressure on borough planning teams in 2026 has made it impossible to ignore any longer.

The issue matters now because the Starmer government has staked a significant portion of its domestic credibility on unlocking housing delivery. Under the revised National Planning Policy Framework, local authorities face mandatory housing targets, and Mayor Sadiq Khan's London Plan is under pressure from Whitehall to produce consented units faster. Any bottleneck in the validation stage — before a case even reaches a planning officer — chips directly at those numbers. Duplicate image uploads are one such bottleneck, and they are more common than most boroughs publicly acknowledge.

How the Backlog Built Up

The roots go back to 2019, when the Planning Portal — the national online system used to submit applications across England — underwent a major technical overhaul. Several London boroughs, including Tower Hamlets and Southwark, reported validation problems in the months that followed as case management systems struggled to synchronise with the new portal. Files submitted with multiple site photographs, floor plan revisions, or resubmitted documents frequently arrived at planning departments with duplicate image files embedded inside the same application reference. Officers had no automated tool to strip them out. Some did it manually. Many did not, and the files piled up.

At Southwark Council's planning department on Tooley Street, staff were already managing one of the highest application volumes in inner London. Tower Hamlets, which in 2023 processed more than 4,500 planning applications, faced similar strain. Both boroughs moved to hybrid working arrangements after 2020, which complicated document quality control further. A submission that might once have been caught at a reception desk arrived digitally with nobody checking the image manifest before a case number was assigned.

The Greater London Authority's Development and Environment team flagged the issue in its 2024 annual monitoring report, noting that validation failure rates across London boroughs had risen compared to pre-2019 levels, though it stopped short of attributing all of that rise to duplicate files alone. The Planning Portal's operator, the Ministry of Housing, Communities and Local Government, has acknowledged ongoing technical development work but has not published a specific timeline for a fix.

What It Means on the Ground

For applicants — whether a homeowner in Peckham adding a rear extension or a housing association submitting reserved matters on a 200-unit scheme in Walthamstow — a validation failure can mean a delay of four to eight weeks as corrected documents are resubmitted and re-queued. On larger schemes, where pre-application fees can run into tens of thousands of pounds, that delay compounds financing costs. The Chartered Institute of Housing has previously estimated that planning delays broadly add between £1,000 and £3,000 per unit to the cost of affordable housing development, though it has not broken out a specific figure for image-related validation failures.

Architects and agents who regularly submit through the Planning Portal have developed informal workarounds — compressing image files below 5MB, labelling each document with a unique date-stamp suffix, and avoiding PDF bundles that embed photographs rather than linking them. The London branch of the Royal Institute of British Architects has shared guidance through its member network. None of it is a structural fix.

The government's Planning and Infrastructure Bill, currently progressing through Parliament, includes provisions to modernise planning data standards. If enacted in its current form, it would require local planning authorities to adopt a common data schema by 2028, which in theory would eliminate the conditions that allow duplicate files to persist undetected. Until then, applicants and borough officers are managing around a problem that was, at its origin, a technical migration fault — one that three years later is still costing London time it does not have.