New York Codes, Rules and Regulations
Title 9 - EXECUTIVE DEPARTMENT
Subtitle V - State Board of Elections
Part 6210 - Routine Maintenance and Testing of Voting Systems, Operational Procedures, and Standards for Determining Valid Votes
Section 6210.8 - Test deck procedures
Current through Register Vol. 46, No. 39, September 25, 2024
Each county board shall prepare a test deck to be used to verify that the voting system's election configuration and ballot configuration is correct and that the voting system will accurately cast and count votes within each individual ballot configuration.
(a) The ballots shall be voted with a pre-determined number of valid votes for each candidate, each write-in position, and each voting option on every proposal that appears on the ballot as certified by the county board in order to verify that the vote system is programmed to correctly count the ballots. The deck includes one or more ballots that are intended to fail, have been improperly voted, or which are voted in excess of the number allowed by law, and one or more ballots on which no votes are cast, in order to test the ability of the system to recognize and/or notify of an under or over vote. If there is more than one ballot configuration for an election, a separate test deck is created for each ballot configuration. In election districts that will utilize a single voting system for two or more ballot configurations, required testing shall consist of a different test deck for each ballot configuration to be utilized on such voting system, to ensure that the addition of multiple ballot configurations has not affected the accurate casting and counting of votes within individual ballot configurations.
(b) Test decks which include sub-decks are created once election configuration and ballot configuration tasks have been completed, and ballot configurations have been verified, utilizing detailed procedures for preparation of a test deck prescribed to the county board by the State Board. Using a tool or tools, (ie Excel) make a test script for each specific ballot within the test deck, such that when all test ballots within the test deck are completely cast it will accurately test all positions, undervotes, overvotes, write-in positions, propositions and ballots that are deliberately designed to fail.
(c) Upon creation of a test deck and prior to use in pre-qualification testing, the test deck must be validated by casting the ballots in the test deck on a voting machine or system, printing out the tabulation report and comparing same to the predetermined expected results for that test deck to ensure accuracy. Any corrections to the test deck must be made prior to its use in pre-qualification testing.
(d) Once a test deck has been validated, test decks are run by a bi-partisan team on each voting system for which that particular ballot configuration is valid. The team shall enter at least one ballot from each sub-deck using each feature intended for people with disabilities, and enter at least one ballot from each sub-deck using each language provided on the unit. While one team member casts 1 votes for the test, the other member shall monitor that votes are cast correctly.
(e) The bi-partisan team shall compare the accuracy of the results reported by the voting system to the expected results and determine if the machine passed or failed. Any discrepancies indicate a failure and must be investigated.
(f) For DRE systems, the paper audit trail records with the accumulation report shall be signed by the testing team, then bound and placed in secure storage. For optical scan voting systems, the results report shall be signed by the bi-partisan team, and placed in secure storage. After all voting systems upon which a particular ballot configuration is valid have been tested, the test deck shall be stored with all corresponding reports, audit trails, log sheets and system logs required to be produced and reviewed pursuant to paragraph (e)(3) of this section.
(g) For central count paper-based systems, after entering all election ballot codes and creating header cards, if required by the software, the following verification procedures shall be performed: