Planning Guide
How to Organise a Cycling Event
Step-by-step guide to organising a cycling event. Covers planning, RSVPs, promotion, and follow-up — with free tools included.
Organising a cycling event involves far more than picking a route and showing up. Between managing pace groups so no one gets dropped, ensuring you have enough mechanical support for mechanicals on narrow lanes, tracking kit orders with 15+ sizes, and getting accurate headcounts for your insurance liability, there's significant coordination required. This guide covers everything from calculating safe group capacity based on your narrowest route section to post-ride follow-up systems that turn first-timers into regulars — with practical systems used by cycling club captains and ride leaders across the UK.
The logistics for a Tuesday evening chaingang are completely different from a 100km sportive or an off-road gravel adventure. Your event format determines insurance requirements, support vehicle needs, pace group structure, and most importantly, how many riders you can safely manage. Getting this wrong creates dangerous situations and frustrated riders.
Choose your ride type and define its specific hazards
Group rides on closed roads are lowest risk but need pace discipline. Sportives on open roads need marshals at junctions and support vehicles. Criteriums require race licence holders and emergency medical response. Gravel adventures need bailout routes and communication systems. Mountain bike events need trail marshals and spotters at technical sections. Each format has completely different insurance and equipment requirements — don't copy another club's structure without understanding your specific risks.
Set pace groups with realistic average speeds for your area
Don't use generic 'A/B/C' speeds — calibrate to your local terrain. Urban routes with traffic lights: reduce averages by 2-3 km/h. Rolling hills: expect 15% slower speeds in headwind. Flat coastal routes: can sustain higher averages. Typical UK club structure: A group 24-28 km/h average, B group 19-23 km/h, C group under 19 km/h. Always add a fourth 'social' pace group under 16 km/h for newcomers and older riders — this group nearly always gets missed and it's where retention happens.
Calculate mechanical support ratio based on your route hazards
City centre rides with smooth tarmac: 1 mechanic per 25 riders. Rural routes with rough surfaces or gravel sections: 1 mechanic per 15 riders. Mountain bike or off-road: 1 mechanic per 8-10 riders. For sportives over 100km: minimum 2 support vehicles with spare wheels, not just pumps. Brief your mechanical support team in advance on common failures on your specific route — they should know if the first 15km has potholes or if there's a rough descent that causes rim damage.
Determine maximum safe group size based on your narrowest route section
Your capacity isn't determined by your start location car park — it's determined by the narrowest point on your route and how many riders you can safely manage through it. Dual carriageway: 50-60 riders manageable. Single-lane country lanes: maximum 20 riders before pace management becomes dangerous. Busy town centre: split into groups under 12 to maintain visibility for drivers. Recce your route and identify your actual bottleneck — that determines your capacity, not some arbitrary number.
Frequently asked questions
How far in advance should I plan a cycling event?
For regular weekly club rides: 7-10 days is sufficient for route recce, RSVP confirmation, and pace group assignment. For one-off sportives or charity rides: 6-8 weeks minimum to arrange insurance, route permissions from councils (required for closed roads), promotion to external cycling groups, and volunteer recruitment. For criteriums requiring temporary road closures: 3-6 months, as you need permission from local police and traffic management companies. For a first event from a new club: budget 12+ weeks to establish insurance, recruit experienced ride leaders, and build initial membership.
How do I manage different pace groups without anyone getting dropped?
Set realistic pace ranges in your RSVP based on local terrain (don't copy national averages). Assign experienced back markers to each pace group — their sole job is staying with dropped riders and slowing the group if it goes too fast. Start groups 3-5 minutes apart, slowest first, so faster riders don't overlap and create pressure. Enforce regroup points every 12-18km where all pace groups wait for each other (this is non-negotiable). Brief riders before departure: 'If you get dropped, soft-pedal until the group regroups — we don't leave anyone behind.' This single statement prevents the anxiety that causes first-timers to quit clubs.
What's the actual mechanical support ratio needed for group rides?
For club rides under 50km on smooth tarmac: 1 mechanic per 25 riders carrying pump, spare tubes, and basic tools. For 50-100km rides with mixed surfaces: 1 mechanic per 15 riders plus a support vehicle with spare wheels and brake pads. For 100km+ sportives: minimum 2 support vehicles positioned 10-15 minutes ahead and behind the main group (they need radio/phone contact with your ride leader). For off-road or gravel: 1 mechanic per 8-10 riders because mechanical failure rates triple on rough surfaces. Always brief your mechanic on the specific route hazards ('The first 15km has potholes', 'There's a rough descent at km 28') so they know what failures to expect.
How do I get genuinely accurate headcounts for capacity planning?
Never rely on Facebook 'interested' reactions or WhatsApp polls — these generate 40-60% no-show rates and have no legal value for insurance. Use a proper RSVP system like Who's In that requires commitment. Set a realistic capacity limit (based on your route's narrowest section and number of ride leaders, not wishful thinking). Set a hard RSVP deadline 36 hours before the event with automatic enforcement — this gives you time to assign pace groups and brief leaders. Who's In's automatic 48-hour reminder reduces no-shows by 30-40% and increases genuine RSVPs because riders see the deadline approaching. Export your final RSVP list to confirm your numbers against your insurance policy limits.
What's the best way to handle kit orders for group rides and jerseys?
Add custom questions to your RSVP form asking for exact sizes: jersey (XS/S/M/L/XL/XXL), bib short inseam or generic size, and whether they want a jacket. Set a firm order deadline 2-3 weeks before manufacture (print and delivery take 4-6 weeks minimum). Export your RSVP data with size information and send directly to your supplier — don't do email back-and-forth asking people their sizes. Set a policy: 'Size changes after the deadline are your responsibility', so people commit to their size selection. For first-time riders, let them order a single item (maybe just a jersey) before committing to full kit — new club members often quit within 3 months, so forcing a £150 kit order on someone joining their first ride is a waste.
What happens if there's a mechanical failure mid-ride with no support vehicle nearby?
This is why assigning experienced back markers is critical. Your back marker stays with the mechanically-failed rider while the rest of the group soft-pedals ahead and stops at the next regroup point (maximum 3-5 minutes away on your route). The back marker assesses the failure: if it's a simple puncture and they can fix it, they do so and catch up. If it's a derailleur or brake issue, they call your support vehicle or the ride leader. The group waits at the regroup point — never leave a rider stranded. For sportives over 100km, having a support vehicle with spare wheels isn't optional; it's essential because you can't guarantee every rider carries spare tubes or has pumping skills. Brief your mechanic to 'shadow' the group 10-15 minutes ahead and be ready to return immediately.
How do I prevent faster pace groups from dropping slower ones at the same start point?
Don't start all pace groups at the same time from the same location — this is the single biggest cause of pace group failures. Start groups 3-5 minutes apart, slowest first. Your C group (social pace) departs first at their actual start time. Your B group departs 3 minutes later. Your A group departs 5 minutes after that. This staggered start prevents faster riders overtaking slower groups in the first few kilometres (which creates chaos) and gives each pace group clear road space. By the time the A group is catching up, they've already merged into the roads while the C group is comfortable and settled. This is standard in cycling events and prevents 95% of pace group conflicts.
How do I use RSVP data to improve future rides?
Export your RSVP list after the event and review: which riders got dropped, which ones exceeded their stated pace group ability, which ones mentioned mechanical issues or equipment problems. Message riders who struggled to understand why ('That climb at km 15 caught a few people out, or maybe you were riding at threshold the whole time?'). Review your pace group distribution next time — if all the nervous new riders ended up in one pace group and got dropped, redistribute experienced riders more evenly. Note which regroup points worked (riders caught up easily) and which ones created bottlenecks (groups got spread out). Ask riders in your post-ride message: 'How did the pace feel? Would you prefer a different group next week?' Gather 3-4 data points about pace groups and then adjust. The second time you run the same route, you'll have much better pace group cohesion.
What should I brief my ride leaders on before the event?
Beyond route directions, brief them specifically on: (1) Their exact pace target ('We're aiming for 21 km/h average for the B group, which means maybe 18-19 on climbs and 24+ on descents'), (2) Where to manage pace — which sections tend to speed up and need slowing, which climbs spread people out, (3) Regroup points with GPS coordinates so they don't miss them, (4) Hand signals and hazard communication (how they'll warn riders about potholes, traffic, tight corners), (5) What to do if someone punctures or gets dropped (do they wait, do they call you, do they soft-pedal back?), (6) Who the mechanical support is and how to contact them. Don't assume experienced club riders automatically know your route hazards or your philosophy on pace discipline. A 10-minute WhatsApp call with your ride leaders the day before the ride prevents 90% of on-the-day chaos.
Ready to collect RSVPs for your cycling events?
Who's In is free, takes 2 minutes to set up, and requires no app download for attendees.
