TripPlanWiseStart Planning

Check the details before you go

Compare editable flight, hotel, passenger, airport, baggage and connection details locally before relying on the itinerary.

Method reviewed July 28, 2026

Review the details before comparing

Choose paste, manual entry, or both. Extracted details stay editable and the comparison runs only after you review them.

Your booking text is processed locally in your browser and is not uploaded by TripPlanWise.

Do not paste passport numbers, ticket numbers, full payment details, barcodes, or full identity documents. Booking reference values are never included in exports.

How do you want to add booking details?
1

Paste sanitized booking text

The extractor looks for known airport codes, flight numbers, dates, times, baggage words, and reference wording. It does not authenticate the booking.

2

Review traveler and trip assumptions

Names are used only for local comparison and are excluded from JSON export unless you explicitly opt in.

Traveller details
3

Review flights and connections

Enter local dates and local times exactly as shown. Timezone conversion is used only when the airport code is in the local reference dataset.

Outbound flight
Return flight
4

Review accommodation and other bookings

Add each stay separately so gaps, overlaps, night totals, references, and cancellation wording can be compared.

Ready to compare?

Run the check only after reviewing the editable fields against the original documents.

No comparison yet

Review the editable fields, then run the consistency check.

What this checker can and cannot do

Compares reviewed fields

It checks passenger counts, airport sequences, timezone-aware flight order, hotel nights, baggage differences, duplicate entries, references, and cancellation wording.

Cannot verify authenticity

Only the airline, hotel, rail operator, booking provider, or official app can confirm that a reservation exists and remains valid.

Keeps raw text local

Pasted text stays in the page session and is never saved to Trip Passport or included in the privacy-safe export.

Requires manual verification

The airport dataset and comparison rules are conservative and not exhaustive. Reopen every original provider document before travel.

The dates do not join up

A field comparison example, not a booking-authenticity check.

Entered details

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.

Why it is flagged

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.

Edge and failure case

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.