How to Build and Check an Eligible Voter List
Build a clean voter list by defining eligibility, removing duplicates, checking contact details, resolving corrections, and collecting only necessary data.
By Votes.ng team · Published · Updated
Start here
The voter list is the foundation of a private organizational election. If the list is wrong, even a perfectly designed ballot can produce an outcome people question.
The goal is not to collect as much member information as possible. The goal is to identify the people who are eligible to participate and give each of them one clear route to the ballot.
Define eligibility before exporting a spreadsheet
Start with the organization's rules.
Eligibility might depend on:
- active membership status
- dues or financial standing
- enrollment status
- employment status
- a record date
- a specific class of membership
- membership in a chapter, faculty, committee, or congregation
Do not change eligibility simply because one member list is easier to export than another.
Write the rule in one sentence first. For example:
Eligible voters are active members recorded as paid through September 30, 2026.
The exact rule is for the organization to decide according to its governing documents and applicable requirements.
Create one source list
Organizations often have several overlapping lists:
- mailing list
- payment list
- WhatsApp group
- event registration list
- member directory
- older election list
Choose one controlled source for the election and reconcile differences before importing voters.
Do not continue editing three separate copies after that point. Name the approved version clearly and record the date it was approved.
Remove duplicates carefully
Duplicate records can happen because of:
- different capitalization in email addresses
- a person using two email addresses
- repeated spreadsheet entries
- a name written differently in two systems
- family/shared contact details
Do not delete a record only because two people share a surname or phone number. Confirm identity using the fields your organization legitimately maintains.
Votes.ng's CSV workflow can help classify duplicates and invalid records during import, but the organizer still owns the decision about who is eligible.
Check contact details
If email will deliver voting access, check obvious problems before launch:
- missing @
- extra spaces
- accidental commas
- old institutional address
- duplicate email assigned to two different people
A clean email list reduces last-minute support requests.
Do not send a test message containing real voting access before the Live election is ready.
Collect only what is needed
A voter list should include only the information needed for this election.
If name and email are enough for the election process, avoid importing home address, date of birth, ID number, notes, or unrelated profile information.
This is both a privacy and operational advantage. Less unnecessary data means less information to protect, review, correct, and eventually delete.
Check the privacy requirements that apply to your organization and voters. Use your applicable regulator and reviewed policy when deciding how to handle election information.
Decide a correction deadline
Voter-list corrections become more sensitive as opening time approaches.
Set a process for:
- a person missing from the list
- a duplicate
- an incorrect email
- a membership-status dispute
- a person who became eligible after the original export
Do not let informal requests in a group chat become the correction system.
Record who is authorized to approve a correction and when corrections stop.
Freeze the Live electorate at the right time
When an election is moving from test preparation to a paid Live run, the platform needs a stable eligible-voter count and roster.
Votes.ng prices a Live election from the eligible-voter count and restricts roster changes during the supported payment and Live workflow. Finish list corrections before starting paid launch.
The organizer should therefore complete voter-list cleanup before beginning the final launch/payment step.
Separate eligibility from ballot choice
The voter list needs to know who may participate and whether voting access has already been used. It should not become a table of people's ballot choices.
Votes.ng keeps eligibility/participation state separate from ballot contents so an organizer can manage the electorate without receiving a direct voter-to-choice record.
Read How Private Online Voting Works.
Review the final list with simple counts
Before launch, compare:
- expected member count
- imported eligible-voter count
- duplicate count resolved
- records missing usable contact information
- special categories if your rules require them
A count that differs from expectation is not automatically wrong, but it should be explained before voting begins.
Keep a controlled record of the final electorate
Your organization may need to show later how eligibility was established. Keep the approved list and decision record according to your legitimate governance and retention needs.
That does not mean retaining voter contact data forever. Separate evidence that an election was properly constituted from unnecessary long-term personal-data storage.
Final checklist
Before launch:
- eligibility rule written down
- one source list chosen
- duplicates resolved
- contact fields checked
- unnecessary data removed
- correction process defined
- final count reviewed
- election tested
Once the list is clean, the next question is how each person reaches the ballot. Continue with Voting Links and Voting Codes and How to Prevent Duplicate Voting.