Connecting election experts, advancing security
Planning insights from the Election Security Exchange

Planning Desk, Week E-13: End-to-End Election Prep & Testing Part 4: Running a Mock Election

Over the last three weeks, we have covered why testing critical election technologies, systems, and processes matters for protecting the integrity and security of data. From software configurations and hardware readiness to post-election workflows and records, functionality and security boundaries must be tested and validated.

Once pre-testing of every component is complete and any issues have been addressed, performing an end-to-end “mock election” can provide the final assurance that all technologies, systems, and processes function seamlessly through each stage of the election. Walking through everything needed to conduct an election as one continuous workflow is another chance to verify that documentation is up to date, training has been effective, and protocols are in place to ensure that data integrity is maintained throughout all data transfers and processing that occurs before, during, and after the election.

A typical mock election might include:

  • Ballot programming and tabulator configuration
  • Creation of absentee and mailed-ballot lists
  • Creation of voter lists for polling locations and electronic poll books 
  • Incorporation of logic and accuracy (L&A) test data to review procedures for data transfer and election night reporting
  • Entry and display of unofficial election night results
  • Reconciliation of ballots, voters, and results
  • Capture and reporting of voter participation information
  • Post-election audits, canvass reports, and certification of the mock election
  • Preparation of storage space and materials needed for record retention

Use a mock election to verify your approach to data integrity and transferring data between election systems, build checklists, and update contact information for key stakeholders and security partners. 

Election officials considering whether to run a mock election might ask themselves:

  • Have we recently experienced high turnover in our office? This end-to-end test is an opportunity for the entire team to review all procedures and can be a vital practice run for new election officials and new and returning staff and election workers.
  • Have we recently implemented new election systems or changes to processes? A mock election can identify training needs and if systems, processes, and data interactions are not functioning as expected. Issues can be corrected before they surface in real time.

With testing of critical technologies, systems, and processes complete and a mock election that ensures they will work in real time, election officials and their teams can approach each stage of the election with renewed confidence grounded in practice and preparation.


The Planning Desk is a running timeline of key election security tasks. You can find prior editions in the newsletter archive.