How to decide where to eat 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.
Decide where to eat on a trip with an AI planner: meals tied to where the day already takes you, rules for cuisine, diet, and budget, reservations as fixed points, room for walk-ins, and every restaurant, hour, and price checked yourself.
Maya and Jonas had a good plan for their first full day in a city neither of them knew: a museum in the morning, a long walk through an old quarter, and a river cruise at six. Then Jonas asked a chat assistant where they should eat. It gave him a lunch spot forty minutes across town from the museum, a dinner place on the far side of the river from the cruise, and three famous options for every meal, all of them with hours and prices it described as current. It suggested a grill house for Maya, who does not eat meat. One of the places, they later found out, closed on the day they would be there.
None of the suggestions were bad on their own. The problem was that each one was chosen as if the rest of the day did not exist. What they wanted was simpler: somewhere decent to eat near wherever they already were, that suited what they eat and what they wanted to spend, with the one dinner they had booked treated as fixed and some meals left open for whatever looked good on the street. This page is about getting that from a model. 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 cannot see which restaurants are open today, what is on their menus, what anything costs, or whether a table is free. Its restaurant names and details may be out of date or simply wrong. Anything it tells you about a real restaurant, café, market, opening time, menu, price, or booking is a guess to check yourself with the place. This page makes no claims about any real restaurant, place, or price, and your draft should not either.
Also see: How to plan an AI itinerary around opening hours · How to plan an AI itinerary around bookings you already have · How to refine an AI itinerary without starting over · Product overview · Guides · Samples (ILLUSTRATIVE) · llms.txt
Anchor meals near the day's plan
The most useful question about where to eat on a trip is not "where is the best food" but "where will we be when we get hungry." A model asked for the best restaurants in a city will happily send you across it for lunch, and the hour you lose in transit is an hour you do not spend doing what you came for.
Plan the day first, then ask for meals that fit it. "Here is tomorrow: [museum in the morning, walk in the old quarter after lunch, river cruise at 18:00 from the north bank]. Suggest lunch within [ten minutes' walk] of where the morning ends, and dinner within [ten minutes] of where the cruise finishes. Mark every walking time 'check.'" Tying each meal to a place you will already be keeps the day in one piece and usually makes the choice easier, because there are only so many options within a short walk.
It also helps to say which meals matter. Most days have one meal you care about and others that just need to be good enough. Tell the model which is which, and it can spend its effort on the one that counts and keep the rest simple.
Rules for cuisine, diet, and budget
A model does not know that you will not eat meat, that one of you cannot have gluten, that you would rather have a long lunch than a long dinner, or that you want most meals to cost about what you spend at home. Without that, it reaches for the famous places, and famous places tend to be expensive, busy, and not always right for you.
Give it a short set of rules and ask it to apply them to every suggestion. "We eat [vegetarian for one of us, anything for the other]. [No shellfish.] We like [local food, casual places, somewhere we can sit outside]. Most meals should be [everyday prices, roughly what we would spend at home]; one dinner can be a treat. If a suggestion does not fit, leave it out rather than flagging it." The food rules guide covers writing those preferences so a model keeps them across a whole trip, and the daily spend guide covers setting a spending limit for each day.
Be specific about allergies and hard rules, and do not rely on the model for them. It can avoid places that obviously do not fit, but whether a kitchen can cook safely for you is something only the place can tell you.
Reservations are fixed points
If you have booked a table, the rest of the day should bend around it, not the other way around. A model will sometimes plan an afternoon that ends an hour's travel from your booking, or suggest a big lunch two hours before a dinner you have been looking forward to for weeks.
Give it your bookings as facts. "Confirmed: [dinner, day two, 19:30, near the old harbor]. This does not move. Plan the afternoon so we arrive on time and hungry, keep lunch light that day, and mark every travel time 'check.'" If there is a place you want but could not book, say so, and ask for a backup in the same area rather than a plan that depends on getting lucky. The bookings guide covers planning around what you have already locked in.
Do not let the model book or confirm anything for you in its answer. If it says a table is free or that a place takes walk-ins, treat that as "check."
Leave room for walk-ins
Some of the best meals on a trip are ones nobody planned: a counter you walked past twice, a place full of people who clearly live nearby, a bakery you smelled before you saw it. A day where every meal is named in advance leaves no room for any of them, and it also leaves you stuck with a choice made weeks ago by a model that has never been there.
Ask for some meals to stay open. "Only name a place for lunch on days we will be somewhere unfamiliar. Leave most breakfasts and at least one dinner open, and for those just tell us the kind of area that tends to have good casual food, so we can pick on the day." A few loose options are more useful than a fixed pick for every meal. The open time guide covers keeping unplanned time in a plan so the model does not fill it.
Check hours yourself
Restaurant hours are where AI drafts go wrong most often. Places close one or two days a week, stop serving lunch earlier than you expect, shut for a holiday or a season, change hands, or close for good. A model may have read about a place years ago and has no way to know.
Treat every name and time in the draft as a lead, not a fact. Before you commit to a meal, check the place's own website or listing for the days and hours you will be there, and call or message if it matters. If something is closed, give the model the real hours and ask for a replacement nearby. The opening hours guide covers giving a model real hours to work with.
Why AI restaurant picks drift
A model asked where to eat reaches for what it has read most: best restaurant lists, famous dishes, places that have been written about many times. Those places may be excellent, but the lists say nothing about where you will be at one o'clock, what you can eat, what you want to spend, or what is open this week. So the model picks each meal on its own, in the abstract, and the picks pull your day apart.
What it needs from you is what the lists leave out: the day's plan, your rules, your bookings, which meals to leave open, and a reminder that every name and hour is something you will check. Those facts change the answer more than asking for somewhere "really good."
A pasteable where to eat brief
Here is a brief you can paste and fill in. Replace the brackets and remove what does not apply.
ILLUSTRATIVE where to eat brief (fill brackets; not a real trip) Help us decide where to eat on [day or days]. THE DAY'S PLAN: - Morning: [activity, area]. - Afternoon: [activity, area]. - Evening: [activity, area, end time]. OUR RULES: - We eat [diet]. We never eat [items]. - [Allergies; we will confirm these with each place ourselves.] - We like [kind of food, kind of place]. - Most meals: [everyday prices]. One treat meal: [day]. FIXED: - Confirmed: [meal, day, time, area]. This does not move. OPEN: - Leave [breakfasts, one dinner] open. Just tell us what kind of area to look in. OUTPUT: - For each planned meal: two or three options within [10 min] walk of where we will be. - Mark walking times "check". - Do not state names, hours, menus, prices, or availability as fact. Mark them "check". - At the end: what to book and what to check.
Three parts of the brief do most of the work. The day's plan keeps meals close to where you already are. The rules keep out what does not suit you. The open line leaves room for the meal you find by walking past it.
Where this guide stops and the others start
This guide is about choosing meals inside a trip that is mostly about something else. If food is the reason for the trip, the food trip guide covers building whole days around eating, with one anchor meal a day and markets in between. If you want help with what happens after dinner, the evenings guide covers that part of the day.
An ILLUSTRATIVE day of meals
ILLUSTRATIVE sketch only, not a real trip. Here is Maya and Jonas's first full day, replanned with the brief above. Two people, one vegetarian, everyday prices except for one dinner later in the trip, which they had booked themselves.
Breakfast stays open. The model suggests looking for a bakery on the way to the museum rather than naming one, and they find a small one two streets from the hotel. Lunch is planned, because the museum sits in an area they do not know. The model gives three options a short walk from the exit, all marked "check," and they look each one up the night before. One is closed on that day of the week, so they cross it off and keep the other two.
The afternoon walk through the old quarter has no meal in it, only a note that it is a good place for coffee and something small if they want it. Dinner comes after the cruise, which ends around 19:30 on the north bank. The model suggests two places within a short walk of the pier, both with vegetarian dishes on the menus it has seen, both marked "check." Jonas calls one in the afternoon to confirm it is open and has room for two.
The first draft had them crossing the city for lunch, a dinner on the wrong side of the river, a grill house for a vegetarian, and a place that would have been closed. This one keeps every meal within a short walk of where they already are, suits both of them, and still leaves breakfast and an afternoon snack to chance. Maya said it was the first time a plan had made eating easier rather than harder.
Red flags in the draft
A meal far from where you will be before or after it. Ask for options near the day's plan.
Restaurant names, hours, menus, or prices stated as current. Mark every one "check" and confirm it with the place.
A suggestion that ignores your diet or allergies. Restate the rule and ask it to drop anything that does not fit.
Every meal at a famous or expensive place. Give it your everyday budget and say which meal is the treat.
A busy afternoon that ends far from a booked table. Plan the day backward from the booking.
Every single meal named in advance. Leave some open.
A place listed as open without a day or time attached. Check the days and hours yourself.
Deciding on the day
Plans change. A lunch place is closed when you arrive, the morning runs long, you are not hungry yet, or you find somewhere better on the way. Keep the request small and say where you are. "We are near [the north end of the old quarter], it is 13:30, we want something light and vegetarian, nothing over [everyday prices]. Dinner at 19:30 stays as it is." A message like "where should we eat?" with no context tends to bring back the same list of famous places.
Keep a short list of what is fixed, like the hotel, any booked meals, and when you need to be somewhere, 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 trips, a general assistant and the brief above are enough. You tie meals to the day's plan, give it your rules, treat bookings as fixed, leave some meals open, and check every name and hour yourself.
A structured profile starts to help when you travel often, or when you want a researched day-by-day that already knows how you eat, what you like to spend, and how far you like to walk, without explaining again in every new chat that one of you is vegetarian and neither of you wants to cross town for lunch.
One option with that shape is Dople (dopletech.com). A short preference survey can carry food, budget, pace, and travel limits 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 tables, travel, or lodging, and it cannot see this week's hours, menus, prices, or which tables are free. 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.
To see meals placed inside real days, the public Lisbon food and pace sample gives every day one food anchor, such as a market or food hall, a tasca or seafood dinner, or a pastry stop, at a moderate pace. The 5 day Lisbon food itinerary for couples walks through how it works. Other public samples show different trip shapes. Samples are examples, not booked trips and not free Trip Projects.
Ready to plan where you will eat on your next trip? Start free and compare trip options. A short preference survey shapes the options, and you pay only for the full day-by-day itinerary you choose. Confirm prices, hours, and availability with each place before you book.
If you would rather not sign up, paste the brief above into whatever chat you already have open, and eat somewhere close.
How do I decide where to eat on a trip with an AI itinerary?
Plan the day first, then ask the model for two or three options near where you will already be at each mealtime, filtered by your diet, tastes, and budget. Treat any booked tables as fixed, leave some meals open for walk-ins, and check every name, hour, and price yourself with the place.
Can an AI tell me which restaurants are open?
No. A model cannot see current opening hours, menus, prices, or availability, and its details may be out of date or wrong. Use its suggestions as leads and confirm the days and hours with each place before you go.
How do I get AI restaurant suggestions that fit my diet and budget?
Give it short, specific rules: what you eat and never eat, any allergies, the kind of food and places you like, and what most meals should cost, with one meal allowed to be a treat. Ask it to leave out anything that does not fit, and confirm allergies with the place yourself.
Should I plan every meal in advance?
Usually not. Book the meals that matter and give them to the model as fixed points, plan meals in unfamiliar areas, and leave some breakfasts and at least one dinner open so you can choose on the day.
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.