July 25, 2026 · Limbo Crew
How to audit an AI trip itinerary for impossible days
Audit geography, opening hours, transfers, luggage and overlapping reservations. Practical steps and a worked example.
Photo: Santeri Viinamäki · CC BY-SA 4.0. Full-frame photograph; cover thumbnails may crop for layout.
An impossible itinerary often looks precise: neat times, full days and confident journey estimates. Audit the transitions and dependencies before admiring the formatting.
In this guide: Audit geography, opening hours, transfers, luggage and overlapping reservations.
1. Check the map logic
Group activities geographically and inspect cross-city or intercity movements. Include luggage, station access and hotel changes. Ask for the source behind any journey estimate that controls a timed booking.
2. Check time and access
Compare proposed visits with current operator hours, ticket rules and the actual trip dates. Treat a missing source as an unresolved check. A model’s confident answer is not proof of availability.
3. Request a minimal repair
Protect confirmed commitments and remove lower-priority items first. Ask the assistant to show before-and-after changes and why they are necessary. Avoid asking for ‘more realistic’ without specifying what failed.
Worked example: what this looks like
Fictional scenario—not a real customer story or executed AI result.
Simulated example: the first draft places a 2 pm museum entry after a transfer that cannot reasonably finish before 2:30. The repair moves the museum to the following morning and removes an optional stop, preserving the hotel and dinner. The result has fewer attractions but no longer relies on an impossible connection.
Photo: Syohei Arai · CC BY-SA 4.0. Full-frame photograph; cover thumbnails may crop for layout.
Give the assistant a test it can actually fail
Define what a useful answer must preserve before requesting it. Examples include the same traveller count, a fixed arrival date, no car hire, a stated budget scope or an unchanged confirmed booking. Then read the answer against those requirements instead of judging its confidence.
When something fails, describe the failure precisely: “This day crosses the city three times and overlaps our confirmed entry.” Ask for the smallest repair and a before-and-after explanation. A vague request to make the plan better invites another attractive rewrite that may discard details you wanted to keep.
If a tool can change the trip, separate the planning conversation from the approved action. Inspect the exact preview, identify the right trip and check the returned result. Do not let an example prompt, draft message or hypothetical itinerary become an instruction to book, pay or speak for someone else.
Copyable AI trip prompt
Replace the bracketed fields with your own details. Read the complete text before sending it; copying it here does not send a message or perform an action.
Audit this trip itinerary [paste] for geography, overlaps, luggage, opening hours, entry rules and realistic transitions. Mark each issue as verified conflict or unverified assumption. Preserve [confirmed commitments]. Propose the smallest repair, with before/after times and source links. Do not invent shorter journeys to make the timetable fit.
Run a focused refinement
Use a follow-up that names the actual problem, not just “make it better”.
Review your answer about [specific trip task]. The issue is [what failed]. Preserve [confirmed facts and constraints]. Change only [scope], show what changed and why, and list any remaining unknowns. Do not invent sources or approvals. Do not save, send, book or pay.
A connected workflow needs the current account access, permissions and client support described in the Limbo setup guide. If a required tool is unavailable, keep the output as a text draft and do not claim that the trip was saved.
Before you call it settled
- The answer preserves the original trip constraints.
- Important facts have a source or are marked unverified.
- The worked example is not mistaken for a real booking or test.
- Any proposed saved action has been previewed precisely.
- Completion is claimed only when a returned result supports it.
Precision should follow verification. A sensible unscheduled afternoon is better than an exact timetable built on guessed facts.
Put the decision somewhere useful
Keep the agreed plan and the information needed to act on it together in Limbo. Save the useful outcome of the conversation—not every abandoned option—and make clear what is still awaiting confirmation.
Sources and further reading
These references support the workflow and further checks; fictional examples are authored illustrations, not evidence of live prices, bookings or customer outcomes.