Volunteer management for a fundraising 5K: coordinating a crew you can't see
A 5K is not a gathered event. Your volunteers are spread along five kilometres of road for a 45-minute window where everything that goes wrong happens at the same time. Here's how to plan, brief, and communicate with a crew you can't see.
Volunteer management for a fundraising 5K is fundamentally different from volunteer management for a gathered event. The standard playbook (pre-event briefing, all-hands communication, a coordinator who can see the room) does not survive contact with a road race. Your crew is spread along five kilometres of route, mostly without line-of-sight to you or each other, for a 45-minute window where everything that goes wrong happens at the same time.
This guide covers the parts of 5K volunteer management that gathered-event experience does not prepare you for: route-based role planning, location-specific briefings, pre-race confirmation that actually reduces no-shows, race-day communication across a distributed crew, and what to do at the finish line to bring half your team back next year.
Plan by position on the route, not by job title
The standard mistake is thinking in role categories. “We need course marshals.” “We need water station volunteers.” That framing produces vague recruitment and uneven coverage.
Start with the route itself. Walk it. Mark every physical position that needs a human:
- Each turn (one marshal minimum, two for confusing turns)
- Each road crossing (one marshal with reflective gear)
- Each water station (two to four volunteers)
- The start (announcer, MC, three to five staging crew)
- The finish (chip puller or tag tearer, photographer, water hand-off, medical eye)
- Setup and teardown crew (separate from the race crew so no one works the entire morning)
A 200-runner 5K typically needs 8 to 12 specific course positions plus 8 to 10 start/finish positions plus 4 to 6 setup crew. That is 20 to 28 distinct named positions, not “around 25 volunteers.”
Each position is a different job with different requirements. The marshal at turn 4 stands alone for two hours and needs to know the cutoff time, the lead bike timing, and what to do if a runner goes the wrong way. The finish line tag tearer is in a high-energy crowd for 30 minutes and needs to know nothing about turn 4. Treating them as interchangeable is what produces volunteers in the wrong role for them.
Once you have the positions counted, the recruitment math follows directly: target two volunteers per fixed marshal location. Twelve marshal positions means recruit 24 marshals. The reason for the doubling is partly no-show insurance, but mostly breaks. A volunteer standing alone at the same intersection for two hours needs a bathroom at some point. Two people at the same location can cover each other.
If fewer show up than the doubled plan (say 18 instead of 24), drop most locations to a single marshal and keep two unassigned as roving floaters. The floaters walk or bike the route giving five-minute breaks to the marshals who are now solo. This is what separates the second-year race director from the first: building break coverage into the plan rather than hoping nobody needs to leave their post.
Brief by location, with the written brief as the primary
A pre-race all-hands briefing fails for two reasons. First, each position needs different information, so briefing everyone together means each person tunes out most of it. Second, briefings ask people to remember things they were told once at 6am, which they don’t.
The model that works: written first, briefing second.
Write a one-page brief per position. Each one covers:
- Arrival time and exact location (with a map screenshot if needed)
- What they will be handed at check-in (signs, cones, vest, water cooler)
- What to do when the first runners arrive
- What to do when the last runner passes (when they can leave, who to confirm with)
- The one named person to call if something goes wrong, and how to reach them
Send it 48 hours before. Print copies for race-morning check-in. The brief is the primary delivery. Anyone who reads it knows their job. The morning briefing exists for the people who didn’t read it and for last-minute questions, not as the main channel for information.
Each role group also needs a position lead: a senior volunteer or staff member who runs that group’s check-in and briefing on the morning. The marshal team has one lead. The water station team has one lead. The start/finish has its own. These leads handle the in-person briefing for their group without being distracted by other roles, take their group through any last-minute changes, and become the first escalation point during the race. A marshal at turn 4 who runs into a problem calls their lead, not the race director. The lead either handles it or escalates it. This keeps the central dispatcher from being buried in low-priority issues during the race window.
Recruit by category, then sort locations within it
The instinct to ask volunteers “what role would you like?” or to publish named positions for direct claim doesn’t work as well as it sounds. Asking by preferred role concentrates everyone at the finish line. Publishing named slots creates a scramble for the easy positions and leaves the hard ones unfilled, with the volunteers who end up at the bad spots feeling cheated.
A better approach: sort by physical preference, then handle location distribution as a second step.
Frame the signup questions around what the work actually feels like, with each option roughly as appealing as the other:
- Would you rather lift heavy things for an hour and then be done, or stand in one spot for two hours?
- Do you prefer being in the middle of a crowd, or quieter work away from people?
- Are you comfortable being outside in cool weather for several hours?
These sort people into the broad categories: setup and teardown crew (heavy lifting, short duration), course marshals (standing alone, quiet), finish line (crowd, energetic), water station (standing, social).
Then within each category, distribute by location. Once the marshal group is assembled, let them see their location options and sort it out among themselves. People accept the road crossing at the edge of the parking lot more readily when they can see that the other marshals are also at remote intersections. The unfairness softens when it is shared with peers doing the same job.
This also produces a better match between volunteer and role than the everyone-applies-for-finish-line approach. People who chose “standing alone, quiet” over “in the middle of a crowd” are the right people for course marshal roles. They self-selected accurately because the choice was framed around the work, not the prestige.
Confirm twice in writing, and use reply rate as your forecast
No-show rates for outdoor charity events typically run between 10 and 25 percent. The single biggest predictor of no-show is recency of last confirmation. The cadence that works:
- At signup: automated confirmation with role, time, and location
- One week before: reminder with the one-page role brief attached, asking for a reply to confirm
- Day before: short message with morning details (parking, weather plan, name and number for last-minute issues)
The reply rate to the one-week-before message is your no-show forecast. Volunteers who reply show up at roughly 90% rates. Volunteers who do not reply show up closer to 60%. If you have 10 unreplied volunteers, plan to be short 4 of them. Recruit a spares list accordingly and have it ready to deploy on race morning.
Most coordinators discover their no-show rate at 6
on race day. The replies tell you a week earlier.Plan race-day communication around a dispatcher
The core decision in race-day communication is not what tool to use. It is who is doing nothing but dispatching.
A 5K underway has dozens of small things happening at once: volunteers checking in, runners needing assistance, sponsors arriving late, supplies running short. Most of these are not urgent. A handful are. The job of separating urgent from routine, and routing each one to the right person, cannot be done by anyone who is also trying to solve the problems themselves. It is a full-time role for the duration of the race.
The traditional setup uses radio for boss-to-boss communication only. The race director has a radio. Each position lead has a radio. The leads call up with issues; the director routes decisions back. This works for larger races with the budget for equipment and the time to train the leads on radio discipline.
Putting radios in the hands of every volunteer does not work. Radio takes training. Brief volunteer calls are hard to keep short and disciplined. The handful of channels available cannot accommodate everyday small-issue traffic (“we are almost out of water cups”) without burying the genuinely urgent calls.
For most charity 5Ks, a digital tool with role-tagged channels replaces the radio model entirely, and replaces the need for a position lead with a radio at every spot. Each volunteer has a phone. Each position group has a channel. The dispatcher sits at one place with visibility on every channel. A shared event communication app gives this structure without the equipment costs or training overhead of radios, and leaves a written log of what happened for the post-race debrief.
Whatever tool you use, the trap is the same: letting the dispatcher leave their post to solve things in person. When water station 1 calls in low on cups, the temptation is to grab cups and run them out. Do not. The moment the dispatcher leaves the desk is the moment a runner falls at turn 6 and there is no-one listening.
The dispatcher’s job is 100% dispatch and delegation. When the cups call comes in, the dispatcher pings the setup crew: “10 sleeves of cups to water station 1, please confirm.” A setup volunteer with a vehicle handles the fix. The dispatcher stays at the desk and is ready for the next call.
This role can be filled by a senior staff member, a board member, or an experienced volunteer who is not holding a critical role elsewhere. What matters is that they sit, they monitor, they dispatch, and they do not go solve things themselves.
Build retention from the start line, not the thank-you email
The single biggest predictor of whether a volunteer comes back next year is whether they felt seen during this year. A generic “thank you to all our amazing volunteers” email does not move the needle. What does:
- The race director walking the route during setup and speaking briefly to each position, even for thirty seconds
- A named hand-off when a volunteer’s shift ends (“Maria is done at turn 4, the support van is picking her up at 9”)
- The post-race thank-you including a photo of each position with the volunteer’s name attached, not a group shot of the start line
- A specific ask the following autumn (“we are planning next May’s race and you were excellent at the finish line. Want the same position again?”)
A 5K that handles this well typically settles into 40 to 60 percent of year 2’s volunteers coming from year 1. That changes everything about the recruitment burden in year 2. People who return know the role, need less briefing, and have realistic expectations. Year 1 is hard. Year 3 is something close to a well-run operation.
This is also where keeping records of the right things matters. Not just who volunteered, but which position they worked, whether they showed up on time, whether they handled the role well, and whether you would put them in a more or less demanding spot next year. Most charities recruit from scratch every year because they kept no notes from the last one.
What this looks like in practice
A 5K with 250 runners that has done this well typically has:
- 20 to 25 distinct positions on the route and at start/finish, recruited at two volunteers per position (40 to 50 confirmed volunteers in total)
- 2 designated roving floaters covering breaks and gaps during the race
- A one-page written brief delivered to each volunteer 48 hours before, with morning briefings as a backup for stragglers
- A position lead for each role group (marshals, water, finish line, setup) who runs their group’s check-in and acts as the first escalation point during the race
- A full-time dispatcher monitoring all communication channels, not solving problems themselves
- A reply confirmation from at least 75% of volunteers in the final week, with spares ready for the rest
- Position-specific thank-yous within 48 hours, naming each volunteer’s actual spot
- A volunteer database that lets next year’s planning start from a list of last year’s reliable people, not from zero
None of these individually is dramatic. Together they are the difference between a race director who runs the event and a race director who chases the event for four hours hoping nothing breaks.
The 5K itself is straightforward. The volunteer operation is what makes it sustainable to run again next year.