On July 21, Governor Sherrill announced that roughly 6,600 people who told the Motor Vehicle Commission they were not U.S. citizens had been registered to vote anyway, between June 2023 and June 2024. Fewer than 400 of them ever cast a ballot. The flaw was fixed in June 2024. The registrations it had already created stayed on the rolls for two more years, and nobody outside a small circle of officials was told.

We spend a lot of time inside New Jersey’s statewide voter file, the same export whose vote-history quirks we wrote about on July 27, so to us this is a data story. A handoff between two systems failed, the cleanup never happened, nobody said anything for two years, and now it is running into a legal deadline the coverage has barely mentioned.

The gate recorded the answer and opened anyway

New Jersey has run automatic voter registration at the MVC since 2018. Get a license or a state ID and, unless you opt out, the same visit starts your registration. The MVC collects answers and passes a package downstream, where the Division of Elections and the county commissioners of registration decide who goes on the roll.

The state says applicants who answered “no” to the citizenship question were carried into registration anyway. The vendor, Idemia, disputes the “software error” framing. Its system, it says, recorded both answers correctly: the no on citizenship and the yes on registering. The citizenship answers were there for the MVC to see. No noncitizen was mislabeled a citizen in the database. And checking eligibility was the state’s job.

All of it can be true at once. That’s what an integration failure looks like. Each system did its own job, and the rule connecting them, that a “no” over here has to stop the process over there, was enforced by neither. An answer that gets stored instead of acted on is a field, not a gate. Two years later, the state and its vendor still don’t agree on whose gate it was. Nobody owned the check, so nobody tested it, so its failure made no sound for twelve months.

Some coverage has leaned on officials calling registration an “honor system” for citizenship. It is one, everywhere. Sworn attestation under penalty of perjury is the design Congress chose in 1993. It isn’t evidence New Jersey was especially careless, least of all when the applicants told the truth and the system ignored them.

Four other states got here first

The most useful fact about New Jersey’s error is that it isn’t new. The same failure has turned up in at least four other states, under officials from both parties.

Illinois is the near-exact match. In 2018 and 2019, a programming error in its automatic voter registration system sent the records of 574 people who had identified themselves as noncitizens through to election officials. Same seam, six years earlier. In Pennsylvania, about 200 noncitizens registered through a glitch in the electronic driver licensing system, according to 2017 testimony that also covered self-reported cases going back to 2000. Colorado ran the error in reverse in 2022, mailing registration postcards to roughly 30,000 noncitizens. Oregon found about 1,600 people in 2024 who had been registered through its DMV without the citizenship documentation its process requires. Most turned out to be citizens, and about 30 ineligible people had voted.

Different vendors, statutes, and parties, same shape. The DMV counter exists to issue licenses, and the citizenship question rides along like cargo. New Jersey had five years and a nearly identical public case in Illinois to learn from.

The patch shipped. The backfill never did.

Fixing the code that produces bad records is half a cleanup. The other half is going back for the records the bug already wrote, and it’s easy to skip, because once the patch ships everything looks fine. You fix the writer and forget the written. These records hid themselves, too: a bad registration looked like every good one, and after June 2024 the only evidence lived in MVC transaction data.

As far as the public record shows, New Jersey never went back. Roughly 6,600 records stayed on the rolls until July 15 of this year, when Sherrill says the Attorney General’s office told her. She went public six days later. The outside firm CSG Law is now working out who knew what in 2024 and why nothing happened next. All 23 Assembly Republicans and 15 Senate Republicans have called for a legislative committee with subpoena power. As of late July, Democratic leaders hadn’t agreed to one.

Whatever the investigation finds about intent, one thing is already visible: nobody owned the cleanup, and nobody owned the telling. Those are two jobs, and both need a name attached before an incident, not after.

New Jersey already had the pipes

New Jersey joined the Electronic Registration Information Center in August 2022, before the failure window opened. Member states send ERIC their voter rolls and motor vehicle data at least every sixty days and get back reports on records that don’t line up. ERIC flags voters who moved, voters who died, and duplicate registrations. It doesn’t check citizenship.

So the state was already cross-matching MVC data against the voter file every sixty days. It just wasn’t running the one comparison that mattered, an internal join of the citizenship answers the MVC recorded against the registrations the MVC generated. The mismatch count should have been zero every month. It was running at something like 550 a month, the 6,600 spread over the twelve months the flaw was live, and nothing was looking.

The fix that would have caught it is a scheduled query.

Why 6,600 became 4,500 and a question mark

On July 28 the state said about 4,500 registrations would be removed outright and roughly 2,100 would go to county election officials for individual review first, because, in the governor’s words, the initial review suggested a number of those people may actually be citizens. Some may have hit the wrong key. Others may have been ineligible when they registered and naturalized since.

A voter file isn’t a list of facts. It’s a ledger of claims, each collected at a particular counter and carrying that process’s error rate. Citizenship is an answer somebody gave on a Tuesday, and one of the few that can honestly change afterward. And the 6,600 came from a keypad at a DMV counter, tapped by people juggling documents with a line behind them. When Oregon checked in 2024, most of the people its DMV flagged were citizens.

So “6,600 noncitizens are on the voter rolls” was never a fact. It was a claim about 6,600 records, a third of which the state now says need a human to resolve. The number will probably move again.

The deadline nobody mentioned

Under the National Voter Registration Act, any program that systematically removes ineligible voters has to finish at least 90 days before a federal election. For this November’s midterms, that quiet period starts August 5. New Jersey began its removals on July 28, eight days before the door closed.

The quiet period doesn’t freeze the rolls. States keep processing registrations, fixing clerical errors, clearing the deceased, and acting on specific information about individual voters. What stops is the broad sweep that flags a whole group at once.

Programs like this have hit that wall before. In 2012 the Eleventh Circuit held that Florida’s noncitizen-removal effort violated the quiet period because it was systematic. In 2024 a federal judge ordered Virginia to restore about 1,600 voters on the same grounds, though the Supreme Court stayed that order days before the election. The Court has since agreed to hear an Arizona case that could narrow the quiet period, with a ruling expected in the spring. The Justice Department is separately arguing that it can hand states individual names to remove right up to Election Day.

Read New Jersey’s two-track plan against that. The clear-cut batch is removed now, while a systematic program is still legal. The uncertain 2,100 get record-by-record review, which stays legal after August 5. Nobody in Trenton has said the deadline drove the design, but if you’ve wondered why a two-year-old mess went from announcement to action in a week, the calendar explains it better than the politics.

The proportion

About 6,600 records sit in a statewide file that the Division of Elections’ own monthly county summaries put at roughly 6.6 million registrations: one in a thousand. Fewer than 400 ballots, spread across multiple election dates from late 2023 through this June’s primary, cast by registered Democrats, Republicans, and unaffiliated voters alike, with no evidence any result changed. (One of the elections those registrations were live for was the 2025 governor’s race, won by the person who disclosed the problem.)

But “small” is not the defense people think it is. The number is small because the traffic through that counter is small. A control that failed 100% of the time for a year is a serious finding at any volume. And nobody in the 6,600 did anything worse than answer a question truthfully at the DMV. This was never a story about voters behaving badly. It was a gate that didn’t gate.

The people at the end of the records

Registering or voting as a noncitizen carries criminal exposure and immigration consequences up to removal proceedings. Intent looks very hard to establish against someone who said “no” at the counter and got enrolled anyway, but for the people involved the process is the punishment. New Jersey is pointing affected residents to a state legal defense initiative whose funding was doubled past $20 million in June.

The letters the MVC mailed on July 25 told affected residents to contact election officials and ask to be taken off the rolls themselves. That’s backwards. You don’t fix your own data defect by asking a noncitizen to walk into a government office in 2026 and flag their own case over a registration they never wanted. The July 28 revision put the work back on the state and the counties. It should have been the first version.

The court fight is running on a different axis

In late July, Judge Zahid Quraishi dismissed the Justice Department’s suit seeking New Jersey’s complete, unredacted voter database, filed in February under Title III of the Civil Rights Act of 1960. The statute, he held, covers records that come into election officials’ possession, not a live database the state maintains itself. He noted he was joining at least sixteen other district courts and a circuit, and that the registration error had no bearing on the question. Separately, Judge Georgette Castner found the RNC lacked standing for its National Voter Registration Act claims, and the RNC has another action pending in state court over list-maintenance records and audit logs from the June 2025 primary.

A bulk copy of the voter file would not have caught this. Every one of the 6,600 looked like a normal registration. The contradiction lived upstream, in the MVC transaction. Compare the two systems and the problem surfaces in an afternoon. Export either one alone and it never does.

The same goes for the federal SAVE system. By recent reporting, 25 states have pushed more than 68 million records through it and surfaced some 28,000 apparent noncitizens and 400,000 deceased registrants. Its citizenship signal leans on Social Security data that was never built to establish citizenship, and it has a documented record of false hits. Like New Jersey’s 2,100, a match is a candidate for review, not a decision.

What would actually prevent the next one

Make refusal end the transaction, and prove it. A “no” on citizenship has to stop the flow, and a test should run on every release proving it produces no downstream registration.

Reconcile the two systems monthly, in public, and publish the mismatch count even when it’s zero. Especially then, because that’s how you know the check is still alive.

Write the rule that was missing in June 2024. A defect that wrote bad records is closed when the affected records have a cleanup plan with an owner, a date, and a disclosure decision. Half of this scandal isn’t the bug. It’s the two years.

Give every match a human: individual review, notice to the voter, and a chance to correct the record before removal. That’s what the counties are doing with the 2,100, and it should be the default for anything that comes back from SAVE.

Some of this is moving in Trenton. A353 pairs a retrospective audit of registrations with a documentary proof-of-citizenship requirement at the MVC. A3802 and S4132 go at the registration prompt itself. The audit and the flow fix shouldn’t wait on the proof-of-citizenship fight, which is a real one. But a proof requirement wouldn’t have caught a system that ignored the answer it already had.

If you work with the file

Nothing here should change how you cut a universe. One record in a thousand, skewed toward people who overwhelmingly didn’t vote, is inside the noise you already carry.

Expect churn in the counties for several months, as the 2,100 referrals get worked twenty-one different ways, with some reinstated. If a refresh shows removals you can’t explain, this is probably it. And if you’re comparing registration counts across refreshes in a heavily immigrant precinct this fall, some of the movement is administrative, not political.

A voter file is a record of an administrative process, not a portrait of the electorate. The fields that look most like facts, citizenship, address, party, status, are usually a claim someone made once that nobody has checked since. That’s why Romulus is stubborn about provenance and vintage: knowing which process wrote a field, and when, is the difference between using data and trusting it.