"Technology-driven centralisation of electoral roll management may improve efficiency but strain the statutory architecture of electoral administration." Critically examine with reference to ECINET.

ECINET is the Election Commission of India's (ECI) single digital platform. It merges over 40 apps and portals into one system [1]. Its efficiency gains are real. But its central access controls do not fit easily with a law that gives roll-making to local officers. The problem is therefore missing safeguards, not the platform itself.

Efficiency gains of centralisation

• Integration: one login replaces fragmented apps such as Voter Helpline and cVIGIL, which cuts data mismatches [1].
• Citizen access: registration, e-EPIC download, Book-a-call with BLO and Know Your Candidate are offered in 22 Scheduled languages plus English [2].
• Roll integrity: a national database can detect duplicate entries of migrant voters. The Supreme Court upheld ECI's power to conduct the Special Intensive Revision (SIR) under Article 324 [5], and ECINET's beta version was piloted during the SIR [2].
• Security: central switches let headquarters quickly disable compromised logins.

Strain on statutory architecture

• ERO primacy: Section 13B, RP Act 1950 makes the Electoral Registration Officer responsible for each roll [3]. That power means little if the officer cannot see the data.
• Central "kill switches": the civic-tech audit Charchagram found a State-wise toggle for viewing enumeration forms and a button to disable State Nodal Officers [4]. One setting at headquarters can cut off a whole State's machinery.
• Collegial dissent: Election Commissioners Sandhu and Joshi objected to the "gradual centralisation" of ECINET [4]. This tests the internal checks of a multi-member Commission.
• Code over law: claims, objections and appeals all run through the ERO [3]. If statutory forms are changed in software, the Registration of Electors Rules, 1960 are bypassed.
• Opacity: the access rules came to light through an external audit, not an official disclosure [4].

On balance, centralising ECINET is administratively sound. It strains the statutory design only where control over data moves away from the officers the law holds accountable. The way forward is to:

• amend the 1960 Rules before changing forms in code;
• require written, logged reasons for every "disable" action, following Section 21(3)'s reasons requirement [3];
• publish a role-based access policy;
• guarantee EROs full visibility of their rolls.

ECI's own rule that statutory forms prevail over platform data [1] should guide these reforms, so that technology serves Article 324's promise of free and fair elections.