Club Communication: One Channel, Not Five

Saturday, 18:40. Rain is forecast from first light, so the ride leader cancels tomorrow's club ride in the group chat. Sensible call. But the Thursday newsletter still lists it, the Facebook event still says "going", the club calendar was never touched, and two riders who muted the chat months ago don't see a thing. Sunday, 08:00: three people are standing at the café in the drizzle, wondering if they got the time wrong.

Nobody did anything wrong, exactly. The club just had five places that each held part of the truth. That's the most common communication failure in club cycling, and it costs you more than a wet morning. Riders who turn up to nothing twice tend not to come a third time.

The fix isn't a better app or more posts. It's a rule: one channel holds the ride details. Everything else points to it. Here's how to pick that channel, what goes where, and how to move a club over without losing anyone.

Why five channels fail

Every channel you add is another place to update every time something changes. A start time moves, a route swaps because of roadworks, a ride is cancelled: each of those needs posting everywhere the old version lives. Miss one and you've published two versions of the truth, and riders will find the wrong one.

The arithmetic is simple and brutal. Take a club that makes four ride changes in a typical week (times, routes, leaders, cancellations):

Updates to post per week for a club making 4 ride changes a week (simple multiplication, for illustration)

Channels holding ride details	Updates per week
1 channel	4
2 channels	8
3 channels	12
5 channels	20

Twenty updates a week, done by volunteers, in the evening, after work. Some will get missed, and you won't know which until three riders are standing in the rain. The cost isn't just the admin. It's that every extra channel adds a way for the information to be wrong.

The test for your club: if the ride changed right now, how many places would someone have to edit? If the answer is more than one, you've found your problem.

Pick one source of truth

Your source of truth is the single place where the real, current details of every ride live: date, start time, meeting point, route, distance, pace group, leader, and whether it's on. It doesn't have to be fancy. It has to pass five tests:

• Everyone can reach it. Including the member who isn't on social media and the one who never installs new apps.
• It shows the current state, not a history. A rider opening it at 07:30 on Sunday sees what's true now, without scrolling through 200 messages.
• Several people can update it. Every ride leader, not just the one person with the password.
• It can carry a cancellation fast. And riders can be notified when it changes.
• It respects members' privacy. Joining it shouldn't mean publishing your phone number to sixty strangers.

The usual options, judged against those tests

Channel	Good at	Weak at	Best role
Group chat	Speed, banter, last-minute coordination	Current state gets buried; in a typical group every member can see every other member's phone number; easy to mute	Chat, or a locked announcement channel
Email list or newsletter	Reaches nearly everyone; good for weekly round-ups and AGM notices	Out of date the moment anything changes	Weekly summary that links to the source
Social page or group	Visible to newcomers; photos; recruitment	Feeds bury posts; not every member uses it; algorithm decides who sees what	Shop window, pointing to the source
Club website calendar	One stable page per ride; easy to link	Often only one person can edit it; no notifications	Source of truth if leaders can edit it
Club app or booking tool	Ride pages, sign-ups, notifications on change, leader access	Members need to set it up once	Source of truth

Whatever you choose, choose one, write it down in the club rules, and say it at every briefing until people are sick of hearing it.

Everything else becomes a signpost

You don't have to shut the other channels. You change their job. Instead of carrying ride details, they point to the place that does.

• The newsletter says "This week's rides" with three one-line summaries, each linking to the ride page. No start times copied in.
• The social page posts a photo from Sunday and "Next club rides are on our calendar", with the link.
• The group chat has a pinned message: "Ride details, changes and cancellations live in [your source]. If it isn't there, it isn't official."

That last sentence is the important one. "If it isn't there, it isn't official" settles every argument about which version is right before it starts. It also protects ride leaders: a leader who updated the source has done their job, even if the chat was busy.

Separate announcements from chat

The other reason messages get missed is noise. A group chat where a ride cancellation sits between 40 messages about someone's new wheels and a debate about tyre pressure is a group chat people mute, and a muted chat is a chat that doesn't tell anyone anything.

Split the two:

• Announcements: a channel only the committee and ride leaders can post in. Most group chat apps have a setting that limits posting to admins. Low volume, high signal, so nobody needs to mute it.
• Chat: everything else. Kit questions, ride photos, café arguments. Mute it as much as you like.

A sensible volume for the announcement channel is a handful of posts a week: new rides published, changes, cancellations, and the occasional club notice. If it's busier than that, something that belongs in chat is leaking in.

One privacy point: ask before adding anyone's phone number to a group, and remove people who leave the club. Data protection rules in the UK and EU apply to club member lists too, and it's also basic courtesy.

What goes where

Write this table into your club rules and share it with every ride leader. It removes the daily question of "where should I post this?".

A club communication map: one example you can adapt

Message	Where it lives	Where it's signposted	When
New ride published	Source of truth	Announcement channel, newsletter	Ideally a week ahead
Change of time, route or leader	Source of truth	Announcement channel	As soon as it's decided
Cancellation	Source of truth	Announcement channel, a direct message to riders signed up if possible	By the deadline in your weather policy
Weekly round-up	Newsletter	Links to each ride	Same day every week
AGM, fees, club rules	Email to every member	Announcement channel	With the notice period your constitution requires
Photos, banter, kit questions	Chat	Nowhere	Whenever
Recruitment, open rides for newcomers	Source of truth	Social page	Before each beginner ride

Notice that the fee and renewal reminders go by email to every member, not just to the chat. Those messages have to reach people who've muted everything else. The membership fees guide covers the reminder cadence.

Cancellations and late changes

This is where single-channel discipline earns its keep. A cancellation is the one message that absolutely has to reach everyone, and it usually happens in a hurry.

1. Decide by a set time. For example, weather calls made by 19:00 the evening before. Your weather-call policy should name the time, and riders learn to check after it.
2. Update the source first. Mark the ride cancelled on the ride page before anything else. Then signpost it.
3. Use the same wording every time. Riders scanning a phone at 06:45 should recognise a cancellation instantly.
4. Tell signed-up riders directly if your tool allows it. A notification beats hoping they read the channel.
5. Cover the meeting point if you can. For a late call, it's kind for someone who lives nearby to swing by at start time for the rider who missed the message. Not compulsory, but it's the kind of thing riders remember.

Ride leaders need to know this routine as well as they know the route. Add it to your ride leader checklist.

Templates you can copy

Consistent messages are faster to write and faster to read. Three templates cover most of what a club sends.

Ride listing:

Sunday 9 March, 08:30, from the market square café. 75 km, rolling, one long climb at km 40. B group, around 27–30 km/h on the flat, regroup at the top of every climb. Leader: Sam. Sweep: Alex. Bring lights, spare tube, food for 3 hours. Café stop at km 50.

Every field a rider needs to decide whether to come, and which pace group fits.

Cancellation:

CANCELLED: Sunday 9 March, 08:30 B ride. Reason: ice on the climbs forecast below 2°C until mid-morning. Next ride: Wednesday 12 March, details on the calendar.

Starts with the word that matters, names the ride exactly, gives the reason in one line, and points to the next one so the message ends on something to look forward to.

Weekly round-up:

This week: Wednesday evening chaingang (A), Saturday beginner ride, 40 km no-drop, and Sunday's B ride to the reservoir. Full details and sign-up on the calendar. Club news: AGM on 20 March, notice and agenda by email.

No times, no routes copied in. The round-up's job is to make people open the calendar, not to replace it.

Moving the club over in four weeks

Clubs don't switch habits overnight, and a sudden switch strands exactly the members who check least often. Run it as a short, announced transition.

• Week 1: announce. Email every member, post in every channel: "From the first of next month, ride details live in one place: [link]. Here's why." Give the three-riders-in-the-rain story; everyone recognises it.
• Weeks 2–3: run in parallel. Post ride details in the new source and keep the old channels going, but every old post ends with "Details now live here: [link]".
• Week 4: switch. Old channels stop carrying details and become signposts. Pin the "if it isn't there, it isn't official" message everywhere.
• Afterwards: catch the stragglers. The ride leader's briefing is your best tool. A quick "everyone know where the ride details live now?" at the start of each ride for a month reaches the people who never read email.

Expect a few weeks of grumbling, then silence, which is what success sounds like. The same routine works when you bring in new ride leaders: point them to the source on day one, as part of recruiting and keeping volunteer ride leaders.

The club communication rule is the same promise as the first group ride playbook: make it easy for riders to turn up at the right place, at the right time, to the right ride. One channel is how you keep that promise every week.

FAQ

What is the best way for a cycling club to communicate with members?

Use one source of truth for ride details, a low-volume announcement channel for changes, and a separate chat for everything social. Email every member for anything formal, such as fees, rules and the AGM.

Should a cycling club use a WhatsApp group?

A group chat is good for banter and quick coordination, but poor as the only home for ride details: messages get buried, people mute it, and in a typical group every member can see every other member's phone number. Use it for chat and point it to your source of truth.

How do we make sure everyone sees a cancellation?

Decide by a fixed time, update the ride page first, use the same cancellation wording every time, notify signed-up riders directly if you can, and announce it in your announcement channel. If it's a late call, have someone check the meeting point at start time.

How many communication channels should a club have?

As many as you like for signposting and social life, but only one that holds the ride details. If a change means editing more than one place, you have too many sources of truth.