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.

Meta description: Trump signed a meat-processing order for ranchers. A beef tariff question went unanswered. Here’s what both policies actually do, and don’t.

President Trump hosted ranchers and farmers at the White House to sign two executive orders. One opens direct-to-consumer meat processing outside the “big four” packing companies. The other authorizes lethal control of federally protected gray wolves. It was billed as the biggest rancher-relief package in decades. Then, in the same room, a reporter asked about a beef tariff suspension that lets Argentine and Brazilian imports undercut the very ranchers the event was built to celebrate. Nobody on stage reconciled the two.

What the meat-processing order actually does

The headline policy lets ranchers and farmers process and sell meat directly to consumers without routing it through what Trump repeatedly called the “big 4” meatpacking processors. That’s a small handful of companies that dominate U.S. meat processing. Trump framed it as ending a monopoly: “For the first time ever, we’re going to give farmers and ranchers the right to process their own food.”

That’s the “first time ever” framing the administration is leaning on. It’s a real, structural change: a rancher can now slaughter and sell their own beef without shipping cattle hundreds of miles to a processing plant they don’t control. The order also directs regulators to streamline the health and safety rules governing that process. Trump and the ranchers present argued small-scale, on-site operations can be inspected just as rigorously as large plants: “I would be willing to say that our ranches will be more sanitary than those plants,” Trump said. He also noted that two of the four dominant processors are based in Brazil, folding foreign ownership into the “monopoly” framing. The day’s later news would cut against that same narrative.

Layered into the same order is a country-of-origin labeling requirement for foreign beef. Trump was vague on timing, saying only that it “is also gonna be a little bit involved with congress” and would be sent to lawmakers “right away.” No firm date was given, and implementation depends on legislative action the administration doesn’t fully control.

Agriculture Secretary Brooke Rollins, appearing alongside Trump, said the orders contain four major provisions in total. She noted they follow a related rollout she announced earlier in the week in Nebraska. American Farm Bureau Federation president Zippy Duval and Wisconsin rancher (and former NFL player) Joe Thomas both spoke in support. Duval framed the processing change as a growth opportunity for “small, beginning young farmers.”

The beef tariff tension nobody in the room reconciled

Here’s the contradiction: the entire premise of the meat-processing order is cutting out middlemen to strengthen domestic ranchers’ market power. In the same press session, a reporter asked Trump directly about a separate, standing decision: the administration’s suspension of tariffs on imported ground beef.

“It’s coming from Argentina. It’s coming from Brazil. It’s coming from a couple of other places.” — President Trump, asked where the tariff-exempted beef imports originate

A follow-up referenced a prior claim that importers had agreed to sell that beef at 25% below market price. Trump didn’t dispute the figure. He said only that “right now, it’s primarily Argentina and Brazil, but there could be other countries,” and that the imports were being allowed “in a very limited fashion because our ranchers can handle it.”

Cutting out the middleman at home while opening the door to foreign beef sold below market price is two moves in opposite directions. No reconciliation was offered. Trump’s closest attempt at a bridge was that ranchers “want the prices to be down too,” which addresses consumer prices, not the structural tension between protecting domestic market share and importing cheaper competition into it. Rollins, who spoke at length about rebuilding the domestic herd, wasn’t asked to square the two policies either.

For a reader trying to track the actual state of the beef-import policy: it exists, it’s currently limited to a handful of countries, and it has no stated end date. Its price-discount mechanism, the “25% below market” figure, has not been independently verified or explained in enforcement terms.

Wolves, state authority, and a public-safety account

The second order authorizes ranchers to kill Mexican gray wolves and other wolf populations preying on livestock, in areas where the animals remain protected under the Endangered Species Act. It also directs federal efforts to supersede state-level protections that persist even where federal delisting has already occurred, a direct reference to states including California, Oregon, and Washington.

The testimony behind this order was personal and specific. A rancher from Arizona traced the Mexican gray wolf reintroduction back to the Clinton administration and described wolves killing livestock, dogs, and horses. A rancher from Washington state described a more serious incident. A woman marking trees in a logging area was reportedly treed by wolves and held there until someone arrived by vehicle to drive the animals off, what he called “an immense public safety concern.”

That same rancher raised a structural complaint that the wolf order alone doesn’t resolve. In his region, wolves are federally delisted, but Washington state has continued protecting them and, he said, has blocked ranchers from acting even where federal law would permit it. He also alleged that state wolf-management funding, money he said originates with the federal government, is being used in ways that work against ranchers. Trump’s response was informal and non-specific: “So let’s terminate it. Take it out.” No mechanism for actually cutting that funding was described. The federal-versus-state conflict in states like Washington may not be fully resolved by this order alone.

The numbers behind the rancher narrative

Much of the event’s framing rested on statistics stated as fact but not sourced in the room. Trump said the national cattle herd fell to “86,000,000, the lowest level in 75 years” under the prior administration. He also said 2023 was the worst farm year in U.S. history, with $90 billion in losses. Rollins put the number of ranchers lost since 1980 at 600,000, a figure carrying more institutional weight given her position as Agriculture Secretary, though she also didn’t cite a specific report. Both officials said egg prices are “down 90%” without specifying a baseline date. Trump cited a same-day jobs report of 162,000 new jobs, calling it roughly five times above projections, without naming a source.

None of these figures should be read as independently verified. They’re the administration’s own claims, delivered without citation. Trump also said estate tax elimination on inherited farms is “saving 2,000,000 family farms,” another uncited number. He also claimed zero illegal border crossings in the past 14 months, an absolute claim that carries a high risk of being inaccurate given the scale of what it asserts.

Beyond the beef: Iran, Ukraine, and a $1 billion super PAC

The signing opened into an unstructured, 30-minute press Q&A that ranged well past ranching. Asked to explain Vice President Vance’s comment that the U.S. isn’t at war with Iran despite resumed strikes, Trump said he prefers the term “military conflict.” He described U.S. actions as “intermittent” strikes on Iranian radar, aircraft, and shipping near the Strait of Hormuz. Pressed on 18 U.S. service member deaths, he didn’t dispute the toll but minimized it by comparison: “In Vietnam, you lost a 100,000 people,” a figure well above the commonly cited U.S. Vietnam War death toll of roughly 58,000. His central claim, “We stopped them from having a nuclear weapon,” was stated as settled fact but reflects his own assessment of the campaign, not a cited intelligence finding.

Asked about a new Russia-Ukraine peace proposal, Trump didn’t answer directly whether it would involve Ukraine ceding territory. He said only that envoys Steve Witkoff and Jared Kushner were headed to Kyiv and Moscow “with a proposal to end the war.” He cited troop losses to underline urgency: “32,000 people, mostly soldiers” lost in the prior month, then, in the same answer, “25,000 soldiers a month” as an average. Those two figures don’t square with each other and aren’t independently verifiable from open sources.

On campaign finance, a reporter asked when Trump’s super PAC, MAGA Inc., would start spending on the midterms. Trump said it already had. He disclosed the scale himself: “I think I have, like, a close to $1,000,000,000 in the super PAC, and I’m allocating probably 4 or $500,000,000” for the midterms. He confirmed leftover funds could carry into 2028. These are self-reported figures, not FEC filings, though they are checkable against public disclosure records.

On data centers and AI, Trump argued communities should welcome data-center development because it generates wealth and, in his framing, increasingly comes with on-site power generation. He put the choice to towns in stark terms: “If you want success, you have to go with the data center… if you want poverty, crime, and squalor, don’t approve data centers.” That framing leaves out water use and local infrastructure strain raised elsewhere in debates over data-center expansion.

What was actually decided

Strip away the Q&A tangents and two concrete actions remain. One is an executive order opening direct-to-consumer meat processing for ranchers, with regulatory streamlining and a country-of-origin labeling push pending congressional action. The other is an executive order authorizing lethal wolf control with a directive to challenge state-level protections. Both are real, signed policy actions with tangible effects for ranchers.

Everything else was asserted, not documented, in the room: herd sizes, farm losses, egg prices, job numbers, war casualties, trade-deficit savings. And the event’s sharpest unresolved thread is the one nobody on stage chose to address. A meat-processing order built around protecting domestic ranchers from middlemen sits next to a beef tariff suspension that opens the market to foreign beef sold, by the president’s own account, below the price those same ranchers charge.

---

Want the policy story without the noise? Subscribe for clear-eyed breakdowns of what’s actually signed, what’s asserted, and what’s still unresolved. No spin in either direction.