Planning a motorcycle group ride comes down to six things you settle before the day: a route with fuel and coffee stops, a time budget, one shared plan with the finish and the overnight stop, a gear and weather check, group rules in writing, and the route exported as a GPX the night before.

The list below is written for the person organising, but it works best when everyone in the group sees it. The road captain checklist covers what the leader does on the day itself.

Route: fuel, coffee and the smallest tank

Plan fuel stops around the bike with the shortest range, not the average one. A sports bike and a big tourer in the same group can differ a lot in range, and the group stops when the first rider needs to. Ask everyone what their reserve light distance is and plan the stops inside the shortest number with some margin.

Coffee stops do a second job: they are the regroup points everyone already knows. Name them in the plan (“the cafe at the top of the pass”, “the fuel station after the bridge”) so a rider who loses the group knows where to go. The regroup plan guide explains why a named place beats “we’ll wait for you”.

Time budget: work back from the finish

Start with the time people need to be home and work backwards. Groups ride slower than solo riders, and stops take longer than anyone expects. The numbers below are not measured. They are a sensible starting point for a day ride:

Part of the day Plan for
Meeting point to departure 20-30 minutes
Each fuel stop 15-20 minutes
Coffee stop 30 minutes
Lunch 60 minutes
Riding Distance divided by a slow group average, not your solo pace

The riding time is the one people get wrong. The NSW Government group riding page tells the leader to ride “at a speed suitable for the least experienced rider”, so budget for that pace. Treat the stop times as a first guess and adjust them after your first ride with a new group. A 30-minute buffer at the end of the day is a sensible start, so the last section is not ridden in a hurry or in the dark.

Send the plan as one message: meeting point, departure time, route link or file, each stop by name, the finish, and the leader’s and sweep’s phone numbers. Pin it. A plan spread over a voice note, a screenshot and three replies is a plan half the group never saw.

From the road. On a 2012 UKGSer thread about drop-off systems, a rider called Taff described a weekend trip where the group “got split at the very first set of lights”, and nobody left behind “knew where the hell we were staying.” The route was not the problem. The hotel name lived in one rider’s head. For anything overnight, the accommodation name and address go in the same message as the route.

Gear and weather check

Two days out, look at the forecast for the whole route, not just home. A mountain section can be a lot colder and wetter than the valley you start in. The night before:

  • Waterproofs packed, or a clear “we cancel if it rains” decision made and shared.
  • Tyres, chain and lights checked. Everyone does their own bike, and the leader asks.
  • Phone mount, charging cable and a charged phone. The phone is the map and the contact list for the day.
  • A basic tool kit and first-aid kit in the group, with everyone knowing who carries what. The breakdown guide covers the first minutes if a bike stops.

Group rules in writing

The MSF group riding guide (a pre-2023 brochure) recommends a riders’ meeting before every ride to “discuss things like the route, rest and fuel stops, and hand signals.” Write the rules into the plan as well, so the late arrival who missed the briefing still knows them:

  • Who leads and who sweeps. The sweep is never overtaken. IAM RoadSmart groups start new riders at the back, just in front of the back marker.
  • Formation. Harley-Davidson’s advice is staggered, at least two seconds behind the rider directly in front and one second behind the rider in the other half of the lane, with single file for freeway exits.
  • What to do when separated: stop at the next named stop and wait. Do not chase.
  • The hand signals the group uses. Signals first; the phone is a backup, never the replacement.
  • No overtaking inside the group except where the leader says so.

The night before: export the GPX

Export the route from your planner as a GPX track, not a route. A route file is a list of points that each app connects in its own way, so riders can end up on different roads. A track is the line itself. GPX track vs route goes through the difference. Open the file on your own phone before you send it, check that the line goes where you planned, then share the same file with the whole group.

In Ridekin, each rider can import the same track and follow it with turn hints and an off-route alert, and on a group ride the leader can load it as the route line every member sees on the group map. It does not calculate a new route if someone misses a turn: they ride back to the line or ride on to the next named stop. Recording and following the line keep working without a phone signal, which matters on the quiet roads groups like most.

The pre-ride checklist in one list

  1. Route chosen, with fuel stops inside the shortest range in the group.
  2. Coffee, lunch and finish named as regroup points.
  3. Time budget worked back from when people need to be home, plus a 30-minute buffer.
  4. Group size set; two groups with their own lead and sweep if more than about seven riders.
  5. One message sent and pinned: meeting point, time, route, stops, finish, accommodation, two phone numbers.
  6. Forecast checked for the whole route two days out, and the rain decision made.
  7. Rules written down: lead, sweep, formation, signals, what to do when separated.
  8. GPX track exported, opened and checked the night before, then shared with every rider.

Sources