AI travel itinerary: a practical guide

1. Ask for a file, not a chat answer

The most useful thing you can change is the output: instead of prose, ask the assistant for a RoadBook, an open JSON format for complete travel itineraries. The file contains days, timed steps, bookings, tickets, travellers and notes; it opens in RoadBook+ on your phone, offline, with no account. The RoadBook prompt does the asking for you.

2. Give the AI what it cannot guess

• Dates, destinations and the route order; arrival and departure constraints.
• Travellers: adults, children with ages, dietary needs, walking tolerance.
• Pace and budget (“two visits a day, one nice dinner, mid-range hotels”).
• What is already booked: paste the confirmations. The assistant maps them to bookings and tickets instead of inventing them.
• Must-dos and no-gos. Mention the season: cherry blossom weekends, Ramadan, national holidays.

3. Insist on structure

Each step with a time and a place; each booking with its status (confirmed, to book, optional); one practical tip and one rain alternative per day; prices flagged as estimates when they are. A structured itinerary is easy to check, easy to edit, and stays useful during the trip. The RoadBook format encodes exactly these conventions; see the format overview.

4. Validate, then iterate

Open the file: the player (or the online validator) tells you if something is malformed, with messages written to be pasted back to the AI. Then iterate in the same conversation: “swap days 3 and 4”, “add a cooking class in Kyoto”, “make day 6 lighter”, and ask for the complete updated file each time. With the RoadBook connector the assistant even previews the roadbook inside the chat.

5. Keep it yours

The result is a file, not an account on a planner. Save it, share it with your co-travellers (RoadBook+ does this end-to-end encrypted), open it in another compatible viewer, or feed it to another AI next year. That portability is the point of an open digital roadbook.