Manifests that reissue themselves.
A transfer manifest is only useful while it is still true. Meridian OS keeps every version, reissues the sheet the moment the plan changes, and puts the current one in front of the driver, the rep and the desk at the same time.
An out-of-date sheet in a driver’s hand.
The manifest is rarely the problem. The copy of it is. A run gets rebuilt at six in the morning — a flight slips, a vehicle is swapped, four more guests land in the pool — and the sheet printed the night before is now fiction. The driver does not find that out at the desk. They find it out at the hotel, guest list in one hand, phone in the other, while the dispatcher is on three other calls.
Meridian OS treats a manifest as a version of the live record rather than a document somebody exported and emailed. Change the run and the manifest reissues itself. The previous version is kept, so months later you can still answer what was sent, to whom, and when — which is the question that actually comes up when a guest complains or an agency disputes a no-show.
Because the sheet is generated from the same record the airport transfer dispatch board is built on, it inherits every check that ran while the run was being assembled. A manifest never carries a plan that conflict detection already rejected.
One run, three different sheets.
A single run does not produce one document. The driver needs their stops in order and nothing else; the airport rep needs the meet-and-greet list for the flight they are standing under; the desk needs the whole picture including the vehicle, the driver and the costs behind it. Meridian OS renders all three from the same record, so they cannot disagree with each other.
The driver’s copy travels in the offline driver app, not in a WhatsApp photo. When the desk reissues the manifest, the run sheet on the phone updates with it, and the confirmations the driver taps — picked up, no-show, completed — flow straight back to the same record. The stop order on that sheet comes from drop-off sequencing, not from the order the bookings happened to be entered in.
Nothing here depends on somebody remembering to resend. That is the whole point: the manifest is not a message, it is the current state of the run, and it is the same state everywhere it appears.
What versioning actually buys you
Versioned by default
Every issue of the manifest is kept. You can answer what was sent, to whom and when, long after the season ends.
Self-reissuing
When the plan changes the manifest reissues itself — nobody is ever working from a sheet that stopped being true an hour ago.
One record, three views
Driver run sheet, rep meet-and-greet list and the desk’s full manifest, all rendered from the same live run.
Issued from a checked plan
Conflicts, tight turnarounds and capacity breaches are flagged before a manifest is ever issued, not after.
See it on your own operation.
No open signup — a short manual review, then a demo populated for your region.