Election Results Reporting Contingency Plan: 7 Steps

An election results reporting contingency plan tells your team how to validate, release, correct, and preserve results when the normal publication channel fails. It prevents a website outage, a vendor disruption, or an unverified screenshot from becoming a governance problem. This guide gives election administrators a seven-step plan adapted to their bylaws, election rules, and vendor agreements.

The goal is not to promise that nothing will go wrong. It is to make sure the right people can make the right decision, publish only verified information, and leave a record that explains what happened.

Separate the election result from the results website

A results page is a communication channel. It is not the election record, and it should never become the only place where the organization can prove what was reported. That distinction matters when a site slows down, a social account is unavailable, or a vendor needs time to investigate an issue.

Start by naming the source of truth for every contest. It may be a certified export, an election administrator report, a teller report, or another record specified by the governing rules. Then document who verifies that source, who approves publication, and which channels may repeat it. The public-election guidance in the EAC checklist for securing election night results reporting makes the same useful distinction: reported results need verification and context, particularly before certification.

For a membership or board election, the terminology may differ. Your rules may use “preliminary,” “unofficial,” “final,” or “certified.” Use the labels your governing documents require. Do not let a rushed status post create a new category of result that no one is authorized to issue.

Build the fallback before voting closes

The best contingency plan is specific enough to use at 9:15 p.m. when the person who normally updates the website is unavailable. Keep it in the working file for the election, alongside the normal election operations calendar, contacts, and approval record.

1. Name the primary record. Identify the report or export that controls each result release and where its approved copy is stored.


2. Assign two-person verification. One person compares the publication-ready figures with the source record; a second person signs off before release.


3. Choose alternate channels. Preapprove a backup page, monitored email address, telephone line, or controlled notice location. Make clear which channel is authoritative if the normal site is down.


4. Prepare holding language. Draft a short notice that says results are delayed, what is affected, when the next update is expected, and where verified updates will appear.


5. Set decision authority. State who can pause a release, correct a post, activate the backup channel, or seek direction under the election rules.


6. Protect the evidence. Retain the source report, proofing record, approval, version of each notice, and relevant vendor or support ticket.


7. Test the handoff. Run the backup channel and a correction workflow before the election opens. A contact list that has never been used is not a plan.

Publish in a controlled sequence

When reporting begins, speed should not outrun accuracy. Use a release log with the time, contest or reporting scope, source record version, verifier names, approver, channel, and link or file location.

Each notice should distinguish what is known from what is pending. If certain ballots, divisions, or reporting units are not included, say so plainly. If your rules require a certification step, avoid language that suggests the result is final before that step occurs. This is especially important when participants are watching multiple channels and screenshots begin to circulate.

A well-designed online voting platform can support controlled access, report exports, and reviewable activity. It does not replace the administrator’s duty to apply the organization’s rules. The plan must also say what happens when the platform is not available, or when the reported figures require a correction before release.

Handle a delay or correction without improvising

A delay is not automatically evidence that the election result is wrong. Treat it as an operational event until the facts show otherwise. Pause the affected publication, preserve the records and logs that may be needed, notify the people named in the plan, and use the approved holding statement. Do not ask staff to make quiet fixes while the public-facing figure remains live.

For a correction, preserve the original notice rather than overwriting history without explanation. Publish the corrected figure with a timestamp, identify what changed, and give a concise reason that does not expose sensitive information or ballot choices. Alert the same channels that received the original result where practical. The purpose is not to create drama; it is to prevent two competing versions from becoming the record.

Communication guidance from CISA emphasizes accurate, timely updates and preplanned roles. In a private election, apply that principle within the authority your bylaws, election policy, and counsel establish. An extension, a re-run, or a change to the reporting schedule may require formal approval. It is not a customer-support decision.

Practice the decisions that create pressure

Tabletop exercises work because they expose the missing decision, not because they predict every technical failure. Gather the election administrator, support lead, technical owner, communications owner, and anyone who holds delegated authority. Give them one short scenario and require them to use the actual plan.

Try an outage 15 minutes before results are due. Then add a candidate’s social post claiming to have seen a different total. Who confirms the source record? Who tells the vendor to investigate? Which statement goes out first? Who has authority to say whether the scheduled result release moves? If the group cannot answer in a few minutes, revise the plan and repeat the exercise.

Close the exercise with an after-action note: what worked, what contact or access right was missing, what template needs approval, and when the correction will be complete. Retain that note with the election file. It is evidence of preparation, and it gives the next election a better starting point.

Frequently Asked Questions

What should be in an election results reporting contingency plan?

Include the authoritative results source, verifier and approver roles, alternate publication channels, holding and correction messages, escalation contacts, evidence-retention steps, and a testing schedule.

Can we post preliminary results while certification is still pending?

Often, yes, if the applicable rules allow it and the status is labeled accurately. State what the report covers and what remains pending.

What should we do if an incorrect result is published?

Pause further distribution, preserve the original publication and source records, verify the correct figure using the assigned review process, and issue a timestamped correction.

Does an online voting vendor own the contingency decision?

No. A vendor may operate the technology and supply technical facts, but the organization’s rules determine who can approve communications, schedule changes, certification, or any remedy.

The Bottom Line

A credible results contingency plan protects more than uptime. It protects the chain between the verified record, the authorized decision, and the message participants receive. Build it before voting closes, rehearse it, and keep every release and correction in the election file.

If you need to test your reporting workflow, escalation roles, and evidence package before the next election, talk with the Votem team before the final election calendar is set.