How to communicate with campaign volunteers: a guide for local coordinators

This is not a guide for a presidential campaign with a twelve-person communications team. It is for the coordinator running the volunteer side of a local race: a mayoral campaign, a city council bid, a school board seat, a ballot initiative. One person, sometimes two, holding the operation together for anywhere from 30 to 1000 volunteers depending on how strong the recruitment is, on a budget that does not extend to enterprise tools.

The communication challenge at that scale is different from what a large campaign faces. You cannot afford to give each volunteer individual attention. You also cannot afford to be the single point of contact when sixty volunteers are scheduled across the weekend and three of them want to text you about the same shift.

What works is a small set of pre-built systems that let volunteers help each other, an information rhythm volunteers can rely on, and clear rules about what travels through which channel. None of these require expensive software. All of them need to be set up before the cycle gets hot, because the final stretch is not the moment to design a communication system.

Match channels to what they carry

Most campaigns dilute every channel by sending everything through all of them. Volunteers get an email about the shift, a text about the shift, and a chat reminder about the shift. Then a separate email about strategy. Then another text. The result is everything gets skimmed and nothing reads as urgent.

A working channel structure assigns each channel a job and protects it.

Email. Newsletter material, campaign news, candidate updates, strategic priorities. Used once a day during the active campaign period (more on the daily newsletter below). Volunteers read campaign email; they do not refresh it.

SMS. Shift confirmations, urgent changes, day-of reminders. Nothing else. SMS is for “your canvas shift starts in 30 minutes at the corner of Maple and 4th,” not for “thank you for your support.” The moment you send a non-essential SMS, your urgent ones stop getting read.

In-app chat or group channel. Peer-to-peer coordination, questions about the candidate’s position on issues, ride coordination, field updates. Coordinator presence in chat should be light: answering when no peer can, posting occasional anchor messages, but not driving every thread.

Phone calls. Retention conversations, recruiting new team leads, talking to volunteers who have gone quiet. The high-touch channel for moments when a text would feel inadequate.

When each channel carries different things, all of them stay meaningful. Volunteers learn what to expect from each one. The newsletter gets read because it is not buried under shift logistics. The texts get attended to because they are rare and always relevant.

Set up group chats that scale

Volunteer chat needs structure to stay useful. With every volunteer in one channel, the chat becomes unreadable as you scale past a few dozen people: too many threads, too many notifications, too much traffic that is irrelevant to any individual volunteer’s role. Most people mute it, and the channel stops doing its job.

The structure that works:

• A chat per team or function, scoped to 8 to 15 people each. The Tuesday phone bank crew has their chat. The west side canvass team has theirs. The literature drop crew has theirs.
• A small leadership chat for you and your team leads, 5 to 8 people total. Where decisions get made.
• One campaign-wide announcement channel, posting-only by you. Volunteers see it but do not reply in it. Replies go to their team chat or to their lead.

This is what chat is for: in-team coordination, peer questions, quick field updates that resolve in minutes. It is not for tracking the steady stream of operational items that need follow-up. Those need their own system.

Build a problem queue separate from chat

Over a campaign cycle you will get hundreds of operational items reported: a yard sign was vandalised, a literature box is empty on Elm Street, an address on the call list is wrong, a voter at house 214 wants to host a meet-and-greet, a phone bank script section is confusing volunteers, the opposing campaign is door-knocking your turf. Chasing these through chat threads is a losing game. Half get forgotten. The other half get half-handled and nobody knows the final status.

A simple intake form solves most of it. Set up one place where any volunteer can log an item with the basics: what, where, when, urgency, their name. A Google Form, a Typeform, a Zelos task submission, or whatever submission tool you already have. Each entry lands in a list that you or a designated problem-solver works through.

What the queue does better than chat:

• Each item is logged separately and tracked to resolution, not lost in a scroll
• You can see at a glance what is open, what is being worked on, what is closed
• Volunteers do not have to remember to bring something up at the right moment; they submit and move on
• The same form captures problems, intelligence, and opportunities. You categorise on review.

Acknowledge submissions. A brief reply within 24 hours (even just “thanks, looking into it”) turns the form from a black box into a real channel. Volunteers who feel heard submit more often, and submitting more often is what makes the queue work.

Tell volunteers about the form during onboarding. Mention it in the newsletter once a week. The instinct will still be to text you directly with each thing. Redirect those messages to the form the first few times and the habit takes hold. Brief your team leads to do the same when items come up in their team chat.

Pre-plan with team leads, don’t just appoint them

Team leads are the difference between a coordinator drowning and one running an operation. Most coordinators wait too long to appoint leads, then drop the role on them without preparation. The leads improvise, the coordinator second-guesses them, and the relationship sours within a fortnight.

Three steps to get leads working before you need them:

Recruit them early. Eight to twelve weeks out, identify volunteers who showed up consistently in the recruitment-phase events. The most reliable, not the loudest. Have one direct conversation with each: “I want you to lead the [team name]. Here is what the role looks like. Are you in?”

Involve them in planning the operation. Before routine canvass and phone bank shifts begin, hold a small planning session with your leads. Walk through the shift cadence, the territory split, the script, the data flow, the escalation rules. Two hours together at this stage prevents weeks of confusion later. The leads will also catch things you missed, because they are closer to the volunteers than you are.

Write a one-page voice guideline and brief them on it. When fifteen volunteers are messaging supporters, voters, and each other, the campaign sounds like fifteen different people unless you have agreed otherwise. A voice guideline covers tone (warm, direct, never sneering), how to refer to the candidate (first name, last name, title), things to avoid saying (don’t attack the opponent personally, don’t promise policy specifics that haven’t been announced, don’t speculate about polling), and how to handle hostile responses (don’t engage, log it for the lead). Include two or three example responses to common questions so leads can show new volunteers what good looks like.

Leads who were involved in planning, given a voice guide, and trusted to make decisions in their teams will run the operation better than you would have. They will also be your candidates for paid roles in the next campaign.

Build a daily newsletter as your communication anchor

If volunteers know that something will always arrive on a predictable cadence with the information they need, two things happen. They stop worrying about missing announcements. And you stop receiving the “is the Saturday shift still happening?” messages, because the newsletter said it was, in the same place it always says it.

Weekly works during the months-out routine phase, when there is not enough day-to-day movement to justify a daily send. The transition to daily comes when shift density picks up: typically four to six weeks before election day, when you need volunteers every day and last-minute changes need same-day communication. From that point through election day, the newsletter goes out every day.

A consistent format, sent at the same time. A suggested template:

• One line about where the campaign is today (a milestone, an event, a thank-you)
• Today’s open shifts that still need volunteers, with sign-up links
• Tomorrow’s confirmed shifts and what to bring
• One operational note (a change, a reminder, a request)
• One personal note (a story from a volunteer, a quote from a voter, a thank-you to a specific person or team)

Send it at the same time. 5pm works for many local campaigns: late enough that the day’s news is in, early enough that volunteers see it before deciding what to do tomorrow. Be ruthless about consistency. A boring newsletter sent every day is better than an exciting one that arrives twice a week.

What this prevents: volunteers anxiously refreshing for updates, asking each other “did I miss something,” reaching out to you to confirm things they already know. The newsletter is the answer to most of those questions before they get asked. It also makes the rules about what to keep out of comms (next section) actually hold, because volunteers trust they will hear what they need to hear.

Make support and exit easy

You do not have time to monitor each volunteer for signs of burnout, and you should not try. Two pieces of infrastructure handle most of what surveillance would have caught, with much less work.

Open office hours. A standing time each week, twice a week as the campaign heats up, when you are available for any volunteer to come talk. In person at the office if you have one, video call if not. No agenda required. Volunteers who are wobbling on whether to continue, frustrated with a teammate, confused about strategy, or just need to feel seen will come. The ones who do not come are usually fine. The ones who do come are the ones who need you. Far more efficient than tracking signals you cannot keep up with anyway.

A graceful step-back option. Every volunteer should know, from their first week, that they can step back at any time without explanation and without burning bridges. Build it into the welcome message and repeat it in the newsletter once a month: “If campaigning is taking more than you can give right now, tell us. We will pause your shifts, take you off the chat noise, and welcome you back whenever you are ready. No questions, no guilt.”

Volunteers without this option ghost instead. They stop replying, stop coming to shifts, and never volunteer again, often because they were embarrassed to admit they could not keep up. Volunteers who do have the option use it occasionally and come back, sometimes for the next cycle. The cost of making the option available is essentially nothing. The cost of not making it available is the volunteers you never see again.

What to keep out of volunteer communication

Some information makes its way into volunteer comms by default and should not. The damage from each piece is small. The cumulative effect is a slow corrosion of morale you only notice when the volunteers who quietly stopped showing up in week six do not come back in week ten.

Keep these out of broadcasts to volunteers:

• Polling fluctuations day to day. Tomorrow’s poll will be different. The whiplash demoralises more than it informs.
• Internal staff conflicts or campaign drama. Volunteers are not your therapy network.
• Strategic pivots before they are decided. “We might shift focus to a new area” is not useful until you actually shift. It just makes the plan feel unstable.
• Funding shortfalls without action. If you need money, ask for it specifically. Do not share the panic without the call to action.
• Negative campaign material before it is launched. Volunteers should hear it from the candidate or the campaign manager, not from the volunteer coordinator.

When those topics are tempting, what to communicate instead:

• “Here is what we know and do not know right now.”
• “Here is what we are doing this week to address it.”
• “Here is how you can directly help.”

Volunteers can handle bad news. They cannot handle the feeling that the campaign is being run on vibes. The daily newsletter is what makes this work in practice: when volunteers trust the channel to deliver real information consistently, they accept the absence of the noise you have decided not to send. You can run a calmer, more retained volunteer base on this combination than on any amount of inspirational broadcast.