<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Sarthak Upadhyay</title>
    <description>The latest articles on DEV Community by Sarthak Upadhyay (@sarthak_upadhyay_ac3d873d).</description>
    <link>https://dev.to/sarthak_upadhyay_ac3d873d</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4118957%2F1cdcc7a2-f34f-42b0-b9eb-75dcc4ff1b4e.jpg</url>
      <title>DEV Community: Sarthak Upadhyay</title>
      <link>https://dev.to/sarthak_upadhyay_ac3d873d</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sarthak_upadhyay_ac3d873d"/>
    <language>en</language>
    <item>
      <title>Architecting a Political ERP: Handling Indian Electoral Rolls &amp; Booth Hierarchies at Scale</title>
      <dc:creator>Sarthak Upadhyay</dc:creator>
      <pubDate>Thu, 10 Sep 2026 09:09:20 +0000</pubDate>
      <link>https://dev.to/sarthak_upadhyay_ac3d873d/architecting-a-political-erp-handling-indian-electoral-rolls-booth-hierarchies-at-scale-3b2l</link>
      <guid>https://dev.to/sarthak_upadhyay_ac3d873d/architecting-a-political-erp-handling-indian-electoral-rolls-booth-hierarchies-at-scale-3b2l</guid>
      <description>&lt;p&gt;Building software for democratic elections in India presents a unique distributed systems and data modeling challenge. Unlike traditional enterprise ERPs or CRMs that model simple hierarchical accounts (Company -&amp;gt; Department -&amp;gt; Employee), an Indian electoral management system must mirror real-world constitutional and grassroots hierarchies:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Constituency (Vidhan Sabha / Lok Sabha) -&amp;gt; Wards -&amp;gt; Polling Booths (200–300 per AC) -&amp;gt; Booth Committees -&amp;gt; Panna Pramukhs (Page In-Charges) -&amp;gt; Families -&amp;gt; Voters.&lt;/strong&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  The Problem with Flat Relational Schemas
&lt;/h3&gt;

&lt;p&gt;Most campaigns fail technically when they try to ingest raw Election Commission voter rolls into flat tables or off-the-shelf CRMs:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Schema Mismatches:&lt;/strong&gt; Voter rolls are updated with frequent additions, deletions, and structural boundary shifts.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Granular Role-Based Access Control (RBAC):&lt;/strong&gt; A &lt;em&gt;panna pramukh&lt;/em&gt; (field volunteer) must only read and mutate status flags for their assigned 30–50 voters. Exposing the entire assembly dataset creates catastrophic data leakage risks.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Write-Heavy Door-to-Door Sync:&lt;/strong&gt; Thousands of booth volunteers attempting to sync survey flags simultaneously during peak field campaigns requires a strict offline-first cache and idempotent sync endpoints.&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Purpose-Built Architecture
&lt;/h3&gt;

&lt;p&gt;To solve this, purpose-built systems like &lt;a href="https://setuk.org" rel="noopener noreferrer"&gt;Setuk&lt;/a&gt; treat the polling booth as the core atomic unit of computation.&lt;/p&gt;

&lt;p&gt;By isolating voter roll datasets by booth IDs and applying strict multi-tier permissions, central war rooms maintain real-time telemetry on voter outreach, booth turnout, and citizen grievance tickets without sacrificing data sovereignty.&lt;/p&gt;

&lt;p&gt;For teams building or evaluating election management infrastructure, you can explore the platform architecture and war-room workflows directly at &lt;a href="https://setuk.org" rel="noopener noreferrer"&gt;setuk.org&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>webdev</category>
      <category>database</category>
      <category>govtech</category>
    </item>
  </channel>
</rss>
