Election Night Reporting (ENR) Use Case

Title: Election Night Reporting Diagram - Description: Election Night Reporting Diagram. This diagram highlights election night reporting in the election process between vote tallying and election reporting, after (and slightly overlapping) auditing. It also shows the flow of reporting unofficial and official results to stakeholders (voters, election officials, media).

The primary purpose of election-night reporting (ENR) is to provide election results to election results consumers (election stakeholders, voters, public, media, and others). Election results represent the total counted votes from each reporting context (precincts, county, etc.) exercised in a state. An ENR tool generally operates from the highest-level reporting context (e.g., state or county). Results may reach the ENR in many possible ways depending on the election processing (distributed, centralized), dominant voting type (absentee only vs. mixture), state laws (deadlines for accepting/processing absentee, provisional ballot types), reporting abilities they are designed to support (incremental, batch; before, during, after election/polls-closed). Typically, initial uploads of results (by EOs) are provided to the ENR and may be updated as additional results or corrected errors are processed. ENR tools may provide users with overall results process completion information indicating what results have been received, are complete, and so forth. Results are finalized and certified after official canvassing which reviews unofficial results after all are loaded and any corrections are made. ENR tools involve the coordination of a number of factors affecting their operation and implementation. They must be prepared to process and provide data accurately, securely, and without loss of service throughout the entire reporting process and under heavy upload or access periods. They must be able to receive, resolve, integrate and manage results data with respect to a number of different sources (systems: tabulator, EMS, VR; reporting-contexts: precinct, county), transport methods (physical; logical/remote: modem, wired, wireless), data formats (CDF, XML, CSV, ), codings (contest, county), and destinations (published web, data subscribers: media, stake-holders). All throughout the security, integrity, and reliability of the data and process should be maintained. ENR implementations may exist standalone or may be embedded inside other systems (such as an EMS). They may also access other systems to obtain results data or context data (such as voter turnout, voter-specific information from a VR system). They may be implemented using a variety of architectures and approaches ranging from standalone, on-site systems to distributed, cloud-based solutions. In all cases, at minimum, they enable users to generate reports per reporting context. Beyond that, many other data interaction, filtering, interpretation, and reporting options are available. Data formats may be used both on the input and output sides, enabling both results input/uploading as well as results access/download via specific formats.

Title: Election Night Reporting Scenarios - Description: Image showing Election Night Reporting Scenarios.
WHAT? Provide election results to the election results consumers
WHEN? Before, during, after an election
HOW? Scenarios:
1. Election results input. Cases: direct aggregation/upload; indirect aggregation/upload; updating; data resolution; canvassing.
2. Election results output. Cases: publish to website; publish to subscribers.
3. Election results use. Cases: access website; access downloadable data; design/generate report; view report.

Image also shows flow chart of ENR to report totals or reports.

Use Case Scenarios

WHAT | Provide election results to election results consumers

WHEN | (Before, during, after)

  1. Voting-process-type (in-person, early-voting, absentee-voting)

  2. Voting-event (election-day; polls-closed)

HOW | Scenarios

  1. Election results input

    1. Direct aggregation/upload (communication from systems: tabulators, EMS, VR -> ENR)

    2. Indirect aggregation/upload (aggregate + share from precinct --> ENR)

    3. Updating (frequency: ad-hoc, incremental; cause: change, error, new-results)

    4. Data resolution (different sources, different codes, different formats)

    5. Canvassing (reviewing/verifying/accepting results, changes, errors, updates)

  2. Election results output

    1. Publish to website (statically, interactively, for download)

    2. Publish to subscribers (media, election stake-holders)

  3. Election results use

    1. Access web-site

    2. Access downloadable data

    3. Design/generate report

    4. View report

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 Action Size Date Who Comment
PNGpng image014.png r1 manage 101.2 K 2016-08-23 - 01:27 BenjaminLong  
PNGpng image015.png r1 manage 98.1 K 2016-08-23 - 03:14 BenjaminLong  
Edit | Attach | Watch | Print version | History: r13 < r12 < r11 < r10 < r9 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r13 - 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.