What to Ask Before You License Voter File Data

Publicly Available Does Not Necessarily Mean Unrestricted

A common procurement mistake is assuming that the right to obtain a voter file also grants unrestricted downstream use. It does not, and NCSL's summary of access to and use of voter registration lists shows how far the rules diverge by state. Some states place no use condition on what they release. Colorado's Secretary of State provides its public voter information without regard to how the requester will use it. Others restrict who can obtain the file at all. California treats voter registration information as confidential, releases it only for election, scholarly, journalistic, political or governmental purposes, and bars commercial use. Many attach conditions that travel with the data. Maine makes commercial use and unauthorized resale of its voter file violations, and Minnesota generally bars recipients from selling, lending or providing access to list information. Those conditions do not stop at the vendor. If your intended use is commercial and the source state restricts commercial use, no contract term with a supplier cures that.

Ask the question in the specific form that produces a checkable answer: for each state in this delivery, what use does that state permit, and what document says so. A supplier who cannot answer per state is describing a blended national product and has not done the work.

Refresh Cadence Is a Per-State Number

Registration files do not update on a common schedule. Some states republish weekly, some monthly, some quarterly, and cadence often tightens near an election and loosens after it. This matters more than buyers expect, because the fields that decay fastest are the ones campaigns and analytics teams actually use: address, status, and party where recorded.

Separate Observed Fields From Modeled Ones

A voter file delivery usually contains three different kinds of field, and buyers routinely treat them as one. There is registration data that comes from the state. There is vote history, which records whether a person voted in a given election and is also from the state. And there is modeling, which is a vendor-produced score that predicts something the state never recorded, such as party affinity in a state with no party registration.

The distinction is not academic. A modeled score is an inference, and if it is built partly on vote history then it inherits the permitted-use restrictions of the underlying record. Ask for the field list annotated with provenance: state-sourced, derived, or modeled. Campaigns combining registration records with postal or email reach should hold the same line on every appended or modeled field built on top of them. Any vendor selling a serious voter product can produce that annotation. The same discipline applies to identity products, where deterministic and probabilistic matching carry different operational costs.

Coverage Is a Per-State Question, Never a National One

A national record count is close to meaningless for voter data. What you need is the count for the states you are buying, the count the state itself reports for the same period, and an explanation of any gap. Gaps are normal and usually benign, because suppressed records, confidential registrations, and protected classes are removed by law in several states. What matters is that the gap is explained rather than discovered later.

Run the same discipline you would run on any file: one seed, one spec, and a holdout. The seed match testing guide covers sample design, and the bake-off checklist covers how to keep finalists comparable.

Put the Answers in the Agreement

Every item above belongs in the paperwork, not the sales thread. Permitted use per state, refresh cadence per state, field provenance, and the remedy if a state changes its rules mid-term. That last one is the clause buyers forget. State access rules do change, and a mid-term change can make part of a file unusable through nobody's fault. Decide in advance who carries that.

Write the Mid-Term Rule Change Into the Contract

State legislatures and secretaries of state revise access rules regularly, and they do not coordinate with your contract term. A state can narrow permitted use, add an affidavit requirement, raise a fee, or restrict redistribution partway through a twelve-month license. None of that is a breach by either party, which is exactly why it needs a clause: absent one, the buyer and the supplier discover mid-term that they disagree about who absorbs the loss.

Three outcomes are worth naming in advance. If a state becomes unusable for your purpose, does the license shrink and the fee adjust, or does the fee stand because the rest of the file is unaffected? If a state adds a compliance step, such as a signed purpose statement naming the end user, who executes it and how quickly? And if the change is retroactive to data already delivered, what is the deletion or quarantine obligation, and who bears the cost of proving it happened? A supplier who has sold voter data through more than one legislative session will have opinions on all three, which is itself a useful signal.

The practical form is a short notice-and-adjust clause: the supplier notifies within a stated number of business days of learning of a change, the parties confer, and the buyer may drop the affected state with a pro-rata adjustment. That is neither exotic nor adversarial. It converts an unpredictable legal event into a defined process, and it is far cheaper to agree while both parties are still enthusiastic than during the week the change lands. Run this diligence against GSDSI's voter and political data file before you sign.