Voter ID Isn't Necessary From a Systems Design Perspective
Sharper Mind
SubscribeSign in
Voter ID Isn't Necessary From a Systems Design Perspective<br>An engineer's view on voter ID
Rob May<br>Aug 04, 2026
Share
Every few years, a familiar argument comes around like a comet: You need an ID to buy a beer, board a plane, or rent a jet ski. Why not to vote?<br>It is a good line. It has survived decades of political combat because it appeals to something most of us feel in our bones — that important things should require proof. I don’t think people who make this argument are acting in bad faith. I think they are running a mental model that fits almost everything else in modern life and happens not to fit this one thing.<br>The model is the point-of-sale transaction. You show up, you present credentials, the clerk decides, the transaction clears. Bar, airport, bank teller. Identity is verified at the moment of the exchange, because there was no moment before the exchange in which to verify it. The bartender has never met you and will never see you again. He has one shot.<br>Elections don’t work like that, and here’s the thing: they never did. An election is not a point-of-sale system. It is an asynchronous, stateful database with a months-long onboarding process, a distributed write phase, and collision detection. Once you see it that way, the ID debate stops looking like a fight about how much security we want and starts looking like a design review — one in which the proposed feature has already been implemented somewhere else in the stack.<br>The authentication already happened. You just weren’t in the room.
Ask any engineer where the identity check belongs in a system like this and you’ll get the same answer: at account creation, not at every login.<br>That’s precisely where it sits. When you register to vote, you hand over a driver’s license number or the last four digits of your Social Security number, plus your name and date of birth. Under the Help America Vote Act, that data gets run against the state motor-vehicle database and, where necessary, against Social Security Administration records. States also periodically scrub their rolls against vital-records data to remove the deceased, and against interstate crosscheck systems to catch people who’ve moved.<br>By the time you walk into a gymnasium in November, the system has already decided who you are. The credential check is done. It happened in July, in a database, against federal and state records, with more rigor than a poll worker squinting at a laminated card could ever apply in eleven seconds.<br>This is not a loophole. It’s the architecture. And it’s the same architecture you rely on every day. Your bank verified your identity when you opened the account — documents, SSN, address history, the whole ceremony. It does not re-verify your birth certificate every time you swipe. It checks a token against a pre-authorized record. Nobody calls that a security failure. We call it a well-designed system.<br>Your name and address aren’t a credential. They’re a query.
Here’s where the intuition really goes sideways. When the poll worker asks for your name and address, most people hear prove who you are. That’s not what’s happening. She’s not establishing your identity from scratch. She’s running a lookup.<br>Your name and address are composite search keys. They locate one row in a poll book, which is itself a geographically sharded slice of the state’s master file. She isn’t authenticating you. She’s finding you.<br>And the address is doing a second job that has nothing to do with security at all. In American elections, geography determines what you’re entitled to vote on. Your address routes you to the right ballot style — the correct school board, the correct city council seat, the correct state house district. Get the address wrong and the system doesn’t hand a ballot to an impostor; it hands the wrong ballot to the right person. Address collection is a routing function that people have mistaken for a security function, which is roughly like assuming your ZIP code is your password.<br>The system’s real defense is that it notices.
The best security feature in the voting system is the one nobody talks about, because it’s boring: the poll book records that you voted.<br>The moment your name is found, your state flips. has_voted goes from false to true. It sounds trivial. It is the entire ballgame.<br>Consider what an in-person impostor actually has to do. He must know the exact name and current registered address of a real voter in the specific precinct he’s standing in. He must know that this person hasn’t voted yet — and won’t show up later. He must do it in a room frequently staffed by neighbors, retirees, and the sort of civically-minded volunteers who have lived on that street for thirty years and know exactly who lives at 412 Maple.<br>If he gets any of that wrong, the system throws an exception. The real voter arrives, the poll book shows the record already marked, and the machinery of...