New Jersey’s Voter Roll Problem Was a Design Choice, Not Just a Glitch
New Jersey has spent the last few months calling this a software error. That word choice matters, because it makes the story sound like a bug that slipped through testing. What came out in a House Judiciary Subcommittee hearing this month is different. The state’s voter registration system was never built to verify citizenship in the first place. The checkbox was the whole system.
Here’s what happened. Between June 2023 and June 2024, roughly 6,600 people registered to vote in New Jersey anyway. All of them had told the state’s Motor Vehicle Commission they were not U.S. citizens. Somewhere between 340 and 400 of them cast a ballot. (The exact number shifted depending on which witness or member was talking, and nobody in the room reconciled it. Worth remembering before anyone repeats a single figure as settled.) The state blamed its software vendor, Idemia, for what it called a serious error. That’s true as far as it goes. But the more useful question is why one coding mistake was able to put thousands of people on the rolls with nothing to catch it.
The design problem, not the bug
Justin Riemer, president of the election integrity group Restoring Integrity and Trust in Elections and a former deputy secretary of Virginia’s State Board of Elections, laid out the actual mechanism in his testimony. New Jersey’s registration system relied on a single attestation: a checkbox asking if you’re a citizen. That’s it. No backend cross-check. No verification against any other record the state already had. If someone handed an MVC clerk a green card, a document that says plainly “not a citizen,” the system would still offer them voter registration. The person had to actively opt out.
The state didn’t catch the problem because it was looking for non-citizens on the rolls. It caught the problem because a batch of records was missing a party affiliation field, a data quirk with nothing to do with citizenship. That’s how you find out your building doesn’t have smoke detectors: after somebody notices the wiring looks strange, not because anything alerted anyone to smoke.
And New Jersey isn’t the only state that built it this way. Riemer’s testimony flagged Oregon, which runs the same attestation-only, opt-out design. Oregon’s DMV staff misrecorded which documents applicants had presented. Nearly 2,000 people ended up registered without ever proving eligibility, and the state didn’t catch it for three years. Same architecture, same failure mode, longer to notice. That’s not a coincidence. That’s what happens when a state builds a registration pipeline with no verification step and calls the honor system a safeguard.
Whose job was it to check
Jason Sena, an election law attorney who practices in New Jersey, added a detail that got less attention than it deserved. State law puts the actual eligibility determination on county election officials, not the MVC. The MVC collects the data and passes it along. Someone downstream is supposed to verify it before registering anyone. That verification, by Sena’s account, didn’t happen consistently. He also pointed to public records from Hudson and Bergen counties. They show non-citizens registered both before and after the state’s own admitted window, and through channels other than the MVC. If that holds up, the state’s 6,600 figure only describes the part of the problem that one software patch happened to catch. It’s not the outer edge of the problem.
Why the popular fix might not fix this
The federal response on the table is the SAVE Act, which would require documentary proof of citizenship at registration nationwide. It’s the headline ask from two of the four witnesses. But the hearing’s fourth witness, Stephen Richer, the former elected Republican recorder of Maricopa County, Arizona, made a point that’s hard to argue with. Arizona has required documentary proof of citizenship since 2005. It had its own major registration data error anyway: a years-long coding problem in the state’s Motor Vehicle Division mismarked more than 218,000 voters as having provided proof of citizenship when it was unclear whether they actually had.
That’s the actual lesson here. A documentation requirement fixes what someone claims about themselves. It does nothing about what happens to that claim once it hits a database that two state agencies built separately and never fully tested together. New Jersey’s failure and Arizona’s failure came from the same place: nobody verified that the handoff between systems worked the way everyone assumed it did. A citizenship checkbox on a form doesn’t catch that. A backend cross-check against a record the state already holds might.
What’s still open
A few things came up in the hearing that never got resolved on the record. Nobody could say which specific municipalities or districts saw illegal votes cast. That means the “this could have swung a close race” framing that ran through most of the questioning stayed hypothetical. The chairman referenced internal Idemia documents he says show the state tested and approved the flawed specifications. Those documents were described in the hearing, not entered into evidence or examined by anyone in the room. And one member alleged, without naming a name, that a witness at the table had ties to a separate election scheme entirely. That claim went unanswered and unattributed.
None of that changes the core finding. New Jersey’s system didn’t have a way to catch this short of luck. Neither did Oregon’s. The fix that would actually address that isn’t a stronger checkbox. It’s making sure the handoff between agencies actually works. The agency that collects the data and the agency that registers voters both need to check what they’re supposed to check. That has to happen before the record goes live, not after someone notices the numbers look off.
New Jersey has spent the last few months calling this a software error. That word choice matters, because it makes the story sound like a bug that slipped through testing. What came out in a House Judiciary Subcommittee hearing this month is different. The state’s voter registration system was never built to verify citizenship in the first place. The checkbox was the whole system.
Here’s what happened. Between June 2023 and June 2024, roughly 6,600 people registered to vote in New Jersey anyway. All of them had told the state’s Motor Vehicle Commission they were not U.S. citizens. Somewhere between 340 and 400 of them cast a ballot. (The exact number shifted depending on which witness or member was talking, and nobody in the room reconciled it. Worth remembering before anyone repeats a single figure as settled.) The state blamed its software vendor, Idemia, for what it called a serious error. That’s true as far as it goes. But the more useful question is why one coding mistake was able to put thousands of people on the rolls with nothing to catch it.
The design problem, not the bug
Justin Reamer, who runs an election administration watchdog group and previously served as Virginia’s deputy elections secretary, laid out the actual mechanism in his testimony. New Jersey’s registration system relied on a single attestation: a checkbox asking if you’re a citizen. That’s it. No backend cross-check. No verification against any other record the state already had. If someone handed an MVC clerk a green card, a document that says plainly “not a citizen,” the system would still offer them voter registration. The person had to actively opt out.
The state didn’t catch the problem because it was looking for non-citizens on the rolls. It caught the problem because a batch of records was missing a party affiliation field, a data quirk with nothing to do with citizenship. That’s how you find out your building doesn’t have smoke detectors: after somebody notices the wiring looks strange, not because anything alerted anyone to smoke.
And New Jersey isn’t the only state that built it this way. Reamer’s testimony flagged Oregon, which runs the same attestation-only, opt-out design. Oregon’s DMV staff misrecorded which documents applicants had presented. Nearly 2,000 people ended up registered without ever proving eligibility, and the state didn’t catch it for three years. Same architecture, same failure mode, longer to notice. That’s not a coincidence. That’s what happens when a state builds a registration pipeline with no verification step and calls the honor system a safeguard.
Whose job was it to check
Jason Sena, an election law attorney who practices in New Jersey, added a detail that got less attention than it deserved. State law puts the actual eligibility determination on county election officials, not the MVC. The MVC collects the data and passes it along. Someone downstream is supposed to verify it before registering anyone. That verification, by Sena’s account, didn’t happen consistently. He also pointed to public records from Hudson and Bergen counties. They show non-citizens registered both before and after the state’s own admitted window, and through channels other than the MVC. If that holds up, the state’s 6,600 figure only describes the part of the problem that one software patch happened to catch. It’s not the outer edge of the problem.
Why the popular fix might not fix this
The federal response on the table is the SAVE Act, which would require documentary proof of citizenship at registration nationwide. It’s the headline ask from two of the four witnesses. But the hearing’s fourth witness, Stephen Richard, a former elected Republican county recorder in Arizona, made a point that’s hard to argue with. Arizona already requires documentary proof of citizenship. It had a nearly identical software failure anyway. A bug in the interface between the motor vehicle division and the state election system marked people as verified when they weren’t.
That’s the actual lesson here. A documentation requirement fixes what someone claims about themselves. It does nothing about what happens to that claim once it hits a database that two state agencies built separately and never fully tested together. New Jersey’s failure and Arizona’s failure came from the same place: nobody verified that the handoff between systems worked the way everyone assumed it did. A citizenship checkbox on a form doesn’t catch that. A backend cross-check against a record the state already holds might.
What’s still open
A few things came up in the hearing that never got resolved on the record. Nobody could say which specific municipalities or districts saw illegal votes cast. That means the “this could have swung a close race” framing that ran through most of the questioning stayed hypothetical. The chairman referenced internal Idemia documents he says show the state tested and approved the flawed specifications. Those documents were described in the hearing, not entered into evidence or examined by anyone in the room. And one member alleged, without naming a name, that a witness at the table had ties to a separate election scheme entirely. That claim went unanswered and unattributed.
None of that changes the core finding. New Jersey’s system didn’t have a way to catch this short of luck. Neither did Oregon’s. The fix that would actually address that isn’t a stronger checkbox. It’s making sure the handoff between agencies actually works. The agency that collects the data and the agency that registers voters both need to check what they’re supposed to check. That has to happen before the record goes live, not after someone notices the numbers look off.
Leave a Reply