Thousands Get Two Ballots – Who’s To Blame?

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

When a county mails two vote-by-mail packets to the same voter, the real test of election administration isn’t whether an error occurred—it’s whether the system cleanly reconciles each voter to one accepted ballot and rejects any extra. Tulare County, California, offers a concrete case study of how that works in practice.

The Short Version

Tulare County attributed thousands of duplicate vote-by-mail packets to a vendor error during a ballot-replacement run.
Officials quantified the scope: 7,791 affected voters, concentrated in the City of Tulare.
Voters were instructed to vote only once, use either packet, and securely destroy the duplicate.
Election staff emphasized a core safeguard: multiple returns from the same voter trigger rejection logic so only one ballot is counted.

What happened in Tulare County and how officials responded

County election staff fielded a surge of calls and in-person reports after some residents received two vote-by-mail packets for the same election. The Registrar of Voters Chief Clerk, Michelle Baldwin, traced the incident to a ballot-printing vendor and reported that the firm accepted full responsibility. Local outlets and regional coverage put the count at 7,791 affected voters—primarily in the City of Tulare—while identifying the vendor as ProVote Solutions, a Porterville-based printer long used by the county.

The county followed with plain-language guidance. The mailed postcard told recipients to submit only one ballot, affirmed that either packet would work, and instructed voters to securely destroy the duplicate. Critically, the office underscored that if two ballots were returned by the same voter, only one would be accepted; additional returns would be rejected and excluded from processing. Baldwin reiterated the same safeguard in interviews, framing the event as a production error that created administrative noise but not a path to double-counting.

Mechanism: why duplicate issuance is not the same as double counting

Election administration separates ballot issuance from ballot acceptance. When a county produces replacement packets—for instance, after an address correction or voter request—it generates additional outbound envelopes tied to the same voter record. That can go wrong at the production layer: a mis-set batch, a file replay, or a mailing-house duplication may send two packets. But back-end acceptance relies on voter-level controls—envelope barcodes tied to a single voter, inbound scanning, and signature verification against the registration record—plus a status check: has this voter already returned a ballot accepted for counting? If yes, the second submission is routed to rejection; if no, the first complete and verified return becomes the counted ballot. Tulare officials described precisely this safeguard stack as their backstop against double-counting.

California counties commonly use these controls across high-volume vote-by-mail environments. Even when rare production errors surface elsewhere—incorrect envelopes in Brooklyn in 2020, or duplicate mailings in other California counties—the decisive question isn’t whether some voters received two packets; it’s whether acceptance logic and reconciliation keep the canvass to one counted ballot per voter. The Tulare office’s explanation fits that standard architecture and its practical intent.

Vendor failure and accountability: what is known

Local reporting named ProVote Solutions as the vendor and stated the company accepted responsibility. Officials described the fault as occurring “during the ballot replacement procedure,” which suggests a control lapse within a discrete run—replacement ballots issued for a defined subset of voters—rather than corruption of the underlying ballot styles or voter database. ProVote’s long-standing relationship with the county, cited in coverage, indicates the county was not experimenting with an untested supplier; longstanding vendors nonetheless face the same requirement as any contractor in critical infrastructure: demonstrate root cause, corrective action, and proof of control efficacy before the next cycle.

Two aspects matter operationally. First, scoping: quantifying affected voters and confirming the error’s containment to duplicate issuance, not ballot content. Tulare provided the figure—7,791—and limited the geography primarily to the City of Tulare. Second, remediation: immediately alerting voters, providing clear instructions, and relying on the established acceptance safeguards so that any attempted double return is screened out. On those fronts, the county acted within best practice: define, notify, constrain, and rely on existing acceptance gates while monitoring returns for anomalies.

Voter instructions and the role of clear communication

When duplicate packets hit mailboxes, confusion is predictable. The remedy is not theoretical assurance but direct, unambiguous direction. Tulare’s postcard did this with imperative guidance—submit only one ballot; either packet is valid; destroy the duplicate; do not return or attempt to vote the extra packet. That language supports two goals at once: it reduces inadvertent dual returns by well-meaning voters, and it signals that any second submission will be intercepted by process controls. Local coverage captured this messaging and the county’s commitment to count only one ballot per voter.

Clarity also shortens the tail of administrative clean-up. Fewer dual returns mean fewer items to research, fewer cure letters to send, and a faster canvass. The faster the canvass, the less oxygen for speculation that mundane production errors equal tabulation failures. In that sense, voter communication is not soft public relations—it is a hard control that materially affects workload and the speed of certified results.

Scale and concentration: why 7,791 in one city drew attention

Nearly 7,800 voters is a consequential number for any jurisdiction, and concentrating most of those mailings in a single city makes the error more visible. Tulare officials and multiple outlets aligned on the scale, which equates to a significant share of City of Tulare registrants. Concentration also helps operations: the registrar can target outreach and monitor returns from a defined cohort more efficiently than if errors were scattered countywide.

From a controls perspective, concentration reduces the analytical search space. Acceptance logs, duplicate-return flags, and signature-review outcomes can be segmented by the affected list to validate that rejection logic functioned as designed. That’s the practical benefit of tight scoping: it enables focused quality assurance without disrupting the countywide canvass.

JUST IN: Thousands of California voters just received duplicate mail-in ballots.

Tulare County election officials confirmed that a “printer vendor error caused duplicate Vote By Mail ballots in the City of Tulare,” in a notification posted to the county website.

The vendor has…

— The Epoch Times (@EpochTimes) October 23, 2026

What rigorous reconciliation looks like after a duplicate-mailing incident

The gold standard after a production error is a reconciliation checklist that election professionals and outside observers alike can understand. It includes: a definitive roster of affected voter IDs and ballot styles; the outbound manifest from the vendor run that produced duplicates; inbound acceptance logs showing which single return per voter was counted; and a report of rejected returns with the specific rejection code—for example, second return received after an accepted ballot on file. Each piece aligns to the same principle: one voter, one counted ballot, with every other artifact traceable and dispositioned.

Tulare’s public posture tracks that logic—identify, notify, and rely on rejection safeguards—while naming the vendor and acknowledging responsibility. The number, the geography, and the operating explanation have been reported consistently by local and regional outlets, and the county’s instruction set to voters is unambiguous. In mail-ballot elections, that’s the difference between an error that creates administrative work and one that compromises results; the former can be managed with disciplined reconciliation, and Tulare described precisely that approach.