Compares reviewed fields
It checks passenger counts, airport sequences, timezone-aware flight order, hotel nights, baggage differences, duplicate entries, references, and cancellation wording.
Compare editable flight, hotel, passenger, airport, baggage and connection details locally before relying on the itinerary.
Method reviewed July 28, 2026
Review the editable fields, then run the consistency check.
It checks passenger counts, airport sequences, timezone-aware flight order, hotel nights, baggage differences, duplicate entries, references, and cancellation wording.
Only the airline, hotel, rail operator, booking provider, or official app can confirm that a reservation exists and remains valid.
Pasted text stays in the page session and is never saved to Trip Passport or included in the privacy-safe export.
The airport dataset and comparison rules are conservative and not exhaustive. Reopen every original provider document before travel.
A field comparison example, not a booking-authenticity check.
Kuala Lumpur to Seoul arrives at 23:10 on 12 October, but accommodation begins 13 October. The onward connection is on a separate ticket, and one passenger name omits a middle name shown on the passport.
The hotel-night sequence may leave arrival night uncovered; a separate ticket may leave no through-protection; and the passenger-name difference needs issuer confirmation. The checker identifies the comparison, but only the airline, accommodation provider, and issuing source can confirm acceptance or correction.
An overnight flight can make dates look inconsistent even when the booking is correct, and airport codes near one city may still require a long transfer. Reopen the original documents, compare local dates and airports, then contact the issuer before editing or cancelling anything.
Next, save the corrected itinerary and run the Trip Reality Checker.