Campaign operations often involve volunteers joining, changing roles or stepping away while work continues. A handover should preserve the status of operational tasks and make clear who now owns them. This guide concerns administration and access, not targeting voters or crafting political persuasion.
Example: an event task changes hands midweek
A volunteer has contacted a venue and requested an equipment quotation, but neither item is confirmed. If the handover says only 'venue sorted', the incoming coordinator may stop following up. A useful record distinguishes enquiry sent, quotation received, approval pending and booking confirmed. Include the next action and the person authorised to approve it.
List the work that remains open
Record each task, its current status, the responsible coordinator and the next action. Include event preparation, document review and logistics where relevant. Separate completed work from work that has merely been discussed. A new volunteer should not need to reconstruct every decision from a long conversation thread.
Preserve operational context
Attach the approved brief, relevant files and the reason for any change. Note deadlines and dependencies in a place the incoming person can access. Keep private information limited to what is necessary for the role. Avoid copying entire contact lists into a handover when a narrower task record is sufficient.
Review access when responsibilities change
Use named accounts and grant only the access required for the assignment. Remove access that is no longer needed while preserving the history of completed work. Check shared documents and communication channels as well as the main platform. A shared login makes it harder to establish who changed a record.
Confirm acceptance of the handover
Have the incoming person review the open items and identify missing information. Record which coordinator can resolve questions. Where the outgoing volunteer is unavailable, assign someone to check the source records rather than inventing the status. A handover is complete when the next person can carry out the work.
Test the platform against this process
Ask Vota to demonstrate the operational features available for task coordination, permissions and history. Confirm any requirements that need configuration or separate development. Keep campaign administration requirements distinct from ballot or election-system requirements. A public product description should be followed by evidence of the actual workflow being proposed.
A quick reference for your team
| Handover field | Useful entry |
|---|---|
| Task | Specific operational work required |
| Status | What is actually completed |
| Evidence | Approved brief or relevant document |
| Next action | What the incoming person must do |
| Owner | Coordinator responsible for questions and approval |
Keep private contact information out of broad handovers
Share only the information needed for the assignment and use the team's authorised channels. Do not move entire contact databases into a personal account because a volunteer is changing roles. Review permissions when responsibilities change and keep the task history available to the appropriate coordinator. Ask the platform provider to demonstrate that access model using separate accounts.
Frequently asked questions
Does campaign administration software also run ballots?
Not necessarily. Treat ballot administration as a separate requirement and ask for explicit evidence of any offered capability.
Should outgoing volunteer records be erased?
Preserve operational history while removing access that is no longer needed.
Discuss your requirements
Discuss your campaign administration and volunteer handover requirements with Vota. Visit Vota.