A secure online ballot system is only one part of a well-run election. The organisers also need a checked voter register, approved ballot, clear responsibilities and a plan for exceptions. For Kenyan associations and organisations, a rehearsal can reveal gaps before voting opens.
Approve the election rules first
Write down who is eligible, what positions or questions are on the ballot, the voting window and how results will be reviewed. The organisation’s authorised decision-makers should approve the rules before they are translated into system settings.
Do not assume a software default matches the constitution or agreed election procedure. Ask an appropriate adviser to review governance requirements where necessary. The platform should implement the approved process, not silently decide it for the committee.
Check the voter register as a separate task
Review duplicate records, missing contact details and the basis for eligibility. Assign responsibility for approving the final register. Keep a controlled process for correcting an error after approval so changes are not made informally by whoever receives a message first.
Use invented voter records in the rehearsal. Include a duplicate entry and an outdated contact to see how staff identify and resolve the issue. Do not send live voting invitations during a sales demonstration or publish the register as proof that the system is working.
Test access without assuming ballot secrecy
Ask the provider to demonstrate how an eligible voter gains access and how repeat access is handled. Then ask a separate question about ballot secrecy: what can administrators see about participation and choices, and which records are retained?
Authentication, participation tracking and secret voting are different properties. Obtain a clear explanation of the proposed configuration and its limits. Do not describe an election as anonymous, independently audited or tamper-proof unless the evidence supports that exact claim.
Rehearse an ordinary voter problem
Choose a scenario such as a voter who cannot find the invitation or whose contact information needs correction. Record who can help, which checks are performed and what gets logged. Support should not become a way to cast a vote on someone else’s behalf.
Test the procedure with the election committee and support contact present. A plan that exists only in a technical document may not help the person answering calls on election day. Make the escalation route and decision owner clear.
Review the ballot on the devices voters use
Check candidate names, question wording, ordering and selection rules. Ask a reviewer who did not configure the ballot to read it from a voter’s perspective. Test the relevant phone and desktop experience without exposing live voter information.
Include incomplete selections and an attempted change before submission. Confirm what the voter sees before a final decision is recorded. The instructions should explain the actual process rather than promise behaviours that have not been demonstrated.
Agree closing and result review
Decide who confirms the close of voting and who reviews the result. Ask what reports are available, what they contain and how access is restricted. Keep participation figures distinct from any information that could reveal an individual’s choice.
Run the rehearsal through closing, an authorised review and export of the appropriate records. Document unresolved points and have them addressed before the live event. A successful rehearsal supports readiness; it is not a guarantee that an election cannot experience an incident or dispute.
Plan the next step
Ask Vota to demonstrate your approved election process using dummy voters. Include duplicate-register handling, voter support, ballot review and result access, then confirm the configuration and responsibilities in writing.
Visit Vota to discuss your requirements.
Powered by Zama Systems.