Every worker on your constituency reads the same voter roll — and each one sees only the part that is theirs. Not a party platform. Your seat, and only yours.
How it works
The roll is not copied, exported or split. Everyone opens the same data, and what they can see is decided by who they signed in as — so nobody works from a stale spreadsheet, and nobody sees a booth that is not theirs.
Your constituency's voters, families and households behind every screen. Updated once, visible everywhere, immediately.
A booth worker opens their booth. An area coordinator opens their cluster. Nobody has to be trusted to look away from the rest.
Lists to call, rolls to print, households to visit — output your team can carry out of the door, not charts to admire.
Your team
The same sign-in works at whichever level a person belongs to. No second account to issue, and nothing to re-explain when somebody moves between roles.
The shared room
Every level signs in to the war room with the login it already has — the seat, a cluster, a booth — and each sees its own part of the picture. It is where the day's picture comes together, and where the roll gets looked at rather than worked.
Rules against real columns. Each one states what it tests, how many rows break it, and opens the list.
Where duplicate entries collect, and how far the roll has drifted from the latest count.
Sign-ins and app faults, newest first, with the level each came from.
Community, religion, age and gender for the seat, off the same roll everyone else reads.
A television on a loop: six channels, each screen held for eight seconds. Nothing to click, nobody driving it — it just runs.
A war room login is admitted at the assembly, cluster and booth sites too, so going to look at one booth's own screen is not a second sign-in.
The work
Day to day, on a phone, standing in a lane. Not a reporting suite.
Find a voterBy the start of a name, or an EPIC number in full
Work a boothEvery voter in it, in order
Families & householdsVisit a house, not a row in a list
Sections & serialsThe order the roll is printed in
Record what you findKept beside the roll, never over it
Community viewOBC · ST/SC · Minority · General
Caste & religionWhere your support actually sits
Age & genderWho to reach, and how
SurnamesCommunity clusters across your booths
Roll changesAdditions and deletions between revisions
Past resultsHow your seat and its booths have voted
Duplicate entriesRepeated name, relation and age — and the booths carrying them
One voter
Two layers, and the difference is the point. Underneath is the published roll, which nobody on your team can change. Over it sits what your workers find at the door. Both show on the same screen, so it is always clear which is which.
From the roll · read only
NameAs printed, in Hindi and in English
EPIC numberThe identifier that survives a revision
Age and genderAs the roll gives them
RelationThe father or husband named against the entry
House numberThe address the roll carries, Hindi and English
Booth, section, serialWhere the entry sits on the page
Roll statusActive, or deleted at a revision
List and roll typeOriginal or supplement; addition or deletion
SurnameAs printed, and the main surname behind it
CommunityOBC · ST/SC · Minority · General, with what it was matched on
What your team adds
Mobile numberThe roll carries none, so this is the only one there is
Caste and communityRecorded at the door, not inferred from a name
FamilyFather, mother and spouse, by name
CorrectionsName, surname, house number, relation
Occupation and educationWhat the household does
Marital status and incomeWhere it has been asked
Party and supporter typeWhich way they lean, as your worker heard it
Voting interestWhether they intend to turn out at all
Nothing in the second list overwrites the first. The published roll is read only in every app, so a correction sits beside the original instead of replacing it and both stay visible. Every field a worker changes is written down against them, with the moment they changed it, so an edit can be traced and put back.
Keeping in touch
Inside the same app, scoped the same way as everything else. A booth account cannot open another booth's thread by guessing at its number, because the query filters on the account rather than on what was asked for.
One thread per booth and per cluster, and an inbox of all of them on your side. The thread belongs to the booth, not to a person: everyone signed in there reads and continues the same conversation, so a handover does not start a blank one.
Write once and it reaches every booth and cluster on the seat. Pin the ones that should stay at the top, and give the rest a date after which they stop showing. Booths receive notices; they do not post them.
A rally, a meeting, a training — venue and start time. Cancelling does not delete: the event stays on the list with its title struck through, because people have already arranged their day around it.
An open conversation keeps itself current. It asks every couple of seconds whether anything has arrived and redraws only when something has, so a phone left sitting on the chat screen is not working all day.
Election AI
Not a chat box, and it will not answer questions about the seat. You pick a booth's rows and the categories to cut them by, say how long a write-up you want, and it returns one.
That booth's own rows — gender, age, surname, caste, community, religion, occupation. It is handed nothing your login could not already open for itself.
Seven kinds of write-up, from about eighty words to about twelve hundred: a headline, an executive summary, a political read, a turnout plan, suggestions, conclusions, or the long one.
It is told to analyse and not to argue for a party. Read it as a second opinion on the numbers, not as advice.
Each run records how much of what it needed was actually filled in, so a confident paragraph written over four fields is visibly that.
With the figures it was written from, so opening an old one shows what was true then rather than quietly re-reading today's numbers.
Any report goes to a PDF for the people who would rather have it on paper.
Where it has not been switched on for an account, the page says so and nothing is sent.
Why it helps
Replaces the spreadsheets, the printed rolls and the WhatsApp forwards.
Scope is enforced at sign-in, not by asking people to be careful.
What you see and what the booth worker sees cannot drift apart.
Coverage is visible, so effort goes where it has not been yet.
The people at the door are not carrying a laptop.
Your constituency's data, not shared into a wider party system.
Getting started
None of this waits on the team being ready. The roll is in place before anybody signs in, so the first person to log in already has something to work from.
Your constituency arrives already split into its booths, each with its own totals worked out, before the first sign-in.
One for the seat, one for each cluster, one for each booth. The scope is fixed to the account, so there is no setting to get wrong later.
Put a name and a mobile number against every cluster and booth login. Until you do, a login is a number and nobody knows whose phone it is on.
Helpers are not accounts. The booth keeps its own record of who is working it, with a number and what they do, and maintains it itself.
The roll does not move. What your team records does, and it is the only figure on the site that changes while people are out.
Each booth is measured against its own roll rather than the seat's, so a small booth half done ranks above a large one barely started.
Android apps
Each person installs the one for their level. Same sign-in as the website.
The whole constituency — booth by booth, with the roll, the communities and the coverage picture behind it.
A cluster of booths and the workers in them — what has been covered, and what is still open.
One booth, voter by voter and family by family. Lists to call, rolls to print, houses to visit.
A television in the office showing the day's picture on a loop. Runs on an Android TV set or box, driven by a remote, with no touch controls.
For the people running the system — accounts, access and the health of the setup. Issued to the IT team rather than the field.
Android only, installed by hand rather than from the Play Store, so your phone will warn about installing from outside it. These carry new package identifiers: a new build will not install over an older app of a different name, so remove the old one first. The office display and the support console are listed here for completeness — ask for those two directly.
Before you ask
Including the ones where the answer is no.
The people you give a login to, and only the part that is theirs. The scope comes off the account, never off the address bar: a booth login asking for a voter in the next booth is told there is no such record, because as far as that query is concerned there is not.
No. A booth login reaches its booth. A cluster login reaches its own booths. The seat reaches all of them. It is checked on every page that needs a sign-in rather than once at the door, so a pasted link is refused the same way a typed one is.
No, and it does not pretend to. The apps are the same site in a window; with nothing to reach they show a plain screen and a retry button rather than yesterday's figures. Anything you save out of one lands in the phone's Downloads.
Their login only ever opened one booth, so there is nothing wider to account for. Every field they recorded is written down against them and can be put back. A helper who stops is marked inactive on the booth's own list rather than removed, so next time round you still know who they were.
Yes, and it is built for it. The conversation belongs to the booth, so a colleague's message appears under their own name in the same thread. Each person's choice of how much of the app to show is remembered separately, so handing the phone over does not reset the other's.
Not the roll itself — it is read only everywhere. A correction your worker records is stored beside the original and the record shows both, so nobody decides on your behalf which of the two is right.
What is included, and what happens to your account data, are set out on the services and privacy pages. Anything else, ask.