Caught at the desk, not on the road.
Double-booked vehicles, turnarounds the vehicle cannot physically make, and capacity breaches are flagged while you are still building the run — in seconds, at the desk, instead of an hour later by a driver with forty guests waiting.
What the system checks while you build.
A double-booked vehicle is the obvious one: the same coach promised to two runs that overlap. It happens because two people were building the day at once, or because one person rebuilt half of it after a flight moved. The system holds every commitment on every vehicle, so it sees the overlap the moment the second run is drafted.
The impossible turnaround is the expensive one. On paper the vehicle is free at 10:40 and the next run starts at 10:50, and on paper that is fine. In the world it is forty minutes back from the resort and the second group is standing outside a hotel. Meridian OS checks whether the vehicle can actually be where you have promised it, and flags the run that cannot happen.
The capacity breach is the quiet one: one more passenger than the vehicle seats, added days after the run was built and never re-checked by anybody. It surfaces as a breach against the seat count that vehicle allocation packed the run to, with ranked alternatives when you need to reassign.
A flag that shows its reasoning.
Every flag says what it found and why, and none of them stop you. The dispatcher keeps the final call — they are the one who knows the second group is a fifteen-minute walk from the pier and the turnaround is fine after all. What the system removes is the case where nobody knew at all.
This is deterministic operational logic, not a prediction model. The same plan produces the same flags every time, which is what makes it usable at 5am. It runs under every way of building a run on the airport transfer dispatch board — the guided builder, the direct form and the drag-and-drop board all pass through the same checks.
Checks run before a sheet is ever issued, so a versioned manifest never carries a plan that was already known to be broken. The conflict is found by the desk, in seconds, which is the only place it is cheap to find.
The checks that run under every screen
Double-booked vehicles
Every commitment on every vehicle is held on one record, so an overlap is visible as it is drafted.
Impossible turnarounds
The run that cannot physically happen is flagged before it is handed to a driver.
Capacity breaches
One passenger over the seat count is a flag, however many days after the run was built it was added.
Reasoning on every flag
No black boxes. Each flag shows what it found; the dispatcher keeps the final call.
See it on your own operation.
No open signup — a short manual review, then a demo populated for your region.