How to Run Your First Club Group Ride: A Playbook from the Front

Nobody remembers your first group ride for the route. They remember whether the slowest rider felt left behind, whether someone got dropped at a junction with no idea where the bunch went, and whether you actually rolled out on time. Nail those three and they come back next week. Miss them and your "weekly" ride quietly becomes "that one time we tried it."

This is the playbook I wish someone had handed me before my first one: the group sizes that actually work, the pace bands that keep wheels together, the route math for mixed legs, and a ride-day timeline you can copy line for line.

Start with the right group size

The biggest mistake first-time organizers make is reading "more people" as "more success." It isn't. Group dynamics, road safety, and your ability to actually lead all fall apart past a surprisingly low number.

The sweet spot for a first ride is 8 to 12 riders. Big enough to feel like an event, small enough that one leader can hold it together, and it fits inside a single working paceline. Past roughly 15 you should split into sub-groups, each with its own leader and a designated sweep — the rider at the back who makes sure nobody slides off the group unseen.

Plan your headcount around two realities almost every club confirms within its first month:

• No-show rate of 20 to 35%. Free, RSVP-only social rides routinely lose a quarter to a third of confirmations, and that climbs sharply the moment the forecast turns. If 14 people say yes, expect 9 to 11 wheels on the line.
• Mid-ride attrition of 5 to 10%. A puncture, a cramp, a wrong turn, or someone who went too deep in the first hour. Plan for it instead of being caught out by it.

So if you want a 10-rider ride, invite toward 14 and let the day-of group self-select to about the right number. Don't chase the no-shows.

Set honest pace bands — and publish them

"Social pace" means nothing. One rider's social is another's threshold effort, and that gap is exactly where a bunch fractures. The fix: publish concrete speed bands up front and let people pick their own. Use rolling average speed on flat-to-rolling roads as the reference, and say it plainly.

Pace group	Avg speed (flat/rolling)	Typical FTP/kg	Best ride length	Regroup discipline
D — Social / No-drop	18–22 km/h (11–14 mph)	< 2.5 W/kg	25–40 km	Wait at every junction
C — Endurance	22–27 km/h (14–17 mph)	2.5–3.2 W/kg	40–70 km	Regroup at tops & turns
B — Tempo	27–32 km/h (17–20 mph)	3.2–4.0 W/kg	60–100 km	Regroup at planned points
A — Fast / Chaingang	32+ km/h (20+ mph)	4.0+ W/kg	80–140 km	Self-sufficient, minimal stops

For a first club ride, run a C-pace, no-drop ride. It's the widest funnel you've got: a strong rider can soft-pedal at 24 km/h without sulking, and a nervous newcomer can sit on without blowing up. Save the A and B splits for when you've got repeat faces and you know whose legs are whose.

One number to keep in your head: a rider sitting in the draft spends roughly 25 to 30% less energy than the same rider on the front. That's why "no-drop" is a promise about the front, not the back — the leader holds the pace so the group stays a group. A no-drop ride where the front keeps hammering isn't no-drop. It's a lie with a friendly name.

Choose a route for the group you'll actually have

Mixed-ability route planning comes down to one rule: design for the third-weakest rider, not the average and never the strongest. The average flatters you, and the strongest will be fine anywhere you point them.

For a first C-pace ride, these limits keep almost everyone comfortable:

• Distance: 40–55 km (25–35 mi). Long enough to feel like it counted, short enough that a slightly underdone rider gets home in one piece.
• Elevation: cap at roughly 10 m/km (about 53 ft/mi). A 50 km route with 500 m of climbing is a pleasant rolling day; the same distance with 1,200 m is a sufferfest that shatters a mixed group on the first real climb.
• Time budget: 2.5–3.5 hours rolling, ~4 hours door to door. At a true C-pace with regroups and one stop, a 50 km ride lands near 2h45 of moving time.
• A loop, not an out-and-back, with at least one bail-out point so a cooked rider or a sketchy mechanical has a shorter way home.

Leave these off a first ride: busy A-roads with no shoulder, more than one technical descent, gravel or surface changes you haven't pre-ridden, and any sustained climb steeper than ~8%. You want a route nobody complains about. The memorable ones come later, once you know the group.

Pre-ride the route

Ride it — or at the very least drive it — within two weeks of the event. GPX files lie about road closures, fresh gravel, and that "quiet lane" that's become a rat-run. Note your regroup points, the bail-out, and where the coffee stop is. A leader who knows the route radiates calm; one squinting at a phone at every junction radiates the exact opposite.

The ride-day timeline

Timing is where social rides live or die. A ride advertised for 9:00 that rolls at 9:25 trains everyone to turn up at 9:20 — and now you're leaving at 9:45. Set the convention and hold it: meet time, then wheels-down time, 15 minutes apart. Here's the timeline I run, anchored to a 9:00 meet / 9:15 roll.

Clock	Phase	What the leader does
8:50	Leader arrives	Be first. Visible, calm, bike ready.
9:00	Meet & check-in	Headcount, names, confirm everyone has tube, pump, ID, water.
9:08	Ride briefing (3 min)	Route, distance, pace, regroup plan, hand signals, who's sweep.
9:15	Roll out	Leave on time even if one person is "2 minutes away."
~10:30	Coffee / regroup stop	Headcount again. Quick mechanical check. 15–20 min max.
~12:00	Return	Final headcount. Thank people by name. Announce next ride.

The briefing is the highest-leverage three minutes of the day. Newcomers don't know your hand signals, your regroup rules, or that "car back" is something they're meant to echo up the line. Say it out loud every single time, even when you're sure everyone knows. The short version: pace and route, where we wait, point out holes and obstacles, call cars front and back, and the sweep — that's [name] — is the back marker; if you're behind the sweep, you've gone the wrong way.

Safety: the numbers that should shape your decisions

Group riding is statistically safe, but the risks aren't random — and they're almost entirely manageable. A few realities worth designing around:

• Junctions and intersections are where it happens. A large share of urban cycling collisions occur at junctions, which is exactly why the regroup-and-cross-together rule exists. Never let a group stretch across a changing light — wait, cross as one, regroup on the far side.
• Helmets cut the risk of serious head injury by roughly 60–70% if you do hit the deck. Make them mandatory and say so in the ride description; that kills any awkward conversation at the start line.
• Most group-ride crashes are rider-to-rider, not car-to-rider — overlapped wheels, a sudden brake, a pothole called too late. That's why the briefing covers signals, and why you cap a first ride at C-pace, no-drop: lower closing speeds, more predictable wheels around you.
• Two-abreast, tight, and predictable is safer than single-file and strung out. A compact group is shorter, easier for a driver to pass cleanly, and easier for you to see end to end.

What the leader carries, every ride: a charged phone, a paper or offline route, a basic first-aid item, two tubes and a pump that actually works, a multitool, and an ICE (in-case-of-emergency) contact for the group. Collect emergency contacts at sign-up, not at the roadside.

After the ride is where the club is built

The ride ends; the loop doesn't. Within a few hours, post the route, a photo, the distance and elevation, and the date of the next ride. Clubs that put up a recap and the next date inside 24 hours see materially higher repeat attendance than the ones that go quiet — momentum is just how short you keep the gap between "that was fun" and "here's the next one."

Three habits compound faster than anything else:

1. Same time, same place, same pace, every week. For the first two months, predictability beats variety. People build their weekend around a ride they can trust to exist.
2. Name people. "Thanks for coming, Sarah" is worth more than any newsletter. A first-timer greeted by name comes back far more often than one who was just a face in the bunch.
3. Protect the back. The fastest rider will be fine without you. The slowest rider is the one deciding whether your club is welcoming or cliquey. The sweep is the most important role on the ride — more than yours.

Run it small, roll out on time, publish honest pace bands, and protect the person at the back. Do that for eight weeks and you won't be organizing a ride anymore — you'll be running a club.