How to Organize a Campaign Ride Desk

Confirm the rules and campaign policy

Transportation laws, election rules, insurance, driver requirements, accessibility obligations, and party policies may apply. The campaign should confirm them before recruiting drivers or promising rides.

Write the policy down. Drivers and dispatchers should know what the campaign covers, what it does not, how incidents are reported, and who can approve an exception.

Collect only what dispatch needs

A ride request should include contact information, pickup point, preferred time, voting location or voting method, number of passengers where relevant, and accessibility information needed to match the vehicle. Avoid collecting medical history or unrelated personal detail.

Ask for consent to share the necessary details with the assigned driver. Keep the full campaign voter record separate from the driver view.

Use clear ride statuses

• Requested: received but not yet confirmed.
• Contacted: dispatcher attempted confirmation.
• Confirmed: time, location, and need verified.
• Assigned: driver accepted the request.
• Dispatched: driver is on the way.
• Picked up: passenger is in transit.
• Waiting or return required: dispatcher remains responsible.
• Completed: rider returned or service concluded.
• Cancelled or unable: reason recorded briefly and respectfully.

Prepare and support drivers

Confirm availability, vehicle type, accessible capacity, phone number, licence and insurance requirements, geographic comfort, and whether the driver can wait or complete a return trip. Give the driver only the information needed for the assignment.

Use a central dispatcher. Voters should not receive a list of volunteer phone numbers, and drivers should not independently rearrange several requests without updating the desk.

Build time and safety buffers

Voting lines, parking, mobility, weather, and traffic make ride duration hard to predict. Do not schedule back-to-back trips with no buffer. Keep at least one backup driver or accessible option where possible.

Create an incident and no-contact process. The dispatcher should know what to do if the rider is unavailable, the voting location changes, the driver is delayed, or a safety concern arises.

A practical example

A voter requests an afternoon ride and notes that a vehicle with easier entry is needed. The dispatcher confirms the time, assigns a suitable driver, shares only the pickup and contact information, and keeps the request active until the voter has returned. The driver never asks the voter to confirm support or how they voted.

Working checklist

• Confirm election, transportation, insurance, accessibility, and campaign rules.
• Create one ride queue and one dispatcher role.
• Collect minimum contact, pickup, timing, passenger, and accessibility information.
• Obtain consent to share details with the assigned driver.
• Confirm drivers, vehicles, availability, and backup capacity.
• Use clear statuses through return and completion.
• Protect ride records and remove unnecessary details when appropriate.

Common mistakes

• Promising rides before confirming driver and insurance policy.
• Collecting detailed medical information that dispatch does not need.
• Giving drivers access to the full voter database.
• Closing a ride when the voter is dropped off without planning the return.
• Connecting transportation service to the voter’s political choice.

Sources and further reading

• Elections Canada — Ways to Vote
• Office of the Privacy Commissioner of Canada — Guidance for political parties on protecting personal information
• Elections Canada — Political Financing Handbook for Candidates and Official Agents

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.