A minute-by-minute account of how Meridian manages a single London-to-New York executive transfer — from the moment a booking arrives to the executive's departure from JFK.
This document describes the standard operating sequence for a retained corporate account. Every transfer — regardless of volume — follows the same sequence. No exceptions, no shortcuts.
The sequence below is live documentation. If something changes operationally, this page is updated to reflect current practice.
The EA's booking arrives via email to the account manager. Within 90 minutes during UK business hours, the following actions are taken simultaneously:
The first GMT-stamped confirmation is sent to the EA at 08:00 GMT — the morning before departure, before they reach the office. The message contains:
Prior to this confirmation, the account manager briefs the chauffeur on executive preferences from the CRM profile: preferred cabin temperature, beverage selection, news source (Financial Times, WSJ, or silence), conversation preference (full silence / brief greeting only / open conversation). The briefing is logged and confirmed by the chauffeur before the message is sent.
Primary vehicle is staged at the pre-designated staging location — a private facility adjacent to JFK Terminal 7, not the public kerb. Staging means the vehicle is physically in position, engine off, ready.
Chauffeur confirms readiness via internal system. Account manager acknowledges. No message to the EA at this stage — this is internal readiness, not client-facing.
Staging occurs at a dedicated private facility — not public parking or airport kerb. This eliminates the risk of the vehicle being displaced by airport operations or traffic enforcement. The executive's vehicle is never waiting in traffic.
A second GMT-stamped confirmation is sent to the EA at 17:00 GMT on the day of travel. This confirmation is conditional — the message branches based on real-time flight status pulled from ACARS and airline API feeds.
Chauffeur departs staging facility for the primary kerb at JFK Terminal 7. Vehicle enters airport traffic management protocol. Simultaneously:
No EA notification at this stage — the T−3h message covers this window.
Chauffeur arrives at the confirmed kerb position — specific door number, specific lane, pre-confirmed with ground operations. Engine on, climate set to CRM preferences. Account manager confirms position to operational log.
Position is not "Terminal 7 arrivals" — it is a specific door and lane, confirmed with the ground operations liaison. This eliminates the executive walking the terminal looking for a vehicle. The executive steps off the plane and the car is in position.
The executive deplanes. The chauffeur is at the confirmed door. The name confirmation protocol is executed with absolute discretion:
The moment the vehicle departs the airport, a GMT-stamped confirmation is sent to the EA:
It is now 11:50 GMT. The EA is arriving at their office in London. The confirmation lands in their inbox before they have to ask for it.
Executive arrives at destination. Chauffeur confirms drop-off via internal system. A GMT-stamped drop-off confirmation is sent to the EA. Trip is marked closed in the operational log.
At month-end, this trip — along with every other trip that month — is compiled into the Monthly Operational Report, delivered to the EA and finance contact. Contains: trip dates, routes, ETAs vs. actuals, and any disruption events handled.
Any deviation from standard sequence — delay, diversion, wait time — is logged with a one-line explanation in the monthly report. Not as a liability. As operational transparency. EAs trust Meridian because nothing is hidden.
A diversion to EWR does not change the executive experience. It changes the logistics — and Meridian handles them without a call to the EA.
The ACARS feed registers a route change or the airline API flags EWR as the destination. Meridian's flight-tracking system flags the event immediately. No manual trigger required — the system alerts the account manager and operational log simultaneously.
An EWR-assigned vehicle is dispatched immediately from the Newark staging facility. The original JFK vehicle is held — not cancelled, held — until the diversion is confirmed as permanent. A second vehicle is staged at EWR Terminal A (British Airways operational terminal) within 20 minutes of the diversion alert.
The executive deplanes at EWR. Chauffeur is in position at the confirmed arrivals gate. Silent handoff executed per standard protocol: name confirmed discreetly, bags handled, vehicle staged immediately outside. No deviation from the JFK standard.
Drop-off confirmation sent to EA. Trip closed in operational log. The monthly report notes the diversion with a single line: "BA117 diverted to EWR. EWR vehicle dispatched. No service disruption."
The executive does not notice the difference. The vehicle they step into at EWR is the same make, model, and standard as the one staged at JFK. The chauffeur briefing — temperature, water, silence preference — carries over to the EWR vehicle. The confirmation cadence is uninterrupted. The EA receives the same number of messages at the same intervals. Meridian handles the logistics so the executive experience is seamless.
Every transfer follows this sequence. Every EA receives these confirmations. Every diversion has a protocol. Open a corporate account and your first trip runs on this clock.