travel · local-first tool
Lay Out a Multi-Stop Itinerary with Local Times and Gaps
A connection can look generous until you notice the arrival and departure clocks use different time zones.
Record itinerary stop, local date/time, UTC offset supplied by the traveler, and transition duration; expose gaps without route advice.
What changes the result: your provider's confirmed local times, time-zone offsets, and transfer estimates.
Privacy: Calculations run in this browser tab. This tool has no input-upload, account, or AI endpoint. The site may send a page-view signal to Cloudflare; this tool does not add form entries to that signal. A draft is stored only if you choose “Save draft on this device”; that browser storage is not encrypted. Avoid identifiers or sensitive details, and delete saved drafts when finished.
Your entries
The starting rows below are fictional examples. Edit them, replace them with non-sensitive labels and values, or load the sample again. The result is not advice or a source verification.
Amount fields use the same units you enter; the app does not choose a currency. Dates are the ones you provide. Up to 100 rows per run.
Calculated output
What the calculation does
Validate and order user-entered dates; keep the status separate from the event description. An open or waiting entry whose date has passed is highlighted for review, not treated as an official deadline or proof that an event occurred.
Question to keep open: Should a planner preserve local clock times as printed or convert everything to one reference zone?
Boundary: This is a user-entered travel organizer, not live travel, entry, border, safety, or provider guidance. Verify current destination and carrier requirements from their official sources before acting.
Copy includes the headline, aggregate metrics, and boundary—not the row-by-row input. The CSV contains entries you choose to download. Review it before sharing.