How to Evaluate a Voting Platform: A Checklist
Evaluate a voting platform on verifiability, auditability, ballot secrecy, and resolution rules, not on feature lists. Here is the checklist I would use.
When you evaluate a voting platform, ignore the feature list and check four things: can voters verify their own ballots, can outsiders audit the count, is ballot secrecy actually preserved, and are the rules locked and public before voting opens. A platform that nails those four is trustworthy even if its interface is plain. A platform that misses them is dangerous no matter how polished the demo. Feature lists are where vendors compete on things that do not matter so you stop asking about the things that do.
I evaluate tools for a living across a portfolio, and voting platforms are the category where the pretty ones are most often the weakest. Here is the checklist I would actually run.
Can voters verify their own ballots
This is the first filter, and it eliminates most of the market. Ask: after I vote, what do I get that lets me confirm my ballot was recorded correctly.
The right answer is a cryptographic receipt, a token tied to your ballot that later appears on a public list of recorded votes. You find your token, you know your vote counted. If the answer is "you get a confirmation screen" or "our system logs it," that is not verification. That is a promise. A confirmation screen proves nothing about what happened after you clicked.
Push on the secrecy angle too. A good platform gives you a receipt that proves inclusion without revealing your choice. If the vendor says they cannot offer receipts because of privacy, they either do not understand the cryptography or are hiding that they never built it. Both are disqualifying.
Can outsiders audit the count
The second filter is independence. Ask: can someone who does not trust you confirm the total is correct.
The count has to be checkable by outsiders, not just inspectable by the operator. That means the recorded ballots are published to a public board and the counting method is open, so anyone can run the count and get the same number. An operator reviewing their own logs is the referee grading their own game, and it is worth nothing when a result is contested.
Watch for the closed-source trap. If the code that produces the total is secret, the total is a black box output and no real audit is possible. Open counting logic is not a nice-to-have here. It is the difference between a result you can defend and a number you can only assert.
Is ballot secrecy actually preserved
The third filter is where verifiability and privacy meet, and it is the hardest to fake.
A weak platform makes you choose: either you can verify your vote or your vote is secret, not both. A strong platform gives you both, because that is exactly what end-to-end verifiable cryptography is for. Ask the vendor to explain how a voter confirms inclusion without exposing their choice. If they cannot walk you through it, they have not solved it.
Also check who can see the link between voter and ballot inside the system. The answer should be nobody, enforced by the design, not by policy. "We promise our staff will not look" is a policy. Cryptographic separation is a guarantee. Only one survives a hostile actor with admin access.
Are the rules locked and public before voting opens
The fourth filter is governance, and it is the one people forget because it is not a feature at all.
Before voting opens, the eligible voter roll, the resolution criteria, and the counting method should all be published and frozen. If any of them can change mid-vote, the result is manipulable upstream of everything else you checked. A clean count on a roll that was edited after the fact is a clean count of the wrong thing. This is the same reason I treat locked, public rules as non-negotiable when I write about running a transparent market.
Run these four filters in order and you will disqualify most platforms before the sales call ends. The ones that survive, like MintVote, treat verifiability and open counting as the core of the product rather than a compliance checkbox. That is the tell you are looking for. The right platform is not the one with the most features. It is the one built so a skeptic can confirm the result without trusting you, and there are fewer of those than the market pretends. Pick from that short list.