VVSG 2.0 for Online Voting Platforms: What to Ask Now
VVSG 2.0 for Online Voting Platforms: What to Ask Now
VVSG 2.0 does not automatically govern every private online election, but it gives election administrators a useful way to evaluate platform claims. If you are reviewing an online voting vendor for a union, association, cooperative, pension fund, or board election, the question is not simply whether the system is “certified.” It is whether the platform can show evidence for security, accessibility, auditability, and voter privacy.
What VVSG 2.0 Actually Covers
The Voluntary Voting System Guidelines are federal specifications used to test voting systems for public elections. The U.S. Election Assistance Commission describes them as requirements against which voting systems can be tested for basic functionality, accessibility, and security. HAVA requires the EAC to maintain the guidelines, but use of the federal standard is voluntary unless a state makes it mandatory.
VVSG 2.0 was adopted in 2021 and is now the standard for new EAC voting system certification applications. The standard places stronger emphasis on cybersecurity, accessibility, usability, auditability, and flexible system architecture.
For private elections, VVSG 2.0 is a reference point, not a shortcut. A labor union officer election, pension trustee vote, association board election, or cooperative member vote may be controlled by bylaws, plan documents, LMRDA rules, ERISA duties, state statutes, or board resolutions. VVSG 2.0 can help you ask better technology questions.
Why Private Election Teams Should Pay Attention
A private election administrator recently asked a question we hear often: “If VVSG is for public voting systems, why should we care?” The answer is that many election failures are not caused by exotic attacks. They come from ordinary gaps that VVSG-style review forces into the open.
Maybe the platform cannot clearly explain how voter identity is separated from ballot selections. Maybe the audit log records final turnout but not ballot setup changes. Maybe the voting flow works on a laptop but fails for a voter using keyboard navigation. Those are the issues that become serious when a losing candidate, trustee, member, or regulator asks how the election was run.
A strong online voting platform should make those answers easier to document.
Five VVSG 2.0 Questions to Ask Your Vendor
You do not need to turn your election committee into a federal testing lab. You do need to ask questions that produce usable evidence. The table below translates VVSG 2.0 themes into practical review questions for private online elections.
| Review Area | Question to Ask | Evidence to Request |
|---|---|---|
| Accessibility | Can voters with disabilities mark, review, cast, and verify ballots independently? | WCAG testing notes, assistive technology review, keyboard navigation results, support process |
| Auditability | Can the election record show who did what, when, and under what authority? | Administrator activity logs, ballot change history, voter file import logs, certification packet |
| Security | How are credentials, administrator access, encryption, and incident response handled? | Security summary, access-control model, penetration test summary where shareable, incident procedure |
| Ballot secrecy | How does the system separate voter identity from ballot choices? | Plain-language architecture explanation, role permissions, sample reports with private data removed |
| Usability | Can voters complete the ballot correctly without unnecessary confusion? | Ballot proofing workflow, voter instructions, test election results, help desk scripts |
The strongest vendors answer with documents, samples, and workflows, not slogans. “Secure and compliant” is not enough. You want a record your board can read and defend.
Do Not Confuse Certification With Election Readiness
Certification language can sound reassuring, but it does not solve every election problem. An administrator can upload the wrong eligibility file. A candidate name can be misspelled. A notice period can be missed. A replacement credential can be issued without enough documentation.
This is why technology review and election procedure review should happen together. Before launch, confirm the governing rule, final voter list, ballot language, candidate approval, notice schedule, support plan, accessibility path, incident escalation process, and records retention plan.
Votem’s election operations work is built around that practical reality. In a close election, process evidence is often what protects trust.
How to Use VVSG 2.0 Without Overstating It
The best way to use VVSG 2.0 in a private election is to treat it as a disciplined lens. Borrow the themes that matter, then map those themes to the rule that actually governs your election.
- Start with the governing authority. Identify whether your election is controlled by bylaws, a constitution, a plan document, a statute, or a board resolution.
- List the evidence you would need after a challenge. Include eligibility records, notices, ballot approvals, administrator logs, support tickets, and final certification materials.
- Ask the vendor to show sample outputs. Do not settle for a feature description when what you need is an exportable record.
- Test the voter journey before launch. Include mobile access, screen reader paths, keyboard navigation, authentication, ballot review, and confirmation screens.
- Assign responsibility for exceptions. Decide before voting opens who handles eligibility disputes, credential replacements, accessibility requests, and incident notes.
This approach keeps your review honest. You are not claiming VVSG 2.0 certification where it does not apply. You are using a respected public standard to improve a private election process.
Frequently Asked Questions
Does VVSG 2.0 apply to private online elections?
Usually not directly. VVSG 2.0 is part of the EAC testing and certification program for voting systems, and it becomes mandatory only where the relevant jurisdiction requires it. Private elections are typically governed by bylaws, statutes, plan documents, union rules, or board resolutions.
Should an online voting vendor claim VVSG 2.0 certification?
Only if the vendor can show the exact certification, product version, scope, and issuing authority. If a vendor says the platform is “VVSG-aligned” or “built to VVSG principles,” ask what that means in writing. Alignment is not the same as certification.
What parts of VVSG 2.0 are most useful for private elections?
The most useful themes are accessibility, usability, auditability, cybersecurity, and ballot secrecy. These areas translate well to private online elections because they affect voter access, trust, and defensibility after results are certified.
How early should we ask these questions?
Ask during vendor selection, then confirm again before launch. Early review helps you avoid choosing a platform that cannot produce the records you need. Pre-launch review confirms the actual election setup matches what was promised.
The Bottom Line
VVSG 2.0 gives private election teams a better vocabulary for vendor review, but it does not replace the rules that govern your election. The practical value is in the questions it helps you ask: Can every eligible voter access the ballot? Is ballot secrecy protected? Are administrator actions logged? Can the result be defended with records rather than assumptions?
If you are comparing online voting platforms for a high-stakes election, do not wait until ballots are live to ask for evidence. Votem can help you review platform controls, accessibility expectations, audit records, and operating responsibilities before deadlines are set. Talk with the Votem team before you approve your next online voting platform.