Special Intensive Revision (SIR) of Electoral Rolls — the Jharkhand Numbers

Open in the app — quiz, notes, Mistake Vault

The news

The Hindu reports that Jharkhand's SIR claims-and-objections deadline has been extended a second time, from September 4 to September 15 and now to September 30. When the draft rolls were published on August 5, the electorate stood at 63,24,116 — but 43,61,987 entries were flagged for removal under the categories of Absent, Shifted, Dead or Duplicate (15,92,194 as 'shifted', 14,50,810 as 'absent/untraceable', and 68,283 as 'duplicate'). Eligible citizens now have until September 30 to seek inclusion or objection.

Static syllabus linkage

Article 324–329 (ECI's powers & electoral machinery); Article 326 (universal adult franchise); Representation of the People Act, 1950 (S.21 — preparation of rolls) & 1951; Draft vs Final electoral rolls; delimitation linkage (the 84th Amendment freezes seat-shares till the first Census after 2026).

Why UPSC loves this

ECI's powers and electoral-roll integrity are tested almost every year in Prelims (institutional powers) and periodically in Mains as a governance/electoral-reform theme. A controversial administrative exercise like SIR — with a headline figure showing nearly 69% of the draft electorate flagged for possible removal in a single State — is prime examiner material for a 'critically examine' question on balancing roll accuracy against the constitutional guarantee of universal suffrage.

Prelims nuggets

SIR is conducted under Article 326 read with the RPA 1950; deletion reasons are classed as Absent, Shifted, Dead or Duplicate; Jharkhand's draft roll (5 August) listed 63,24,116 electors, of which 43,61,987 were flagged in these four categories.

Analysis

Frame this as a 'Type I vs Type II error' problem that no electoral-roll design eliminates simultaneously. Type I error — deleting a genuine voter — violates Article 326's affirmative promise of universal suffrage; Type II error — retaining a bogus or duplicate entry — undermines one-vote-one-value integrity and invites fraud. SIR, unlike routine annual revision, is a full re-verification exercise compressed into a fixed window, which structurally raises the error rate on both sides but especially Type I, because BLOs verifying an entire electorate in weeks default to 'non-response equals absent' rather than exhaustive multi-visit confirmation. The 69% flagging rate in Jharkhand's draft roll is too large to be explained by genuine deaths/duplication alone — it signals that 'shifted' and 'absent/untraceable' tags are catching large numbers of seasonal/labour migrants who remain legitimate residents but were simply not home when the BLO called. This mirrors the controversy around Bihar's 2025 SIR, suggesting a structural design flaw (compressed deadlines, single-visit verification, urban/migrant-heavy areas being hardest to reach) rather than a one-off Jharkhand problem. The political fight over whether deletions disproportionately hit poor, migrant or minority voters is ultimately an empirical claim that only disaggregated data can settle — but the burden-of-proof question (should the state have to justify each deletion, or should the citizen have to justify each re-inclusion?) is the real constitutional fault line.

Possible Mains question

"The Special Intensive Revision of electoral rolls, while intended to improve accuracy, risks disenfranchising genuine voters through opaque deletion criteria." Critically examine, and suggest institutional safeguards.

Model approach

Introduction: Define SIR versus routine revision, and state the paradox — an exercise built to improve accuracy that, if mismanaged, produces mass disenfranchisement. Body — argue in four steps: (1) the legitimate rationale for SIR (removing bogus/duplicate/dead entries protects one-person-one-vote integrity); (2) the disenfranchisement risk, using Jharkhand's ~69% flagging rate as evidence, and naming who bears this risk disproportionately — migrant workers, the urban poor, women who relocate after marriage; (3) whether existing safeguards (the claims-and-objections window, appellate review) are adequate in practice given literacy and digital-access constraints, or merely adequate on paper; (4) a brief comparative note — some democracies use automatic voter registration tied to other government databases specifically to avoid this trade-off. Conclusion: Roll accuracy should be pursued through technology-assisted, multi-source verification and genuinely long, well-publicised objection windows — not through compressed bulk exercises whose administrative convenience is bought at the cost of constitutional inclusion.

Administrator's brainstorm

As the District Election Officer of a Jharkhand-like constituency where nearly seven in ten draft-roll entries have been flagged for removal, what ground-verification checks would you insist on before any deletion becomes final?

Move from single-visit, non-response-equals-absent verification to a mandatory two-visit protocol at different times of day/week to catch shift and seasonal workers. Require corroboration from at least two independent sources (Aadhaar-linked address, ration card, utility bill, employer certificate) before any 'shifted/absent' tag is finalised, rather than accepting BLO non-contact alone. Run mohalla-level verification camps with local ward representatives and civil-society volunteers to catch cases BLOs miss, and maintain a time-stamped, photographic/GPS record of each visit so decisions are auditable. In short, shift the standard from 'delete unless the BLO happened to find them' to 'delete only on clear, corroborated evidence'.

How do you balance two competing public goods — a 'clean' roll free of bogus/duplicate entries, and the constitutional promise that no genuine citizen loses their vote to an administrative shortcut?

Treat enfranchisement as the constitutional default and deletion as the higher-burden exception — the presumption should favour retention unless there is affirmative, corroborated evidence of ineligibility, not merely an absence of confirmation. This reverses the practical incentive BLOs currently face (where an unverified entry defaults to deletion) and instead makes the administration responsible for proving a name should come off, not the citizen responsible for proving they still belong on it.

What would you tell a migrant worker registered at both his native village and his rented city address — fraud, or a structural gap the system hasn't solved?

Structural gap, not fraud, as long as he is not voting from both. The fix is a formal, low-friction 'address transfer' or portable-registration mechanism (ideally linked to Aadhaar-based address updates as corroborative evidence) that lets a migrant regularise his registration without being penalised for the system's own rigidity — the administrative failure is the absence of an easy transfer pathway, not the migrant's dual footprint.