Choose where to start
Start with the decision you still need to make. A traveller choosing between destinations needs a comparison. Someone with a hotel and train tickets needs a schedule that fits those bookings. Someone leaving tomorrow needs a short list of feasible activities and immediate checks. Giving all three the same itinerary prompt wastes time.
| Your situation | Ask ChatGPT to produce | Keep fixed |
|---|---|---|
| Destination or dates undecided | Two or three options compared on travel effort, usable days, interests and total cost categories | Departure point, available leave, budget ceiling and entry requirements to check |
| Transport and accommodation booked | A daily plan starting and ending near your base, with arrival and departure days treated separately | Actual booking times, neighbourhood, cancellation deadlines and group limits |
| Itinerary already drafted | A review of long transfers, crowded days, missing costs and date conflicts | Confirmed reservations and the activities you most want to keep |
| One part has changed | A replacement for the affected day plus its cost and transport consequences | Everything outside the changed part unless a dependency also breaks |
For an international trip, identify the passport nationality, destination, transit countries and travel purpose needed for an entry-rule check. Verify the resulting requirements with the responsible government and carrier before committing money. You can give ChatGPT those categories without sharing a passport number. If permission to enter or transit remains uncertain, solve that decision before comparing sightseeing plans.
Write a brief with usable limits
A useful brief tells ChatGPT what a day can contain. Replace “not too expensive” with a total ceiling and its exclusions. Replace “easy walking” with the amount your group is comfortable doing, whether stairs are acceptable, and when you need a seated break. These are your planning limits; another family's comfortable pace may be unsuitable for you.
Destination: [chosen place, or places to compare]
Departure point: [city, if transport is in scope]
Dates: [dates, including arrival and departure times]
Group: [adults; children's age bands where relevant]
Base: [neighbourhood or station; booked or undecided]
Budget: [total, currency, per person or whole group]
Included costs: [transport, accommodation, meals, tickets, other]
Already booked: [date and time; no booking reference needed]
Must keep: [activities or priorities]
Nice to have: [optional activities]
Pace: [walking limit, stairs, breaks, earliest start, latest return]
Food and access needs: [only information relevant to planning]
Excluded: [items this conversation should not plan]
Output: options, daily schedule, budget, checks and alternativesCount usable hours before naming attractions. A flight landing at lunchtime does not create a full sightseeing day. Airport exit, luggage, transfer, check-in and food all take time, and their duration needs a realistic allowance. Ask for a light arrival day and a departure day that works backwards from the carrier's current check-in guidance. Check luggage storage separately when you must leave accommodation before travelling.
If people disagree about pace or interests, collect each person's must-do item and exclusions first. A short shared list is more useful than asking ChatGPT to guess what “something for everyone” means. Mark which requirements are essential, which can move to another day and which are optional.
Download the fill-in trip brief if you want a reusable copy. A neighbourhood, age band and planning requirement are normally sufficient. Leave out full names, passport numbers, payment details, account credentials and reservation codes.
Compare destinations and accommodation before filling the days
When the destination is open, ask for a shortlist with explicit tradeoffs. Include the journey from home, arrival and departure times, transfer effort, accommodation, local transport and the activities that match your interests. Ask the model to identify missing information that could change the ranking. A cheap flight with a late arrival and an early return may leave less useful time than a more expensive connection.
Compare these options using my brief: [options].
Use a table with travel effort, usable time, accommodation area,
cost categories, fit for my priorities, and unresolved checks.
Explain which option fits each priority. Show assumptions.
Use current official sources for transport and entry claims.
Leave unsupported amounts blank; label any supplied estimate.For accommodation, compare actual candidates or neighbourhoods against the likely daily route. Include the room total, taxes and fees shown by the provider, cancellation deadline, breakfast if relevant, station access and likely return journey. Check room occupancy and sleeping arrangements for the whole party. “Family room” alone does not tell you whether it fits your group's needs.
Make the cost comparison across the trip. A lower room price can be offset by additional fares or taxis. Ask ChatGPT to calculate the difference using the prices and routes you provide, then inspect the arithmetic. Keep time as a separate column: saving money may be worthwhile even with a longer journey, but the group should choose that tradeoff deliberately.
For a short stay, compare a simple base with fewer hotel changes against a plan that moves accommodation. For several cities, put travel days into the schedule before activities. Include checkout, luggage, station or airport transfers, the main journey and the next check-in. Avoid treating the advertised train or flight duration as the entire move.
Draft the itinerary by area, then add time
Once you have chosen the destination and base, ask ChatGPT to arrange activities. Start with one main activity per day and optional additions that can be removed. Increase the density only when your group wants it and the travel, visit and rest allowances fit. A compact museum visit and a full theme-park day need different treatment.
Use my brief to draft the itinerary first.
Group activities by area and respect fixed reservations.
Show each day's start and end point, main activity, meal break,
travel legs, rest buffer, and optional activity.
Give arrival and departure days their actual usable hours.
Keep transport durations, prices and opening claims provisional
until checked. Show the assumptions you made.
Explain what to remove first if the day runs late.
Do not make bookings or claim that any reservation exists.Look at the area sequence before accepting exact times. If the same day crosses the city repeatedly, move an activity to a nearby day or remove it. If the plan keeps you near one area, check that the activities actually suit your interests; geographic efficiency alone is not a reason to visit something.
Next add confirmed entry times and transport information. For a timed ticket, work backwards from the required arrival time using a checked journey and a buffer you choose. Add walking from the stop to the entrance, any security or queue allowance stated by the venue, and a meal break. Ask ChatGPT to show the calculation instead of producing an unexplained minute-by-minute schedule.
Keep optional activities visibly optional. Each day should have a point at which you can finish without losing a paid reservation or creating a difficult return journey. If a plan only fits after removing lunch and rest, reduce the activities before tightening the day.
For London, the official TfL Journey Planner provides departure or arrival settings, route preferences, walking limits and access options. Use the actual endpoints and travel time. Ask ChatGPT to incorporate the result into your schedule; recheck disruptions near departure rather than treating a saved route as a promise.
Build a budget you can use to choose
Separate confirmed costs, planning estimates and missing costs. A confirmed cost comes from your actual booking or the exact provider quote you checked. An estimate helps compare options but needs its assumptions, currency and date. An unresolved item still belongs in the budget, even when the amount is blank.
| Budget row | Record | Common omission to catch |
|---|---|---|
| Long-distance travel | Party total, fare type, baggage, seats, transfers and currency | Getting to and from the station or airport |
| Accommodation | Total nights, occupancy, taxes, fees and refund terms | Different totals for refundable and non-refundable rooms |
| Local transport | Actual modes, zones, adult and child conditions, caps or passes | Taxis needed because the walking or last service does not fit |
| Activities | Party ages, general admission, paid galleries, timed slots and extras | A free venue with a separately paid activity |
| Food | Number of meals, supplied allowance or checked menu range | Travel-day meals and meals excluded from the room rate |
| Other costs | Relevant entry documents, insurance, parking, tolls, charging, data or equipment | Costs outside the sightseeing portion of the plan |
Ask for totals per person and for the party, but calculate from one consistent base to avoid counting a shared room twice. Keep different currencies in separate columns until you supply an exchange rate and its date. Include any known conversion or payment fees. A budget total that still excludes a major category should say so beside the number.
Here is arithmetic with chosen teaching inputs, not London price quotes: use a £45 daily lunch allowance for the whole party and £20 daily adult-transport allowance over four days, then a £95 activity allowance. The subtotal is 4 × £45 + 4 × £20 + £95 = £355. If the supplied ceiling for those categories is £320, the gap is £35. Accommodation, dinner, long-distance travel and other excluded costs must remain separate. These inputs demonstrate a calculation; replace them with your own allowances or dated quotes.
Calculate the budget from these inputs: [paste rows].
Show the formula and party size for each row.
Separate confirmed costs, estimates and missing amounts.
List everything excluded from the total.
If the plan exceeds my ceiling, compare alternatives:
keep the main activity, reduce optional paid activities,
change the accommodation area, or shorten the trip.
Show money saved and the time or experience given up.Set the amount you are willing to reserve for unplanned costs yourself. Ask ChatGPT to show the result with and without that reserve. Do not let a generated percentage quietly become part of your requirements. If the ceiling cannot fit the essential costs, change the destination, dates, duration or scope before selecting more attractions.
In the London example below, free general museum entry is a checked category, while optional exhibitions, adult fares and meals need separate rows. The example budget sheet includes those unresolved costs instead of presenting a partial total as the cost of the trip.
Verify the claims that can change the plan
Use a separate follow-up turn for verification after reviewing the draft. OpenAI's search guidance says ChatGPT can use web search and show sources, while workspace settings may limit access. Request current official information explicitly and inspect the citations. Writing “verify” in a prompt does not establish that a page was accessed or a date-specific calendar was checked.
Now review the draft against official sources for my dates.
For each decision-sensitive claim, give:
claim; official URL; checked date; status; planning consequence;
next check; person responsible; deadline or trigger.
Use: checked, needs date-specific confirmation, unknown, rejected.
Check opening and last entry, closures, ticket requirements,
party age rules, prices and the transport conditions we use.
If a page or calendar cannot be accessed, mark that gap unknown.
Explain any change to the draft. Keep my confirmed bookings fixed.
Do not infer availability from general opening hours.Open the relevant links yourself. A result from an old article, an unofficial directory or a search snippet may help locate the venue, but use the venue's current page for the claim that affects your booking. On a dynamic calendar, select the exact date and party. If two pages disagree, keep the conflict visible and use the provider's booking or contact channel to resolve it.
Use “checked” for the narrow statement the page supports. A daily-hours page can support its published timetable; it does not confirm that your chosen ticket slot is available. Keep a closure that caused a rejected option in the table so a later revision does not accidentally add it back.
When search is unavailable, ask ChatGPT to create the questions and blank table, then paste the relevant public text you checked. Include its URL and access date, remove private details, and ask the model to use only that material. If the information is missing, the output should keep the gap. For ambiguous entry, health, food-allergy or access requirements, use the responsible authority, provider or qualified professional.
A four-day London example with practical next steps
This example uses the original fictional brief: two adults and one nine-year-old, based near Victoria, with four full sightseeing days from 8 to 11 October 2026. Their interests are natural history, hands-on science, ships and one historic site. They prefer limited walking, vegetarian lunches and one main attraction each day. Flights, hotel selection and airport transfers are excluded from this example. The plan is an editorial illustration, not a current booking or a new ChatGPT test.
The Natural History Museum's visit page, rechecked on 4 October 2026, lists a South Kensington closure on Friday 9 October. It also describes free galleries and free entry tickets. That makes the closure a concrete reason to keep the museum on Thursday rather than swapping the two South Kensington days.
| Day and area | Working schedule | Finish or change rule |
|---|---|---|
| Thu 8 Oct: South Kensington | Travel from Victoria using a checked route; visit the Natural History Museum; take a seated lunch; continue selected galleries only if wanted; keep 60 minutes unallocated. | Omit outdoor additions or finish early when energy or queues use the buffer. Confirm Thursday entry requirements and gallery notices. |
| Fri 9 Oct: South Kensington | Use the Science Museum as the main activity; choose free galleries or a separately priced activity; include lunch and 60 minutes spare. | The Natural History Museum stays excluded on this date. Check whether the chosen hands-on activity needs its own ticket. |
| Sat 10 Oct: Tower Hill | Keep the Tower of London provisional until its date selector and ticket page are checked; allow at least three hours plus lunch, travel and a 60-minute buffer. | If opening, tickets or access are unsuitable, replace this visit with a separately checked option or make it a rest day. |
| Sun 11 Oct: Greenwich | Check the outward and return journey; visit the National Maritime Museum; include lunch and 60 minutes spare; add a short outdoor stop only if wanted. | Keep the visit indoors in rain. Check the actual activity charge and last entry; do not automatically add another paid venue. |
The Science Museum advertises free general admission and separately lists paid experiences. The Tower's visit guidance recommends at least three hours depending on queues and describes access limitations. Its date-dependent opening page still needs the selected travel date. The National Maritime Museum describes free entry, recommended advance booking and separately charged events. These pages were reviewed on 4 October 2026; no exact-date ticket availability was established.
For the child fare, the checked TfL visitor guidance says under-11s travel free on buses and trams. Up to four under-11s can travel free with a fare-paying adult on the Tube, DLR, London Overground, Elizabeth line and some National Rail services. Retain the service and adult conditions when choosing transport. This statement does not price the adults' fares or every possible journey.
| Unfinished decision | Concrete next action | Owner and timing |
|---|---|---|
| Museum entry and paid activities | Select the exact day and party on each official booking page; record free entry and optional paid activities separately. | The person managing tickets, before reserving |
| Tower suitability | Check Saturday opening, admission total and access information; decide whether the walking suits the group. | Ticket organiser and affected travellers, before paying |
| Transport | Check actual endpoints, walking preference, return options and applicable fares; recheck disruptions. | Person leading each journey, during planning and before departure |
| Lunches | Choose a meal area or venue, check its current menu and relevant food requirements, then enter a party allowance or quote. | Meal organiser, before the day; contact the venue for necessary confirmation |
| Bad weather or low energy | Keep the indoor visit when suitable; remove the optional stop; check whether changed tickets or transport incur a cost. | Group decision, when conditions change |
Assign real names or roles in your own copy. Add actual deadlines when a cancellation window or timed ticket makes them necessary. Download the itinerary sheet and budget sheet to keep the next checks beside the plan. The budget covers the example's sightseeing scope and marks broader trip costs as excluded until you choose to include them.
Change one constraint without losing the whole itinerary
After the first useful draft, continue the same conversation with a specific change. Paste the current approved plan if the conversation has become long or the model has lost track of it. Give fixed bookings their dates and times, list the parts that may move, and request a changed-versus-kept explanation.
Revise this approved plan: [paste plan].
Change: [new budget, sold-out ticket, weather, pace or location].
Keep fixed: [confirmed bookings and priorities].
Change only the affected day and dependent travel or cost rows.
Give two alternatives and explain the tradeoff.
Show removed activities, new checks, refund or cancellation
questions, and the revised budget. Do not claim a refund occurred.If the Tower ticket is unavailable, preserve the other three days first. Ask whether a rest day, a nearby checked alternative, or swapping a flexible day is workable. Recheck every moved attraction: the Natural History Museum closure means an apparently tidy swap can create a new conflict. Do not pay for a replacement until you know what happens to any existing reservation.
If the budget falls, identify the adjustable rows before reducing everything. A prepaid non-refundable cost has a different consequence from an optional activity you have not bought. Ask for savings against the actual booking terms and supplied amounts. Treat any refund as pending until the provider confirms it.
If the group becomes tired, ask for the shortest viable version of the day that keeps its main priority, meal and return journey. If your accommodation moves, recalculate every day's first and last travel leg. A single restaurant change usually needs a local repair; a different base or arrival time may affect the entire plan.
Adapt the plan to your travelling group
Use the relevant cases below to change the brief and the expected output. You do not need all of them. Open the case that changes an actual decision for your trip.
Children, older travellers or a slower pace
Specify comfortable walking, rest intervals, meal timing and any nap or early-return requirement. Ask for a shorter version of each day, toilets or rest facilities to check, and the optional activity to remove first. Use children's ages where tickets or transport depend on them. Keep a preferred child activity distinct from a parent's preferred stop so the model can explain a workable compromise.
For an older traveller, describe the actual requirement rather than assuming an age determines ability. A person who manages long flat walks may still need to avoid stairs. Ask for transfer count, seated breaks and the final walk to the entrance. Review the difficult segment with the person who will use it before making a group booking.
Solo travel
Give your own priorities, latest comfortable return time and preference for organised or independent activities. Ask for accommodation-area comparisons and a return option for evening events. Check late service times and local safety guidance on responsible sources. A suggested neighbourhood or cheerful description is insufficient evidence for a personal safety decision.
Decide which activities benefit from an advance reservation and which you want to leave flexible. Ask for the extra costs created by travelling alone, such as a room rate or private transfer that cannot be divided among a group. Save the plan and relevant official contact information in a form you can access without the conversation.
Friends with different interests
Collect each person's essential activity, exclusions and budget limit. Ask for activities to do together, optional parallel activities and a meeting point with a fallback if someone is late. Make any split-group transport or ticket cost explicit. Do not let a majority preference silently override a food or access requirement.
Use one agreed version of the plan and give a named person responsibility for each booking. If several people book independently, record which reservation belongs to which day and who must check the terms. Avoid sharing credentials or reservation codes in a group AI prompt.
A strict budget
Tell ChatGPT which costs are already paid and which can still change. Ask it to rank optional spending by your priorities, then compare the cheapest feasible version with the preferred version. Show the cost of moving accommodation, replacing an attraction, adding a taxi or changing the trip length.
Check pass calculations using the exact activities you intend to visit, party ages and ticket conditions. A pass only helps your plan when the included uses fit its validity period and any required reservations. Ask for the break-even calculation from supplied prices; verify eligibility and availability with the provider.
Mobility, sensory or access needs
Separate the accommodation, journey, entrance, internal route and facilities. Ask which segments remain unconfirmed, whether assistance must be arranged, and what happens if a lift or route is unavailable. An accessible station does not establish the suitability of the complete venue visit.
For London, TfL's accessible-journey guidance explains route preferences, walking limits, access options and disruption checks. Review the venue's own information and contact it about requirements that the published page does not resolve. For sensory needs, ask about quiet spaces, crowded periods and specific events to check; keep those checks visible rather than promising a quiet visit.
Vegetarian meals or food-allergy requirements
For a food preference, identify current menu options near the planned area and record the expected meal cost. For an allergy or another safety requirement, the model can prepare questions, but the venue needs to confirm the relevant ingredients and handling. Keep those categories separate when deciding whether a proposed meal is suitable.
Ask for a backup meal area, enough time to reach it, and the effect on the next reservation. If no option has been confirmed, keep the meal unresolved and decide how to handle it before the day. A menu containing an apparently suitable dish is not a guarantee about preparation or cross-contact.
Several cities or countries
Add a transfer row for every move: local departure time, checkout, luggage, route to the station or airport, main transport, onward transfer and check-in. Record time zones on dated tickets. Ask ChatGPT to calculate usable sightseeing time after those commitments and to identify connections that need carrier confirmation.
Keep entry and transit requirements, currencies and payment assumptions separate for each country. Compare fewer bases with a faster-moving itinerary. Ask what activity time and transfer cost the extra stop consumes, then decide whether that stop still serves the purpose of the trip.
A road trip or theme-park visit
For a road trip, provide the driver's preferred daily limit, passenger breaks, vehicle type and overnight stops. Ask for driving legs and separate tasks for road closures, parking, tolls, charging or fuel, and access to the destination. Check those conditions through the relevant road, vehicle and site operators. Leave charging compatibility and availability unresolved until they have been checked for the actual vehicle and route.
For a theme park, start with date-specific admission, reservation rules and your group's priorities. Check official ride restrictions, closures, access guidance and any paid queue product. Ask for a priority order, meal and rest breaks, and the ride to omit when queues are longer than expected. Avoid a timetable built from invented wait times.
Repair common problems in ChatGPT's answer
| What you see | Ask for this repair | Check before accepting it |
|---|---|---|
| A crowded list of famous places | Rank activities against your interests; keep one main activity and label optional additions. | Travel, visit, meals and rest fit your usable hours. |
| Exact times without sources | Separate planning blocks from checked opening, ticket and route times. | The provider supports the exact date and the route endpoints. |
| A neat total with missing costs | List included and excluded categories, party size and every formula. | Food, local transport, fees and paid extras appear even when unresolved. |
| A link that fails or does not support the claim | Mark the claim unknown and identify the official provider page to check. | A replacement source actually states the relevant fact. |
| The model says it checked a live calendar but gives no usable evidence | Request the selected date, party, ticket type and access limitation. | Open the provider calendar yourself; a generic link is insufficient. |
| A revision changes paid bookings you wanted to keep | Repeat the fixed commitments and request changes only to affected parts. | Dates, cancellation consequences and transport still align. |
| The output claims tickets are booked | Correct the statement and separate the proposed action from its completion. | A real provider confirmation exists before you treat it as booked. |
If the answer stays generic, give one concrete priority and one constraint it violated. If it keeps changing unrelated days, paste the approved table and ask for only the replacement rows. If it cannot verify a critical claim, complete that check through the provider before building further commitments on it.
About the retained example
What the August 2026 exercise checked
The August 2026 exercise retained two Codex CLI outputs for the fictional London brief, with scores of 11/14 and 14/14 against a small local checker. The ordinary output had already found the museum closure and avoided visiting on that date. Its lower score partly reflected missing records and action-list structure. The runs used different reasoning settings, and the second prompt supplied official URLs, so the score difference cannot be attributed to the prompt structure alone.
The original checker detected changes in all five deliberately altered samples. Four received a failing overall verdict; removing a daily rest buffer reduced the score to 13/14 but still received a passing verdict. The archive now reports that distinction. The original final output also omitted meal costs; the separate editorial budget sheet adds that missing planning row without relabelling an edited file as a retained model response.
The exercise used Codex with web search, not the ChatGPT website. It does not establish ChatGPT interface behaviour, general accuracy, live availability or travel suitability. The optional example archive preserves the original prompts, outputs and checker with a correction note. Use the current planning prompts and your own verified inputs for a new trip; their publication is a documented method, not a claim of a new ChatGPT test.
Complete the checks before paying
Read the merchant's booking screen yourself. Confirm the domain, date, local time, party ages, quantity, ticket or room type, selected extras, currency, total and cancellation conditions. A general visit page, draft itinerary or AI statement is not a completed reservation.
Work through the decisions in an order that respects fixed commitments. Resolve entry and critical access requirements first. Then confirm the main transport and accommodation decisions relevant to your trip, check timed activities against them, and finish the supporting journeys and meals. For an already booked trip, start with those commitments and verify the remaining parts around them.
- Every day has enough usable time and a feasible start and return.
- Every cost category is included, estimated with a stated basis, or explicitly excluded.
- Every critical unknown has a responsible person and a deadline or trigger.
- Every moved activity has been checked again for its new date.
- Every fallback says what changes, what stays fixed and whether a cost or cancellation is involved.
After purchasing, update your own schedule with the provider-confirmed time and terms. Keep private confirmation details outside shared AI prompts. Save a readable itinerary, necessary addresses or meeting points, official links and transport checks for use during the trip. Reopen only the affected part when a closure, delay, weather warning or personal requirement changes.
