Canadian CampaignsData, Security & TechnologyGOTV & Election Day

Advance Poll GOTV Checklist

A practical advance-voting checklist for testing the campaign’s turnout universe, staffing, zones, calls, rides, data updates, and reporting.

Direct answer

What is the practical answer?

Use advance polls as a live GOTV rehearsal. Confirm the official dates and voting information, prepare a current supporter universe, assign door and phone lists, staff ride and data workflows, set reporting times, remove voters who have already voted, and debrief after each day. The goal is both to help supporters vote and to expose problems before Election Day.

On this page
  1. Confirm official voting information
  2. Prepare the advance-vote universe
  3. Run the full operating cycle
  4. Debrief with evidence
  5. Carry the lessons into Election Day
  6. A practical example
  7. Working checklist
  8. Common mistakes
  9. Sources and further reading

Confirm official voting information

Use the election authority’s current information for dates, hours, locations, identification, registration, and voting methods. Do not rely on an old election graphic or a volunteer’s memory.

Prepare a short, approved voting-information reference for callers and canvassers. They should know where to find an answer rather than guessing.

Prepare the advance-vote universe

Identify supporters and other approved voters who may use advance voting, have requested a ride, need information, or have not confirmed a plan. Remove do-not-contact, moved, invalid, and already-voted records.

Size the universe to the available hours and volunteers. Advance voting is a rehearsal only if the campaign can complete and review the work.

Run the full operating cycle

  • Current door and phone lists.
  • Zone or shift ownership.
  • Short advance-vote script and response codes.
  • Ride request, dispatch, and completion process.
  • Voted update import or manual entry.
  • Paper list return and reconciliation.
  • Fixed command reporting times.
  • Volunteer check-in, food, breaks, and safety.

Debrief with evidence

After each day, compare the starting universe, voters confirmed as voted, remaining priority records, open rides, completed calls or routes, and unresolved data issues. Ask what delayed the operation and whether the information was usable.

Assign corrections with owners and deadlines. “Improve the ride desk” is not enough. “Add a return-trip status and recruit two accessible-vehicle backups before Friday” is.

Carry the lessons into Election Day

Update zone size, scripts, training, volunteer roles, list formats, driver capacity, and backup plans. Preserve what worked rather than redesigning the entire system.

The Election Day plan should be simpler because advance voting removed voters and answered operational questions.

A practical example

During the first advance-vote day, the campaign learns that callers cannot see which voters requested rides and the ride desk closes requests too early. That evening, the team adds a shared status, assigns a dispatcher for each shift, and separates drop-off from completed return. The correction is tested the next day.

Working checklist

  • Verify official dates, hours, locations, identification, and registration information.
  • Create the current advance-vote target universe.
  • Prepare lists, scripts, outcomes, zones, and shift leads.
  • Staff phone, door, ride, data, and command functions.
  • Set reporting and list-return times.
  • Update already-voted records and rebuild the remaining universe.
  • Debrief each day and assign specific corrections.
  • Update the Election Day plan from real results.

Common mistakes

  • Treating advance voting as only a reminder campaign.
  • Using unverified voting information.
  • Running a smaller operation with completely different tools and roles.
  • Leaving already-voted supporters on later lists.
  • Holding a debrief without assigning corrections.

Sources and further reading

Election law, privacy, calling rules, voting methods, and campaign-finance requirements vary by jurisdiction and can change. Verify current requirements with the applicable election authority before acting.

Key takeaways

What campaign teams should remember

  • Use official voting dates, hours, and locations.
  • Run the same basic workflow planned for Election Day.
  • Update already-voted records promptly.
  • Track ride, access, list, and staffing failures.
  • Make specific corrections after each advance-voting day.
Frequently asked questions

Common questions about advance poll gotv checklist

Why are advance polls important to GOTV?

They allow supporters to vote earlier and give the campaign a real test of lists, scripts, rides, data entry, and reporting.

Should the campaign contact every supporter during advance polls?

Use the campaign’s priority and capacity plan. Focus on people with advance-vote intentions, ride needs, uncertainty, or another approved reason for follow-up.

How should already-voted information be handled?

Use the lawful and approved source, record the update, and remove the person from active chase lists as quickly as practical.

What should be reviewed after each day?

Review voter completion, list quality, staffing, route size, phone pace, ride performance, access problems, data delays, and unresolved requests.

CampaignGatewayEditorial review

Reviewed by CampaignGateway Operations Team on 2026-06-17. Campaigns should always verify legal, election, privacy, accessibility, and voter-contact requirements with the appropriate election authority or qualified adviser.

CampaignGateway platform

Put the plan into practice

CampaignGateway brings voter contact, volunteers, walklists, GOTV, scheduling, public campaign pages, and reporting into one campaign workspace.