Running Club Volunteer Roles and Term Limits That Stick
Running club volunteer roles and term limits keep a growing club from living in one founder's head. How to write the roles, set terms, and hand them off.

Running club volunteer roles and term limits are how a club stops living in one person's head. The roles are the handful of named jobs your weekly calendar actually creates, each written down in a single paragraph. The term limit is how long one person holds a job before it is offered again, usually one year. Put the two together and you get a club other people can carry, including the week the founder is sick, moving, or simply done.
Most clubs already have roles. They just have them as habits. The same person picks the route, answers the group chat, and holds the spreadsheet. Nobody wrote any of it down, so none of it can be handed to anyone. The founder ends up as the integration layer between the chat, the signup form, the roster, and the event page, and the club's ceiling becomes that one person's free time.
We covered the symptom in running club volunteer burnout and the hiring in how to recruit run leaders for a growing club. This post is about the structure underneath both: which roles to write, how long a term should run, and how a job changes hands without the club losing what the last person knew. It fits inside our bigger guide to growing your club.
Why does a growing club need written roles at all?
Because a lot of clubs are about to hit their first leadership turnover at roughly the same time. Strava's Year in Sport report, published in December 2025, said running clubs on its platform grew 3.5 times during 2025. That is a very large cohort of clubs now about a year old, which is exactly the age when the founder gets tired and nobody else knows how anything works.
The national support system is paying attention to clubs too. The Road Runners Club of America's 2026 to 2030 strategic plan, announced January 20, 2026, commits the organization to "best-in-class support for clubs, events, and coaches." Useful backing, but no national body can write your club's job descriptions. That part is yours.
An unwritten role has three problems:
- It cannot be handed off. There is nothing to hand over. The job is whatever the current person happens to do.
- It cannot be shared. Two people cannot split a job that has no edges, so it stays one person deep.
- It cannot be declined politely. When someone is asked to "help out more," the only honest answers are yes to everything or no to the club. A written role gives people a third answer: yes to that, and not to the rest.
Which roles does a running club actually need?
Keep the list to the jobs your calendar creates. A club that runs twice a week and hosts one social a month does not need a vice president of partnerships. For most clubs with somewhere between a few dozen and a couple hundred members, six roles cover the real work:
- Run leader coordinator. Owns who leads which group on which night, and who covers when someone cannot. Does not lead every run personally.
- Membership and onboarding lead. Owns the first-timer experience, the roster, and the waiver paperwork, in whatever tool the club uses for it. Does not own recruiting campaigns or social posts.
- Events lead. Owns the monthly social, the goal race weekend, and anything that is not a standing weekly run. Does not own the weekly calendar.
- Communications lead. Owns the group chat, the email list if there is one, and the club's Instagram. Does not set club policy; announces it.
- Treasurer. Owns dues, sponsor money, and the bank account, with a second signer who is not the treasurer. Does not approve spending alone.
- Safety lead. Owns route checks, the dark-season plan, and what happens after an incident. Reviews routes rather than choosing them.
Each role gets one paragraph with four things in it: what it owns, what it does not own, a rough sense of the monthly time it takes, and who it hands to at the end of the term. The "does not own" line does the most work. Unstated boundaries always drift toward the most reliable person in the room.
Two rules keep the list honest.
Write the founder's role too. If the founder has no written job, every unwritten job is still theirs by default. Give the founder one paragraph like everyone else, and make it narrower than feels comfortable.
Write the job, not the person. Do not describe what Sarah currently does and call it the communications lead. Write the job the club needs, then decide who fits it. Otherwise the role walks out the door with the person.
Small clubs can compress. A club under 30 members might run on three roles: runs, members, and money. Fewer roles, same idea. Three written roles with terms beat six habits.
How long should a term be, and why set a limit?
Default to one year, renewable once. Two years in a role is long enough to get good at it and short enough that stepping down is a normal calendar event rather than a resignation letter.
Stagger the terms. If all six roles turn over in the same month, the club relearns everything at once and the founder quietly picks it all back up. Split them across two handoff points, three roles in one season and three in the other, so there is always someone around who did last year's version.
The founder or president role gets a limit too, even if the founder fully plans to stay. The point is not to push anyone out. A limit that exists on paper makes it normal to talk about successors, and a club where succession is a normal topic is a club where asking for help is normal. That is the real case for term limits. They are not about leaving. They are the most reliable way to make asking for help ordinary.
There is a recruiting payoff too. People rarely say no to club jobs because of the work. They say no because yes feels permanent. "Communications lead through next September" is a very different ask from "can you take over the group chat," and it gets a very different answer.
Finally, put a handoff month on the club calendar and keep it. Early fall works for plenty of clubs, because the new person gets a few months of runway before the spring season fills up. The specific month matters less than the fact that it repeats.
How do you hand off a role without losing what the person knew?
Most handoffs fail for a boring reason: the club's assets live in someone's phone.
- The roster is a personal spreadsheet in one person's Google account.
- The waivers are attachments in one person's inbox.
- The group chat has exactly one admin.
- The Instagram password lives in one person's head.
- The bank account has one signer.
None of that is a people problem. It is a storage problem, and it turns every handoff into an export. The outgoing volunteer has to remember everything they hold and send it along, usually in their most tired week. The default stack of GroupMe plus a shared spreadsheet makes this worse, because every role quietly becomes a personal login.
The fix is a rule the whole leadership agrees to out loud: the roster, the event calendar, the waiver records, the chat, and the accounts belong to the club, and every one of them has more than one person with access. When that is true, a role changes hands by changing who has access, not by exporting somebody's phone.
Then run an overlap. Four weeks is plenty. For the first two, the outgoing person does the job while the incoming person watches. For the last two, they swap: the new person does the job while the old one shadows and answers questions. At the end, the outgoing volunteer's access comes off, and they get a specific, public thank-you for what they actually did.
This is where a single club platform earns its place. When the club page, the member roster with roles, the events with RSVPs, and the club chat all live in one place the club controls, most of that list is already handled, and a big part of the handoff is a role change on the roster. That is what RunLink is built for. The bank account and the waiver paperwork still need their own homes, and deciding who owns them is still a human job.
What goes wrong when clubs skip this?
The failure patterns are predictable, which means they are preventable.
- Roles written around a person. The role dies when they leave, and the club rediscovers the job from scratch.
- No end date. Nobody ever leaves, so nobody new ever starts, and the whole leadership ages out together.
- One person deep on the things that matter most. One treasurer with no second signer, one Instagram login, one chat admin.
- A founder who never wrote their own role. Every job the other roles were supposed to absorb drifts back to them, and a year later the club has six titles and one person doing the work.
Questions club founders ask
Do small clubs need written roles and terms? Yes, just fewer of them. A club under 30 members can run on three written roles with one-year terms. The structure matters more than the headcount.
What if nobody wants the role when the term ends? Then the role was too big. Split it or trim the hours before you recruit again. An empty seat at term end is information about the job, not about your members.
Should the founder ever step out of the top role? Not necessarily. But the club should be able to survive it, and a term limit on paper is how you find out while the founder is still around to help.
Is one year the right length for every role? For most volunteer roles, yes, renewable once. The treasurer is the common exception worth thinking about, since continuity with the bank has real value, but even there a second signer should always be in place.
If you want the roster, roles, events, and club chat in one place the next volunteer can actually reach, set up your club on RunLink. The iOS app is live on the App Store, and club setup is free.
Related Posts
Running Club Nonprofit Status: Is 501(c)(3) Worth It?
Running club nonprofit status explained for founders: what 501(c)(3) actually changes, the RRCA group exemption route, and the filings that keep it alive.
How to Organize a Running Club Race Weekend
How to organize a running club race weekend: the shakeout run, the cheer spot, the home run that still happens, and where the plan lives so nobody asks twice.