💬 Multi City Layover Pick
Compares two or three multi-city layover options from flight times and connection rules you provide, and ranks them without inventing delays or airline policies.
The prompt
You help a US traveler pick among multi-city or layover itineraries. Rank options using only the flight times, airports and rules I paste. Do not invent minimum connection times, delays, visa rules or airline policies.
Trip goal: {{trip_goal}}
Party and constraints: {{party}}
Option A (airports, local times, layover length, bags if known):
{{option_a}}
Option B:
{{option_b}}
Optional Option C (or "none"):
{{option_c}}
Connection / visa notes I already confirmed:
{{known_rules}}
Write:
1. A comparison table: Option | Total travel time (if I gave enough clocks) | Longest layover | Same-day risk notes | Bag recheck stated? | Fit to constraints | Rank
Use "—" when a value was not provided. Do not guess clocks.
2. Ranked recommendation with 3 bullets explaining the winner using only my numbers and known_rules.
3. A "tighten or avoid" list: layovers that look short vs any minimum connection I stated, overnight risks I mentioned, and airport changes that require leaving security if I said so.
4. Up to 4 clarifying questions (visa, terminal change, bag through-check) for anything still MISSING.
Rules:
- No live delay APIs. No invented MCT. If I did not give a minimum connection, write [ADD_MCT] rather than a number.
- Not a booking agent; do not claim seats or fares.
Variables
Replace each {{name}} before you send the prompt.
| Variable | What to put in | Example |
|---|---|---|
{{trip_goal}} | Where you are going and why timing matters. | DEN → SLC → LAS over 4 days, want daylight in Zion area without a brutal red-eye |
{{party}} | Who is traveling and hard constraints. | 2 adults, 1 carry-on each, no checked bag, avoid under 60 min connections |
{{option_a}} | First itinerary with local times and layover length. | DEN 08:10 → SLC 09:35; 3h20 layover; SLC 12:55 → LAS 13:50. Bags through-checked per airline email. |
{{option_b}} | Second itinerary details. | DEN 06:00 → LAS 07:15 direct, then separate LAS → next city next morning (not applicable — rewrite if needed): DEN 14:00 → PHX 15:05; 1h10 layover; PHX 16:15 → LAS 17:20. |
{{option_c}} | Optional third option or none. | none |
{{known_rules}} | Connection or visa facts you already confirmed. | Self-imposed minimum connection 60 minutes. No international segment. Both options domestic US. |
Example
trip_goal: DEN to LAS with optional SLC stop, prefer daylight party: 2 adults, carry-on only, avoid under 60 min connections option_a: DEN 08:10→SLC 09:35; 3h20; SLC 12:55→LAS 13:50; bags through-checked option_b: DEN 14:00→PHX 15:05; 1h10; PHX 16:15→LAS 17:20 option_c: none known_rules: Self-imposed MCT 60 min; domestic US only
### 1. Comparison Table | Option | Total travel time (if I gave enough clocks) | Longest layover | Same-day risk notes | Bag recheck stated? | Fit to constraints | Rank | | :--- | :--- | :--- | :--- | :--- | :--- | :--- | | **Option A** | 5h 40m (clock difference DEN to LAS)* | 3h 20m (SLC) | Low connection risk; 3h 20m layover is well above your 60m threshold | No (through-checked per airline email) | High (08:10 departure avoids red-eye; arrives 13:50 for Zion daylight; connection > 60m) | 1 | | **Option B** | 3h 20m (clock difference DEN to LAS)* | 1h 10m (PHX) | Moderate connection risk; 1h 10m (70m) is only 10 minutes above your 60m minimum | — | Moderate (avoids red-eye, but 17:20 arrival cuts into daylight; connection is tight to minimum) | 2 | *\*Note: Clocks reflect raw differences between local departure and arrival times; exact elapsed travel time cannot be calculated without assuming unstated time zone offsets.* --- ### 2. Ranked Recommendation **Winner: Option A (Rank 1)** * **Maximizes Daylight for Zion:** Option A arrives in Las Vegas at 13:50 local time, giving you 3 hours and 30 minutes more afternoon daylight compared to Option B’s 17:20 arrival. * **Safer Connection Buffer:** The 3h 20m connection in SLC easily exceeds your self-imposed 60-minute minimum, whereas Option B's 1h 10m layover sits within 10 minutes of your cutoff. * **Meets Schedule Comfort:** Departing DEN at 08:10 fulfills the requirement of avoiding a brutal early red-eye while still reaching LAS early enough in the day. --- ### 3. Tighten or Avoid List * **Short Connection Warning:** Option B’s PHX layover is 1h 10m (70 minutes), which leaves only a 10-minute margin above your 60-minute minimum rule. * **Overnight Risks:** None identified (neither itinerary contains an…
Real, unedited output from a test run on Nov 4, 2026 · Gemini · model gemini-flash-latest.
Full output · Gemini (gemini-flash-latest)
### 1. Comparison Table | Option | Total travel time (if I gave enough clocks) | Longest layover | Same-day risk notes | Bag recheck stated? | Fit to constraints | Rank | | :--- | :--- | :--- | :--- | :--- | :--- | :--- | | **Option A** | 5h 40m (clock difference DEN to LAS)* | 3h 20m (SLC) | Low connection risk; 3h 20m layover is well above your 60m threshold | No (through-checked per airline email) | High (08:10 departure avoids red-eye; arrives 13:50 for Zion daylight; connection > 60m) | 1 | | **Option B** | 3h 20m (clock difference DEN to LAS)* | 1h 10m (PHX) | Moderate connection risk; 1h 10m (70m) is only 10 minutes above your 60m minimum | — | Moderate (avoids red-eye, but 17:20 arrival cuts into daylight; connection is tight to minimum) | 2 | *\*Note: Clocks reflect raw differences between local departure and arrival times; exact elapsed travel time cannot be calculated without assuming unstated time zone offsets.* --- ### 2. Ranked Recommendation **Winner: Option A (Rank 1)** * **Maximizes Daylight for Zion:** Option A arrives in Las Vegas at 13:50 local time, giving you 3 hours and 30 minutes more afternoon daylight compared to Option B’s 17:20 arrival. * **Safer Connection Buffer:** The 3h 20m connection in SLC easily exceeds your self-imposed 60-minute minimum, whereas Option B's 1h 10m layover sits within 10 minutes of your cutoff. * **Meets Schedule Comfort:** Departing DEN at 08:10 fulfills the requirement of avoiding a brutal early red-eye while still reaching LAS early enough in the day. --- ### 3. Tighten or Avoid List * **Short Connection Warning:** Option B’s PHX layover is 1h 10m (70 minutes), which leaves only a 10-minute margin above your 60-minute minimum rule. * **Overnight Risks:** None identified (neither itinerary contains an overnight layover). * **Security Exit / Airport Changes:** None stated in your inputs. --- ### 4. Clarifying Questions 1. **Multi-day Stopover vs. Layover:** Your trip goal mentions "DEN → SLC → LAS over 4 days," but Option A shows a same-day 3h 20m layover in SLC. Did you intend to book a multi-day stopover in SLC, or is SLC purely a connection city? 2. **Option B Bag Handling:** Are both legs of Option B on a single ticket, or would you need to retrieve carry-ons if forced to gate-check? 3. **Terminal Layouts / Re-clearing Security:** Do either the SLC or PHX connections require changing terminals outside the secure area? 4. **Time Zone Offsets:** Would you like elapsed flight durations calculated once local time zones (MDT vs. MST vs. PDT) are specified for your travel dates?
Full output · DeepSeek (deepseek-flash)
Option B is ambiguous as pasted, so I did **not** force it into one total travel time. I compare its visible components and treat it as not fitting the stated DEN→SLC→LAS path unless clarified. ### 1. Comparison table | Option | Total travel time | Longest layover | Same-day risk notes | Bag recheck stated? | Fit to constraints | Rank | |---|---:|---|---|---|---|---| | **A** | **6h40** elapsed from DEN 08:10 to LAS 13:50 local, including layover | **3h20 in SLC** | SLC layover is **2h20 above** your 60-min self-minimum. No airport change stated. Arrives LAS 13:50 local; no red-eye shown. | **Yes** — through-checked per airline email. You have no checked bags anyway. | Fits DEN→SLC→LAS; connection >60 min; no checked bag issue. | **1** | | **B** | **— as one coherent itinerary.** Visible clocks: DEN→LAS direct = **2h15**; DEN→PHX→LAS = **4h20** | **1h10 in PHX** on the DEN→PHX→LAS component; direct DEN→LAS has no layover; “next morning” separate leg has no clocks | Not a single DEN→SLC→LAS path as pasted. Direct DEN 06:00→LAS 07:15 skips SLC. DEN 14:00→PHX→LAS has a **1h10 PHX connection**, which is only **10 min above** your 60-min minimum, but also skips SLC. The “LAS → next city next morning” text is marked not applicable but is an overnight/next-day risk if actually used. | **— / not stated** | Does **not fit** DEN→SLC→LAS as pasted. If the intended B is only DEN→PHX→LAS, it meets your 60-min rule by 10 min but omits SLC. | **2 — verify** | ### 2. Ranked recommendation - **Winner: Option A.** It is the only option as pasted that actually follows **DEN→SLC→LAS**. - Its SLC connection is **3h20**, safely above your self-imposed **60-minute** minimum, and arrives LAS at **13:50 local**, with no red-eye shown. - Option B is not usable as a single DEN→SLC→LAS itinerary as pasted: the direct DEN→LAS leg skips SLC, and the DEN→PHX→LAS leg also skips SLC and has only a **1h10** PHX connection. ### 3. Tighten or avoid - **A / SLC 3h20:** Not tight against your 60-min rule. No airport change or security-exit requirement stated. - **B / PHX 1h10:** Above your 60-min minimum, but only by **10 minutes**. Flag as the tighter connection if B is reconsidered. - **B / “next morning” separate LAS leg:** Overnight/next-day risk is mentioned, but it is marked “not applicable.” No clocks provided; do not rely on it without clarification. - **Airport changes:** None stated for A or B. No terminal-change or bag-recheck details are provided for B. ### 4. Clarifying questions 1. For **Option B**, which is intended: the **DEN 06:00→LAS 07:15 direct**, the **DEN 14:00→PHX→LAS** itinerary, or both as one plan? 2. Is the “separate LAS → next city next morning” truly **not applicable**, or is it part of the trip? 3. For Option B’s PHX connection, is there any **terminal change** or **bag through-check** stated? A states through-check; B does not. 4. Do you require **SLC to be included** exactly as in Option A? If yes, Option B as pasted does not qualify.
How to use it
Works in ChatGPT, Claude, Gemini and DeepSeek. Paste two or three layover options with clocks you already have and get a ranked comparison — without invented delays or airline policy guesses.
Planning aid only; not a ticket purchase. Missing minimum connection times stay marked, not filled in.
Test log
| Date (UTC) | Tool | Model | Run | Result | Checks | Tokens in / out |
|---|---|---|---|---|---|---|
| Nov 4, 2026 | Gemini | gemini-flash-latest | Test | Passed | 3/3
| 0 / 0 |
| Nov 4, 2026 | DeepSeek | deepseek-flash | Test | Passed | 3/3
| 476 / 9,997 |
Each row is a real run recorded by our test runner. For each tool, the latest test run decides whether it appears under “Tested on”. Baseline runs do the same task with no skill installed and never count.