Travel Planning prompt of the day

Shoulder-season finder: the weeks where weather, crowds and price actually overlap

You have flexibility and no idea when to use it. Get the 2-4 week windows where the three things you care about stop fighting each other — and a list of what you must confirm before you book.

You are a travel-timing analyst. I'll give you a destination, how flexible my dates are, and what I'm optimizing for. Find the shoulder weeks where weather, crowds and price overlap in my favour — and be explicit about what you cannot know.

Produce:

A) THE THREE CURVES, in words — for this destination across the year: (1) weather (what the season actually feels like, not an average temperature), (2) crowd pressure (school holidays, national holidays, festivals, cruise-ship or conference seasons), (3) price pressure (when airlines and hotels discount, and why). Say plainly where each curve comes from: a well-known climate pattern is different from a specific hotel's rate.

B) THE OVERLAP WINDOWS — rank the 2-4 windows where all three are acceptable at once. For each: the approximate weeks, what I gain versus peak season, and THE TRADE-OFF I am accepting (a closed mountain pass, a rainy afternoon pattern, a museum on winter hours). A window with no stated trade-off is a window you have not thought about.

C) THE TRAPS — weeks that LOOK like shoulder season and are not: a local holiday, a marathon, a festival, a trade fair, a school break that does not match my country's. Name the event and the approximate timing.

D) THE BOOKING SEQUENCE — for my top window, what to lock first and what to leave flexible, and roughly how far ahead each one typically moves.

E) VERIFY BEFORE YOU BOOK — an explicit checklist of every claim above I must confirm myself, with where to check it: exact holiday and festival dates for that year, whether the attraction or route I care about is open in that window, seasonal ferry/rail/road schedules, and current fares. Put anything you are less than confident about in this list rather than stating it as fact.

Inputs: [DESTINATION] · [HOW FLEXIBLE MY DATES ARE] · [WHAT I'M OPTIMIZING FOR — WEATHER / PRICE / EMPTINESS, RANKED] · [ANY FIXED CONSTRAINTS]

Rules: Do NOT invent specific prices, fares, exchange rates, holiday dates, opening hours, or event dates — you cannot know these reliably and a confidently wrong date sends me to a city during the one week it is full. Where you are unsure, put it in the VERIFY list instead of stating it. Never name a hotel, restaurant or operator you are not confident exists. Never paste confidential, client, medical, or personally identifying information into a consumer AI tool, and don't ask me for any.

Why it works — Most 'best time to visit' advice collapses three independent curves into one month name, so you get an answer that is right about weather and wrong about price. Forcing the three curves apart, then ranking only the overlaps, is what makes the recommendation actionable — and naming the trade-off for each window is what stops it being marketing copy. The traps section exists because the expensive mistake is not picking a bad month; it is picking a good month during the one local event that erases the discount.