How to run guided bike tours

A guided tour is the best margin in the building when it runs full, and the worst when it runs at two riders or falls over on the morning of. The difference is rarely the route or the guiding; it's the plumbing. Who's coming, on what bike, having signed what, warned about what weather, and refunded how when the southerly arrives. Get those answers systemised and the tour itself becomes the easy part.

Set group sizes you can actually guide

Your capacity is a safety number before it's a revenue number. One guide can genuinely look after six to eight riders of mixed ability on shared paths; with a second guide sweeping you can stretch to twelve to fourteen. Past that, the group strings out through intersections and the back half has a worse ride than they paid for. Set a capacity per departure and a minimum too: decide in advance the number below which a departure doesn't run, and say so on the booking page. Velobook's tours take scheduled departures with a capacity per departure, and stop selling at the line.

Hold hire bikes against real stock

The classic tour operator failure: ten riders booked, six need hire bikes, and the rental side of the business hired two of them out yesterday. If you offer bikes with your tours, the tour booking has to hold actual rental stock, not a guess. Decide per tour how bikes work: bring your own only, hire bike offered as an add-on, or a bike included in the price. In Velobook those are the three modes, and when a hire bike is part of the tour it holds real rental inventory at booking time, so the tour desk and the rental counter can't promise the same machine to two people.

Get waivers signed before the ride, not on the kerb

A paper waiver on a clipboard at the meeting point is the worst version of a necessary thing: it delays the start, it gets signed unread, and it lives in a shoebox when you need it two years later. Move it to booking time. The rider accepts the waiver and your terms as part of paying, you keep a timestamped record against the booking, and the 9am start is spent fitting helmets instead of handing out pens. Velobook attaches per-tour waivers and your shop terms to the booking flow, so nobody rides unwaivered and nothing needs a shoebox.

Run waitlists on the departures that sell

Tours cancel more than most bookings, because travel plans move. That's not a problem if there's a waitlist behind every full departure: a cancellation becomes an automatic upgrade for the next person in line rather than an empty seat and a refund. The waitlist is also your scheduling signal; when Saturday morning has a queue three deep every week, that's the data telling you to add a second departure. Waitlists are built into Velobook's tour bookings.

Have a weather policy before you need one

1. 1Write the policy now, in plain words: what conditions cancel a tour, who decides, by when, and what the rider gets (full refund, credit, or a free transfer to another date).
2. 2Put it on the tour page and in the confirmation email, so the first time a rider reads it isn't the morning it's used.
3. 3Decide the night before where you can. A 6am cancellation text beats a 9am one at the meeting point in the rain.
4. 4Refund fast and visibly. Because online tour payments settle straight to your own payment provider, refunds run from your own dashboard, and a same-day refund turns a rained-out rider into a rebooking instead of a chargeback.

Make the meeting point unmissable

"Meet at the fountain" works until there are two fountains. Tourists don't know your city's landmarks, and a rider wandering the wrong end of a park at 8:55 is a departure held for everyone. Pick a meeting point that's specific, sheltered and easy to describe, and give it as a map pin, not a sentence. Velobook shows the tour's meeting point on a map in the booking flow and the confirmation, so the pin travels with the rider instead of living in a reply you sent last Tuesday. Name a rolling time as well as a start time: "we meet at 8:45 and roll at 9:00" gives latecomers a buffer without punishing the punctual.

Remind riders what to bring

Tour no-shows are usually logistics failures, not changed minds: wrong meeting point, no water, cotton hoodie in a heatwave. The reminders, a week out and 24 hours out by default in Velobook, are where you fix that. Edit the copy so the day-before message covers the meeting point with a pin, start time and rolling time, what's included, what to wear, and your weather policy again. Riders who feel briefed arrive early; riders who feel unsure ring you at dinner or don't come.

Pitfalls to avoid

• Capacity set by the bus, not the guide. Selling fourteen seats with one guide is a review problem and a safety problem before it's a revenue win.
• Hire bikes promised from memory. If tour bookings don't hold rental stock, peak season will find the collision for you.
• Waivers at the start line. Signed-unread paper protects nobody and burns your departure time.
• No minimum-riders rule. Running a two-person tour at a loss because nobody decided a floor is a self-inflicted wound.
• A weather policy invented per phone call. Ad-hoc refunds feel unfair in both directions; a published policy is faster and kinder.