Introduction - These guidelines cover Brevets and Populaires. Team Events such as the Flèche
and Grand Randonnées such as the Colorado High Country 1200 are managed differently.
As a ride leader, you are taking care of a few things before, during, and after the ride:
· collecting waivers,
· answering rider questions at the ride start,
· compiling results.
Before the Ride
· Registrants - Registration is optional for most events.
You can see who is registered by going to the results page and clicking on the ride date
in the results grid.
· Waivers - Occasionally a rider may email you an image
of a signed waiver rather than bringing a paper copy to the ride start.
· Extra Waivers - Print off a few extra waivers
for riders who have forgotten to bring theirs.
· RUSA Membership - It's a good idea to verify that riders
have a current RUSA membership. You can check via the Member Search on the RUSA website. Note the dropdown allowing you to see expired
or pending members.
· Postponing a Ride -
If weather or road conditions look like they may be unsafe on the scheduled date,
or there's a reason the course may be impassable and not practical to reroute,
discuss with the RBA. We can postpone ACP-sanctioned brevets up to a week, and postpone or reschedule
RUSA-sanctioned ones as needed. Postponements like this will be posted on the Colorado Rando Google Group,
and we can also send emails to the registrants. Another good reason for riders to register.
At the Ride Start
· Waivers - Collect waivers from the riders.
If a rider has forgotten to bring a waiver, you can have the rider sign one of the extras you brought.
· Orientation and Questions -
Briefly cover the course and any issues, e.g., that a pre-ride may have uncovered, and answer questions, if any.
You might also mention upcoming events, particular awards, etc.
· Proof of Passage - Remind the riders about proof of passage options.
Most riders use GPS, and they will need to email you a link
to their track, not a file attachment (e.g., .fit or .gpx, unless you're ok working with those). Photos are also an option,
or in rare cases, brevet cards. More details on this in the rider orientation [to be updated].
After the Ride
· Waivers - Send the waivers to the RBA, either by USPS or
as emailed images.
· Results and Validation - Collect and compile the rider times from GPS tracks,
photos, etc. For GPS tracks posted on a website, you may have to dig a little to find the elapsed time.
Many websites such as Strava
and RideWithGPS highlight the riding time, but they will also publish the elapsed time, which is what counts.
If the rider had technical issues, there may be more than one GPS track (or a combo of GPS tracks and photos, etc.).
That's ok, as long as there is documentation for the starting time, finishing time, and time through each checkpoint.
· Contacting Riders - If you need to follow up with any riders
and do not have their email addresses, the RBA can provide them.
· Results Submission - RUSA wants results submitted within 7 days
of the end of the event. If there are issues getting everyone's results, let the RBA know. Email the results (including DNFs)
to the RBA. The most helpful format for compiling results is the one that RUSA requires:
Best is to use a CSV file or Excel or Google Docs spreadsheet. Otherwise, it may take some work to reformat.
You can look up riders' RUSA#s using the RUSA Membership Search
or on our brevet results page, if the rider
finished an earlier event this year.
You can also add another column for comments, as some rider leaders have done. Here is a
sample CSV file.