The route puts itself in order.
Hand a run a set of hotels and Meridian OS works out a sensible stop order — closest-first on arrival, furthest-first on departure — so the driver gets a clean run sheet instead of a guess, and the day on the road matches the day at the desk.
Closest first in, furthest first out.
Arrivals and departures are not the same problem reversed. Coming from the airport, you want the closest hotel first: the coach empties steadily and the guests with the longest ride are not sitting through six stops that were never theirs. Going back, you want the furthest hotel first, because every guest picked up after that is already pointed at the airport.
Meridian OS applies the right direction automatically from the leg you are building, and computes the order as you build the run rather than after you have committed it. There is also a guard for the stop that does not belong: add a hotel that sits in the opposite direction to the rest of the run and it is blocked, because that is the stop that quietly adds forty minutes and a complaint.
The sequence is part of the run, so it travels with everything else that comes off it — the versioned transfer manifest and the run sheet in the driver app both carry the same order, in the same direction, at the same version.
Estimates from the planned route. Not live traffic.
Each stop gets an estimated time derived from the planned route, and that estimate is sent to the driver’s app so the guest waiting in a lobby at seven can be told something honest. It is a sensible plan, not live road-traffic tracking. Meridian OS does not watch the roads, does not re-route around a jam, and will not tell you the coach is nine minutes out.
We would rather say that plainly than let an operator sell a promise the system does not make. What the sequencing gives you is a stop order that is defensible before the vehicle leaves, and an estimate consistent with it. What happens on the road on the day is still the driver’s call and the dispatcher’s phone.
Sequencing runs on the same record as the rest of airport transfer dispatch, so the order recomputes when the run changes — a hotel added, a vehicle swapped by vehicle allocation, a guest moved to the later coach.
How the stop order is decided
Directional by default
Closest-first on arrival legs, furthest-first on departure legs, chosen from the leg you are building.
Opposite-direction guard
The hotel heading the wrong way is blocked before it lands on a driver’s run sheet.
Estimated stop times
An estimate per stop from the planned route, sent through to the driver’s app.
Not traffic tracking
No live road data, no re-routing, no ETA promises the system cannot keep. A plan, stated as a plan.
See it on your own operation.
No open signup — a short manual review, then a demo populated for your region.