Last-minute changes can create real operational chaos. This issue breaks down what to do when it happens to you. ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­    ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­  
View in browser
ESX News Header

June 10, 2026

TLP:CLEAR

In This Issue:

  • Situation Room: Lessons in Louisiana and Texas illustrate the operational risks of last-minute changes.
  • Resource Library: A new guide, Ready for Redistricting: Implementing New District Boundaries, offers a roadmap for rushed remapping.   
  • Planning Desk: Improve election security with a lessons-learned review after full recovery from any incident.  
Header text: Situation Room

Operational Risks of Last-Minute Changes

 

As election cycles approach, policymakers and courts may adopt last-minute adjustments to election rules and procedures. Election offices can be left scrambling to follow new directives with limited time for implementation.

 

Some Texas counties faced a cascade of changes in the run-up to their March 3 primary. Texas allows political parties to make certain decisions about the conduct of their primaries. One such decision, made by county parties, resulted in a change in two counties. Previous elections relied largely on vote centers, but this election required voters to use the polling places designated for their precincts.

 

While election office communications about the change reached many voters, large numbers remained unaware and attempted to vote from a familiar voting center. Office staffers mounted an effort to redirect them on election day, but the results were chaotic.

 

Citing “mass confusion,” a lower court extended polling hours to allow voters to reach their appropriate voting sites. However, the Texas Supreme Court overturned the extended hours. The conflicting orders created uncertainty about valid ballots, required special handling and new processes by election officials, and increased the risk of error.

 

In another instance of late-breaking change this year, in May Louisiana postponed the congressional primary just days before early voting. Vote-by-mail ballots had already been mailed, with some already returned. In this case, the immediate outcome was that any votes cast in those contests were suppressed from official results. Some voters expressed confusion and anger. Election officials in Louisiana will now need to determine what map is to be used, re-link addresses to the correct districts, and pull together a new election on a short timeline.

 

While changes may be well-intentioned, a 2006 U.S. Supreme Court decision (Purcell v. Gonzalez) emphasized that changes to election procedures shortly before an election can create confusion and risk. Such changes introduce practical and security-related challenges:

  • Operational Confusion - Late changes require rapid updates to procedures, which can create vulnerabilities like miscommunication among election workers, inconsistent implementation across jurisdictions, and errors in voter processing or ballot handling.
  • Increased Risk of Mistakes - Introducing new rules late in the process compresses training schedules and increases the likelihood of human error. Mistakes - such as issuing the wrong ballot style or misapplying eligibility rules - can affect both election integrity and public confidence.
  • System Vulnerabilities - Any rushed update can increase the risk of technical glitches or unintended vulnerabilities, particularly if systems are not fully tested before deployment. Sudden changes may require updates to voter registration databases, reprogramming voting equipment, and adjusting ballot layouts or distribution plans.
  • Public Confusion - When rules change close to an election, voters may receive conflicting information about where, when, or how to vote. This confusion can be exploited, even unintentionally amplifying incorrect guidance. Confusion can deter voting and undermine trust.

When changes happen late, election officials can’t eliminate all risk, but they can minimize, contain, and control it. Focus on:

  • Segmentation - don’t mix old and new systems! Clearly segment old versus new election data. Recent examples show ballots may already be mailed or even returned before changes occur. Separating datasets prevents confusion over which rules apply to which votes. This can preserve chain of custody and support accurate auditing and legal defensibility.
  • Verification - double-check critical data! Run a full validation of data. Prioritize the impacted areas, but verify all data to ensure no downstream effects.
  • Contingency - use fail-safe/provisional ballots! When rules change late, some voters will inevitably arrive at the wrong place. Train poll workers on when and how to use provisional ballots and have clear processes for review.
  • Redundancy - require two-person review! Two sets of eyes are better than one. Have two trained staff review changes. This will minimize human error and the potential for system misconfiguration.
  • Communication - have consistent and clear voter communication! Establish one official, frequently updated source. Confusion about where or how to vote spreads quickly when rules change. Be the single, trusted, authoritative voice! 

The Situation Room focuses on real security incidents and threats in the news relevant to election security. To review previous issues, see the newsletter archive.

Header text: Resource Library

A Roadmap for the Remapping

 

Last-minute redistricting introduces security risks because rushed boundary changes can cause operational confusion, mistakes, system vulnerabilities, and public misunderstanding. A clear process and strong quality controls help election offices reduce these risks while implementing new district boundaries.

 

Ready for Redistricting: Implementing New District Boundaries is a timely guide from Ready for Tuesday to assist election officials who may be required to redistrict at an unanticipated moment in the election cycle, on a tight timeline. It offers checklists for planning ahead and proofing before going public, helping keep the process secure under a compressed timeline.

 

The planning checklist, Safeguards against Common Redistricting Errors, walks through three critical aspects of redistricting work.

 

1. Procedures and Quality Control stresses the importance of:

  • maintaining relationships in your data so that difficult addresses don’t require new research

  • managing address edits by adherence to written procedures and limiting access to appropriately trained staff

  • conducting quality control or review whenever addresses have been edited 

2. Staffing and Capacity reminds you to:

  • allocate sufficient time and resources

  • assemble a team (internal and/or external) with appropriate experience and training

  • set touchpoints where the geographic specialist(s) and election data expert(s) share information and build mutual understanding

3. Data Management covers:

  • normalizing addresses to a common standard

  • troubleshooting geocoding of addresses

  • understanding your district and precinct data

  • coordinating digital and manual updating of splits and using them for quality control

    Redistricting errors can result from the complexity of drawing boundaries when election officials are often dependent on data from a number of different sources they don’t control. The quality control checklist, Common Redistricting Implementation Errors and How to Catch Them, is a simple spreadsheet listing common errors with troubleshooting techniques.


    Ready for Redistricting: Implementing New District Boundaries also offers oversight suggestions for an administrator who may not be working directly on mapping but needs controls in place to coordinate work with other agencies providing map data or services and to ensure timely, accurate completion of the work. 

     

    The Resource Library section of the newsletter spotlights election security resources. All highlighted resources are available online in the Resource Library.

    Header text: Planning Desk

    Week E-21: Post-Incident Activity - Power-up!

     

    Post-incident activity is the final phase of the Incident Response Process, centered on organizational learning to prevent future incidents or mitigate their impact. After recovery is complete - whether the incident was cyber, operational, or physical - this phase is a critical opportunity to capture lessons learned, strengthen incident response and reporting, and enhance overall election security and resilience.

     

    Prioritize post-incident activity with three straightforward steps:

     

    1. Schedule a lessons-learned meeting.

    • Involve all relevant stakeholders.

    • Attendance should be mandatory following any major incident.

    • Your Election Security Working Group should meet after every incident, regardless of severity.

    2. Set clear goals to drive actionable improvement.

    • Understand the root cause of the incident.

    • Evaluate and refine response and reporting processes.

    • Bolster election security and resilience.

    3. Review the incident timeline, response effectiveness, and communication flow by asking these questions:

    • What happened?

    • How well did the Incident Response Team perform?

    • Were our Incident Response Plan and procedures followed?

    • Were our Incident Response Plan and procedures adequate?

    • What information was missing?

    • What actions slowed recovery?

    • What could be done differently?

    • What can be done to prevent future incidents?

    • What indicators should be monitored in the future?

    • Encourage participants to raise additional questions relevant to your jurisdiction to help the Election Security Working Group identify and address vulnerabilities.

    Continuous improvement through post-incident analysis sharpens response strategies and reduces the likelihood or impact of future incidents. Every jurisdiction should regularly revisit and test its Incident Response Plan with the core team and security partners who would support real-world response and recovery.

     

    Encourage your team and partners to subscribe to this newsletter to stay informed about good practices as you update your Incident Response Plan in advance of the 2026 general election.

     

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

    Header text: Election Security News


    Want to get daily updates on election news? Subscribe to electionline.

    • As American elections become more tense, officials are turning to local police | NPR (June 6, 2026) // National
    • Bot web traffic has overtaken human web traffic, data shows | NBC News (June 4, 2026) // National
    • What we learned mapping a year's worth of AI-enabled cyber threats | Anthropic (June 3, 2026) // National
    • 1 big thing: Anthropic's most powerful AI yet | Axios PM (June 9, 2026) // National
    • New CISA directive would reshape how agencies prioritize cyber risk, official says | Nextgov/FCW (June 9, 2026) // National
    • Shasta County election results update delayed following midnight power outage | KRCR News (June 3, 2026) // California

    LinkedIn
    YouTube
    Email
    Website

    Copyright © 2026 Election Security Exchange. All rights reserved. TLP:CLEAR

     

    You are receiving this email because you subscribed to the Election Security Exchange Newsletter.

     

    Find this useful? Pass it along and invite other election teams to subscribe.

    Subscribe

    Election Security Exchange

    712 H Street NE, Suite 2456

    Washington, DC, 20002, United States

    Unsubscribe Manage Preferences