How to plan an AI itinerary around bookings you already have
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.
Tell an AI planner which flights, hotel check-ins, and tickets are already paid for, and what may move around them, so the draft does not invent a day that ignores the confirmation emails.
The confirmation said land at 11:40. The draft still had you in a neighborhood market at 10:00, then a "light lunch," then a note that you could check in "after" if the room was ready. You were still on the jet bridge at 12:05. The hotel would not take the bags until 15:00. The paid walking tour started at 14:00 across town. By the time you found a locker and a cab, the tour had left without you, and the market had never been real. The emails were the plan. The draft had invented a different morning.
Someone who would pay for a plan usually already owns part of the week. A flight with a seat assignment. A hotel with a check-in window and a nonrefundable night. A dinner you put a card on. A museum slot or a tour that already charged. Generic AI still builds a sightseeing sheet and sets those confirmations down as soft preferences, as if both were the same kind of plan. This page is about the paid anchors. The flight clocks. The hotel windows. The tickets that cost money if you miss them. What may still move around them. Most of it works in ChatGPT, Claude, Gemini, or a similar assistant even if you never sign up for anything.
Also see: How to plan an AI itinerary around a fixed event · How to fit timed entries into an AI itinerary · How to set lodging rules for an AI itinerary · How to set food rules for an AI itinerary · How to protect arrival and recovery days in an AI itinerary · How to plan the last day of an AI itinerary · How to plan an AI itinerary around work · How to refine an AI itinerary without starting over · Product overview · Guides · Samples (ILLUSTRATIVE) · llms.txt
What you are actually deciding
The paid booking is a hard block, not a pin you can nudge for a better museum hour. Write the flight number, the departure city clock, the arrival city clock, and the earliest you will actually be useful after you land. A 11:40 arrival is not a 12:00 neighborhood walk. Bags, immigration, the ride, and the first glass of water sit inside that landing. "We land in the morning, so the afternoon is free" is how a draft books a 13:00 timed entry you will miss while you are still waiting for a suitcase.
Hotel check-in is a window with a street address, not a vibe. Write the earliest bags can land, when the room is usually ready, and whether you already paid for early access. A confirmation that says check-in from 15:00 means the bags have a place to go at 15:00, or they do not. Leaving them at a desk while you "start the day" across town is a plan only if you wrote the locker and the return. If the desk will not hold bags, write that too, because the draft will assume a magical closet exists between the airport and the tour. Checkout is the same kind of clock on the way out. The draft likes to keep you in a gallery until the minute before a flight. The hotel wants the key back earlier than that, and the airport wants you seated earlier still.
A dinner or a tour you already paid for is a block with a door time, not a suggestion. Write the name on the confirmation, the start, how long you are committed, the address, and the cancellation rule if you still have one. A 19:30 table that charged a deposit is not competing with a sunset viewpoint the model found three neighborhoods away. A 14:00 walking tour with a prepaid guide is not optional because a museum slot looked scarce. If missing it costs money or burns a nonrefundable hold, it belongs in the same sentence as the flight.
What may still move around those anchors needs its own honesty. Unpaid museum wishes. A neighborhood walk with no ticket. Lunch that is not a reservation. The order of two free afternoons. Those can slide. The paid dinner cannot. If you do not say which lines are free, the model treats every line as free, including the ones that already charged your card. Write the free list in plain words, even if it feels obvious. "Everything else can move" is clearer than hoping the model will infer which pins came from an email.
What you refuse has to be specific, or the revision dodges it with a smaller version of the same mistake. A sightseeing morning that starts before you land. A hotel night on a different street than the confirmation. Moving the paid dinner an hour so a scarce museum can finish. Treating a prepaid tour as optional because the day looked thin. Inventing a second hotel because the draft liked a base closer to a cathedral. Sliding the outbound flight to a later day so Saturday can hold more sights. One line covers the shape: confirmation clocks stay; unpaid stops rearrange or leave.
Who else is on the booking matters when the confirmation has more than one name. A partner on the same flight. Kids on the hotel folio. Friends who already paid for the same tour. Their clocks are part of the block. A solo cafe across town fails when you were supposed to be at the gate together. Write the names that appear on the email. "Traveling with others" is too soft. The model will still tuck in a stop only you would like, in the window when you were meant to be in a security line.
Why drafts still ignore confirmation emails
Training days want a morning, an afternoon, and a night. A flight that lands at midday still leaves a morning column in the model's head, and the morning column receives whatever highly rated stop was not placed yet. The arrival becomes a line under the market, with a time and no bags, no ride, and no check-in. The column looks cared for. You are still on the plane.
Hotels show up in sample text as a pin on a map. Check-in shows up as something that happens whenever you arrive, as if every desk holds bags and every room is ready at 10:00. Tours and prepaid dinners show up as evening color, easy to slide because "restaurants are flexible." Prepaid is not flexible. The deposit says so. The draft stacks a viewpoint before the table because stacking is how it proves it used the city. On the night you already paid for, the stack is the problem.
You say the morning is impossible. The next pass often moves the market earlier, or swaps in a smaller market, still before you land, because a day that starts at the airport looks thin. Thin is what the confirmation bought. A fresh regenerate will sometimes delete the flight time, or invent a different hotel street, so the day can resemble the others.
Prepaid tickets get the softest treatment because the model has read a thousand evenings that "can shift." A deposit dinner looks like a reservation you can call about. A walking tour looks like something the city always offers again tomorrow. Your card says otherwise. Unless the brief marks the charge and the cancellation rule, the draft will keep offering a better sunset first and a later table second.
A ranked list of wishes makes this worse when you paste it with no fence around the paid lines. The cathedral was number one. The nonrefundable dinner was not on the list, because you thought a confirmation email was obvious. The draft schedules the cathedral through 19:15. The dinner appears later as a conflict the model offers to "balance," which means you leave the cathedral late and hope the table waits. Anything already charged still has to be written as a block. A star rating will beat an assumption.
Two pins in one city look like a short hop. The hop is a river, a street closure, or a queue of cabs that are not yours. The draft's transfer from the airport to the tour is twenty minutes. Yours is seventy, and you are holding a suitcase the hotel will not take yet. If you do not write the minutes and the bag plan, the twenty-minute version wins.
A pasteable bookings brief
The block below is ILLUSTRATIVE. It is a shape, not a live confirmation, and not a claim about a real airline, a real hotel, or a real table. Paste it before you ask for the week, or before you ask for the one day that put a market on top of a flight you already bought. Fill the brackets with your clocks, your addresses, and the tickets that already charged. Keep a wedding or a game, museum slots you are still choosing, lodging preferences that are not yet booked, food rules, the landing mood, the flight home, work hours, and refine edits on the briefs linked under the block. If a line is paid, the sheet should say paid. A blank is an invitation to invent.
ILLUSTRATIVE bookings brief (fill brackets; not a live confirmation) Trip: [cities / region], [N] nights Travelers on the confirmations: [who] PAID ANCHORS (do not move, delete, or "improve"): - Inbound flight: [carrier + number], depart [city clock], arrive [city clock on DATE]. Earliest useful after landing: [time], after bags and the ride. Do not schedule sightseeing before that. - Hotel: [name + street], check-in from [15:00], early bags [yes/no / desk only until room ready], checkout by [11:00] on [DATE]. Do not invent a different hotel or a different street. - Paid dinner or tour: [name on the confirmation], [DATE] [start clock], address [street], duration about [N hours], cancellation [nonrefundable / free until X]. This is a hard block, not a suggestion. - Other paid tickets already charged: [museum slot / transit pass start / show]. Same rule: clocks stay. WHAT MAY STILL MOVE: - Unpaid museum wishes, neighborhood walks, lunches without a reservation, the order of free afternoons - Ranked must-dos that are not on a confirmation yet - Anything without a charge on a card or a nonrefundable hold MUST NEVER: - Do not schedule a sightseeing morning that starts before we land or before we are useful - Do not treat check-in as optional, or move us to a different hotel because a sight is closer - Do not slide a paid dinner or tour by an hour so a scarce museum can fit - Do not mark a prepaid ticket optional because the day looks thin - Do not invent a day that ignores the confirmation emails - Do not put a long unpaid stop between the airport and the first paid clock when bags still need a desk - Do not regenerate the week in a way that relocates a flight, a check-in, or a paid reservation LAYER WITH OTHER BRIEFS (paste short lines, do not reinvent them here): - Fixed event (a wedding or game that is social, not a paid tourism ticket): [paste] - Timed entries (slots you are choosing or still holding as barcodes on other days): [paste] - Lodging rules (preferences for future nights; this hotel is already booked): [paste] - Food rules (allergies and meal style; the prepaid dinner is already the table): [paste] - Arrival / recovery (how wrecked the landing feels; the flight clock still wins): [paste] - Last day (checkout + airport hard stop on the way out): [paste] - Work (calls that block hours; do not slide a paid dinner for a cafe): [paste] - Refine (how to move Monday without touching these anchors): [paste] OUTPUT I WANT: - Every paid clock unchanged - Bag / check-in plan written when the landing meets a same-day ticket - Unpaid stops placed only in hours that are actually free - Displaced wishes moved to other days, or cut - Checklist: no sightseeing before useful-after-landing; hotel street matches confirmation; paid dinner/tour not slid
One follow-up catches the failure before you are in a cab with the wrong morning. Ask the model to restate, for each paid date only, the flight or check-in or dinner clock, and what sits before and after it. If a line still shows a market before you land, a different hotel street, or a start time with no bag plan, send that date back. Do not ask for a new trip.
The lines this page will not swallow are already their own guides, linked in the next section and in the list under the title. Paste those short versions beside this block. The refine guide is how you move Tuesday without touching the confirmations.
Where this stops and the other guides start
A fixed event is one social hour you cannot move: a wedding, a game, a reunion dinner that was on the calendar before the trip existed. It may or may not have charged a tourism vendor. This page is the paid tourism and travel confirmations: flights, hotel windows, prepaid tours, deposit dinners. If both are true on one Saturday, paste both briefs. The fixed-event guide holds the ceremony. This page holds the flight that gets you there and the hotel that holds the bags. Do not let a museum win against either.
A timed entry is a museum slot you chose, or are still choosing. You can miss it or rebook it more often than you can miss a nonrefundable flight. If you hold a barcode on a different day, keep the choosing and fitting work on the timed entries guide. On a day that already has a prepaid tour, a second timed ticket inside the same buffer is a refusal, even when the site said it was the last slot. This page does not teach you how to pick slots. It stops the draft from treating a slot you already paid for as optional scenery.
Lodging rules are preferences for where you sleep when the night is not yet booked: quiet, elevator, near a tram, no party hostel. Once a hotel confirmation exists, the street and the check-in window are anchors, not preferences. Future nights can still use the lodging rules guide. Do not let this page redesign a paid folio, and do not let a lodging preference invent a second hotel on a night you already bought.
Food rules are allergies, meal timing, and what you will not eat. A prepaid dinner is already a table. Rules about spice or seating still matter, and they live on the food rules guide. This page does not rewrite the menu. It stops the draft from sliding the reservation so a viewpoint can fit, or from adding a second heavy dinner the same night because the model likes stacking.
Arrival and recovery are how wrecked you are after the landing, and what the first night is allowed to be. That mood lives on the arrival guide. The flight clock still wins. This page writes the useful-after time and the bag plan. The arrival guide can keep you from a heroic first evening. It should not be used as an excuse to ignore the confirmation times the draft already wants to overwrite.
The last day is checkout, the bags, and the hour you have to be moving toward the airport. Paste the last day guide beside this one when the outbound flight is already bought. You do not fix a tight departure by inventing a later flight, and you do not fix a museum wish by pretending checkout is flexible. The cut is the unpaid stop between the key return and the security line.
Work blocks are calls and deadlines on the local clock, with a chair you can actually use. That shape lives on the work guide. A paid dinner does not move for a cafe the model invented so you could "take the call nearby." If both a call and a prepaid table share a day, both briefs stay. This page does not decide wifi. It stops the draft from treating the deposit as the flexible line.
Refine is how you edit one date without restarting the week. Keep it on the refine guide. An anchor fix should move the unpaid museum, not the flight. When a revision sneaks the market back before landing, repair that date. Do not regenerate the trip to see if a cleaner city appears.
An ILLUSTRATIVE day that keeps the paid commitments
ILLUSTRATIVE sketch only, not a real booking. Five nights, one hotel already confirmed, two adults on the same inbound flight. Arrive 11:40 local. Useful after bags and the ride: about 13:15. Hotel check-in from 15:00; desk will hold bags from 13:30. Prepaid walking tour at 16:00, two blocks from the hotel, ninety minutes. Dinner is open; no deposit.
The sheet that respects the emails looks dull in a good way. No market at 10:00. No museum across town at 14:00. Land, ride, bags at the desk, short sit near the hotel, room when it opens, walk to the tour you already paid for, then a simple dinner within a short walk. The cathedral they wanted is Tuesday morning, with a timed entry that does not touch the landing. Wednesday holds the neighborhood walk that used to be jammed into arrival day.
A generic draft for the same Saturday usually keeps a 10:00 market, a 13:00 lunch near that market, check-in as a footnote, and the tour as a 16:00 pin with a twelve-minute "transfer" from a gallery on the far side of the river. The twelve minutes are the fantasy. The suitcase at a desk you have not reached is how you know the draft did not read the confirmation.
The same shape works when the paid line is a dinner. ILLUSTRATIVE again. Thursday, deposit table at 19:30, address on the confirmation, ninety minutes committed. Afternoon can be one neighborhood you can leave by 18:15. It is not a museum that closes the loop on the far side of the city at 18:40. After dinner, the sheet says the walk back or a drink you named, not a viewpoint three hills away. "Dinner is flexible, so the sunset comes first" is the sentence that burns the deposit.
On the way out, the outbound flight is already bought for Sunday at 16:10. Checkout is 11:00. Useful toward the airport by 13:00 once bags and the ride are honest. Sunday morning can hold one short stop near the hotel. It cannot hold a second neighborhood and a long lunch. That cut belongs with the last-day brief, and the flight confirmation still sits on this page as the reason the cut exists.
Red flags in the draft
Sightseeing that starts before you land, or before the useful-after time you wrote. The word light does not save it. If you would still be at baggage claim, it should not be on that morning at all.
A hotel on a different street, or a second hotel invented because a sight was closer. The confirmation has an address. A prettier pin is the violation.
Check-in treated as a vibe. "Drop bags whenever" with no desk plan, while a prepaid tour starts before the room exists. You said the window. The draft ignored the window.
A paid dinner or tour slid. 19:30 became 20:30 so a timed entry could finish. Or the tour moved to Sunday because Saturday looked crowded with the flight. A smaller unpaid stop on the same collision is the same error in a quieter voice. So is a day trip that promises you will be back "in plenty of time" for a table that already charged.
The paid line deleted. A later revision has a clean Saturday of sights and the flight time is gone, or the dinner is marked optional, because the inflexible line made the day look ugly. Paste the brief again until the clocks and the refusal are on the sheet. If that Saturday is also a work call or a wedding, those blocks stay on their own guides. Do not solve the collision by sliding the confirmation.
Bags with nowhere to go. A plan that sends you across town between landing and a prepaid ticket, with no desk, locker, or return written. The suitcase is part of the block. A pleasant gallery that assumes someone else is holding your life is wrong.
Someone missing from a shared confirmation. You named a partner on the same flight and the draft gives you a solo coffee across town at the hour you were meant to be in the security line together, or gives them a different hotel night than the folio. The block includes the names on the email. A plan that is pleasant for one of you and late for the gate is wrong.
Change the free parts without moving the paid ones
A bad bookings day rarely needs a full regenerate. Regenerating tends to relocate the flight, invent a hotel, or drop the dinner, because the model is optimizing for a day that looks like its other days. It can also "improve" Tuesday, which was already the day you had reserved for the cathedral. Stay in the thread. Edit by date. The confirmation dates are the ones you are not allowed to improve.
Say the collision in clock times and places. "Saturday has a market at 10:00 and a flight that lands at 11:40. We are not useful until 13:15. Cut the market. Cut the lunch near the market. Do not replace them with a smaller sight before 13:15. Do not move the flight. Put the cathedral on Tuesday morning if Tuesday can hold it. If it cannot, drop it." "Make Saturday lighter" gets you a shorter market, still before you land, plus a note that you can see the city from the cab.
Restate the paid clocks, the bag plan, and the other names on the confirmation in that same message. Ask to see them on the revised date. If the dinner time shifts by half an hour, reject the shift even when the new time looks more convenient for a ticket you did not ask to protect. Leave fixed-event blocks, timed entries on other days, lodging preferences for unbooked nights, food rules, arrival mood, last-day hard stops, and work chairs alone. An anchor fix should not eat them, and it should not redraw the week except to receive the stops the paid day refused.
The refine guide has the keep, change, and drop pattern. Add one line to it for this date: "Keep [Saturday] [land 11:40, useful 13:15, hotel desk bags, tour 16:00 paid]; move [the cathedral] to [Tuesday]; do not move the flight, the hotel, or the tour." When a revision sneaks the market back, or slides the table, repair that date. Do not regenerate the week to see if a cleaner city appears.
How this sits with the other briefs
This page is the paid anchors, and it stops once the flights, hotel windows, prepaid tickets, and the free-versus-paid split are on the sheet. A wedding or a game, barcodes you are still choosing, lodging preferences for nights not yet bought, food rules, how wrecked the landing feels, the outbound hard stop, work chairs, and the edit pattern stay on the guides linked above. Refine is how Tuesday receives the cathedral after Saturday was already wrong. None of those pages get a vote on moving a confirmation email. If a collision needs two briefs, paste both. Do not ask this page to swallow a wedding dress rule or a call chair.
When a preference survey is worth it
If you are willing to keep pasting the bookings brief, a general assistant plus the paid clocks, the bag plan, and the refusal is enough for a lot of trips. A confirmation you will actually meet matters more than a nicer paragraph about the city on either side of it.
A structured profile starts to matter when the chat keeps putting a market back before you land after you cut it. Or when "tour at 16:00 paid" disappears by revision four and a twelve-minute transfer from across town returns. Or when you want a researched day-by-day that holds the anchors without teaching them again in every new thread, including the names on the folio.
One option with that shape is Dople (dopletech.com). A short preference survey can carry pace, food, and lodging alongside the flights, hotel windows, and prepaid tickets you already hold. You compare trip options shaped by that profile, and you can buy a Trip Project: a researched day-by-day meant to hold those preferences, so a draft does not keep inventing a morning that ignores the confirmation emails. The account and the survey start are free. Full itineraries are paid. More on that work: a comparison with ChatGPT and what the product is.
Public samples show ILLUSTRATIVE day-by-day shapes only. They are not live bookings, and they are not free Trip Projects.
If that survey path sounds useful, sign up once, when you are ready. If it does not, use the brief above in whatever chat you already have open. The confirmation clocks work either way.
What does planning an AI itinerary around bookings you already have mean?
It means telling the model which flights, hotel check-ins, and tickets are already paid for, and what may still move around them. The draft then keeps those confirmation clocks. It does not invent a day that ignores the emails.
Why do AI drafts ignore confirmation emails?
Sample days keep a full morning even when you are still in the air, and the unused famous stop goes there. A flight time with no useful-after line lets the draft call the gap a transfer. Hard paid blocks, a bag plan, and a refusal give it fewer ways to book the market.
What belongs in a bookings brief?
Each paid flight with clocks, each hotel with check-in and checkout, each prepaid dinner or tour as a block, what may still move, and what you refuse. Point at fixed-event, timed entries, lodging, food, arrival, last day, work, and refine instead of rewriting them here.
Should I regenerate the trip when a day ignores a paid booking?
No. A new draft often slides the flight or drops the dinner so the day can look normal. Name the date, restate the paid blocks, move the unpaid stops off that collision. Editing in place is the refine guide.
Are the public samples real bookings?
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.