How is this different from weather and season rules?

Weather and season rules tell the model which outdoor plans to prefer or avoid by month and climate. Backup plans name the specific indoor or nearby alternate for a primary stop when that stop fails on the day. You usually need both: season rules reduce fragile days; backups rescue the afternoon when something still closes.

How to build backup plans into an AI itinerary

Q: What belongs in a backup-plans brief?

Named primary stops that need coverage, a named indoor swap and a nearby same-neighborhood swap for each, travel minutes between primary and backup, swap-versus-cancel rules, and short links to weather-season, rest-day, open-time, must-do, timed-entry, walking, long-transit, and arrival briefs.

Q: Should I regenerate when a primary closes and the afternoon goes blank?

No. Regenerating often invents a denser day elsewhere and drops your named swaps. Refine in place: name the closed primary, attach the indoor or nearby backup by name, restate swap-versus-cancel, keep rest days and transit pins.

Give AI indoor and nearby swaps so a closure, strike, or rain day does not strand the whole schedule.

Purple lupine flower spike fading to pale buds against a black background

Day 4 looked solid until the museum texted a strike closure at 09:10. The draft had one outdoor garden for the morning and that museum for the afternoon. No indoor alternate. No nearby gallery in the same neighborhood. No rule for when to swap versus cancel. By noon the group was walking in light rain past closed ticket windows, scrolling for "things to do indoors" while the rest of the week still assumed that afternoon had been spent. The model had shipped a single-point plan.

This page is the backup-plans pattern. Named alternate activities tied to primary stops: indoor swaps, nearby same-neighborhood swaps, and a clear call for when to swap versus cancel the day. So a closure, strike, or rain day does not strand the whole schedule. Not weather and season preference rules alone, not mid-trip rest days, not within-day open-time buffers, not must-do ranking, not day-trips-from-a-base, not long transit days. Those have their own guides. Here you stop AI from listing one museum with no indoor swap. 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 backup pins can beat paste-and-hope.

What backup plans mean (and what they are not)

A backup plan is a named alternate tied to a primary stop. Indoor when the primary is outdoor or weather-fragile. Nearby and same-neighborhood when you do not want a fresh transit across town after a closure. Plus a swap-versus-cancel rule so the model knows when to pivot the afternoon and when to clear the day instead of inventing a denser stack elsewhere.

It is not weather and season rule-setting alone. Season rules tell the model which outdoor plans to prefer or avoid by month and climate. Backups name the specific indoor gallery or covered market you will use when the outdoor garden or ferry view fails on the day. Pair with the weather and season guide to reduce fragile days; use this page so a remaining closure still has somewhere to go.

It is not a mid-trip rest day. Rest days are intentional light squares for laundry, sleep-in, and one neighborhood stroll with no tickets. A rain backup that sends you to a named museum is still a packed afternoon with a swap, not a rest day. Use the rest days guide when every packed day burns people out. Use this page when a primary fails and the draft has no alternate.

It is not within-day open time. Open time is slack between blocks so a late tram does not collapse lunch. Backups are replacement activities with names and neighborhoods. Pair with the open time guide for buffers; use this page for the indoor or nearby swap itself.

It is not must-do ranking. Must ranks decide which stops keep a slot when the week is full. Backups decide what replaces a fragile primary when that primary cannot run. Soft stops should not overwrite a must when you swap; pair with the must-dos guide.

It is not day-trips-from-a-base or long transit days. Day trips lock leave-and-return from one overnight bed. Long transit days protect multi-hour intercity moves from attraction stuffing. A backup that sits forty minutes away by train is often a bad swap after a morning closure; keep backups nearby and leave hop protection to the day trips from a base guide and the long transit days guide.

If you only say "have indoor options if it rains," models often still print one outdoor primary and a vague "museums" line. If you say "PRIMARY: Riverside Garden (outdoor); BACKUP INDOOR: City History Museum (same district, 12 minutes walk); BACKUP NEARBY: Covered Market Hall food + indoor stalls; SWAP if garden closed or sustained rain; CANCEL afternoon only if both backups closed and energy is shot; MUST NEVER leave a primary with no named indoor or nearby swap," the draft has fewer ways to strand you.

Why AI ships single-point plans

Training data rewards tidy day shapes. One morning stop, one afternoon stop, dinner near the hotel. Closures and rain barely appear as failure modes. The model rarely invents a same-neighborhood alternate unless you demand named backups.

Soft language makes it worse. "Indoor alternatives if needed" without a named museum invites a noon scramble. "Something nearby" without travel minutes often becomes a gallery across town that burns the walking budget. Weather preference lines without stop-level swaps still leave a blank square when the outdoor must closes.

Regenerate loops often invent denser days elsewhere and drop the fragile primary entirely. New cafe names, same single-point risk on the next outdoor afternoon. Without a backup brief pasted into every refine, named swaps vanish by revision three.

A pasteable backup-plans brief

Paste this as the backup source of truth before you ask for morning-afternoon-evening detail on every night. Fill brackets with real day numbers, primary names, indoor and nearby swaps, and travel minutes. Attach weather-season, rest-day, open-time, must-do, timed-entry, walking, long-transit, day-trip, and arrival lines you already trust. Ask for a day-by-day that shows PRIMARY and BACKUP on fragile days and never leaves a single-point afternoon.

Trip: [cities / region], [N] nights, [month/season], travelers: [N]

WEATHER / SEASON (already locked; do not invent new climate rules here):
- [paste short weather-season lines: outdoor vs indoor preference by month]

BACKUP PLANS (named alternates tied to fragile primaries):
- Day [4] PRIMARY: [Riverside Garden / outdoor viewpoint / ferry deck]
 BACKUP INDOOR: [City History Museum], same neighborhood, ~[12] min walk
 BACKUP NEARBY: [Covered Market Hall], ~[8] min walk, indoor stalls + seating
 Travel between primary and backups: under [15] minutes walk preferred; no fresh cross-town transit after a closure
 SWAP WHEN: [garden closed / strike / sustained rain / timed ticket sold out]
 CANCEL AFTERNOON WHEN: both backups closed AND energy is shot; do not invent a denser stack elsewhere
 Label PRIMARY + BACKUP on the day-by-day for this square

- Day [6] PRIMARY: [timed gallery ticket 14:00]
 BACKUP INDOOR: [second museum in same district with walk-up or later slot]
 BACKUP NEARBY: [bookstore cafe + short covered arcade walk]
 SWAP WHEN: ticket window closed, entry delayed past [N] minutes, or building inaccessible
 CANCEL: only if backups fail; keep evening must intact

MUST NEVER ON BACKUP HANDLING:
- Do not leave a fragile primary with no named indoor or nearby swap
- Do not use a backup that needs a long transit after a morning closure
- Do not write vague "something indoors" without a place name and neighborhood
- Do not let a soft backup overwrite a locked must-do on another day
- Do not count a swap afternoon as a mid-trip rest day
- Do not delete named backups in refine loops to make room for new must-sees

LAYER WITH OTHER BRIEFS (paste short lines):
- Weather / season preference rules: [paste]
- Rest days (separate from swap afternoons): [paste]
- Open-time buffers on packed sightseeing days: [paste]
- Must-do ranks (backups must not steal must slots): [paste]
- Timed entries + opening hours + weather delay notes: [paste]
- Walking ceiling for primary vs backup walk: [paste]
- Long transit days (do not park a backup on a hop day): [paste]
- Day-trip-from-base return-by (backups stay near the day's base area): [paste]

OUTPUT I WANT:
- Day-by-day with PRIMARY + BACKUP lines on fragile days
- Indoor and nearby swaps named with travel minutes
- Swap-versus-cancel rule visible
- Checklist: no single-point fragile afternoons; backups nearby; musts and rest/transit pins untouched

One follow-up that catches single-point days early: ask the model to list every fragile PRIMARY with its indoor backup, nearby backup, travel minutes, and swap-versus-cancel line. If a day shows one outdoor stop and no named alternate, or a backup sits across town, or cancel rules are missing, the brief did not stick. Send that day back by name. Demand a backup repair without regenerating the whole trip.

For shared constraint lines, lean on briefs you already trust: weather and season, rest days, long transit days, open time, must-dos, timed entries, walking budget, day trips from a base, opening hours, and generic AI itinerary.

How backup plans sit with weather-season, rest days, open time, must-dos, timed entries, walking, and long transit

Weather and season rules reduce how often outdoor primaries land on wet months. Backup plans rescue the afternoon when something still closes. Lock season lines with the weather and season guide, then pin named indoor and nearby swaps here.

Rest days clear mid-trip squares for laundry and sleep-in. A swap afternoon is still an activity day with a different primary. Do not let the model rename a failed outdoor day as your rest day and then pack every other square solid. Keep rest pins with the rest days guide.

Open time keeps packed days reachable when a tram runs late. Backups replace a failed stop. Pair buffers from the open time guide with named swaps so you are not inventing a new museum across town in the leftover slack.

Must-dos keep soft stops from eating scarce slots. When you swap, the backup should not steal a must that still lacks a day. Pair with the must-dos guide. Timed entries need a backup when the window closes or the building is inaccessible; keep weather-delay notes with timed entries and opening hours.

Walking budget changes when the backup adds a longer walk than the primary. Paste a ceiling from the walking budget guide. Long transit days stay light or empty; do not park a "backup museum" on a five-hour train day. Protect hops with the long transit days guide.

A fragile week that still has somewhere to go

ILLUSTRATIVE sketch only, not a real booking. Eight nights, one base. Days 1 and 2 soft on arrival recovery. Day 3 packed with a timed entry and open-time buffers. Day 4 PRIMARY: riverside garden (outdoor); BACKUP INDOOR: city history museum twelve minutes walk in the same district; BACKUP NEARBY: covered market hall; SWAP on closure, strike, or sustained rain; CANCEL afternoon only if both backups fail. Day 5 day trip with return-by 20:00 and its own indoor cafe backup near the station if the outdoor site floods. Day 6 packed must-do indoors. Day 7 mid-trip rest: laundry, sleep-in, one stroll, no tickets. Day 8 light packing. When Day 4's garden closes at 09:10, the group walks to the named museum instead of scrolling blank. Boring on a spreadsheet; usable in rain.

Compare the common AI default: same garden afternoon, plus "museums if weather is bad" with no place name, plus a regenerate that invents a ferry across town. Walking budget blows. The difference is a backup brief that survives refine loops.

Ask the model to print PRIMARY and BACKUP lines on fragile days before filling restaurant detail. If fragile days still show one stop and no named alternate, clear those days by name before you negotiate dinners.

Red flags in AI output

Single outdoor afternoon with no indoor swap. Garden or viewpoint stands alone; rain or closure leaves a blank square.

Vague "something indoors." No place name, no neighborhood, no travel minutes from the primary.

Backup across town. Alternate needs a long transit after a morning closure; walking budget and energy both fail.

Swap that steals a must. Soft gallery eats the only free slot while a locked must still lacks a day.

Failed day renamed as rest. Model counts the blank afternoon as your mid-trip empty day and packs every other square solid.

Backup parked on a transit day. Indoor "filler" lands on a five-hour train day that should stay light.

Rules live only in chat. By revision three every named swap disappears. Paste the backup brief into every refine until PRIMARY and BACKUP lines stay visible.

Refine without restarting the whole trip

A blank afternoon after a closure rarely needs a full regenerate. Regenerating often invents denser days elsewhere, drops your named swaps, and reshuffles musts. Switch to an in-place refine.

Name the broken square first. "Day 4 PRIMARY Riverside Garden is closed; use BACKUP INDOOR City History Museum (same district, 12 min walk); keep Covered Market Hall as secondary nearby; SWAP not CANCEL; keep evening must and Day 7 rest intact." Specific beats "add indoor options."

Restate indoor and nearby names, travel minutes, and swap-versus-cancel in the same message. Ask for PRIMARY and BACKUP lines on the revised day. If backups disappear, the refine did not stick. Recheck must ranks if a soft swap ate a must slot. Keep rest days and long transit pins untouched.

The refine guide has the keep/change/drop pattern. Add one backup line: "Keep PRIMARY/BACKUP pairs on Days [4, 6]; named indoor and nearby swaps with travel minutes; swap-versus-cancel intact; do not leave single-point fragile afternoons; do not count a swap day as rest; do not park backups on transit days." When only one primary failed, refine that day and the neighbors. Do not regenerate the whole week.

How this sits with the other briefs

This page is the backup-plans pattern: named indoor and nearby alternates tied to primary stops so a closure, strike, or rain day does not strand the schedule. Sibling briefs keep season rules, rest, slack, ranks, tickets, walking, hops, and outbound days from fighting those swaps.

Weather and season sets outdoor versus indoor preference by climate. Backups name the stop-level alternate when something still fails. Rest days clear mid-trip laundry and sleep-in squares. Swap afternoons are not rest days.

Open time is slack between blocks on packed days. Backups are replacement activities with names. Must-dos keep soft swaps from stealing must slots. Timed entries and opening hours need a backup when a window closes.

Walking budget caps distance when the backup walk exceeds the primary. Long transit days stay light; do not park filler museums on hop days. Day trips from a base keep leave-and-return days; backups for those days should stay near the day's area, not invent a second overnight.

Generic AI itinerary work is the fuller stack before draft one. Refine is the edit loop after a primary closed and the afternoon went blank.

When a preference survey and Trip Project path helps

If you like prompt work and you will keep pasting the backup brief yourselves, a general assistant plus the primary/backup pins above is enough for many trips.

The structured path starts to matter when chat keeps shipping single-point outdoor afternoons after you locked named indoor swaps. Or when PRIMARY and BACKUP lines, weather-season rules, rest-day pins, and walking ceilings drift by revision four. Or when you want a researched day-by-day that holds nearby alternates without re-teaching the model every session.

One option with that shape is Dople (dopletech.com). A short preference survey can capture backup-plan 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 with one museum and no indoor swap on a rain day. 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 backup plans in an AI itinerary?

Backup plans are named alternate activities tied to primary stops: indoor swaps, nearby same-neighborhood swaps, and a clear rule for when to swap versus cancel the day. Without that pin, drafts often list one museum or outdoor garden with no alternate, and a closure, strike, or rain day leaves a blank afternoon.

How is this different from weather-season rules, rest days, or open time?

Weather and season rules set outdoor versus indoor preference by climate. Rest days are intentional light mid-trip days for laundry and sleep-in. Open time is slack between blocks on packed days. Backup plans name the indoor or nearby alternate for a fragile primary when that primary fails. You usually need backups plus those sibling briefs.

What belongs in a backup-plans brief?

Named primaries that need coverage, a named indoor swap and a nearby same-neighborhood swap for each, travel minutes, swap-versus-cancel rules, and short links to weather and season, rest days, open time, must-dos, and long transit days alongside it.

Should I regenerate when a primary closes and the afternoon goes blank?

No. Regenerating often invents denser days elsewhere and drops named swaps. Refine in place: attach the indoor or nearby backup by name, restate swap-versus-cancel, keep rest days and transit 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.