It is 6:45 on a Saturday morning. Your club is meeting at the trailhead at seven. You are standing in the parking lot with a coffee in one hand and your phone in the other, and you need to know four things in the next ten minutes.

Who actually RSVPed for today. Who paid dues this month. Whose waiver is on file. Who is brand new so you can greet them by name when they walk up.

You open five tabs to find out. Strava clubs for the activity feed. The Google Sheet for the official roster. Eventbrite for the RSVP list. WhatsApp to scroll for last-minute confirmations. Mailchimp to double-check who got the run reminder. Three minutes before kickoff, your pace coach asks if the new guy has a waiver. You honestly do not know.

This is what running a running club actually looks like for most founders and admins. The roster is not in one place. It is in five places, and none of them agree.

What roster management actually means for a run club

A roster is not just a list of names. For a real running club, it is a living record that has to hold a lot of moving pieces at once.

Real roster data looks like:

Contact info that stays current (phone, email, emergency contact)
Active vs lapsed status
Membership tier (free trial, paid annual, family plan, ambassador, etc.)
Waiver and liability status, with date signed
Attendance history across group runs, races, and social events
Communication preferences (newsletter yes, race emails no)
Pay-through date for clubs with dues
New-member onboarding state (welcomed, paired with a pace buddy, added to the group chat)

That is the data set you are actually trying to keep current. And right now you are trying to do it across five tools that were not built for any of this.

The fragmented default stack and why it falls apart

Most clubs build their stack the same way. They pick up tools one at a time as the club grows, and they end up with something like this:

Strava Clubs for activity and segments
WhatsApp or Discord for chat
Google Sheets for the "real" roster
Eventbrite or Google Forms for RSVPs
Mailchimp for the newsletter
Venmo or Zelle for dues
Instagram for promotion
A folder in Drive for signed waivers

Each one is fine in isolation. As a system, it leaks data everywhere.

Six specific things break.

No source of truth. Sarah Lopez shows up in your Google Sheet as "Sarah L.", in Strava as "saraaalopez", in Eventbrite as "Sara Lopez" with a different email, and in WhatsApp as a phone number with no name attached. Is that one member or four? You cannot tell at a glance, and neither can anyone covering for you.

Sync gap. Someone signs up via your Eventbrite form. They are now in Eventbrite. They are not in your Strava club, not on the Sheet, not on the mailing list, and not in the WhatsApp group. You have to manually add them to four places before they are actually a member of your club. Eight out of ten times, you miss one.

Stale data. Phone numbers go bad. Emails bounce. People move. Nobody updates the master spreadsheet because nobody owns it. Six months in, half the contact info is wrong and nobody knows which half.

Visibility gap. Strava clubs catch GPS runs, which covers Saturday group runs but misses your weekly pub night, your annual gear swap, and your trail cleanup. Real attendance is bigger than logged miles, and your tools cannot see most of it.

Compliance gap. Waivers come in by email, signed PDF, sometimes a photo of a paper page. They live in someone's inbox or a Drive folder nobody opens. When a member rolls an ankle on a group run and you need their emergency contact, you have about four minutes to find it. The folder is not going to help.

Burnout. The unpaid labor of reconciling all of this lands on one person. Usually the founder. Typically four to eight hours a month of nothing but data hygiene. That admin work is exactly what kills the energy that started the club in the first place.

This is the trap that platforms like Strava, Heylo, and Meetup do not actually solve. Strava is a tracking app with a "clubs" tab bolted on the side. Heylo is a general-purpose groups tool. Meetup is an event listing site with a dated interface. None of them were designed around the data model a real running club needs to manage. So clubs end up duct-taping them together, and the duct tape is the founder.

What good roster management looks like

You do not need a perfect tool to recognize a healthy roster system. The shape is the same regardless of what powers it.

One database, one identity. Sarah Lopez is one record. She has one email, one phone, one waiver, one set of preferences, one attendance log. If she updates her phone number once, every part of the club that uses it sees the new number.

Self-service member profiles. Members update their own info. The admin does not type other people's phone numbers into a spreadsheet. New members fill in their own waiver, their own emergency contact, their own communication preferences. The admin role is review and approve, not data entry.

Attendance captured at the event. When a run happens, the system knows who was there. Not because the admin took manual roll call, but because the tool was built to associate check-ins with members.

Status changes live on the same record. Joined the club. Paid dues. Signed waiver. Switched from monthly to annual. Lapsed. Came back. All of it is on one member record, not scattered across four tools.

Communication built on the roster. The newsletter goes to active members. The Saturday reminder goes to people who RSVPed. The "we miss you" nudge goes to people who have not shown up in 60 days. You do not maintain a separate mailing list because the roster is the mailing list.

This sounds simple. It is not how most clubs run today, because the default tools were never designed to work together this way.

Roster health metrics most clubs do not track

Once your roster is one record per member, you can start tracking things that actually matter. Most clubs never see these numbers because the data is too scattered to compute.

90-day active rate. Of your total members, what percentage have attended at least one event in the last 90 days. Healthy clubs run 50 to 70 percent. Under 30 percent and your club is paper members and a small core.
New-member 30-day retention. Of members who joined in the last 90 days, what percentage came back for a second run within 30 days. If this is under 40 percent, your onboarding has a leak. The first run was fine, the second invitation never landed.
Waiver compliance. Percentage of active members with a current, signed waiver on file. Should be 100. Most clubs are honestly between 50 and 80.
Contact accuracy. Percentage of active members with a valid email and a valid phone. If you have not verified in 12 months, this is lower than you think.
Pay-through-date freshness. For clubs with dues, percentage of paid members who are current through this month vs in the grace window vs lapsed.

You cannot fix what you cannot see. The reason most clubs do not see these is not lack of interest. It is that you cannot compute them when the data lives in five tools.

What to look for in a roster tool

Concept criteria, not a brand recommendation. If you are evaluating whether a tool can actually run your club roster, look for these things.

Running-specific data model. Built for clubs, not adapted from a generic CRM. The platform should know what a group run is, what a pace group is, what attendance means.
Mobile-first for the admin. You are not at a desktop on Saturday morning at six. You are in the parking lot with your phone.
Self-service member profile. Members can edit their own info, their own waiver, their own preferences. Without a support ticket to you.
Attendance capture at events. Not just GPS runs. Social events, races, volunteer days, anything you run as a club.
Waiver storage tied to the member record. Signed, timestamped, retrievable in under 30 seconds.
Messaging built on the roster. Active vs lapsed, paid vs unpaid, new vs core, anyone in your last event. Send to a segment, not a static mailing list.
Exportable. If you ever want to leave, you should be able to take your data with you. Anything else is a hostage situation.

When to stop duct-taping and consolidate

You do not need to switch tools the day you start a club. The fragmented stack works fine for a 12-person crew that meets one morning a week.

You do need to consolidate when one of these is true.

You spend more than two hours a week on roster reconciliation.
You have lost track of who paid this month.
A member got hurt on a group run and finding their emergency contact took longer than five minutes.
You missed adding a new member to the group chat for so long they stopped showing up.
Your 90-day active rate dropped and you cannot see why because attendance data is scattered.

Any one of those is a signal. Two or three of them at once is your club telling you the admin work is eating the joy of running it.

The takeaway

Running club roster management does not have to be five tools and a spreadsheet held together by one volunteer's free time. The shape of a healthy roster system is clear: one record per member, self-service updates, attendance captured at the event, status and communication living on the same data, exportable in case you ever want to walk away.

The default stack does not deliver that. It was never designed to. It works for the first year of a small club and then it starts costing the founder hours every week.

If you have hit that point, it is worth looking at a tool built for this from the ground up.

RunLink is one app for running a running club. Roster, waivers, RSVPs, attendance, messaging, and event GPS routes, all on one member record. Built by people who got tired of duct-taping six tools together. Free club setup at runlink.app.

Running Club Roster Management: One Source of Truth Instead of Five