Electronic Pollbooks (EPBs) Use Case

Title: Electronic Pollbook Diagram - Description: Electronic Pollbook Diagram. This diagram highlights e-pollbooks in the election process between ballot creation and ballot marking.
It also shows how e-pollbooks can be synced between two voting sites; and the relationship between e-pollbook and the VRDB, voter, and ballot.

The purpose of electronic pollbook (EPB) technology is to identify voters and manage their ballots during election operations.Most typically this involves being able to check-in a voter at a given voting location and, depending on the EPB’s technology platform, it may also able to activate a voter’s ballot before they vote on it. Traditionally, these capabilities were made possible via the EPB’s use of voter registration data, which was often pre-loaded on the EPB so it could function in an offline, standalone mode during the election. In other cases, an EPB is able to access this data via a direct, online connection to its corresponding voter registration system. In still other cases, EPB units may be used at multiple voting locations (e.g., vote centers, etc.) and may be able to connect and synchronize with one another, sharing information such as what voters have checked-in and/or voted at particular locations. In addition to these variations, an EPB may support many additional functions ranging from merely looking up/verifying voter information to supporting ballot generation, activation, as well as others.Thus, in this particular form, an EPB begins to appear as a general election operations technology integration platform. In such cases, it inherits the roles, functions, and responsibilities of its dependent use-cases.

Use Case Scenarios

WHAT | Manage voters during election

HOW | Scenarios: check-in voter, activate voter ballot via

  1. Typical-offline: standalone, offline data from VR, activating voter ballots

  2. Online: Case #1, but via online connections (e.g., online connection to VR)

    1. Connect to other sites:

      1. EPB-to-EPB communication between vote centers

  3. Multi-function: Includes cases #1 and #2, but also supports any additional functions (BoD, BM, Ballot activation, etc.)

    1. e.g.,

      1. Lookup voter information

      2. Verify voter information

      3. Ballot generation

      4. Ballot activation

      5. ...

    2. EPB as election technology integration platform

Request for Feedback

For each use case scenario, please address these questions:
  1. Is the use case scenario in scope for the Next Generation VVSG for development of requirements that will undergo testing and certification? or
  2. Is the use case scenario in scope to develop as guidelines for election officials and voting system manufacturers? or
  3. Is the use case scenario not in scope for this work?
  4. If different parts of the use case scenario fall in 1., 2., and/or 3. Please identify as such.
  5. Is anything missing?


Topic attachments
I Attachment History ActionSorted ascending Size Date Who Comment
PNGpng image002.png r1 manage 101.0 K 2016-08-23 - 01:11 BenjaminLong  
Edit | Attach | Watch | Print version | History: r15 < r14 < r13 < r12 < r11 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r15 - 2016-08-23 - BenjaminLong
This site is powered by the TWiki collaboration platform Powered by PerlPLEASE NOTE: This wiki is a collaborative website. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. All the material on this website is in the public domain, including any text, diagrams, or images, unless indicated explicitly. Don't share anything on this site that you do not want to be public. Do not pass any proprietary documents or put any on the TWiki with implied public disclosure. If you do, it shall be deemed to have been disclosed on a non-confidential basis, without any restrictions on use by anyone, except that no valid copyright or patent right shall be deemed to have been waived by such disclosure. Certain commercial equipment, instruments, materials, systems, software, and trade names may be identified throughout this site in order to specify or identify technologies adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the systems or products identified are necessarily the best available for the purpose. Any data provided on this site is for illustrative purposes only, and does not imply a validation of results by NIST. By selecting external links, you will be leaving NIST webspace. Links to other websites are provided because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other websites that are more appropriate for your purpose.