London's Duplicate Image Problem: The Key Decisions Ahead for Planning and Housing Records

London's planning system is sitting on a quietly growing administrative crisis. Across dozens of borough councils, duplicate images attached to planning applications — identical photographs filed under different reference numbers, or mismatched site photos swapped between entirely separate developments — are creating delays, legal exposure, and in some cases, invalid approvals. The problem is not new, but pressure from the Starmer government's planning reform agenda has forced it into sharper focus.

The immediate trigger is the Planning and Infrastructure Bill, which passed its second reading in the Commons in May 2026. The legislation pushes councils to digitise their planning registers fully by a deadline that the Ministry of Housing, Communities and Local Government has set for the end of the 2026-27 financial year. That means every supporting document — including site photographs and elevation drawings — must be verifiable, correctly attributed, and free of duplication before records go live on the new national planning data portal.

Where the Problem Shows Up on the Ground

The issue is visible in practice at the coalface of London's busiest development corridors. Tower Hamlets Council, which handles some of the highest volumes of planning submissions in England, acknowledged earlier this year that its legacy casework system — used for applications submitted before 2021 — contained a significant number of document errors including duplicate image attachments. Southwark Council, processing major applications along the Old Kent Road regeneration zone and around Elephant and Castle, has flagged similar issues in internal audit processes as it migrates data to a new digital platform.

The Greater London Authority's own planning team, which handles strategic applications above a certain threshold, runs a separate document management system. Coordination between the GLA's portal and borough-level registers has produced what planning lawyers describe in general terms as a fragmentation problem: the same image appearing under conflicting reference numbers across two systems, with no clear record of which version is authoritative. For applicants on major schemes — say, a mixed-use tower on the Greenwich Peninsula or a residential block in Wembley — that ambiguity can stall reserved matters applications by weeks.

The Local Government Association estimated earlier in 2026 that English councils collectively process more than 500,000 planning applications annually. London boroughs account for a disproportionate share of the most complex, multi-document submissions. Any systemic error rate in image handling compounds across that volume fast.

What Needs to Happen — and Who Decides

Three decisions will determine how this gets resolved. First, the MHCLG must clarify whether the national planning data portal will accept retrospective corrections to legacy records, or whether boroughs must formally withdraw and re-submit affected applications. That distinction matters enormously for developers with live permissions; a forced re-submission on a scheme already under construction on, say, Stratford High Street or Canning Town's Rathbone Market site could trigger contractual penalties.

Second, individual councils must decide how to prioritise their correction queues. Tower Hamlets and Southwark are understood to be piloting automated image-matching software that flags probable duplicates for human review. The question is resourcing: planning departments across London have faced staffing pressures for years, and the additional workload of a full document audit is not trivial.

Third, the Mayor of London's office will need to take a position on whether the GLA's strategic planning portal should serve as a single authoritative image repository for major applications, with boroughs drawing from it rather than maintaining parallel records. City Hall has not yet published a formal policy on this point.

For developers, architects, and planning consultants operating in London right now, the practical advice is straightforward: audit your live applications before the borough does. Check that every image in your submission matches the correct plot, elevation, and planning reference. If you find a mismatch, notify the case officer in writing and request a formal correction note on the file. Waiting for the council to catch the error puts the timeline — and potentially the permission itself — in someone else's hands. The window for orderly self-correction is open, but it will not stay open indefinitely as the MHCLG's digitisation deadline approaches.