Here are two addresses.
123 North Main Street, Apartment 4B
123 N MAIN ST APT 4B
You read those and see one house. A computer reads them and sees two different places in two different towns.
That gap — the distance between how a human writes an address and how a machine stores one — is quietly breaking voter roll maintenance in most of the counties in this country. Not through fraud. Not through conspiracy. Through formatting.
This is the least glamorous problem in election integrity, and we think it may be the biggest one.
What the law actually requires
Start with the duty, because everything here follows from it.
The National Voter Registration Act doesn’t tell counties to wait for news to arrive. It tells them to run a program:
“...each State shall ... conduct a general program that makes a reasonable effort to remove the names of ineligible voters from the official lists of eligible voters...” — 52 U.S.C. § 20507(a)(4)
The Help America Vote Act adds the tempo — list maintenance performed “on a regular basis” through “[a] system of file maintenance” — 52 U.S.C. § 21083(a)(2)(A), (a)(4)(A).
A program. A system. On a regular basis. Congress is describing something continuous — not a cleanup before a big election, and not a response to a complaint.
And eligibility isn’t one question. It’s four, and each can change without anyone telling the county:
Is this person still alive? Are they a citizen? Do they still live in this jurisdiction? Are they disqualified under state law by a felony conviction or an adjudication of incapacity?
An address answers only one of those four. But the address is the field that decides whether a county can check the other three. Here’s why.
Every check is a match, and every match is a comparison
To find out whether a registrant died, or moved, or registered somewhere else, a county can’t just look at its own file. It has to compare that file against an outside source — state death records, USPS National Change of Address data, another state’s registration list.
That comparison is a match: a computer lining up two records and deciding whether they describe the same human being.
And here’s what nobody tells election officials. Those outside sources are almost all keyed on standardized addresses — specifically, addresses processed through CASS, the Postal Service’s Coding Accuracy Support System. NCOA is built on them. Commercial address and identity data is built on them. Standardized form is the common language the entire American data ecosystem uses for addresses.
Which means the match is, in large part, a comparison of address strings. And strings only match if they look alike.
Watch what happens when they don’t:
What’s in the voter roll:
123 Main Street
Saint Augustine, Florida 12345
What the outside source has:
123 MAIN ST
ST AUGUSTINE, FL 12345-6789
Looks like the same address to human eyes. But they are NOT THE SAME to a computer and WILL NOT MATCH. Something as simple as a spelled-out directional, an abbreviated saint, a period, a comma — and the computer reports back: no match.
The false clean bill of health
Now follow that all the way down, because this is the quiet failure at the center of American list maintenance.
A county runs its roll against NCOA. It gets a low match rate. The supervisor looks at that number and draws the obvious conclusion: our rolls are in good shape — hardly anybody came back as moved.
That conclusion may be completely wrong.
A low match rate against a standardized source is at least as likely to mean our addresses aren’t in the format required to match anything as it is to mean our voters haven’t moved. The county didn’t audit its roll. It audited its own formatting — and then filed the result as a clean bill of health.
This is what we see over and over. Registrations typed by humans, from handwritten forms, across decades, with no standardization step anywhere in the pipeline — then checked against sources that were standardized from the start. The two never had a chance of lining up.
Meanwhile the county can say, accurately, that it ran the program. It did run it. It just ran it on data that couldn’t answer.
So the order of operations is not optional:
Standardize first. Then match. Then verify. Then act.
Run it in that order and NCOA, death records, and cross-state comparisons start returning what’s actually there. Run it out of order and you get a low match rate, a false sense of security, and a roll nobody has meaningfully checked in years.
The real fix: catch it at the door
Everything above is about finding bad addresses after they’re already on the roll. That’s remediation. Every other industry that handles addresses at scale gave up on remediation a long time ago.
Buy something from Amazon. Type in a shipping address. Before your order goes through, a small box appears:
“Did you mean 123 N MAIN ST APT 4B?”
You click yes. Google, UPS, FedEx, your bank, your insurer, the IRS, online passport forms, every serious checkout page in America — same pattern, every time.
Here’s what happened in that half-second. What you typed was run through CASS software, standardized, checked against the Postal Service’s file of deliverable addresses, and handed back to you to confirm. And the record that got saved was the standardized one — not what you typed.
That is the industry standard, and it has been for more than twenty years. It exists because companies that ship physical objects learned an expensive lesson: an address is cheapest to fix at the moment it’s captured, and most expensive to fix once it’s buried in a database and already being used.
Now look at how a voter registration is captured. Somebody fills out a paper form at a library table, or a DMV screen, or an online portal. It goes into the statewide database as typed. Nobody standardizes it. Nobody validates it. Nobody asks the applicant to confirm it.
The one moment when the person who actually knows the right address is sitting right there, available, and happy to answer — is the exact moment the system skips.
Then, years later, somebody runs a match, gets a poor hit rate, and either declares victory or pays a vendor to clean up the mess.
What changes when you reverse the order
Validate at the door and four things happen at once:
The registrant confirms their own address — in their own words, at the counter, before anything is saved. No notice. No waiting period. No guessing on the county’s behalf.
The record enters the database in the same format as every source it will ever be checked against. Matching starts working, because there’s finally something to match.
An undeliverable address gets caught on day one, when a human being can simply fix it — not in year three, when fixing it takes a confirmation notice, a two-election waiting period, and somebody’s legal opinion.
Ballots, notices, and confirmations actually reach the voter. Which is, after all, the entire point.
And be clear about who this protects. A voter who confirms a standardized address at registration is far less likely to be flagged by a matching program years later — because their record will match. Validation at the door is a voter protection at least as much as it is a roll-integrity measure.
We should be blunt about our own tool here: ELLY finds address problems, and ideally it would never have to. Downstream detection is what you’re left with when nobody validated upstream. We would rather counties stop generating the discrepancies than pay anyone — us included — to go find them.
None of this requires a court ruling, a new statute, or federal permission. The Postal Service licenses CASS. Certified software is a commodity, and free tools exist. A county can add an address-confirmation step to its registration intake the same way a hardware store added one to its checkout page fifteen years ago. It just has to decide to.
🗳️ Take Action
Two letters. Both short. Both cite a federal statute your county already has to answer.
Letter one — did the match actually work?
“Under Section 8(i) of the National Voter Registration Act, 52 U.S.C. § 20507(i), I request records sufficient to show, for each list-maintenance comparison run in the past two years — including USPS National Change of Address, death records, and any cross-state comparison — the number of records submitted, the number returned as matches, and whether the addresses submitted had been standardized using USPS CASS-certified software before the comparison was run.”
That last clause is the whole letter. A county reporting a very low match rate that cannot show it standardized first has not demonstrated a clean roll. It has demonstrated an untested one.
Letter two — the question nobody asks.
“When a new voter registration is submitted to this office, is the applicant’s address standardized and validated against USPS CASS-certified data, and confirmed by the applicant, before the record is saved? If not, why does this office hold voter registrations to a lower address standard than an online shoe order?”
Three outcomes, and every one tells you something:
They produce the records — good, now you know the numbers and whether to trust them.
They’ve never run it — that absence is itself a finding, and it’s a public record.
They refuse — the NVRA carries a private right of action at 52 U.S.C. § 20510.
And check your own registration. Look at how your address is written on the public roll. If it does not have an extra 4 digits added to your zip code, or worse, it says “Street” and “Apartment” and has a period after the abbreviation, you’re looking at the problem.
Visit TheElectorList.com to see what ELLY™ has found in your state, volunteer as a county reviewer, or get help drafting either letter.
The Bottom Line
An entire category of government recordkeeping never adopted a data-quality step that the private sector treats as table stakes. Then it built a legally required checking program on top of that data and reported the results as if they meant something.
A correct address can’t tell you whether a registrant is alive, or a citizen, or still lives in the county. But it’s the field every one of those checks runs through. When it’s wrong — or merely formatted wrong — the checks the law requires quietly return nothing, and everyone mistakes the silence for a clean roll.
The moment to get it right isn’t two years later, when the fix requires a notice and a waiting period. It’s at the counter, while the voter is standing there.
Amazon figured this out to protect a shipment of paper towels. We can manage it for a ballot.
If this explained something you’d been trying to put your finger on, share it — and then send the letter.
Missed the first half? A Ballot Needs a Real Address explains the new Postal Service rule that put address verification on every federal ballot envelope — and why it won’t clean your county’s roll for you.
Sources
Statutes
52 U.S.C. § 20507 — NVRA Section 8: (a)(4) the “general program” removal mandate; (d) notice-and-confirmation process; (i)(1) public records
52 U.S.C. § 20510 — private right of action
52 U.S.C. § 21083 — HAVA Section 303: (a)(2)(A) list maintenance “on a regular basis”; (a)(4)(A) reasonable effort to remove ineligible registrants
Postal standards
Kit 600: Official Election Mail, 2026–2027 — USPS (”To obtain automation discounts, a Delivery-Point ZIP Code from CASS-certified (Coding Accuracy Support System) software is required.”)
Ballot Mail for Federal Elections, final rule — USPS, 39 CFR Part 111, effective August 21, 2026 (FR Doc. 2026-17238), adding DMM 705.24



In all my years of database management and cleanup (garbage in - garbage out), standardization procedures, training, and review of entries are key to maintaining a viable database. This email addresses how the CASS system should be used at the beginning of the voter registration process and not 2 years later in an attempt to clean it up. Standardization should also be set for name entries at the local level also. Try searching for O'brien in the voter roll and you will find it entered in several different ways (IE: O'BRIEN, O BRIEN, OBRIEN). Pick one and use it even though all are valid names, the same for DE LA GARZA or DELAGARZA, both are correct names but only 1 should be used in a database structure. MCDONALD or MC DONALD, the list goes on. Standardization of entry procedures, training and review of entries are the key to maintaining any database.
Very informative and actionable. I will try to spread the word the best I can!