How to set weather and season rules for an AI itinerary
Give AI rain pivots, heat limits, and shoulder-season shutters so outdoor plans do not collapse the first wet morning.
Day three opened on wet pavement and a gray that would not burn off. The draft still wanted the cliff path at 9:30, the plaza lunch, the viewpoint at golden hour. No raincoat plan. No museum swap. No "if rain, do X" line. You stood under a cafe awning refreshing the radar while the day you paid for sat outdoors in a forecast the model never had to live through. Same trip, hotter week: a ridge walk pinned for 14:00 when the local heat advisory said stay inside until late afternoon. The prose still sounded adventurous. Your feet and the sky disagreed.
This page is about weather and season constraints in AI day plans. Rain pivots. Heat caps. Indoor backups. Shoulder-season hours and shuttered routes. Not calendar closed days, not buffer minutes, not hard vetoes, not priority ranks. Those have their own guides. Here you teach the model what to do when the sky or the season makes the outdoor stack collapse even if the doors are open. Most of it works in ChatGPT, Claude, Gemini, or similar even if you never sign up. Near the end we note when a preference survey that holds these rules across revisions can beat paste-and-hope.
Also see: How to plan an AI itinerary around opening hours · How to leave open time in an AI itinerary · How to prioritize must-dos in an AI itinerary · How to fit timed entries into an AI itinerary · How to set dealbreakers for an AI itinerary · How to refine an AI itinerary without starting over · How to plan a trip around your pace · How to set a walking budget for an AI itinerary · How to protect arrival and recovery days · How to choose bases for a multi-city AI itinerary · How to stop getting generic AI itineraries · What is Dople? · Guides · Samples (ILLUSTRATIVE) · llms.txt
What weather and season rules are (and what they are not)
Weather and season rules are contingency constraints. If steady rain, swap the cliff path for Museum A or the covered market. If afternoon heat above your comfort, move hiking to early morning or an indoor block. If shoulder season, expect reduced ferry runs, earlier last entry at outdoor sites, and some gardens or high trails closed. You write the pivots into the brief so the model cannot invent a week that only works under postcard skies.
They are not opening hours. Opening hours are closed Mondays, last entry, kitchen clocks. A museum can be open on a wet Tuesday and still be the right rain pivot. Pair calendar facts with the opening hours guide so your indoor backup is actually open that day.
They are not open time. Open time is slack between blocks so a late tram does not collapse lunch. Weather rules decide which block you run when the sky turns. Pair with the open time guide so a rain swap still keeps honest gaps.
They are not dealbreakers. A dealbreaker is a hard veto: no boats, no starts before 9:30. Weather rules assume you still want the outdoor stop on a good day; they name the backup when the day is not good. Use the dealbreakers guide for categories you refuse in any weather.
They are not priority ranks. Must / should / nice / skip decide which stops own the good half-days. Weather rules decide how a must outdoor stop pivots when rain or heat hits. Pair with the must-dos guide so your top outdoor pin has a named indoor twin, not a shrug.
If you only say "we like hiking and viewpoints," models often print a sunny week. If you say "MUST outdoor: Cliff Path Day 2 or 3 morning; RAIN PIVOT: Museum A or Covered Market B; HEAT: no exposed ridge walks 12:00-16:00; SHOULDER: ferry to Isle C limited weekdays, confirm or replace with coastal walk D," the draft has fewer ways to strand you under an awning with no plan B.
Why AI drafts assume postcard weather
Training data loves clear-day itineraries. Outdoor stacks look complete and photogenic in prose. Rain, heat advisories, and shoulder-season cutbacks rarely appear unless you force them. The model can name a famous viewpoint without ever checking whether November ferries still run, or whether a July plaza lunch at 13:30 is survivable for your group.
Seasonal tone leaks. A summer guidebook voice sneaks into a March trip: long evenings, full ferry schedules, gardens in bloom. Or a mild spring brief gets pasted onto a humid August city week and the afternoon walking budget quietly dies. Soft language makes it worse: "weather permitting" without a named pivot is not a rule. It is a shrug you discover at breakfast.
Forecasts change after draft one. A sunny plan written two weeks out meets a three-day rain band on arrival. Without an indoor backup list already vetted against opening hours, you improvise under the awning and lose the must you ranked. Timed entries make it sharper: a prepaid outdoor slot in heat or rain still guilt-trips you into going. Buy weather-flexible tickets for musts, or accept the pivot before you pay.
Regenerate loops often keep the outdoor bias. New cafe name, same cliff path at 9:30 with no rain line. Without an explicit weather brief pasted into every refine, the model forgets the pivot by revision three.
A pasteable weather and season brief
Paste this as the weather source of truth before you ask for morning-afternoon-evening detail. Fill brackets with real rain pivots, heat windows, indoor backups, and shoulder-season notes. Attach opening-hours, open-time, must-do, timed-entry, walking, pace, spend, food, lodging, and dealbreaker lines you already trust. Ask for a day-by-day that never leaves an outdoor must without a named backup, and never pins heat-sensitive walking in the worst afternoon window.
Trip: [city / region], [N] nights, [month/season], travelers: [N] Expected climate: [e.g. shoulder spring / humid summer / rainy shoulder / cold dry] Comfort limits: heat max outdoor [e.g. avoid exposed walks above ~28 C / 82 F midday]; cold / wind notes: [e.g. no long ridge walks in gale forecasts] WEATHER AND SEASON RULES (locked; do not schedule over these unless I reopen them): - Rain pivots (outdoor MUST / SHOULD stops): - [Cliff Path / Viewpoint A]: if steady rain or high wind, swap to [Museum / Covered Market / Indoor gallery B]; keep open-time buffer - [Garden / ruin / ferry walk C]: if rain, swap to [Indoor backup D] or move to next clear morning - Heat / cold windows: - Exposed hiking / plazas: prefer [early morning / late afternoon]; do not pin [12:00-16:00] on hot days - If heat advisory or humid misery: move outdoor MUST earlier, fill midday with indoor blocks from the backup list - Cold / ice / gale: cancel exposed ridge; use [lower trail / indoor] instead - Indoor backup list (already check opening hours; ILLUSTRATIVE placeholders until I fill real names): - [Museum / gallery 1] - [Covered market / food hall 2] - [Library / civic building / mall walk 3] - [Spa / bath / cinema matinee 4] if that fits our bar - Shoulder-season / seasonal shutters: - [Ferry / garden / high trail / beach club]: reduced or closed [months / weekdays]; if our dates fall inside, replace with [alt] or confirm hours before pinning - Daylight: plan outdoor MUST before [earlier dusk clock]; do not assume long summer evenings - Layer with other briefs: - Opening hours / last entry for every indoor backup: [paste short lines] - Open-time buffers still apply after a rain swap: [paste short lines] - MUST outdoor pins that need pivots: [names] - Timed entries: prefer refundable / weather-flexible for outdoor MUSTS; do not stack prepaid outdoor slots on the same wet-risk morning MUST NEVER: - Do not build an all-outdoor day with no named rain pivot - Do not pin exposed ridge / plaza walks in the worst heat window - Do not schedule a shoulder-season ferry, garden, or high trail as if peak summer still applies - Do not leave a MUST outdoor stop without an indoor or covered backup that is open that day - Do not invent "weather permitting" without naming the swap OUTPUT I WANT: - Day-by-day with rain pivots and heat windows visible on outdoor hard stops - Indoor backups named (not vague "museums if rain") - Checklist: no orphan outdoor MUST; no midday heat hike; shoulder-season hours respected; opening hours checked for backups
One follow-up that catches postcard-weather failure early: ask the model to list every outdoor hard stop with its rain pivot and heat window. If a must cliff path has no indoor twin, or a plaza lunch sits at 13:30 in a heat week with no move-earlier rule, the brief did not stick. Send that stretch back by name. Demand a weather repair without regenerating the whole trip.
For shared constraint lines, lean on briefs you already trust: opening hours, open time, must-dos, timed entries, dealbreakers, pace, walking budget, arrival and recovery, multi-city bases, and generic AI itinerary.
How weather sits with hours, slack, musts, and tickets
Opening hours decide whether your rain pivot is legal. A covered market closed Mondays is useless as the wet-Monday swap. Lock calendar facts for every indoor backup with the opening hours guide before you trust the pivot list.
Open time keeps swaps reachable. A rain pivot across town with a twelve-minute fantasy still fails when trams slow in weather. Rank the backup near the morning base or keep a larger buffer. Pair with the open time guide.
Must-dos decide which outdoor stops deserve a named pivot at all. A nice viewpoint can drop in rain. A must cliff path needs a twin indoor block that still feels like a win. Use the must-dos guide so you do not spend pivot energy on stops you marked nice.
Timed entries harden weather risk. A prepaid outdoor slot in a storm becomes sunk-cost theater. Prefer flexible tickets for weather-exposed musts, or accept the indoor pivot before you buy. See the timed entries guide.
Walking budget and pace shrink in heat and rain. Wet stone and humid afternoons blow ceilings faster than dry mornings. Arrival and recovery days are worse: jet lag plus a heat wave is not the week to invent a midday ridge. Multi-city transfer mornings in rain eat the good outdoor slot; keep the backup near the new base.
Dealbreakers still cut categories. If boats are a hard no, do not list a ferry as a fair-weather should. Weather rules only pivot among stops you still allow.
Red flags in AI output
All-outdoor day, no pivot. Cliff, plaza, viewpoint, golden hour, zero indoor line. One wet morning collapses the plan.
Vague "weather permitting." No named museum, market, or covered walk. Soft language is not a backup.
Heat-of-day ridge or plaza. Exposed walking pinned 12:00-16:00 in a hot or humid week with no move-earlier rule.
Shoulder-season summer fantasy. Full ferry schedule, late dusk hike, garden tour in months when those run reduced or closed.
Indoor backup on a closed day. Rain pivot points at a Monday museum or a seasonal shutter. Opening hours were never checked.
Must outdoor with no twin. Your top hike has no indoor alternative; rain demotes the must into a lost day.
Prepaid outdoor stack on one wet-risk morning. Two timed outdoor entries back to back with no flexible cancel path.
Rules live only in chat. By revision three the model forgets the rain line. Paste the weather brief into every refine until pivots stay visible on outdoor hard stops.
Refine without restarting the whole trip
A wet or heat-wrecked day rarely needs a full regenerate. Regenerating often reprints the same outdoor stack with a new lunch name and the same orphan cliff path. Switch to an in-place refine.
Name the broken outdoor pin first. "Cliff Path is MUST outdoor; today is steady rain; swap morning to Museum A (open, last entry 16:00); keep evening show; do not add a new postcard hike." Specific beats "make it work if it rains."
Restate pivots and heat windows in the same message. Ask for rain-pivot and heat-window tags on every outdoor hard stop in the revised day. If tags disappear, the refine did not stick.
Check opening hours on the backup before you lock the swap. A closed indoor twin is not a pivot. Restate last entry and open-time buffers if the swap crosses town.
Restate must tiers if rain is eating your top sight while nices stay outdoors. Promote the must indoor block; drop a nice plaza. The refine guide has the keep/change/drop pattern. Add one weather line: "Keep locked pins [A, B]; swap wet outdoor MUST [C] to indoor backup [D]; move heat-sensitive [E] before 10:30; do not reintroduce all-outdoor Day [N]; tag outdoor hard stops with rain pivot and heat window."
When the forecast flips mid-trip, refine the next two days only. Do not regenerate the whole week and lose lodging, tickets, and ranks you already trust.
How this sits with the other briefs
This page is weather and season: rain pivots, heat caps, indoor backups, shoulder-season shutters so outdoor plans survive real skies. The others keep calendars, slack, ranks, and tickets from fighting those pivots.
Opening hours are closed days, last entry, kitchen clocks. Weather pivots still need legal doors for indoor backups.
Open time is slack between blocks. Weather swaps still need honest buffers when trams slow.
Must-dos rank which outdoor stops deserve a named pivot. Nices can drop in rain; musts need twins.
Timed entries place ticket slots. Prefer flexible tickets for weather-exposed musts.
Dealbreakers are hard nos. Weather rules pivot among stops you still allow.
Pace and walking budget shrink in heat and rain. Arrival and recovery keep first days light when jet lag meets bad weather. Multi-city bases put backups near the night you sleep.
Generic AI itinerary work is the fuller stack before draft one. Refine is the edit loop after a forecast still wrecks an outdoor day.
When a preference survey and Trip Project path helps
If you like prompt work and you will keep pasting the weather brief yourselves, a general assistant plus the rain-pivot and heat-window rules above is enough for many trips.
The structured path starts to matter when chat keeps printing all-outdoor days after you locked pivots. Or when rain backups, opening hours, must ranks, and timed tickets live in one messy thread and drift by revision four. Or when you want a researched day-by-day that holds season notes without re-teaching the model every session.
One option with that shape is Dople (dopletech.com). A short preference survey can capture weather-style constraints alongside pace, food, walking, and lodging, you compare trip options shaped by it, and you can buy a Trip Project: a researched day-by-day meant to hold those preferences across revisions so you are not stuck reprinting postcard-sunny stacks. Account and survey start are free. Full itineraries are paid. More detail: Dople vs ChatGPT and What is Dople?.
Public samples show ILLUSTRATIVE day-by-day shapes only. They are not live bookings and not free Trip Projects.
If the survey path sounds useful, sign up once when you are ready.
What are weather and season rules in an AI itinerary?
Weather and season rules tell the model how to pivot when rain, heat, cold, wind, or shoulder-season hours hit outdoor plans: named rain pivots, heat windows, indoor backups, and seasonal shutters. Without them, drafts assume postcard weather every morning and collapse on the first wet or extreme day.
How is this different from opening hours, open time, or must-dos?
Opening hours are whether the place is open that calendar day and until what clock. Open time is buffer minutes between blocks. Must-dos rank which stops own good half-days. Weather and season rules decide what to do when the sky or season makes an outdoor plan unsafe or pointless even if doors are open and ranks are clear. You usually need weather plus those sibling briefs.
What belongs in a weather and season brief?
Rain pivots for outdoor musts, heat or cold windows that shift hiking and plazas, an indoor backup list checked against opening hours, shoulder-season notes for reduced ferries or closed gardens, and must-never lines that forbid all-outdoor days with no backup. Paste opening hours, open time, must-dos, and timed entries rules alongside it.
Should I regenerate when rain wrecks the outdoor day?
No. Regenerating often reprints the same outdoor stack with a new lunch name. Refine in place: swap the wet morning for an indoor backup, move heat-sensitive pins earlier, restate pivots, and keep locked pins (see the refine guide).
Are Dople samples real bookings?
No. Samples are ILLUSTRATIVE examples of itinerary shape. Real Trip Projects are researched per traveler after the preference survey. More context: Personalized travel itineraries FAQ.