Ride leading - any advice?

[srw]

I've been volunteered to lead the "slow" group (supposedly 10-12mph) in my work's sponsored three-day bike ride (70+ miles per day) - something less than 10 people, some of whom are likely to be pretty inexperienced. Saying "no" wasn't really an option - with seniority comes responsibility! Insurance is covered (there are some advantages that come with working for an insurance company) so I don't need to worry about that. The route will be provided - I've had some input already, and have asked for paper maps to back up the GPS system. Fortunately I've got a good memory for maps. We've got vehicle support available if necessary, and I know how to change an inner tube and how to fiddle with brakes. I'll learn quickly how to re-index gears!

Apart from the obvious psychological points to encourage people through the difficult times and stay together as a group and have fun I've thought of:
Re-group at the top of hills, before junctions and periodically at other times.
Know in advance where the hills are and where the route goes.
Insist on no overtaking me without agreeing where you're going to stop to wait.
Basic roadcraft - don't ride in the gutter, own the road especially in pinch-points, keep using the "lifesaver" over-the-shoulder glance.
Don't go too quickly, and stop regularly to admire the view!

Any other hints gratefully received.

 

[corshamjim]

I've hardly ever done any leading, but as a follower one bit of advice I've been most grateful for is to drink and eat plenty at regular intervals.

 

[TheDoctor]

Make sure you have enough tea stops

 

[mark barker]

Don't forget to time the stops from when the last person arrives. If you've been stood around for a while waiting for the group to get back together 9especially after a climb) its easy to forget that they've only just arrived as you're ready to head off again.

Its also worth having a couple of short cut options planned just incase things go wrong.

 

[style over speed]

Insist on no overtaking me without agreeing where you're going to stop to wait.

if you've all been given route sheets, let people go at their own pace... you ought to stay at the back to give support and technical assistance to the slowest (and the ones who had the most tea and cake stops)... groups will naturally wait at hills and junctions just to check the route sheet if nothing else...

theres nothing more depressing than seeing someone shoot up the hills while your struggling, go slowly, make sure everyone is happy. Carry sweets and treats and spare bits. And sudocream. And energy bars.

 

[Andy_R]

Just make sure everyone is enjoying themselves. Be at the front in areas where people might get lost, and make sure they're going the right way, be at the back when folks need encouragement up the hill, and if anyone has to get off and walk, get off and walk with them. Carry tools that will fix anyone's bike, not just your own, and demand beer at the end of the ride!

 

[alecstilleyedye]

make sure the points in the op are pointed out to all the riders. it's all very well to ride at the speed of the slowest on the flat, but on tough climbs/descents it really is every man/woman for themselves, so waiting at the top (or bottom) and regrouping is essential, as is the group waiting while on-road mechanical problems are sorted out.

if you can recruit a trusted lieutenant or two to lead while you ride at the back and vice versa, it will save endless riding up and down the group making sure the people at the front aren't riding too fast and that people aren't dropping off at the back. it's important that they know not only the destination, but also the route.

take everyone's cellphone numbers, and make sure they have yours. make sure you do periodic head-counts; waiting at a turn for everyone to go through is one way of doing this without stopping.

if you have inexperienced cyclists with you, don't assume their bikes are mechanically sound either. take a track pump for both schrader and presta and ensure everyone has decent pressure in their tyres to reduce the likelihood of punctures. if possible, get people to show you their bikes some days prior to the ride, in case they need attention such as recabling etc.

for the inexperienced, it is certainly worth showing them the correct saddle height; it's amazing how many adults believe that the right seat position is that the seat should be low enough for the rider to put both feet on the floor, which will leave them with sore knees and burning quads. the best position is so that there is a slight bend in the leg when the crank is at 6 o'clock, which can be obtained by getting the rider to put their heel on the pedal at 6 o'clock and raising the seat until the leg is straight. they should be able to put one foot down with the bike at a gentle angle, and be able to stand astride the bike over the top tube with a couple of inches clearance to the crotch.

good luck.

 

[david1701]

and take food because someoneone won't, we get Jelly babies from the leader on Sunday rides

 

[alecstilleyedye]

70 miles is a long way for the inexperienced, especially when backed up over three days. set realistic targets for arrival times. it's essential that everyone gets a really good meal each night, and you will need at least three café stops during the day, one of which should be lunch. make sure the lunch stop offers more that just tea and cakes. encourage people to eat a decent meal; anyone who is on a calorie-controlled diet should put it on hold for the duration of the tour.

expect much flagging towards the end of each day. the first time i did the club's weekend run to bishop's castle (100 miles each way) i was on my knees at the end of each day, and i'm hardly inexperienced (although i'm assuming you're keeping the route flatter than ours was; ascending long mynd at the end of day 1 ).

if you've got a broom wagon available, make sure you've got a comprehensive toolkit on-board, especially a chain tool. also plenty of chain oil and gt85, should you get a wet day.

 

[snorri]

in my work's sponsored three-day bike ride (70+ miles per day) - some of whom are likely to be pretty inexperienced.

70mpd for three days sounds quite hardcore to me.

 

[fossyant]

70 miles per day for an in-experienced cyclist is a long day. You are looking at 7-10 hours in the saddle.

Alec has said it all, I can't add much. Just have a laugh.

There are a few from Work that do CTC, and they split the groups, but all ride regular - some are quick some slow - maybe match folk.

 

[rusty bearing]

Most things have been covered but although I'm sure you know everyone you're riding with I would mention it's worth checking for any medical issue, diabetic, hypoglycaemia that sort of thing, and pehaps carry a small first aid kit just in case.

 

[alecstilleyedye]

diabetes is not necessarily a problem. a clubmate of mine is diabetic and is an excellent cyclist nonetheless…

 

[Andy_R]

diabetes is not necessarily a problem. a clubmate of mine is diabetic and is an excellent cyclist nonetheless…

it isn't a problem, but it is useful for leaders to know about it........especially if someone is about to bonk. Also, check for bee allegry at this time of year (anaphylactic (sic) shock) and if you have any riders with this, make sure you know how to use an epi pen. Also, make sure you know about nut allergies, as some are so extreme that even being around nut based products never mind ingesting them can be very serious (this has actually happened to me when teaching!)

 

[david1701]

As Andy mentions, its worth quietly asking if theres anything medical you should know about before hand. Are you being first aider too, or not worrying?