E-ticket code and ticket link
For every traveller on a leg you record their e-ticket code and a link to their ticket, alongside the flight reference of the leg.
Race logistics software for cycling teams
Flights, transfers and hotels for every race, in one place
Plan the travel for every race in the VelOps back office: flights, trains, vehicle transfers and pick-ups as separate legs, booking details for each traveller, hotel bookings per race and team cars in the fleet calendar. Each rider then finds their own trip in the rider app.
Travel per race
Every trip, leg by leg
VelOps is team management and race logistics software for professional cycling teams (men's, women's and development squads): a back office for races, selections, travel, staff and team cars, plus a rider app. For travel, every race in the back office has a Logistics tab where staff build the trip one leg at a time and add the people on each leg.
Five kinds of leg
A leg is one part of the journey: a flight, a vehicle transfer, a train, a pick-up or own transport. Legs are grouped per race, so the whole journey to and from a race sits together in one list.
Places, times and references
For every leg you record the departure and arrival place and time, plus the flight reference, the driver and the vehicle where they apply.
- Flight, vehicle, train, pick-up or own transport
- Departure and arrival place and time for each leg
- Flight reference, driver and vehicle on the leg
- Travellers listed per leg, with their booking details
Per traveller
The details for every traveller
Each leg lists the riders and staff travelling on it. For every person on the leg you record the booking details they need on the day: their e-ticket code, a link to their ticket and their baggage.
Baggage per person
Record the baggage for each person on the leg, so staff and riders both know what has been booked.
The ‘also on’ flag
When a traveller is also booked on another leg, an ‘also on’ flag shows that leg next to their name, so you can see at a glance who is on more than one leg.
One leg, two races
A leg can be linked to a second event, so one flight can serve two races, for example when the flight out of one race also takes riders to the next.
Visibility
Publish when it’s ready
Each leg has a visibility setting. Flights and trains appear in the rider app only once staff mark them visible, so flight and train details can be arranged and checked before riders see them.
What riders see for each race
- Each leg with its times and reference
- Flight reference, e-ticket code and baggage
- The hotel for the race, with name, dates and extra info
- Race documents, shown with the trip
- Who else is going: the other riders and the staff on the race
Hotels
Hotels, booked per race
VelOps keeps one hotel list for the team, and every race has a Hotels tab with its hotel bookings. Bookings belong to the race rather than to individual people, so staff see at a glance where the team is staying, when, and how it is paid.
-
Hotel list
The hotels the team works with, kept in one list.
-
Dates per booking
The dates of each stay, recorded on the booking for the race.
-
Booking type and stay type
Both recorded on each hotel booking for the race.
-
Payment method
How each hotel booking is paid, stored with the booking.
-
In the rider app
Riders see the hotel name, dates and extra info in their trip for that race.
Team cars and fleet
Team cars in the fleet calendar
In the fleet calendar you plan every vehicle, from team cars to the bus and the truck. For each day you see which race a vehicle is assigned to, who is driving, what is at the service course and which vehicles are free.
- Race assignments for every team car, bus and truck
- Driver initials on each assignment
- Service course and free periods at a glance
- Contract expiry shown when it falls within a month
- Vehicle maintenance recorded in the same back office
From selection to travel
Who travels comes from the selection
Logistics starts with the race selection. The riders and staff selected for a race, each with their own period, are the starting point for planning the travel. The same selection also feeds the calendars and the rider app.
- 1
Select
Pick the riders and staff for the race, each with a period and a status: selected or reserve.
- 2
Build the legs
Add flights, transfers, trains and pick-ups, then put each traveller on the right leg with their booking details.
- 3
Hotels and cars
Add the hotel bookings for the race and assign team cars in the fleet calendar.
- 4
Publish
Mark flights and trains visible, so riders see them in My trip in the rider app.
Questions
Race logistics: common questions
Can one flight serve two races?
Yes. A transport leg can be linked to a second event, so a single flight can serve two races, for example when riders fly straight from one race to the next.
When do riders see their flights in the rider app?
Flights and trains appear in the rider app only once staff mark them visible. From then on, the rider sees each leg of their trip with times, reference, flight reference, e-ticket code and baggage, together with the hotel for that race.
Are hotels booked per rider or per race?
Per race. Each hotel booking is linked to the race, with dates, booking type, stay type and payment method. Riders see the hotel name, dates and extra info in their trip for that race.
Book a demo
Plan your next race in VelOps
In a demo we walk through a race from selection to the rider’s trip: legs, travellers, hotels and team cars. Staff work in the back office with a VelOps Crew licence and riders use the app with a VelOps Rider licence, both billed per user per month, price on request.
Compare the VelOps Rider and Crew licencesOr email us directly: info@velops.app