Draft an itinerary from dates, budget, and preferences
Author: AILesson9 min setupTested with:ChatGPTReviewed: 2026-08-28
Quick answer
Build a paced route with cost envelopes, dated verification tasks, access needs, buffers, and fallbacks. Provide: Dates, travelers, and route, Preferences, pace, and access needs, Budget and current-fact evidence. Expected result: A provisional day-by-day itinerary with budget reconciliation and booking gates.
1
Add your context
Your text stays in this browser. AILesson Prompts does not send it to a model or server.
2
Your prompt
Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt
Draft a provisional itinerary from the supplied travel requirements and dated evidence. Treat schedules, prices, availability, entry rules, weather, closures, and local restrictions as time-sensitive unless verified from current authoritative sources.
Origin, route, dates/timezones, travelers, arrival/departure, commitments, documents, and transport:
[trip]
Interests, must/avoid, pace, sleep/meals, walking/mobility, health, care, privacy, rest, and risk tolerance:
[preferences]
Budget, currency, paid/refundable items, dated sources, opening/transport facts, deadlines, and unknowns:
[budget]
Start with hard constraints and a budget ledger that keeps estimates separate from paid amounts. Check geographic sequence, realistic door-to-door time, timezones, opening windows, booking dependencies, accessibility, meals, rest, weather exposure, and contingency. Do not fill every hour or invent restaurants, prices, travel times, rules, or availability. For each day provide anchor, optional nearby activity, transfers, meal/rest windows, cost envelope, booking status, verification source/date, decision deadline, and low-energy/weather/closure fallback. Preserve at least one buffer and avoid irreversible bookings until entry, transport, cancellation, accessibility, and total cost are verified. Reconcile all categories to the total, show overage or reserve, and finish with booking order, 72-hour recheck, daily safety/contact plan, and unresolved questions.
Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.
From input to outcome
A worked example
See how concrete context turns this recipe into a usable result
Actual input
Dates, travelers, and route
Two adults travel Shanghai–Kyoto 14–18 Nov 2026. Land KIX 14 Nov 13:20 local; depart KIX 18 Nov 16:30. Hotel near Kyoto Station paid CNY 3,200, refundable until 7 Nov. Fixed tea workshop 16 Nov 14:00–15:30 near Gion, paid CNY 600. Passports valid; entry requirements not checked. Prefer rail, no car.
Preferences, pace, and access needs
Interests: gardens, crafts, one quiet neighborhood walk. Avoid nightlife and animal attractions. One traveler can walk 8 km/day but needs a seated break every 90 minutes and no steep continuous climb. Vegetarian with egg/dairy; peanut allergy requires direct confirmation. Start after 09:00, one main anchor/day, one free half-day. No medical claims.
Budget and current-fact evidence
Total CNY 12,000 for both including paid CNY 3,800; flights already excluded. Envelopes: local transport 1,500, food 2,400, attractions/workshop 1,200 including paid workshop, contingency 1,100, remaining accommodation. No current rail schedule, opening hours, prices, weather, entry, allergy-capable dining, or attraction availability verified. Use official sources and record check dates before booking.
Example output
Budget reconciles: accommodation 3,200 paid; attractions/workshop 1,200 including 600 paid; transport 1,500; food 2,400; contingency 1,100 = 9,400, leaving 2,600 unallocated reserve. Flights are explicitly excluded. No new price is treated as current.
Draft: 14 Nov is arrival only—verify current KIX-to-Kyoto rail route, accessibility, luggage and last practical connection from official operators; hotel check-in, simple verified allergy-safe meal, rest. 15 Nov one central garden anchor only after official opening/access confirmation, with nearby seated indoor craft venue as weather/energy fallback. 16 Nov free morning near hotel, long lunch/allergy confirmation, fixed Gion workshop, direct return and rest. 17 Nov protected free half-day plus a level neighborhood walk selected only after gradient/access review; optional craft museum nearby. 18 Nov checkout and airport transfer with a conservative buffer based on verified operator guidance; no attraction anchor.
Booking gates: verify entry requirements from official government sources; verify hotel/workshop cancellation and accessibility by 7 Nov; check attraction hours/reservations and rail schedules; contact dining venues directly about peanut cross-contact without assuming safety. Recheck all transport, weather, closures, tickets, and contacts 72 hours before. Keep the 2,600 reserve until current costs reconcile, and retain one main anchor/day plus seated breaks.
Why this works
1
Anchors, buffers, and optional nearby choices create a usable trip without false hour-by-hour precision.
2
Dated verification and booking gates keep unstable travel facts from becoming irreversible commitments.
Check the result
Do dates, timezones, transfers, opening windows, rest, accessibility, and geography fit?
Are current facts source-dated and separated from estimates and unknowns?
Does the budget reconcile with reserve, paid/refundable status, booking order, and fallbacks?
Use it with confidence
Frequently asked questions
Practical answers about when to use this recipe, what to provide, and where human review still matters
What should I prepare before using “Draft an itinerary from dates, budget, and preferences”?
For “Draft an itinerary from dates, budget, and preferences,” prepare Dates, travelers, and route, Preferences, pace, and access needs, and Budget and current-fact evidence. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.
When is the “Draft an itinerary from dates, budget, and preferences” result not ready to use?
The result is not ready if it does not yet deliver the stated outcome—A provisional day-by-day itinerary with budget reconciliation and booking gates—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.
Which AI tools have recorded tests for “Draft an itinerary from dates, budget, and preferences”?
The published test record for “Draft an itinerary from dates, budget, and preferences” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.
ChatGPT