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

Delhi's civic databases are carrying a quiet but costly burden: duplicate digital images embedded across multiple government record systems have inflated storage costs, slowed verification processes, and introduced errors into everything from ration card approvals to property tax filings. Officials at the Delhi Secretariat have known about the scale of the problem for months. The question now is who acts, when, and at whose expense.

The issue matters right now because Phase 4 of the Delhi Metro expansion — covering corridors through Janakpuri West, Tughlaqpur, and the aerocity link — has required fresh rounds of land acquisition and resident verification. Each verification depends on accurate identity records. When the same photograph appears under two or more citizen profiles in the Delhi government's e-District portal, approvals stall. Compensation cheques for displaced families in areas like Dwarka Sector 21 have reportedly been delayed for weeks while clerks manually reconcile conflicting records. That direct human cost is sharpening the urgency.

What the Records Show — and What They Don't

The National Informatics Centre, which manages the technical backbone of Delhi's e-District system, has previously estimated that image duplication rates in large state government portals can run as high as 12 to 18 percent of total records when identity documents from multiple legacy systems were merged without de-duplication protocols. Delhi's own portal consolidation — which brought together older Municipal Corporation of Delhi databases with the unified Delhi government system — happened in phases between 2019 and 2023, precisely the window when duplication risk is highest. No public audit specific to Delhi's current figure has been published.

The Delhi State Data Centre, located in Dwarka Sector 10, hosts the infrastructure in question. A separate set of records tied to the Delhi Development Authority's housing allotment system — particularly relevant for flats in Rohini and Narela — also carries legacy image files that predate the current verification standard. Both systems need a decision on who runs the de-duplication exercise: the NIC, a contracted private vendor, or an in-house team at the Chief Minister's Secretariat on Civil Lines.

The procurement question is politically charged. The AAP administration has historically resisted large IT contracts handed to outside vendors, preferring to route technology work through NIC or Delhi government departments. The BJP-led central government, which controls NIC's broader mandate, has its own preferred timeline for a nationwide identity record clean-up tied to the Aadhaar seeding programme, which the Union Ministry of Electronics and Information Technology has flagged as a 2026–27 budget priority. Whether Delhi's fix happens inside that national framework or separately is a genuine open question — and the answer determines both the cost and the timeline.

The Decisions Ahead

Three choices will shape what happens next. First, the Delhi government must decide by the end of this financial quarter — September 2026 — whether to issue a fresh Request for Proposal for a standalone de-duplication tool or to formally join the MEITY-led national exercise. The second decision sits with the Delhi Metro Rail Corporation: DMRC has discretion to pause certain land-compensation disbursements pending record verification, or to proceed on provisional approvals and correct records after the fact. Families waiting near the Lajpat Nagar station corridor affected by Phase 4 land work cannot afford an open-ended delay.

The third and most consequential decision involves transparency. The Delhi High Court has taken up related petitions concerning digital record accuracy in government welfare schemes before. Advocates at the Patiala House Courts complex have argued in earlier filings that citizens have a right to know when their records contain errors. A formal public disclosure mechanism — a dashboard showing the volume of duplicates identified, resolved, and pending — would change the accountability dynamic entirely. Without it, the clean-up happens invisibly, its progress impossible to verify.

The practical next step for Delhi residents is straightforward: anyone who has received a notice of discrepancy from the e-District portal, or whose Aadhaar-linked document check has returned a mismatch, should visit their nearest district Suvidha Kendra — there are currently 25 operating across the city — and request a manual record review. Waiting for the systemic fix to arrive is not a strategy. The systemic fix has not yet been decided.