Glossary · Bookings
Flight verification
Updated
Flight verification is confirming the flight number on an airport booking against the airline's actual schedule, and doing it when the booking is taken, not the morning of. Airlines change gates, times and sometimes flight numbers between booking and the day, which means an unverified airport run is a chauffeur standing at arrivals on a guess.
Verification catches three things early. A flight number that does not exist (the customer typed the return flight). A flight that lands at a different terminal or airport than the booking says. And a scheduled time that has already moved. Each of those is a cheap fix at booking and an expensive one at the kerb.
On the day, the verified flight is what the wait-time clock runs from. A chauffeur who knew the flight was 40 minutes late arrives 40 minutes later and nobody is billed for waiting. The common mistake is treating verification as a one-time check and not watching the flight again on the day, so the dispatcher learns about the delay from the chauffeur.
How liverybook handles it
The flight number on a leg is verified through AeroDataBox and the trip carries a flight badge on the run board. The board receives flight.delay events over the WebSocket alongside status changes, so a dispatcher sees the change on the row rather than in a separate tab. Live delay watching through FlightAware is on the roadmap. Verified flights are the reference for the wait time charge on the leg. See bookings.
Related terms
This term lives in Bookings. liverybook is the operating system for ground transportation.