Group passengers by direction
Start with clear passenger clusters and common arrival times. Do not combine distant groups into one route just because seats are available. Counts per pickup and likely journey time matter more than a total disconnected from geography.
Work backwards from arrival time
Set the required arrival time, then account for the gate, movement inside the site, road time and boarding. Shifts may allow vehicle reuse or create overlaps requiring more vehicles. Review the schedule before deciding.
Compare the vehicle mix
A large bus can serve a dense cluster while a van serves a smaller one. The goal is to match capacity, route, time and comfort. Financial comparison requires actual like-for-like offers and cannot be inferred solely from empty seats.
Review when conditions change
Keep an agreed operating list covering route, times, headcount and contact. Changes in accommodation, shifts or numbers should trigger a review. Record changes and additional-work terms before applying them.
An example of grouping demand before pricing
Suppose three accommodation clusters share one required arrival time. Send counts and locations per cluster, not only a total, together with feasible departure times. Distant clusters in different directions can make a sequential pickup route long for some passengers. Compare independent routes, alternative meeting points or different vehicle classes, then review time, seats and scope. A mixed fleet is not automatically cheaper: class pricing, hours, mileage and availability require actual offers before a financial conclusion.
Simple indicators for reviewing a route
Once the schedule is defined, discuss a proportionate review method: actual versus planned numbers, pickup changes and observations about timing and waiting. These are operating-data examples, not a claim that tracking or automated reporting is included. The goal is to base reviews on agreed information and understand why seats or timing need to change. Reports, technology and dedicated coordination should be requested and specified rather than assumed in every service.
- An agreed pickup list and a person responsible for updates.
- Outbound and return counts and differences between shifts.
- Required on-site arrival time and gate procedures.
- Accommodation, site or headcount changes triggering review.
- Reporting or coordination scope if the organization needs it.
