SIR Deletions — Elector Numbers Fall Below 2025 Turnout in a Third of Delhi's Seats

Open in the app — quiz, notes, Mistake Vault

The news

A Hindu Data Point analysis finds that in more than one-third of Delhi's 70 Assembly constituencies, deletions under the Special Intensive Revision (SIR) have left the draft roll with fewer electors than the number of people who actually voted in the February 2025 Assembly election. Delhi's electoral rolls had 1.56 crore electors in February 2025, of which 94.9 lakh had voted; after two stages of culling — a pre-SIR deletion of close to 11 lakh electors and a further 47.6 lakh deleted during SIR itself — the draft roll is now down to just 97.5 lakh electors, only 2.6 lakh more than the 94.9 lakh who voted in 2025. The Tughlakabad constituency saw the deepest cut, with only 1,00,386 electors left on rolls that had 1,14,961 actual 2025 voters — implying the roll is now smaller than the number of people who are certain to be genuine, verified voters.

Static syllabus linkage

Article 324–329 (ECI's powers and electoral machinery); Article 326 (universal adult franchise); Representation of the People Act, 1950 (Section 21, preparation of electoral rolls); the distinction between draft and final rolls; the constitutional 'buffer' logic built into roll revision to accommodate ordinary residents who did not vote but remain eligible.

Why UPSC loves this

SIR's disenfranchisement-risk debate — already a hot Mains theme after Bihar (2025) and Jharkhand (covered in this digest previously) — has now produced hard, ward-level arithmetic for Delhi. A question that asks you to interpret an actual dataset (electors vs turnout) rather than recite the debate abstractly is exactly the kind of 'applied' framing UPSC has been moving toward.

Prelims nuggets

Delhi's February 2025 electorate: 1.56 crore, of which 94.9 lakh (60.8%) voted; current draft roll after SIR: 97.5 lakh electors; Tughlakabad constituency has only 1,00,386 electors against 1,14,961 people who voted there in 2025 — a shortfall, not merely a thin buffer.

Analysis

The analytical trick in this story is a simple but powerful benchmark: since everyone who voted in 2025 was, by definition, a real, verified elector at that time, any constituency where today's roll has fewer electors than that turnout figure must have deleted at least some genuine voters, not just bogus or dead entries — the deletions have eaten into the 'floor' of confirmed real voters, not just the 'buffer' of unconfirmed ones. This reframes the SIR debate away from abstract disenfranchisement fears toward a falsifiable test: compare draft-roll size to last-election turnout, constituency by constituency. Delhi's SIR ran in three phases with differing 'buffer' shrinkage — the article notes Phase 3 constituencies show the smallest buffer (most aggressive deletions), suggesting later phases either learned to delete more aggressively or faced tighter deadline pressure as the exercise progressed. This is a testable hypothesis for a strong answer: if deletion aggressiveness increases as SIR nears its deadline, that points to a process-design flaw (verification rigour trading off against time pressure) rather than a one-off implementation error. The comparative State-wise buffer data (Bihar's Phase 1&2 seats show large buffers, Karnataka's Phase-3-type seats show much smaller ones) also lets you argue SIR's error rate is not uniform — it is shaped by how compressed the revision window was in each region, which is itself an administrable, fixable variable rather than an inherent flaw in the exercise.

Possible Mains question

"Where a Special Intensive Revision leaves an electoral roll smaller than the number of people who voted at the last election, the exercise has deleted genuine voters, not merely non-existent ones." Examine this claim using Delhi's SIR data, and suggest procedural safeguards that would prevent such outcomes.

Model approach

Introduction: State the benchmark test — draft roll size versus last-election turnout — as a way to convert an abstract disenfranchisement debate into a falsifiable, ward-level claim. Body: (1) explain why turnout is a reliable floor for 'genuine elector' counts, and why falling below it is different from a shrinking buffer; (2) present the Delhi evidence, including the Tughlakabad-type worst cases; (3) analyse the phase-wise pattern — later SIR phases showing smaller buffers — as evidence of a deadline-driven verification trade-off, not random error; (4) propose fixes: staggered, non-compressed verification windows, mandatory buffer floors, and independent audit sampling before deletions are finalised. Conclusion: Argue that SIR's core objective (roll accuracy) and its current execution (compressed, single-pass verification) are in tension, and that fixing the timeline is more urgent than abandoning the exercise.

Administrator's brainstorm

As a Chief Electoral Officer reviewing SIR results, how would you use the 'roll below turnout' test operationally, before rolls are finalised?

Run this comparison as a mandatory automated check on every constituency before finalisation — any constituency where the draft roll falls at or below the previous election's turnout should be flagged for a second, independent verification pass rather than allowed to proceed to the final roll, treating the flag as a hard gate rather than an advisory statistic.

How would you redesign SIR's phased rollout so that later phases don't show more aggressive deletion patterns than earlier ones?

Decouple the verification timeline from a single fixed nationwide deadline — allocate each phase's window based on the actual number of entries requiring re-verification in that region, and give later phases the same per-elector verification time as earlier ones got, rather than compressing the remaining work into whatever time is left before a common deadline.