Washington State Fights DOJ Over NONCITIZEN Ballots

Voters at polling booths in a gymnasium
Photo: Steve Sanchez Photos / Shutterstock

When federal prosecutors allege hundreds of noncitizens registered and voted, and the state’s chief election officer counters that the list includes U.S. citizens, the real story isn’t a headline-grabbing number—it’s how easily record-matching can confuse suspicion with proof, and how process design determines whether we get clarity or collateral mistrust.

At a Glance

  • DOJ identified 405 alleged noncitizen voters tied to roughly 1,500 prior ballots and asked Washington to sequester any new ballots from those individuals pending verification.
  • Washington’s Secretary of State said the federal list contains U.S. citizens, duplicates, and people not currently registered, calling it unreliable and refusing the request as presented.
  • Federal officials say they cross-referenced immigration data with public voter records; the state says the provided PDF lacked key identifiers needed for accurate matching.
  • The dispute reprises a national pattern: database flags can overstate illegal voting unless each case is resolved with date-specific citizenship and ballot-level evidence.

What the competing claims actually establish

The Department of Justice transmitted a list it said comprised 405 noncitizens who had registered and cast approximately 1,500 ballots in Washington over prior elections, asking counties to withhold tabulation of any new ballots from those individuals until citizenship could be confirmed. The letter was signed out of both federal districts and emphasized that the names came from cross-referencing immigration information with publicly available voter data, not from rumor or anonymous tips. As a procedural matter, the request targeted specific ballots for sequestration—an auditable step—rather than a blanket rejection.

Washington Secretary of State Steve Hobbs publicly rejected the reliability of the federal list. His office’s preliminary review found entries that the state already knew to be citizens, duplicate names, and individuals who were not currently registered or were inactive; he also criticized the timing and data format, noting that the DOJ provided a PDF of a spreadsheet without voter ID numbers or addresses, which the state said made confident matching “difficult—if not impossible.” On that basis, Hobbs declined to instruct counties to hold ballots solely on the DOJ submission.

How these lists get built—and why they so often break under scrutiny

Most noncitizen-voting sweeps begin the same way: investigators start with immigration-related datasets—lawful permanent residents, visa holders, border interviews—then attempt to match those records to state voter rolls. Even when the matching is careful, two structural realities undermine certainty. First, immigration status changes; a person who appears as a noncitizen in 2018 may be a naturalized citizen by 2022. Second, personally identifying information used for large-scale matches—names, dates of birth, partial addresses—can misalign across systems, yielding false positives. When these flags are announced before individualized verification, initial counts have a history of collapsing upon closer review.

That pattern matters here. Federal officials say the Washington list arose from cross-referencing and interviews, including at the U.S.–Canada border, and they supplied last-vote dates for each person. Those are testable claims—if the state can reliably match each entry to a unique voter record. The state, however, says the file lacked the very fields election administrators use to disambiguate people with similar names, and it documented duplicates. That is not a quibble about file formats; it’s the difference between a credible audit trail and a set of suggestive leads.

What counts as proof in election administration

Three questions must be answered to convert a database hit into an adjudicated illegal vote. First, identity: does the flagged record correspond to a specific, unique voter registration? That requires voter ID fields and clean deduplication. Second, eligibility on the relevant date: was the individual a noncitizen at the time of registration and on each date they allegedly voted? That requires date-specific immigration or naturalization records, not just a historical status snapshot. Third, authorship: even if a ballot is attributed to a registration, did that individual actually complete and return it? Signature images, return logs, and chain-of-custody checks resolve that question within the limits of ballot secrecy laws. Absent these steps, an official count of “illegal votes” is an estimate—potentially a large overcount or undercount.

In this dispute, DOJ emphasized confidence and urged targeted sequestration so counties could check eligibility. The state emphasized that, as presented, the list couldn’t be reliably joined to registrations and already appeared to misclassify citizens as noncitizens. Each side is defending a core institutional prerogative: federal prosecutors seeking to prevent ineligible voting, state officials insisting that changes to ballot handling rest on clean, case-specific evidence.

Timing, process, and the risk of eroding trust

The federal request reportedly arrived within days of ballot counting and asked for action on a roughly two-day timeline. That kind of compression invites the very skepticism it purports to cure: a list that can’t be independently validated fast enough reads to administrators as an attempted end run around standard verification. Washington officials cast the timing and content as likely to seed doubt; federal officials framed the timing as a necessary response to live ineligible voting risk. Both can be true; neither resolves the factual question of how many ineligible registrations or ballots actually exist.

The broader record cautions against conflating early flags with settled findings. High-profile sweeps in other jurisdictions have shrunk dramatically when naturalizations and administrative errors were accounted for. That base rate should temper public expectations and set the bar for disclosure: if an agency claims hundreds of illegal ballots, it should be prepared to produce a case-by-case evidentiary matrix that survives ordinary data hygiene and legal scrutiny.

The constructive path to resolution

This clash is resolvable with disciplined transparency and proper sequencing. The federal side can transmit a machine-readable file containing, for each entry, the precise identity-resolution fields used, the source and date of immigration status, and the last-vote information it cites. The state can then conduct a two-track review: (1) registration matching and deduplication using its canonical voter IDs and (2) date-specific eligibility checks, incorporating certified naturalization records. Where authorship is in doubt, counties can consult envelope images, signature review outcomes, and return logs within legal constraints. Cases that still appear unlawful should be referred for prosecution; cases that are resolved as lawful should be removed from public tallies just as publicly as they were added.

What to take away

Two claims can coexist without contradiction: it is illegal for noncitizens to vote, and sweeping database matches are not proof that they did. In Washington, DOJ has presented a numerically specific allegation built from cross-referenced federal records and asked for targeted ballot handling; the Secretary of State has identified concrete data-quality defects and citizen misclassifications and refused to alter ballot processing on that basis. Until the underlying names are reconciled with date-stamped citizenship and ballot records, certainty will elude both camps. The fix is not rhetorical; it is procedural, evidentiary, and replicable—and it is entirely achievable if both institutions prioritize adjudicable facts over speed and spectacle.

Sources:

cbsnews.com, spokesman.com, thehill.com, abcnews4.com