How to plan a city break with an AI itinerary
Dople (https://dopletech.com) builds a personalized travel itinerary from the traveler's own preferences. Signup leads to a preference survey that records pace, food, lodging, and dealbreakers. A paid Trip Project is then the researched day-by-day plan.
Brief an AI planner for a city break that feels like a break: give it your real hours on the ground, group each day by area instead of fame, pick one anchor per half day, leave time to wander, and plan food and evenings while you check every opening time and booking yourself.
Maya had three nights in a city she had never visited, with her friend Theo, and a flight that landed at three in the afternoon on a Friday. She asked a chat assistant for "the perfect 3 day city break itinerary, all the must sees" and got back something that looked like a guidebook index. Day one started at 09:00 with a cathedral, two museums, a market, a tower "for sunset views," and a dinner at "the most famous restaurant in town." Day two crossed the city four times. Day three squeezed in a day trip to a town an hour and a half away and still had a museum after it. Monday's flight left at noon, and the plan had them at a brunch spot on the far side of the river at 10:00.
Theo counted fourteen named places on day one alone. Maya noticed the plan started six hours before they would land. Neither of them could tell which of the places needed tickets, which were shut on the day the plan put them there, or whether the famous restaurant took bookings at all. And the thing they actually wanted from the weekend, long breakfasts and wandering around somewhere new, was nowhere in it. This page is about briefing a model for a city break that feels like a break: giving it your real hours on the ground, grouping each day by area, picking one anchor per half day, leaving room for the city itself, and planning food and evenings around how you like to spend them. It works in ChatGPT, Claude, Gemini, or a similar assistant, and you do not need to sign up for anything to use it.
One note before you start. A model does not know the city this week. It cannot see opening hours, closures, ticket rules, strikes, works on the metro, or which restaurants still exist. Treat anything it says about a real place, price, opening time, route, or booking as a lead to check yourself with the venue or the city's own sites. This page makes no claims about any real place, and your draft should not either.
Also see: How to protect arrival and recovery days in an AI itinerary · How to set transit rules for an AI itinerary · How to prioritize must-dos in an AI itinerary · How to leave open time in an AI itinerary · How to refine an AI itinerary without starting over · Product overview · Guides · Samples (ILLUSTRATIVE) · llms.txt
Tell the model your real hours on the ground
A "3 day" city break is rarely three full days. You land in the afternoon, get through the airport, find the train or a taxi, drop bags, and work out where you are. On the last day you check out, carry bags somewhere, and leave for the airport well before the flight. A model that hears "3 days" plans three full days, so the first and last days end up packed with things you will never reach.
Give it the clock, not the count. "We land at [15:00] on [Friday] and should be at our place by about [17:00]. We leave for the airport at [09:30] on [Monday]. Plan only the hours in between, and treat arrival evening and the last morning as light." Then say what those light parts are for. Arrival evening might be a walk near where you are staying and an easy dinner. The last morning might be breakfast and one short thing within walking distance of the bags.
If you are taking an early flight or a night train in, say so, because a tired first day changes what makes sense. The arrival and recovery guide covers how to stop a model from filling the first hours, and the last day guide covers the morning you leave.
Group each day by area, not by fame
Most drafts are ordered by how famous each place is, which has nothing to do with where it is. That is how you get a morning on one side of the river, lunch on the other, a museum back where you started, and sunset across town again. Every crossing costs time and energy, and on a short trip those minutes come straight out of the part you came for.
Ask the model to plan by area. "Give each half day one area of the city, or two that are next to each other. Put places in an order we can walk, and tell us roughly how long each walk or ride between them takes, marked 'check.' No more than [one] cross city trip per day." Add your limits, too. "We are happy walking about [8] kilometers a day. Above that, use public transport. Taxis only late at night."
Once each day has an area, the rest of the plan gets easier to judge. You can see at a glance whether a day is too much, and you can swap a place for something nearby without breaking the day. The transit rules guide covers how to tell a model how you like to get around, and the walking budget guide covers daily limits it will keep to.
One anchor per half day
A city has more worth seeing than any weekend can hold, and a model will try to show you all of it. Fourteen places in a day means about thirty minutes at each, counting travel, which is not enough to enjoy any of them. It is better to pick a few things that matter to you and give them real time.
Choose an anchor for each half day: the one thing you would be sorry to miss. "Our must dos are [the big art museum], [a food market], and [an evening by the river]. Make each one the anchor of a half day, with at least [two] hours for it, and fill the rest of that half day only with things nearby that we can skip." Rank them, so the model knows what goes first if something closes or it rains. The must dos guide has more on ranking.
Then check the anchors against the calendar. Big museums and sights often close one day a week, change hours by season, or need a ticket for a set time. Ask the model to list, for each anchor, "opening days, hours, and whether a timed ticket is needed, all 'check'," and confirm them yourself. The opening hours guide covers how to stop a model putting you outside a closed door.
Leave room for the city itself
For a lot of people the best part of a city break is not on any list. It is the long breakfast, the street you wander down because it looked nice, the bookshop, the bench in a square, the drink that turns into two. A draft that schedules every hour leaves no space for any of it, and the trip starts to feel like a job.
Tell the model to plan the gaps on purpose. "Leave at least [two] hours each day with nothing in it. Name the area we will be in, but not what to do there. Start no earlier than [09:30] and keep breakfast slow." If the main sights get very busy, ask for anchors early or late in the day and the open time in the middle, when the crowds are worst. The open time guide covers how to stop a model filling free time back up, and the crowds guide covers timing around busy places.
Food, evenings, and where you stay
Food is a big part of a city break, and it is where drafts are least reliable. A model will happily name a famous restaurant that has closed, moved, or needs a booking weeks ahead. It will also put dinner on the far side of town from where you spent the afternoon. Ask it for the kind of food and the area, not the name. "Dinner near where we finish each day. One booked dinner we look forward to, the rest casual. Lunch should be quick on anchor days. Treat any named restaurant as 'check'." The food rules guide has more on diets and dislikes.
Say how you like evenings to go. Some people want a show, a bar, and a late night every night. Others want dinner and a walk home. A draft will assume one or the other. "Two late nights at most. Saturday is our late night. Our last night is early, because we leave in the morning." The evenings guide covers this in more detail.
Where you stay shapes every day of a short trip. A place near a main transport stop and close to the areas you most want to see saves an hour or more a day compared with somewhere cheaper but far out. Ask the model to suggest areas to stay that fit your anchors, with the trade offs, and to mark everything "check." The lodging rules guide covers how to tell a model what matters to you in a place to sleep.
Why drafts turn a city break into a checklist
When a model reads "city break," it reaches for the patterns that show up most under those words online: top ten lists, "the ultimate weekend in," must sees ranked by fame, a famous restaurant every night. Much of that writing is built to cover everything a visitor could do, not what one visitor can do in two and a half days. Stacked into a plan, it becomes every list at once, ordered by fame, with no travel time, no closing days, and no time to just be there.
The draft also does not know you. It does not know that you land mid afternoon, that you care more about food than towers, that one museum is the reason you picked this city, or that you would rather sit in a square for an hour than see a fifth church. Giving it those facts changes the plan more than asking it to make the trip "relaxed."
A pasteable city break brief
Here is a brief you can paste and fill in. Replace the brackets and remove what does not apply.
ILLUSTRATIVE city break brief (fill brackets; not a real trip) We are planning a city break. [N] people, [N] nights in [describe the city], staying in [area, or "help us choose"]. The point is a few things we love and time to wander, not seeing everything. OUR HOURS: - Arrive at our place about [17:00 Friday]. - Leave for the airport at [09:30 Monday]. - Plan only the hours in between. Arrival evening and last morning are light. - Start no earlier than [09:30]. Slow breakfast. OUR ANCHORS (ranked): 1. [the big art museum] 2. [a food market] 3. [an evening by the river] - One anchor per half day, at least [2] hours. - Opening days, hours, timed tickets for each anchor, all "check". EACH DAY: - One area per half day, or two next door. - Places in walking order, with walk or ride times, "check". - About [8] km of walking a day. Public transport above that. Taxis late at night. - At least [2] hours a day with nothing in it. FOOD AND EVENINGS: - Dinner near where we finish each day. - One booked dinner. The rest casual. - [Two] late nights at most. [Saturday] late. - Treat any named restaurant as "check". DO NOT ADD: [e.g. a day trip out of the city, more than one cross city trip a day, a tower at sunset, plans before we land]. OUTPUT: - Day by day, by area, with rough times. - At the end: what to book and what to check. - Do not state opening hours, prices, routes, or bookings as fact. Mark them "check".
Three parts of the brief do most of the work. The hours lines stop the model planning time you will spend on a plane or in a taxi. The anchor lines give each half day one thing worth the trip and let everything else be optional. The area lines keep the day in one part of the city, which is what makes it feel like a break rather than a commute.
Where this guide stops and the others start
The short trip guide covers any trip of a few days, whether it is a city, a beach, or a cabin, and how to keep a short plan from collapsing under its own weight. Use it for the general rules and this one for what is particular to a city.
The multi city bases guide covers trips that move between several cities: how many bases, how long in each, and the travel days between them. If your break is one city, you can skip it. If it grows into two or three, start there.
An ILLUSTRATIVE city break, three nights
ILLUSTRATIVE sketch only, not a real trip. Here is Maya and Theo's weekend, replanned with the brief above. Two people, three nights, a small hotel in an old neighborhood near a main metro stop. Every opening time, ticket, route, and restaurant was marked to check, and they checked them the week before.
Friday is arrival. They reach the hotel at about 17:30, drop bags, and walk the streets nearby with no plan. An easy dinner ten minutes away, a drink in a square, and bed.
Saturday morning is the anchor they came for: the big art museum, with timed tickets for 10:00, booked the week before. They stay until lunch and eat at a cafe around the corner. The afternoon is open in the old town next door, which turns into a bookshop, a long coffee, and a street of small galleries they had not heard of. Saturday night is the booked dinner and a late walk by the river.
Sunday morning is slow. Breakfast at 10:00, then the food market, which is on their side of the city and open on Sundays (they confirmed it). Lunch is whatever they find there. The afternoon has a park and nothing else, and the evening is a short ride to a viewpoint and a casual dinner nearby.
Monday is going home. Breakfast near the hotel, one last walk, and the metro to the airport at 09:30.
The first draft had fourteen places on day one, plans starting before they landed, four trips across the city, a day trip, and a brunch they would have missed their flight for. This one has one anchor per half day, every day in one or two areas, real time to wander, and a last morning that ends at the airport on time. Theo has already sent the brief to his sister.
Red flags in the draft
Plans that start before you land or run past when you leave. Give the model your real hours on the ground.
A long list of places with no time at any of them. Pick one anchor per half day and give it at least two hours.
Days ordered by fame rather than area. Ask for one area per half day and places in walking order.
Several trips across the city in one day. Allow one at most.
Museums or sights on the day they close. Ask for opening days and hours for each anchor and check them.
No timed ticket or booking notes. Ask what needs booking and when.
A day trip squeezed into a short break. Drop it, or give it a whole day.
A famous restaurant every night, far from where you are. Ask for food by type and area, and book one dinner.
No free time at all. Ask for at least two empty hours a day.
Opening hours, prices, routes, or restaurants for real places stated as fact. Mark each one "check" and confirm it yourself.
Changing the plan on the day
City plans change on the morning. It rains, a museum has a queue round the block, someone wants to sleep in, the area you were saving for later turns out to be the one you love. Keep changes small and say what stays. "Saturday: raining all afternoon. Keep the museum in the morning. Swap the old town walk for something indoors in the same area. Dinner stays." A message like "what else should we see today?" tends to bring back the fourteen places.
Keep a short list of what is fixed, like the hotel, the timed tickets, the booked dinner, and the time you leave for the airport, and paste it at the top of each change. The refine guide has the keep, change, and drop pattern in full.
When a preference survey is worth it
For most city breaks, a general assistant and the brief above are enough. You give it your real hours, group each day by area, pick an anchor per half day, leave room to wander, and check every opening time and booking yourself.
A structured profile starts to help when you take short city trips often, or when you want a researched day-by-day that holds your preferences on pace, walking, food, and how late you like to stay out, without re-explaining in every new chat that you hate early starts, want one good dinner, and would rather wander than queue.
One option with that shape is Dople (dopletech.com). A short preference survey can carry pace, walking limits, lodging style, and food alongside how you like to spend your time. You compare trip options shaped by that profile, and you can buy a Trip Project: a researched day-by-day itinerary meant to hold those preferences across the dates and places you give it. It does not book hotels, tickets, tables, or transport, and it cannot see closures, queues, or the weather on the day. You still check those and book them yourself. The account and the survey start are free. Full itineraries are paid. More on that: a comparison with ChatGPT and what the product is.
Public samples show ILLUSTRATIVE day-by-day shapes only. They are not real trips, and they are not free Trip Projects.
If that survey path sounds useful, sign up once, when you are ready. If it does not, paste the brief above into whatever chat you already have open. The city is the same either way.
What does planning a city break with an AI itinerary mean?
It means telling the model when you actually arrive and leave, what you most want to see, how far you like to walk, and how you like to eat and spend evenings, then asking for a plan that gives each half day one area and one anchor, leaves free time, and lists what to book and check. You check every real opening time, ticket, route, and restaurant yourself.
How much should I plan for each day of a city break?
Less than the draft suggests. One anchor per half day, with at least two hours for it, plus a few nearby things you can skip. Keep each half day in one area, and leave at least two hours a day with nothing planned.
Should I plan a day trip on a short city break?
Usually not on a break of three nights or fewer. A day trip takes a whole day once you count travel, and it costs you the city you came for. If it matters, give it a full day and cut something else, rather than squeezing it in around a museum.
How do I stop an AI itinerary crossing the city all day?
Ask the model to give each half day one area, or two that are next to each other, to put places in walking order with travel times, and to allow no more than one cross city trip a day. Then check the times yourself before you go.
Are the public samples real trips?
No. Samples are ILLUSTRATIVE examples of itinerary shape. Real Trip Projects are researched per traveler after the preference survey. More context sits on the FAQ.