Running Club Volunteer Burnout: How to Stop It
Run club volunteers quit from vague, endless jobs, not hard ones. How to scope roles, share the load, and keep the people who keep the club running.

Running club volunteers burn out when the job has no edges. Someone says yes to one visible task, leading a pace group or posting the weekly run, and then slowly absorbs everything adjacent to it, with no term, no backup, and no graceful way to hand it back. The fix is not more gratitude. It is scoping every role down to one repeatable task with a visible boundary and an end date, and moving the club's operational memory out of one person's phone.
Most advice about growing a running club is about recruiting members. Almost none of it is about the six or eight people who make those runs actually happen. That small group is the real ceiling on how big a club can get, and it is the part nobody plans for.
Why do running club volunteers burn out?
Because the work expanded and the agreement never did.
A volunteer agrees to lead the Saturday 9:00 group. Two months later they are also answering route questions in the group chat, welcoming new runners, deciding the weather call, and getting texts that start with "hey can you post this." Nobody handed them those jobs. The jobs just drifted toward the person who was reliably there.
This is not a motivation problem, and it is worth saying that out loud because clubs get it backward constantly. The people who quit are usually the ones who cared most. Caring is exactly what made them absorb the extra work in the first place.
It also matters more every year, because club formation is outrunning the volunteer bench that has to support it. Strava's 2026 community report, published in May 2026, found that running club creation grew roughly 3.5 times year over year through the back half of 2025, with club-organized events up about 1.5 times, and the platform passing one million clubs across all sports. More clubs and more events do not automatically produce more people willing to organize them.
What burnout looks like before someone quits
The signals are quiet, and they are almost always misread as scheduling problems.
- The run leader who used to arrive ten minutes early now shows up right at start time.
- Replies in the group chat get shorter, then stop having questions in them.
- Someone silently drops the part of the job they liked least, like the post-run photo or the newcomer follow-up, and nobody notices for a month.
- A volunteer starts appearing only on the weeks they are scheduled to lead, and not otherwise.
The loudest signal is silence. People rarely announce that they are burned out. They just become less available, and the organizer reads the calendar conflict instead of the pattern underneath it.
Turnover is also the normal baseline, not a sign something went wrong. A 2026 summary of volunteer retention research put the commonly cited average retention rate at about 65 percent, meaning roughly one in three volunteers do not return from one year to the next. That figure comes from a July 2026 VolunteerBadge roundup aggregating 2025 and 2026 sector sources. Read it as planning data: if a third of your bench turns over annually and your bench is four people, you are one bad quarter away from being the club.
The four jobs that quietly become one person's problem
Almost every club concentrates the same four responsibilities on the same one or two people.
Route and pace planning. Starts as picking a loop. Becomes owning every distance option, every weather call, and every new runner's "what pace is that group" question.
The welcome. Whoever is naturally warm to newcomers becomes the permanent greeter, then the follow-up texter, then the person who feels personally responsible when someone does not come back a second time.
Communication. One person ends up posting every run, answering every DM, and carrying the calendar in their head.
The record. Who came, who paid dues, who is new, who has not been seen in a month. This one is invisible right up until that person is on vacation, and then nobody in the club can answer any of it.
Notice the pattern: three of those four are information jobs. That is precisely why they collapse onto one person. Information sticks to whoever happened to write it down first, and it does not transfer just because someone else volunteers.
How do you scope a volunteer job so it does not grow?
Write the job in one sentence that contains a verb, a frequency, and an end.
"Lead the 9:00 pace group on the first and third Saturday, through December." That sentence is a job. "Help with run leading" is not a job, it is an open invoice.
A few rules that make roles survivable:
- Give every role a term with an actual end date. A term turns stepping down into a normal calendar event instead of a resignation someone has to feel guilty about. It also gives you a natural moment to ask again, which is much easier than asking cold.
- Name what the job is not. The run leader does not own recruiting. The social lead does not own the roster. Unstated boundaries always default to "yes, apparently that is yours too."
- Never staff a role one deep. Two people on a job means one can miss a week without it becoming a group-chat emergency. It also means the second person already knows how the job works when the first one's term ends.
- Ask for the specific thing, not for help. "Can you lead the 9:00 group on the 14th" gets a yes. "We really need more volunteers" gets sympathy and silence.
Get the club's memory out of one person's phone
Here is the part most clubs skip, and it is the one that makes everything else possible.
The reason a volunteer job cannot be handed off is usually that the information behind it lives nowhere official. The roster is buried in a chat thread. The route is in somebody's watch history. Attendance is in one person's memory. Dues are in a text message that says "got it, thanks." You cannot hand off a job whose entire operating manual is somebody's recall.
Fix the record first and the roles become transferable almost automatically. That means a shared roster with named admin roles, events with RSVPs that more than one person can post, and a single place the calendar actually lives.
This is where the default tool stack costs the most. GroupMe or WhatsApp for the talk, Strava for the run, a Google Form for signups, a spreadsheet for the list, and Venmo for dues is a workable setup for exactly one person: the one who owns all five logins. Nobody can take over a job that spans four tools they do not have access to. Consolidating the operational side is most of what makes running a running club a role someone else can step into rather than a personality trait of the founder.
How do you build a bench before you need one?
You recruit from the people already doing the informal version of the job.
The runner who always brings extra water is your logistics person. The one who talks to every unfamiliar face at the start line is your welcome lead. They are already doing the work. All you are adding is a name for it and a boundary around it.
Then make the first ask small and time-boxed. One shift, one event, one month. People say yes to a defined commitment and freeze at an open-ended one, which is the same dynamic that burned out the last person.
Thank people in public and specifically, by what they actually did. "Thanks to everyone who helps out" lands on nobody. "Maria led the 10:00 group every other Saturday since March and rerouted us around the closed bridge twice" lands on Maria, and on the three people quietly deciding whether this club appreciates its organizers. Recognition is the cheapest retention tool a volunteer-run club has.
Finally, run a real handoff when a term ends. One run shadowed, the roster and role access actually transferred, and a public thank-you. A clean exit is the single biggest reason the next person says yes, because they can see that the job has a door on both ends.
Common questions about running club volunteers
How many volunteers does a club actually need? Fewer than you think, if the roles are scoped, and far more than you have if they are not. A practical floor is two people per recurring responsibility, so no single absence cancels anything.
Should volunteers be paid or comped? Most clubs cannot and do not need to. What volunteers consistently ask for is a defined job, a term, and visible appreciation. Comped race entries or club gear are nice, but they do not fix an unbounded role.
What do you do when a burned-out volunteer goes quiet instead of quitting? Ask directly and privately, and make the easy answer available. "Do you want to keep the 9:00 group through the end of your term, or hand it off in September?" Giving someone a dignified exit usually keeps them in the club as a member, which is worth far more than one more month of a resentful run leader.
How do you ask someone to step down? Use the term. That is what it is for. When the term ends you thank them, run the handoff, and do not automatically renew. No confrontation required.
If you want the roster, roles, events, and RSVPs in one place instead of spread across five apps, that is what RunLink is built for. Set up your club and get the club's memory somewhere the next volunteer can actually reach it.