Live ride sheet
Route, rider list, notes and any mid-ride change, updated live on the guide's phone as the tour moves.
SIZ Group builds a bike tour staff app that gives guides a daily ride sheet, mechanics a set of safety checks for each bike and support drivers a live list of pickups and drop-offs. It keeps the whole crew working from the same facts before the first rider clips in.
A bicycle tour depends on people who are far apart. The guide sits at the front of the group, the mechanic trails at the back with a spare tube and the driver waits at the next water stop. A paper ride sheet cannot show any of them what has changed, so the crew relies on radio calls and whoever happens to be closest to a phone.
A staff app gives each role its own view of the same tour. The guide ride sheet shows the route and the rider list, the mechanic sees which bikes need attention and the driver sees pickup times. Because every view comes from one record, a change made at the rack reaches the guide before the group reaches the first hill.
Riders compare tours on the route, the bike quality and whether the guide speaks their language. Many want a clear promise about breakdowns, so they ask whether a mechanic rides with the group and what happens if a tyre fails far from town. Those questions reach the crew through the booking notes, and the answers must match what the crew actually does on the road.
For this project, the crew app should show each rider's booking notes beside their name, so the guide knows who asked about a breakdown plan. A bicycle tour crew checklist confirms that spare kit and the support vehicle are ready before the ride leaves. The promise made at booking and the routine on the road stay the same.
The operations manager will test the app on a busy departure day with two tours leaving at once. Agree on that test in writing, including who receives which task, how a late bike swap gets recorded and what happens when a pickup changes after the van has left. Run it against the real fleet list and the tour support vehicle schedule.
The second check is the handover from the morning crew to the afternoon crew. Open issues on a bike should carry over with a name and a time attached, so nobody rides a bike that was flagged the day before. The manager should be able to follow that trail from a desk without asking anyone in the yard.
Route, rider list, notes and any mid-ride change, updated live on the guide's phone as the tour moves.
A short check for each bike with photo proof for wheels, brakes and gears, locking any bike that fails.
Pickup and drop-off points for the driver, with rider notes and the order of stops for the day.
Each role sees its own tasks with done marks, so a tyre change goes to the mechanic and not the driver.
Open issues carried from one crew to the next, each with a name and a time attached.
At 6:15 a.m. the mechanic opens the app and runs the bike fleet inspection, which lists eight bikes due for a brake check, two of them flagged after yesterday's ride. Each bike gets a short check with a photo of the rear wheel bolts, and a failed item locks that bike out of the day's list. The guide sees two replacement bikes appear on the ride sheet before breakfast.
Mid-morning, the support driver marks the first pickup point as complete and sees the next stop, along with a rider's note about a knee injury. At the midday water stop the guide closes the segment, notes a headwind and the mechanic adds a tyre change to the record. By late afternoon the evening crew opens the same tour and carries on without a single phone call.
The most common mistake is giving every role the full screen. A driver who sees brake checks and wheel inventories will ignore the one line that matters to them. Each role should see only its own tasks, along with the rider notes that affect its work.
Another is relying on the app for things that happen out of signal range. Many routes cross ridgelines or forest sections with no coverage, so the crew needs an offline plan. Records should sync on return, and the crew must know which tasks still need a radio call until then.
Track the share of tours that leave with a completed bike check, the number of mid-ride breakdowns that had a note beforehand and the number of late pickups. Compare those figures with the same period before launch, using the crew's paper or spreadsheet records, so the change is clear.
Look at repeat complaints as well. A rise in complaints about bikes or delays usually points to a missed check rather than a faulty app. When the numbers stall, we would examine the task order and the handover first, then adjust the workflow before adding features.
Checks, notes and pickup updates save on the device and sync when the van reaches coverage. The driver can keep working through a dead zone, but a locked bike stays locked on every screen until someone clears it. We test the offline routes on the actual tour, not in an office.
Yes. The guide can mark a segment as closed or re-routed, and the change reaches the support driver and the mechanic straight away. The original route stays in the record, so the change can be reviewed later. Only the guide and the operations desk can make route changes.
The driver marks the pickup as requested, and the operations desk approves the change before the van moves. Once it is approved, the rider's notification updates automatically. Early pickups are logged so the timing can be reviewed afterwards.
The mechanic's tasks move to the next available person on the roster, and the bike list keeps any open checks visible. The app does not assume anyone is free. It flags the gap, and the operations manager decides who covers it.
Most crew members learn their own screen in one session before a practice ride. Each role sees a short task list, so the learning curve stays small. Training is planned during the build, so nobody is learning the app on a busy departure morning.
Book a free scoping call and we will walk through a real departure day with your crew, then confirm scope and price in writing.