Delhi's Duplicate Image Problem: The Key Decisions That Will Define the Fix

Delhi's civic and administrative databases are carrying a problem that has quietly ballooned for years: duplicate images — repeated photographs attached to resident records, property files, and identity documents across multiple government portals — are now creating delays, errors, and, in some cases, wrongful rejections of legitimate applications. The immediate question facing the Delhi government is not whether to act, but how, and in what order.

The issue has sharpened because Phase 4 of the Delhi Metro expansion is generating fresh waves of land acquisition paperwork through the Delhi Metro Rail Corporation, while the Arvind Kejriwal-led AAP administration is simultaneously pushing its digitisation drive across municipal services. Two parallel processes, both generating large volumes of scanned identity photographs, have made the duplicate image backlog significantly worse over the past eighteen months.

Where the Problem Is Felt Most

In Shahdara district, residents applying through the Delhi e-District portal have reported applications bouncing back because photograph records from older aadhaar-linked submissions and newer municipal filings do not reconcile. Staff at the Patparganj sub-divisional magistrate office have been handling a growing queue of manual reviews as a result. Similarly, in Karol Bagh, traders renewing licences under the Delhi Municipal Corporation's unified licensing system have faced rejections tied to mismatched image records pulled from different database generations.

The South Delhi Municipal Corporation — now merged back into a unified MCD following the 2022 reunification — inherited at least three separate image repositories when the trifurcated bodies were brought back together. Those repositories were built on different software standards and have never been fully reconciled. That unresolved technical debt is now surfacing in the day-to-day processing of property tax filings and ration card renewals across localities from Mehrauli to Lajpat Nagar.

India's National Informatics Centre, which maintains the backend infrastructure for several Delhi government services, has identified de-duplication of biometric and photograph records as a priority task under the Digital India land records modernisation programme. The central government's Department for Promotion of Industry and Internal Trade has set a deadline of March 2027 for states to achieve a defined threshold of clean, non-duplicate records across citizen-facing portals — putting Delhi on a ticking clock.

The Decisions That Cannot Be Deferred

Three choices now sit at the top of the agenda. First, Delhi's IT department must decide which database is treated as the master record when two images conflict. Defaulting to the newest photograph risks disenfranchising residents whose most recent scan was done under rushed or low-quality conditions during pandemic-era digitisation camps held between 2020 and 2022 at venues including the Talkatora Indoor Stadium and district community centres. Defaulting to the oldest record raises separate problems around outdated images for people who have legally changed their appearance or documentation.

Second, the MCD and the Delhi government need to agree on a shared de-duplication algorithm. Using a human-review model alone is impractical at scale: MCD processes upwards of 1.8 lakh property-related transactions annually, according to figures published in the corporation's annual report. Automated image-matching tools exist but require procurement, testing, and a legal sign-off on what constitutes an acceptable match threshold — none of which has been completed.

Third, and perhaps most politically sensitive, is public communication. Residents who receive a notice that their photograph record has been flagged as a duplicate need a clear, simple grievance channel. The current process routes complaints through the CM Helpline 1076, which was not built to handle technical database disputes and regularly passes them back to department-level desks with no resolution timeline.

The practical next steps are not mysterious. Delhi's IT department is expected to table a de-duplication framework before the standing committee of the Legislative Assembly before the monsoon session closes in late July. Whether the committee accepts it without amendment, sends it back for revision, or allows it to lapse into the bureaucratic queue is the decision that will determine whether Delhi's duplicate image problem gets fixed before the March 2027 central deadline — or becomes the next inherited mess for whoever runs the city after the next election cycle.