How to plan a trip around your pace
Build day-by-day plans that match your energy, walking limits, and recovery needs instead of a packed highlight reel.
The day looked perfect on paper. Morning at a big museum, then a viewpoint that needed a hill climb, lunch in a different neighborhood, an afternoon market, and a sunset ticket across town. ChatGPT had arranged it neatly. Claude would have done the same shape. By 3pm your feet were wrecked, you were skipping the market you actually cared about, and dinner felt like one more obligation. You did not hate travel. You hated that the plan never asked how much walking you could stand before the day turned mean.
Pace, here, is a set of limits that decide whether a day is livable. This page is about naming those limits, scoring a day plan before you book anything, and pasting a short pace brief into any AI chat tool so the output stops pretending every day can hold five trophies. Most of it works without signing up for anything. Later we note when a stored preference profile and a researched day-by-day plan can save you from rewriting the same pace rules in chat.
Also see: How to stop getting generic AI itineraries · Personalized travel itineraries FAQ · What is Dople? · Dople vs ChatGPT · Samples (ILLUSTRATIVE) · llms.txt
What pace actually means
Pace is how many hard things a day can hold before you resent the trip. It shows up in boring details the highlight reel skips.
Stops. One major museum plus a neighborhood wander is a different day than three ticketed sites with transit between each. Decide a max for major stops. Two is enough for a lot of people. Three starts to feel like work. Five is how you end up eating a granola bar on a metro platform and calling it lunch.
Walking. Kilometers on a map lie. Cobblestones, luggage days, heat, and hills change the math. Light, moderate, or heavy is a useful label only if you also say whether hills and stairs after 4pm are ok. Plenty of "moderate" days quietly include a late staircase that ruins the evening.
Stairs and elevation. Cities love viewpoints. Your knees might not. If stairs after late afternoon are a hard no, write that down before the model suggests another miradouro.
Lunch length. A 25-minute grab-and-go keeps the schedule moving. A 90-minute lunch with nowhere to be after is how some people actually enjoy a city. Chat tools default to short meals so more attractions fit. Push back if you want the long version.
Evening energy. After a packed day, do you still want a late reservation and a loud room, or an early meal and a quiet walk back? Evening plans that ignore morning load are how you get irritable in a restaurant you would have loved on a lighter day.
None of this makes you a "slow traveler" as a brand. It makes the week match how your body actually behaves on day three of a trip, which is usually different from day one.
How to score a day plan before you book anything
Take any day-by-day draft (from a blog, a friend, or an AI chat) and score it before money leaves your account. You do not need a fancy rubric. Count the hard parts.
Major stops: how many ticketed or "we have to be there" moments? If the number sits above your max, cut before you book.
Walking load: estimate door-to-door walking plus transit. If the draft never mentions travel time, assume it is optimistic. Cross-town hops that look short in a paragraph often take 35 to 50 minutes.
Stairs and hills: circle every viewpoint, castle, metro exit with stairs, or "short climb." If more than one lands after mid-afternoon and you hate that, the day fails.
Meal spacing: are lunches treated as fuel stops between sights? If you wanted a real midday break, the day is still packed even when the stop count looks fine.
Empty space: a workable day often looks slightly incomplete on paper. Blank afternoon blocks are not failure. They are where you sit down, change plans, or recover without apologizing to the itinerary.
Arrival and departure days: if day 1 after a red-eye starts with a 9am museum, score it as failed until someone lightens it. Same for the morning you fly home with a 6am checkout and a "quick" last attraction.
A day that scores poorly on paper rarely improves on the ground. Fix the shape first. Book tickets second.
A simple pace brief you can paste into any AI chat tool
Use this inside ChatGPT, Claude, Gemini, or similar. Fill the brackets. Ask for a day-by-day plan that obeys the pace rules instead of padding the week to look complete.
Trip: [destination], [N] days, [month/season], [solo/couple/friends/family ages] Pace profile: - Max major stops per day: [1 / 2 / 3] - Walking: [light / moderate / heavy]; hills: [ok / limit]; stairs after 4pm: [ok / avoid] - Lunch: [short / 60+ min / 90+ min with nothing booked after] - Evenings: [early quiet / mixed / late social]; after a heavy morning, evenings must be [light / open] - Transit comfort: [happy on metro / prefer taxis for hops over 25 min] Energy rules: - Arrival day after travel: [light only / one neighborhood walk max / sleep first] - At least one recovery half-day in the middle of the trip: [yes / no] - No back-to-back heavy days: [yes / no] Output I want: - Day-by-day with morning / afternoon / evening - Travel time between stops (minutes, honest) - Explicitly drop famous spots that break the pace rules (name what you dropped and why) - Do not fill empty blocks just to look thorough
One follow-up worth using: ask the model to restate your max stops, stair rule, and arrival-day rule before it writes the days. If it cannot repeat them, the brief did not stick.
"Make it more chill" rarely works. "Cut day 2 to two stops, move the hill climb to morning, and leave the afternoon blank after lunch" is something a plan can obey. For a fuller brief that also covers food, lodging, and dealbreakers, see How to stop getting generic AI itineraries.
Recovery and arrival days
The week fails in the gaps chat tools love to fill.
Arrival day. You landed tired, maybe hungry, maybe with luggage. A light neighborhood walk, an easy meal near the lodging, and an early night usually beats a "welcome" museum. Plans that start heroically on day 1 often steal energy from day 2 and day 3.
Mid-trip recovery. After two hard days, a half-day with no tickets is not wasted. Laundry, a long lunch, a park bench, a nap. People who skip recovery often abandon the "fun" evening they paid for because they are cooked.
Weather and body days. Rain, heat waves, a pulled calf, a bad night of sleep. Build one indoor backup and one low-walk option into the week so you are not inventing a new plan while miserable.
Departure mornings. Checkout plus airport transit is already a day. Adding one last attraction sounds romantic in the draft and stressful with a suitcase.
If an AI draft treats every calendar day as equal energy, rewrite it. Human weeks are lumpy. Good trip plans are too.
When a preference survey and Trip Project path helps
If you enjoy prompt work and you are willing to verify venues yourself, keep using a general assistant. A clear pace brief fixes a lot of ambitious AI itineraries.
The structured path starts to matter when chat keeps restacking trophy days after you already said two stops max. Or when your constraints span pace, food, lodging, and hard dealbreakers and the thread drops pieces by day four. Or when you want a researched day-by-day plan that holds walking limits and recovery rules without rebuilding the brief every session.
One option with that shape is Dople (dopletech.com). A short preference survey builds a traveler profile, you compare trip options shaped by it, and you can buy a Trip Project: a researched day-by-day itinerary that is supposed to hold your pace rules instead of dropping them by day four. Account and survey start are free. Full itineraries are paid. More product detail lives at Dople vs ChatGPT, Dople vs Mindtrip, and What is Dople?.
Public samples show ILLUSTRATIVE day-by-day shapes only (Lisbon food and pace, Tokyo week, and similar). They are not live bookings and not free Trip Projects.
If the survey path sounds useful, sign up once when you are ready.
How many stops should I plan per day?
Most people do better with a max of two major stops, sometimes three on a high-energy day. Five ticketed musts with transit between them is a common AI default and a common reason feet give out by mid-afternoon. Set your own number and make the plan drop famous spots that break it.
What should I tell ChatGPT about walking and stairs?
Say light, moderate, or heavy walking, whether hills are ok, and whether stairs after 4pm are allowed. Ask for honest travel time between stops. Without that, models stack viewpoints and cross-town hops that look fine in a paragraph and feel brutal on the ground.
Why do AI itineraries ignore recovery days?
Short prompts under-specify energy after flights and mid-trip rest. Models fill the calendar so the week looks complete. State arrival-day rules, ban back-to-back heavy days if you need that, and require at least one recovery half-day when you want it.
Are Dople samples real bookings?
No. Samples are ILLUSTRATIVE examples of itinerary shape, including pace-aware days. Real Trip Projects are researched per traveler after the preference survey.