Delhi's Duplicate Image Problem: Why Bad Data Is Costing Residents Real Money and Real Time

The filing clerk at the South Delhi Municipal Corporation office in Saket told the family their land mutation was stuck — again. The problem was not paperwork, not a pending fee. It was a photograph. The digitised property file had pulled in a duplicate image from another applicant's submission, and until the mismatch was cleared, the record was frozen in a backlog queue that stretched back to February 2026.

It sounds like a bureaucratic footnote. It is not. Across Delhi's layered stack of government digital systems — the Delhi Land Records system maintained under the Revenue Department, the ration card database under the Food and Civil Supplies Department, and the voter ID rolls managed by the Delhi Chief Electoral Officer — duplicate and misidentified images have become a structural problem with direct, material consequences for ordinary people. Property transactions stall. Welfare entitlements get suspended. Identity verification at bank branches and telecom counters fails. The person bearing the cost is almost never the system; it is the resident.

Why the Problem Has Grown Worse in 2026

The timing matters. Delhi's various departments have been in an aggressive phase of database consolidation through late 2025 and into 2026, partly driven by the central government's push to integrate state records into national platforms under the Digital India mission. When separate databases merge, duplicate image entries multiply. A photograph uploaded to a ration card record in 2018 through a fair price shop in Sangam Vihar may reappear, attached to the wrong name, when that record migrates into a unified portal. The system flags it as a match. The resident has no idea why their card stopped working at the ration shop on Devli Road.

The scale is significant. Delhi has more than 20 million registered voters, roughly 4.5 million active ration card holders, and tens of thousands of property mutation applications processed annually through the six revenue district offices. Even a one percent error rate across those databases translates to hundreds of thousands of affected records. Civic tech researchers studying Indian municipal digitisation have noted that image-level errors — wrong photograph attached, low-resolution scans misread by automated systems, or identical file names overwriting distinct images — consistently outpace text-level errors in legacy migration projects.

Residents in high-density resettlement colonies such as Madanpur Khadar in southeast Delhi and Sultanpuri in the northwest are disproportionately affected. These areas have large populations of migrant families who relied on older, paper-based documentation before digitisation. Their records were often scanned in bulk by contracted agencies between 2016 and 2021, a period when quality control varied considerably across vendors. When a bulk scan produces a blurred or duplicated image, the automated deduplication tools built into newer platforms can reject or misfile the whole record.

What Residents Can Actually Do Right Now

The Delhi Revenue Department runs a grievance portal — the e-District Delhi platform — where residents can flag documentation errors including photograph mismatches. The process requires the applicant to upload a fresh, self-attested photograph along with a supporting identity document and to cite the specific application or record number. Complaints filed through e-District are assigned a token number and are supposed to receive acknowledgment within three working days, though resolution timelines vary by case type.

For ration card image disputes, the Food and Civil Supplies Department has a dedicated helpline — 1967 — and walk-in grievance counters at Circle Offices including those at Karol Bagh and Laxmi Nagar. Residents carrying original Aadhaar cards and two passport-size photographs can request an on-the-spot correction for straightforward mismatch cases, according to the department's publicly posted Standard Operating Procedure updated in March 2026.

The broader fix requires the departments themselves to run systematic image deduplication audits before the next round of database integration, expected later in 2026 as part of the Unified Delhi Citizen Services project. Until that happens, the burden of proof stays exactly where it should not be — with the resident standing at a counter in Saket, or Devli Road, or Sultanpuri, trying to explain why the photograph in the government's file is not theirs.