How to Recruit Run Leaders for a Growing Club

You recruit run leaders by naming a small, specific, repeating job, asking one person directly to do that job, and giving them enough access to run it without checking in with you first. Posting an open call for volunteers in the group chat almost never works. A vague ask gets a vague answer, and a specific ask made to a specific person gets a yes.

That is the whole method. The reason it is worth a full article is that most club founders do the opposite by accident, and then conclude that nobody in their club wants to help. Usually two or three people already do want to help. They just have not been handed anything small enough to say yes to.

Why does club growth outrun club leadership?

The growth is real and it happened fast. In its 2025 Year in Sport data, released in December 2025, Strava reported that run club creations were up 3.5 times year over year and that global run club membership grew 59 percent. Club-organized events were up 1.5 times over the same period, and the platform passed 1 million total clubs across all sports.

If you run a club, you did not need a report to tell you that. You noticed it on a Saturday when the group you used to count by eye became a group you had to count twice.

Here is the part the growth numbers do not capture. Membership scales in weeks. A good post, a friend bringing a friend, one local mention, and suddenly forty new faces show up over two months. Leadership does not scale that way. Leadership is built on trust and repetition, and it takes months, because a run leader has to show up consistently enough that the group starts treating them as a fixed point.

So the two curves separate. More people, same single set of hands.

The failure mode this creates is not dramatic. Clubs rarely collapse. What happens instead is that the founder gets tired. The group runs stay on the calendar but the energy drains out of them, the newcomer who showed up alone does not get greeted, the route does not get scouted, and the founder starts feeling a small dread on Friday night about a thing they built because they loved it. That is the actual risk. Not failure, just the slow loss of the reason you started.

Run leaders are the fix, and they are better understood as a growth constraint than as a nice-to-have committee. You need them to exist before the next forty members arrive, not after.

Who is already leading your club without the title?

Before you recruit anyone, look at who is already doing the job. In almost every club, the best future run leader is already doing about 70 percent of the work, unpaid and unnamed.

You can spot them from things you already see every week:

• The person who always hangs back and runs the last mile with whoever is struggling.
• The one who answers questions in the group chat before you get to them.
• The one who brings a friend every month, which means they are comfortable representing the club to strangers.
• The one who posts the recap or the photos without being asked.
• The one whose attendance is boringly regular, which matters more than pace, experience, or enthusiasm.

Notice that none of those signals are athletic. A run leader does not need to be your fastest runner and often should not be. What the role actually requires is reliability and warmth toward strangers.

Watch where newcomers drift on their first night. People are good at sensing who is safe to ask a dumb question. Whoever they gravitate toward has already been selected by your club. You are just confirming it.

What does a run leader actually own?

The single biggest reason the ask fails is that the job is undefined. "Do you want to help lead the club" sounds, to the person hearing it, like an unbounded claim on their life. They picture themselves being on the hook for everything you are on the hook for, and they say they are flattered and busy.

Define the job so narrowly that it fits in one sentence. Good versions sound like this:

• Lead the intermediate pace group on Wednesday nights.
• Own the monthly beginner-friendly run, one night a month.
• Be the person who runs the Saturday route when the founder is traveling.

Then write down what is in the job and what is not. In the job: show up on time, know the route, keep the group together, welcome anyone new, and let someone know if you cannot make it. Explicitly not in the job: club finances, sponsorships, the website, social media, membership disputes, and anything involving conflict between members. Those stay with you until you deliberately hand them to someone else as a separate, equally specific role.

That written boundary matters more than it sounds. Volunteers rarely quit because the work was too hard. They quit because the work kept quietly growing after they said yes. Scope creep is the thing that burns people out, and the antidote is written expectations rather than implied ones.

How do you make the ask without scaring someone off?

Ask in person, or one to one. Never in the group chat.

A group ask produces diffusion of responsibility. Everyone reads it, everyone assumes someone else is better suited, nobody replies, and now you have public evidence that nobody wants to help, which is both demoralizing and untrue.

When you make the ask, do four things:

Name why you picked them specifically. "I have noticed you always end up running with whoever is having a rough day, and that is exactly what I need for the beginner night." People say yes to being seen far more often than they say yes to a need.

Name the time cost honestly. If it is ninety minutes on a Wednesday plus fifteen minutes of route checking, say ninety minutes plus fifteen. Underselling the commitment buys you a yes now and a resignation in six weeks.

Give it an end date. A three-month trial with a real exit is dramatically easier to say yes to than an open-ended commitment. Most people renew. The ones who do not were going to leave anyway, and now they leave cleanly instead of by ghosting you.

Say what happens if they cannot make it one week. If the honest answer is "the run gets canceled and everyone is disappointed," you have designed a role that no reasonable person should accept. Fix the design before you make the ask.

How do you keep run leaders from burning out?

Design the role around the two reasons people actually stop volunteering. Club-management research published in March 2026, drawing on Australian volunteering data including the HILDA Survey, University of Sydney research, and the 2025 NSW State of Volunteering Report, found that 40 percent of people name lack of time as their main barrier to volunteering, and 12 percent name burnout as the reason they step away. That is Australian data rather than a United States figure, so treat it as directional. It is also consistent with what most club founders watch happen in their own group.

Both of those are design problems, and both have practical fixes.

Rotate, and always have two. Put two leaders on each run night, alternating weeks. A missed week then becomes a normal thing rather than a canceled run. This one change removes most of the pressure that makes the role feel heavy.

Make recognition operational, not sentimental. A thank-you text is nice. Being named on the club page, listed on the event, and credited in the recap is better, because it makes the role visible to the rest of the club. Visible roles get respected, and respected roles are easier to fill next time.

Stop being the router. If every question a run leader has to answer requires texting you first, you have not delegated anything. You have added a middle step to your own workload and given someone else the illusion of responsibility.

What breaks when club leadership lives in one person's phone?

This is where most delegation quietly fails, and it is a tooling problem more than a people problem.

The roster is in your contacts. The route is in your camera roll or your head. The RSVPs are in a group chat thread you have to scroll to reconstruct. The answer to "is the run still on if it rains" lives only with you. When all of that sits in one person's phone, nobody else can lead a night even when they want to and you have already asked them to.

Strava Clubs is worth naming here, because it is genuinely where a lot of this growth showed up and where new runners find clubs in the first place. But a club feed is a discovery and activity surface. It does not give a second person the roster access, the event control, or the member context they need to actually run a night on your behalf.

The fix, whatever tools you use, has three parts. The member roster lives somewhere more than one person can open. Routes live somewhere other than one phone. And roles come with real access, not just a title.

That is the specific gap growing your club runs into, and it is what RunLink is built around: role-based access for founders, admins, and runners, a shared member roster, events with RSVP and a mapped route attached to them, and in-app chat, so a run leader can show up on a Wednesday and run the night without you in the loop.

If your club is growing faster than the number of people who can lead it, that is a good problem with a fixable cause. Start with one person, one night, one clearly defined job.

RunLink is free to download on the App Store. You can set up your club at runlink.app.