Trip organisation

How to turn boarding passes and booking confirmations into one itinerary

Flights live in PDFs. Hotels sit in confirmation screens. Train tickets hide in photos. The useful itinerary is the layer above them: one chronological view that keeps every detail tied to its source.

Start with the original files

Save the actual PDF or image when you can. A manually copied note is faster once, but it loses the source, makes typos hard to spot and becomes stale when a booking changes.

Use fake references in demos and screenshots. A real confirmation code should never become sample content for a blog, support article or social post.

Extract the fields that affect a day

The itinerary should display useful operational details while preserving the original document behind the card. That source link is what lets you settle a mismatch later.

  • Flights: local departure and arrival date, time, airports, flight number, terminal, gate and seat
  • Stays: property name, check-in and check-out dates, address and booking reference
  • Rail and ground transport: stations, service number, date, departure time and seat
  • Activities: venue, date, entry time, duration and meeting point

Place dated bookings automatically

A dated flight or train belongs on the matching calendar day. A hotel spans check-in through check-out. Once the date is reliable, placing the card chronologically removes a second round of manual filing.

Noma follows that rule. Dated document cards join the timeline automatically. Uploading the same original inside a trip is deduplicated rather than creating a second booking card.

Mark uncertainty instead of hiding it

Document extraction is not perfect. Cropped screenshots, low-contrast scans, unfamiliar date formats and multi-leg bookings can all weaken a result. The interface should expose uncertainty where a wrong value matters.

In Noma, extraction confidence below 0.72 is marked for review. Check the field against the original, edit it if needed, and keep the source close enough to verify again at the airport or hotel.

The safe automation rule is simple: reliable dates can organise the timeline; uncertain booking fields stay visible for review.

Keep a travel-day fallback

  • Download critical tickets for offline use before departure.
  • Keep the provider app or original PDF available when a barcode is required.
  • Do not make an itinerary app your only copy of a visa, identity document or boarding credential.
  • Check time zones and overnight arrivals before trusting a day boundary.
Inside Noma

See how tickets, stays and saved places become one editable timeline.

Organise a trip

Sources

  • Noma supportCurrent extraction states and guidance for documents that need review.
  • Noma termsWhy travellers should verify consequential details against original documents.
← All field notes