Somewhere Warm' Is a Wish, Not a Plan: Scoring Your Shortlist

WEEK 93 :: POST 3 :: CLAUDE

Directions Given To The A.I. This Week+

Instructions Given to each A.I. — Please provide 3 prompt variations that share this objective:

Each A.I. also received two static attachments: the blog post template (structure) and the authoring instructions (voice and standards). The text below is the week-specific assignment as sent — reflowed for the web; wording unchanged.

I'd like you to write this week's Ketelsen.ai post. Two files are attached: the blog post template (the structure to follow) and the authoring instructions (context, voice, and standards). Please read both before you begin, then produce the complete post in a single response.

This week's theme: "Where Should We Go?" — Destination Intelligence and Shortlisting.

This is Week 2 of an eight-week series on planning a vacation with AI. Last week the reader established their real constraints — a validated budget ceiling and a constraint profile covering money, dates, travellers, and trip purpose. This week they use it.

The job is to turn a fuzzy wish — "somewhere warm, not too touristy" — into a scored shortlist of three to five real destinations, each evaluated against the Week 1 profile rather than against vibes. This is the week that replaces "where do you want to go?" with "where actually fits?"

The three prompts should help a reader evaluate candidates on:

  • Cost of living on the ground — not just flights and lodging, but what a day actually costs once you're there. Two destinations with identical airfare can differ enormously on daily spend.
  • Seasonality and weather windows — whether the reader's available dates are good, tolerable, or actively wrong for each candidate.
  • Crowd calendars — school holidays, festivals, and local peak seasons that turn a good destination into a bad week.
  • Safety and visa friction — entry requirements, processing times, and anything that could quietly disqualify a destination late.
  • Flight accessibility from the reader's home airport — a destination three connections away is a different trip from a nonstop, regardless of ticket price.

The output a reader should walk away with is a ranked shortlist with a composite fit score and the reasoning behind it — something they can defend to a travelling companion, not just a gut preference.

A note on the strongest version of this week: at the advanced end, this is a destination dossier matrix — one row per candidate, columns for cost index, weather risk, crowd level for the specific travel dates, entry requirements, and a composite score. That structure is worth reaching for.

Series dependency chain, for the Metadata block: Week 2 consumes Week 1's validated budget ceiling and constraint profile — the shortlist is scored against them, and any prompt that ignores the reader's established constraints has missed the point of the series. Week 2 produces the chosen destination (or final shortlist), which feeds Week 3 (airfare strategy), Week 4 (lodging), and Week 5 (itinerary). It is the hinge of the whole series: everything downstream assumes it.

Because readers may arrive at this post without having read Week 1, the prompts should work for someone who has their constraints roughly in mind, while making clear that the reader gets far more out of them with a real constraint profile in hand.

Three difficulty tiers as always — Beginner, Intermediate, Advanced — each a genuinely different approach to the same problem, not the same prompt at three lengths.


A note on supplied figures. Anything marked `[SUPPLIED — use as given]` above came from Ketelsen.ai's own research brief. Use it freely — you are not fabricating by repeating it, and you will not be marked down for leaving it uncited. Do not attach an invented source to it. Presenting it as a sensible planning rule of thumb rather than a precise measured statistic is the right treatment. (No supplied figures this week — the constraint stands for the series.)

Week 2 :: Vacation Planning Series

"Somewhere warm, not too touristy" is a wish, not a plan — and it's where most vacations quietly go wrong. This week turns that fuzzy wish into a scored shortlist of real destinations, each one checked against the budget and dates you locked down in Week 1 instead of against a pretty photo. Three prompts take you there at three depths: a plain-English shortlist you can run cold, a weighted version that ranks candidates on the factors you actually care about, and a full destination dossier matrix you can defend to whoever you're travelling with. By the end you'll be able to answer "where should we go?" with a reason, not a shrug.

01
BeginnerPrompt 1 of 3

The Fuzzy-Wish Shortlist

Turn "somewhere warm and cheap" into five real, defensible destinations.

Most people start a vacation with a feeling: warm, cheap, somewhere they haven't been. Feelings don't book flights. The gap between "somewhere warm and not too touristy" and an actual place with an actual price is where good intentions turn into three hours of open browser tabs and a vague sense of defeat. This first prompt closes that gap with almost no effort. You describe the trip in the same plain words you'd use with a friend, and you get back a handful of real destinations — each with a reason it fits and one honest reason it might not. No scoring, no setup, no jargon. Just a shortlist you can actually react to.

Why this matters now

Right now, the reflex for "where should we go?" is to ask the internet and drown. Search engines sell you inspiration; they don't weigh it against your budget or your dates. This prompt flips the order — it starts from your constraints and works toward places, instead of starting from places and hoping they fit. For anyone staring at a blank calendar with money set aside and no idea where to point it, that first honest shortlist is the difference between planning and stalling.

The prompt — copy and paste this

I'm planning a vacation and I want you to act as a practical travel-planning assistant, not a travel brochure. Here's my situation: [describe your trip in plain words — roughly how much you can spend in total, your rough dates or month, how many people and who they are, and the kind of trip you want, e.g. 'somewhere warm and relaxed, not too touristy']. Suggest 3 to 5 real destinations that actually fit what I described. For each one, give me: a one-line reason it fits my budget and dates, roughly what a normal day there costs once I've arrived (cheap / moderate / expensive, and why), and one honest thing that might not work for me. Don't rank them yet — just give me a shortlist I can react to. If any detail I gave is too vague to work with, tell me what you'd need to know.

How the AI reads this prompt

“act as a practical travel-planning assistant, not a travel brochure”
This hands the model a job and, just as important, tells it what job it is not doing. Without the role, the model drifts toward the breezy, everything-is-amazing register of destination marketing — which is exactly the voice that ignores your budget. The "not a travel brochure" clause is a negative instruction, a guardrail against a known failure mode, and it earns its place because inspirational travel content is such a strong default. The transferable principle: when a model has an obvious bad default for your task, naming the thing you don't want is often more powerful than describing the thing you do.
“Here's my situation: [describe your trip in plain words...]”
This is the whole input, and the prompt deliberately asks for it in plain language rather than a rigid form. Leave it thin and the shortlist is generic; fill it honestly — money, dates, who's coming, the vibe — and the model has enough to actually filter. Vague inputs are the single biggest cause of disappointing AI output, and travel is no exception. The principle: the quality of a prompt's output is capped by the specificity of what you put into it, so treat the input as the work, not the prompt.
“Suggest 3 to 5 real destinations that actually fit what I described”
Three moves in one line. The number bounds the answer so you get a shortlist, not an overwhelming wall; "real" blocks the model from inventing plausible-sounding places or resorts; "actually fit" ties the suggestions back to your stated constraints instead of its greatest-hits list. Drop the count and you may get twenty options or two. Drop "fit" and you get famous places, not appropriate ones. The principle: constrain quantity and tie output explicitly to your inputs, or the model optimises for coverage over relevance.
“roughly what a normal day there costs once I've arrived (cheap / moderate / expensive, and why)”
This is the theme of the whole week compressed into a clause. It pulls attention away from flights and lodging — the numbers everyone fixates on — and onto daily spend, which is where two similar-looking trips actually diverge. Asking for "and why" forces a reason rather than a bare label, so you can tell whether "expensive" means restaurants or just hotels. Without it, the model quietly optimises for the wrong cost. The principle: name the specific dimension you care about, or the model will answer the easy, obvious version of your question.
“one honest thing that might not work for me”
This deliberately asks the model to argue against each suggestion. Left out, an AI will happily present five upsides and no downsides, because agreeableness is its default posture. Forcing a single honest caution per option is what lets you eliminate candidates quickly — the caution is often more decisive than the pitch. The principle: models lean positive, so if you want balance you have to explicitly request the downside; a prompt that only asks for pros will only ever give you pros.
“Don't rank them yet — just give me a shortlist I can react to”
This controls scope on purpose. At the shortlist stage, a premature ranking makes the model over-commit to reasoning it doesn't yet have the information to support, and it nudges you toward its top pick before you've formed your own read. Holding the ranking back keeps this a divergent, options-generating step. The principle: match the model's task to the stage you're at — generate before you converge, and don't let a tool collapse your options before you've seen them.
“If any detail I gave is too vague to work with, tell me what you'd need to know”
This builds in a self-correction valve. Rather than silently guessing when your input is thin — and burying the guess inside a confident answer — the model surfaces the gap so you can fill it. Without this line, vagueness gets papered over with assumptions you never see. The principle: invite the model to flag its own uncertainty, and you convert hidden guesses into visible questions you can actually answer.

Practical examples from different industries

A working couple with one week off in late October and a mid-range international budget wants warm, walkable, and not overrun. They paste their situation in and the AI returns a shortlist — say southern Portugal, a stretch of coastal Mexico, and a Greek island still in shoulder season — each with a plain note on why the dates work, what a normal day's spending feels like, and one caution (that Greek island in late October may have half its restaurants already shuttered for winter). They now have three concrete places to talk over at dinner instead of a vague argument about "somewhere nice." The caution line does the real work here: it kills a tempting-but-wrong option before they've spent a cent.

A family of four can only travel during a fixed spring-break week and needs somewhere that keeps two kids happy without wrecking the budget. They add "two children, ages 7 and 10, need things for them to do" to the situation line. The AI shortlists destinations where the weather is reliable that specific week and daily costs stay sane for four people, flagging one option as great-but-expensive-once-you-add-activities. The value is that the family sees the true daily cost for four — not the two-adult fantasy — before falling for a place they can't actually afford to enjoy once the park tickets and the extra hotel bed are counted.

A solo traveller with a modest ceiling and flexible dates wants somewhere safe, cheap to simply exist in day to day, and interesting for a couple of weeks alone. They note "solo, flexible on exact dates, comfortable on a budget." The AI uses the flexibility as a lever — pointing out where nudging the trip three weeks later drops it out of peak pricing — and returns a shortlist loosely ordered by how far the money stretches on the ground. It matters because this surfaces the cheap-to-live-in destinations that a flight-price-first search buries under whatever happens to have a cheap fare that week.

Creative use case ideas

Run it live at the kitchen table with every family member's must-haves typed in, so the shortlist — not the loudest person — sets the options up for debate.

Reverse-engineer a milestone trip by describing a 40th-birthday or anniversary vibe rather than a place, and let the shortlist propose destinations that match the feeling you're chasing.

Reality-check a Pinterest board: paste the dreamy caption ("cliffside village, turquoise water, cheap local wine") and get real places that actually match — plus the ones that only exist in a filter.

Use it as a "can we even?" gut check before you get emotionally attached to a bucket-list place, to see whether your dates and budget make it plausible at all this year.

Plan around a fixed event — you're already flying somewhere for a wedding or a reunion — and ask for nearby add-on destinations worth tacking onto the trip while you're in the region.

Adaptability tips

Tighten or loosen the count: ask for three if you're decisive, five if you want to browse. Add a single hard "no" — "no long-haul flights," "nowhere I need a rental car," "nowhere in its rainy season this month" — and watch the list sharpen instantly. When you're ready to move from feel to numbers, swap the cost scale by changing "cheap / moderate / expensive" to "give me a rough daily spend per person." And feed it your Week 1 profile verbatim: the more of your real constraint profile you paste in, the less the AI has to guess, and the less generic the shortlist comes back.

Pro tips

Run it twice with one variable changed — same trip, two different months — and compare the two shortlists. The destinations that appear in both are your weather-robust options, the ones that work whenever you can actually get away. If the AI leans on the usual suspects (Paris, Bali, Cancún), add "surprise me with at least two places most people wouldn't think of"; the best shortlist mixes safe bets with a genuine discovery. And close your input with "tell me which one detail, if I changed it, would most expand my options" — a cheap way to learn where your own constraints are quietly boxing you in.

Prerequisites

A rough sense of four things: how much you can spend in total, when you can go (even just a month), how many people and who they are, and the kind of trip you want. You do not need Week 1's formal constraint profile to start — but if you have it, paste it in. Nothing else is required.

Required tools

Any general-purpose AI chat tool — ChatGPT, Claude, or Gemini, free tiers included. No account upgrades, plugins, or setup needed. A model with live web access will give more current suggestions, but the plain shortlist works fine without it.

Frequently asked questions

What if the destinations it suggests are too obvious?

That usually means your input was broad. Add a constraint or two — a firm no, a specific interest, a tighter budget — and the list gets more interesting immediately. You can also ask directly for a couple of less-obvious picks alongside the safe ones. The prompt is only ever as specific as what you feed it.

Can I trust the daily-cost estimates?

Treat them as a rough feel, not a quote. A general AI model estimates from patterns in its training data, which can be dated or off for a specific city. Use the cheap/moderate/expensive read to compare candidates against each other, then verify the real number for your finalist before you book. The comparison stays useful even when the exact figure isn't.

I don't have my Week 1 budget yet — can I still use this?

Yes. Give it a ballpark ceiling and rough dates and it works. You'll get a looser shortlist, and the prompt will tell you where your vagueness is costing it precision. Coming back later with a real profile in hand sharpens everything downstream.

It asked me a question instead of answering — did I do something wrong?

No, that's the prompt working as designed. It only asks when a detail is too vague to give a useful shortlist. Answer the question and you'll get a better list than if it had guessed blindly. If you'd rather it just guess, add "make reasonable assumptions and note them" to your input.

Recommended follow-up prompts

The Weighted Shortlist (Variation 2 in this post), for when you're ready to rank the shortlist instead of just reacting to it. Week 1's budget-ceiling prompt, if you skipped it — run that first so this shortlist has a real number to work against. And a "day in the life" cost prompt for your top pick: ask the AI to walk through a typical day's spending in your leading candidate to pressure-test the cost read before you commit.

Tags and categories

Tags:

travel planning, destination research, vacation shortlist, budget travel, beginner prompts, AI travel assistant Categories: Travel & Lifestyle, Beginner Prompts

Citations

NOT APPLICABLE — the prompt and its breakdown are original work. Rather than citing sources here, the prompt directs the reader to verify any cost, weather, or entry detail against primary sources before acting on it.

02
IntermediatePrompt 2 of 3

The Weighted Shortlist

Score candidates on the factors you actually care about.

A plain shortlist is great until two of the options feel equally good and you can't say why. That's the moment you need a way to make your priorities explicit — because "equally good" usually means you haven't admitted what you actually care about. This prompt makes you say it out loud. You assign a weight to each factor — daily cost, weather, crowds, flights, safety — and the AI scores every candidate against all of them, then ranks the results by a composite that reflects your priorities, not its own. The output isn't just a list; it's a list with an argument attached. And because the weights are yours, you can change them and watch the ranking move.

Why this matters now

Most travel advice assumes everyone wants the same thing. You don't. A retiree optimising for calm weather and easy flights and a student optimising for the cheapest possible month are running completely different searches — but the generic web serves them the same articles. This prompt lets you encode your own priorities as numbers the AI has to respect. When the choice comes down to two or three finalists, a transparent score behind the ranking is what turns a hunch into a decision you can explain to the person sitting next to you.

The prompt — copy and paste this

Act as a destination analyst helping me build a ranked shortlist for a vacation. I'll give you my constraints and my priorities, and I want you to score candidate destinations against them.

My constraints: [total budget ceiling; travel dates or window; number and type of travellers; trip purpose].

My priorities — score each destination from 1 to 10 on these five factors, and weight them as follows (adjust the weights to reflect what matters to me):

- Daily cost on the ground: 30%

- Weather fit for my dates: 25%

- Crowd levels during my dates: 20%

- Flight accessibility from [my home airport]: 15%

- Safety and visa/entry friction: 10%

Propose 4 to 6 candidate destinations that plausibly fit my constraints. For each, give a 1-to-10 score on all five factors with a one-line justification per factor, then a weighted composite score. Rank them by composite. End with the two candidates you'd look at first and why. Flag clearly wherever you're estimating rather than confident, and tell me what I should verify myself.

How the AI reads this prompt

“Act as a destination analyst helping me build a ranked shortlist”
The role here is analytical, not inspirational — an analyst weighs and compares, where an assistant merely suggests. That framing primes the model to reason in trade-offs and scores rather than enthusiasm. Skip it and you tend to get prose recommendations that resist being turned into a ranking. The principle: choose a role whose real-world job matches the cognitive mode you want — "analyst" buys you comparison, "coach" buys you encouragement, and the two are not interchangeable.
“I'll give you my constraints and my priorities”
This separates two things people usually blur — what's fixed about your trip (constraints) and what you care about (priorities). Constraints filter which destinations are eligible; priorities decide how the eligible ones rank. Collapse them and the model treats a preference as a hard limit, or the reverse. The principle: distinguish the non-negotiable from the merely-preferred in your prompt, because the model handles them differently and mixing them corrupts the result.
“score each destination from 1 to 10 on these five factors, and weight them as follows...”
This is the engine of the prompt. Naming explicit factors forces the model to judge every candidate on the same axes instead of on whatever it happens to find salient, and the weights encode your priorities as math the ranking has to obey. Without fixed factors, two destinations get judged on different merits and can't be compared; without weights, every factor counts equally whether you like it or not. The principle: define your evaluation criteria explicitly and the model's judgments become comparable and steerable rather than ad hoc.
“adjust the weights to reflect what matters to me”
This one line converts a static prompt into a control panel. It tells you — and the model — that the weights are yours to move, which is the whole lesson of the intermediate tier: you shape the output by shaping the criteria, not by rewriting the request. Omit it and readers treat the sample weights as fixed and miss the point. The principle: expose the levers. A prompt that invites the user to change its parameters teaches control in a way a locked prompt never can.
“a one-line justification per factor”
This forces the model to attach reasoning to every number. A score with no justification is unfalsifiable — you can't tell a considered 8 from a random one. Requiring a reason per factor lets you spot where the model is confident, where it's bluffing, and where you simply disagree. Without it, you get a tidy set of numbers you have no basis to trust. The principle: never accept a rating without its reasoning; make the model show the "why" behind each score so you can audit it.
“a weighted composite score. Rank them by composite”
This is the aggregation step — combine the weighted factor scores into one number and order by it. Making the composite explicit means you can check the arithmetic and see how a destination's strengths and weaknesses net out. Leave it implicit and the model may rank by vibe while claiming to rank by score. The principle: when you want a decision from multiple inputs, specify how they combine; an unspecified aggregation is where a model smuggles its own preferences back in.
“Flag clearly wherever you're estimating rather than confident, and tell me what I should verify myself”
This is the honesty valve. Weighted scores look authoritative, which is dangerous when some of the inputs are guesses. Asking the model to mark its estimates and hand you a verification list turns confident-looking output into something you can responsibly act on. Without it, you can't tell the solid scores from the shaky ones. The principle: the more structured and numeric your output looks, the more you need the model to expose its own uncertainty, because structure reads as certainty whether or not it's earned.

Practical examples from different industries

A retired couple isn't chasing the cheapest option; they want reliable weather, short and simple flights, and low hassle at the border. They set weather and flight accessibility high and daily cost lower. The AI scores four candidates and the ranking rewards the calm, easy-to-reach places even where they cost a little more, surfacing a winner that a pure-budget search would have buried three pages down. The weighting is what makes the tool optimise for their real goal rather than the internet's default assumption that cheapest always wins.

A solo traveller flips the weights: daily cost at 40%, everything else trailing. The same five candidate cities get re-scored and a completely different order falls out, led by the places where a day simply costs the least to exist. What the reader learns here is as valuable as the ranking: the exact same destinations rank differently under different weights, which drives home that the "best" destination isn't a fixed truth but a function of what you value — the tool is only ever answering the question you actually asked it.

A family sets crowd levels and daily cost as their top two — school-holiday crowds and four-person costs are their real constraints — and keeps weather moderate. The composite rewards destinations that stay affordable and bearable during their fixed break week, and the per-factor justifications let the parents spot the one option that scores well overall but poorly on the single factor they can't compromise on. The breakdown by factor, not just the total, is what catches the deal-breaker hiding inside an otherwise attractive average.

Creative use case ideas

Settle a two-person tie by having each traveller fill in their own weights, running it twice, and comparing the two rankings to see exactly where your priorities diverge.

Stress-test a favourite by cranking the weight on the factor you're secretly worried about — crowds, say — and seeing whether your preferred destination survives its own worst case.

Hand the prompt to a teenager planning a first solo trip so they learn to trade factors off against each other instead of chasing one shiny variable like the cheapest flight.

Re-rank for a different season: keep the candidates, change only the weather weight and your dates, and watch which places rise or fall — a fast way to find the best time to visit somewhere you already love.

Choose a group-trip destination by collecting weights from everyone going, averaging them, and letting the composite pick the place that annoys the fewest people in the chat.

Adaptability tips

Change the factors, not just the weights: swap "safety/visa friction" for "kid-friendliness" or "nightlife" if that's what actually decides your trip. Add a sixth factor when one matters enough to trade other things for — accessibility, a pet policy, the language barrier. Ask for the ranking shown two ways, your weights and equal weights, because the gap between them reveals how much your priorities are really driving the result. And lock the weights and re-run monthly: as prices and seasons shift, the same weighted prompt becomes a repeatable check rather than a one-off answer.

Pro tips

Force honesty about weak scores by adding "for any factor a destination scores below 4 on, explain what would have to change for it to score higher" — it turns weaknesses into an action list. Ask the AI to name the factor doing the most work ("which single factor is driving the top ranking?") so you know whether your winner is genuinely balanced or riding one strength that could evaporate. And have it flag ties: when two composites land within a couple of points, you want it to say so explicitly rather than perform a precision it doesn't actually have.

Prerequisites

Your constraint profile from Week 1 (budget, dates, travellers, purpose), your home airport, and a few minutes to decide which factors matter most to you. You don't need to get the weights perfect — the whole point is that you can adjust them — but having a first guess ready makes the prompt land faster.

Required tools

Any general-purpose AI chat tool works. A model with stronger reasoning handles the scoring and re-weighting more consistently, and one with live web access gives more current cost and season reads. Free tiers are enough to run it; the value lives in how you set the weights, not the tier you're on.

Frequently asked questions

How does the AI actually calculate the scores?

It assigns each destination a 1-to-10 rating per factor based on its own knowledge, then multiplies by your weights and sums to a composite. The numbers are judgments, not measurements — their value is in comparing candidates consistently under the same rules. Ask it to show the arithmetic if you want to check the composite yourself.

What weights should I use if I have no idea?

Start with everything equal, run it once, and see which ranking feels wrong. Your reaction tells you which factor you actually care about more than you claimed, and you adjust from there. The prompt is designed to be re-run, so a rough first guess is genuinely fine.

The scores look confident — should I believe them?

Believe the ordering more than the exact numbers. A general model can rank "cheaper vs pricier" or "calmer vs busier" reasonably well, but it can be wrong on a specific figure or a recent change. The prompt asks it to flag estimates for exactly this reason — verify anything a decision truly hinges on.

Can I use this with the destinations from Variation 1?

Yes, and that's the intended flow. Run the beginner prompt to generate candidates, then feed those same places into this one to rank them. You can also hand it your own list if you already have places in mind — it'll score whatever you give it against your weights.

Recommended follow-up prompts

The Destination Dossier Matrix (Variation 3), for when you want disqualifier logic and a defensible, reusable matrix rather than a weighted list. Week 3's airfare-strategy prompt, once the ranking has a clear leader and it's time to price the flights. And a sensitivity-check prompt: ask the AI to tell you the smallest weight change that would flip your top two, so you know how stable your winner really is.

Tags and categories

Tags:

travel planning, weighted scoring, destination comparison, decision criteria, intermediate prompts, trip prioritisation Categories: Travel & Lifestyle, Intermediate Prompts

Citations

NOT APPLICABLE — original prompt and analysis. The reader is pointed to primary sources to verify any figure the scoring depends on rather than treating the AI's numbers as cited fact.

03
AdvancedPrompt 3 of 3

The Destination Dossier Matrix

Build a reusable decision matrix that survives a companion's scrutiny.

There's a specific kind of vacation argument this prompt exists to end: the one where you've picked a place, someone you're travelling with asks "why there and not somewhere else?", and you don't have an answer that survives the question. A gut pick can't be defended. A matrix can. This prompt builds a full destination dossier — candidates screened against hard disqualifiers first, then scored across cost, weather, crowds, entry friction, and flight access, with the scoring method shown so it can be challenged rather than simply trusted. It's slower to run, and it's meant to be. What you get back is reusable: paste in a new candidate months later, re-run it, and the analysis still holds.

Why this matters now

High-stakes trips — a honeymoon, a big group holiday, a once-a-decade splurge — are exactly the ones where "it just felt right" isn't good enough and a bad call is expensive to unwind. This prompt front-loads the disqualifiers most people discover too late: a visa that takes longer than you have, a weather window that's quietly wrong, a cost that only reveals itself once you're on the ground. Running the analysis before you're emotionally committed to a place is when it's worth the most, because that's when it's still cheap to change your mind.

The prompt — copy and paste this

Act as a destination-selection analyst. I want a defensible, reusable shortlist matrix I can show a travelling companion, not a gut pick. Work in this order and show your work at each stage.

Step 1 — Restate my brief. Here is my constraint profile: [budget ceiling and how firm it is; exact travel dates; number and type of travellers, including any school-age children; trip purpose; home airport]. Before scoring anything, restate these back to me in your own words so I can confirm you understood them. If any constraint is missing or contradictory, say so.

Step 2 — Apply hard disqualifiers first. Before scoring, screen out any candidate that fails a non-negotiable: visa or entry processing longer than the time I have, a weather window that is actively wrong for my dates (monsoon, extreme heat or cold), or a realistic total cost that breaks my ceiling. List what you disqualified and the one reason each was cut.

Step 3 — Build a dossier matrix for the survivors. Propose 4 to 6 candidates that pass Step 2. Present one row per destination with these columns: relative cost-of-living on the ground (indexed, cheapest candidate = 100), weather risk for my exact dates, crowd level for my exact dates (note school holidays, festivals, or local peak season), entry/visa friction, flight accessibility from my home airport (nonstop / one stop / worse), and a composite fit score out of 100.

Step 4 — Show your scoring method. State plainly how you scored each column and how the composite is weighted, so I can challenge the weighting.

Step 5 — Calibrate and rank. Rank by composite. For every cell where you're estimating rather than confident, mark it and list exactly what I should verify against a primary source (official visa page, airline routes, a cost-of-living reference) before I commit. End with your top pick and the strongest argument against it.

Keep the matrix compact enough to read on one screen, and write it so I can paste new candidates in later and re-run the same analysis.

How the AI reads this prompt

“I want a defensible, reusable shortlist matrix I can show a travelling companion, not a gut pick”
This sets the design goal before any mechanics, and every later step serves it. "Defensible" tells the model the output must withstand a challenge, which raises the bar on transparency; "reusable" tells it to produce something structured enough to re-run; "not a gut pick" rules out the confident single recommendation models love to give. State the goal up front and the model organises its whole response around it. The principle: lead with the standard the output must meet, and the model holds itself to it throughout instead of optimising for a quick answer.
“Work in this order and show your work at each stage”
This forces a chain of reasoning rather than a leap to conclusions. Complex judgments degrade when a model jumps straight to the answer; making it move through explicit stages keeps each step inspectable and stops early errors from hiding inside a confident finish. Remove it and the matrix may look complete while skipping the reasoning that makes it trustworthy. The principle: for any multi-part decision, sequence the steps and demand the working — visible intermediate reasoning is both more accurate and more auditable than a black-box verdict.
“Step 1 — Restate my brief... restate these back to me in your own words so I can confirm you understood”
This is a grounding checkpoint. By making the model paraphrase your constraints before acting, you catch misreads while they're still cheap — before they've propagated through the disqualifiers and the scores. If it misunderstood your dates or your budget, everything downstream is wrong, and you'd much rather learn that in sentence one. The principle: on high-stakes prompts, make the model confirm its understanding of the inputs before it uses them; a mirror step at the start prevents a compounded error at the end.
“Step 2 — Apply hard disqualifiers first... List what you disqualified and the one reason each was cut”
This gates the analysis. Scoring a destination that's actually impossible — a visa you can't get in time, a monsoon during your only free week — wastes effort and, worse, can leave an impossible option ranked near the top where it tempts you. Screening non-negotiables first removes them cleanly, and listing the cuts keeps the exclusions auditable rather than silent. The principle: separate elimination from optimisation. Filter out the disqualified before you rank the rest, or a high score will disguise a fatal flaw.
“one row per destination with these columns... a composite fit score out of 100”
This defines a strict output schema. Handing the model the exact columns forces every candidate to be evaluated on the same dimensions, which is what makes a matrix comparable rather than a pile of paragraphs. A loose "compare these places" gets you inconsistent coverage; a fixed schema gets you a grid you can read straight across. The principle: when you need structured, comparable output, specify the structure explicitly — the schema is what turns generation into analysis.
“relative cost-of-living on the ground (indexed, cheapest candidate = 100)”
Asking for a relative index instead of absolute dollar figures is a deliberate hedge against false precision. A model guessing exact daily costs invites confident, wrong numbers; anchoring everything to the cheapest candidate produces comparisons that stay useful even when the underlying figures are rough. Ask for absolutes and you get precision you can't trust; ask for an index and you get a reliable ordering. The principle: when exact values are shaky but relative differences matter, request a normalised or indexed output — you keep the signal and drop the false accuracy.
“Step 4 — Show your scoring method... so I can challenge the weighting”
This is where "defensible" is earned. By making the model state how it scored each column and weighted the composite, you get something you can argue with instead of a number handed down from nowhere. If the method is hidden, you can't tell a good ranking from an arbitrary one — and neither can the person you're travelling with. The principle: transparency is what makes an output defensible; an exposed method invites scrutiny and survives it, while a hidden one only demands trust.
“Step 5 — ... mark it and list exactly what I should verify against a primary source”
This is the calibration and hand-off step. It turns the model from something you're tempted to trust into a research assistant that tells you what it doesn't know and where to look. Marking the estimated cells and naming the official pages to check converts a slick matrix into an honest one. Without it, the polish of the output hides its soft spots. The principle: require the model to separate what it's confident about from what it's inferring, and to point you at primary sources — good AI output ends by telling you what to check, not by asking you to believe it.
“write it so I can paste new candidates in later and re-run the same analysis”
This bakes in reusability, which is the difference between a one-off answer and a tool. Because the method lives inside the prompt, the model applies the same logic every time, so results stay comparable across runs and across trips. Skip it and each run reinvents its own approach, and you can't compare last month's matrix to this one's. The principle: when you'll need something more than once, prompt for a repeatable process rather than a single result — encoding the method makes the output a system you can reuse.

Practical examples from different industries

A couple planning a two-week honeymoon feed their full profile — firm budget, exact dates, home airport, "no long layovers." Step 2 quietly does the heavy lifting: it disqualifies a dream island because entry processing for their passports would run past their travel date, cutting it before they fall for it. The surviving candidates get a matrix with a transparent composite, and the couple walk into the decision holding a one-screen document they've both signed off on. The disqualifier gate caught a trip-killer that a scoring-only approach would have ranked highly and hidden inside a good-looking total.

An organiser planning a trip for eight across two generations needs a place that clears everyone's non-negotiables. They add constraints for mobility and school-age kids. The matrix scores crowd levels against the exact holiday week and flags which candidates spike during local festivals, while the "show your scoring method" step lets the organiser defend the ranking to relatives who'd otherwise relitigate it in the group chat. A shared, transparent score is far harder to argue with than one person's preference — which is the real problem in group travel, and the thing this variation is built to solve.

A retiree with flexible dates but firm limits on flight length and heat wants somewhere to spend a month cheaply and comfortably. Because the dates are flexible, they run the matrix twice for two candidate months and compare — the reusability is the entire point. The verification list tells them exactly which cells (visa rules, a specific festival's dates) to confirm against official pages before booking. The calibration step is what turns the AI from an oracle into a research assistant that admits what it doesn't know and hands back a checklist.

Creative use case ideas

Save the filled-in prompt as a reusable family template and re-run it every year for the annual trip, changing only the dates and the candidates.

Compare two very different trip styles by running one matrix for "cheap and adventurous" candidates and another for "comfortable and easy," then setting the top of each side by side.

Audit a decision you've already made by running the matrix on the place you've booked plus two alternatives, to see whether your choice actually holds up — reassuring or clarifying, either way.

Build a "someday" list by using the disqualifier step to sort bucket-list dreams into "possible next year" versus "needs a different life stage," based on real entry and cost friction rather than wishful thinking.

Reuse the staged approach — restate, disqualify, score, show method, calibrate — as a transferable template for any high-stakes choice, from picking a car to choosing a college, not just travel; the structure is the lesson, and it travels well beyond vacations.

Adaptability tips

Change the columns to fit the trip: swap "crowd level" for "accessibility" or "internet reliability" if you're planning a working trip or travelling with mobility needs. Adjust the disqualifier list, because your non-negotiables aren't everyone's — maybe a direct flight is mandatory, or a language you speak is required — and putting them in Step 2 makes them screen early. Ask for the matrix as a labelled block you can copy into a notes app or spreadsheet, so re-running later is a paste-and-edit rather than a rewrite. And scale the candidate count: five or six is readable, but if you're early and still exploring, allow eight and then narrow.

Pro tips

Make it argue against itself: the prompt already asks for "the strongest argument against your top pick," so lean in and require a second, independent objection. A winner that survives two real arguments is a winner you can trust. Demand a confidence column — high, medium, or low per cell — so you can see at a glance where the matrix is solid and where it's guessing. Ask it to split each cell into what it's fairly sure of versus what it inferred, which makes the verification list write itself. And re-run once with web access on and once off: comparing the two exposes exactly which claims came from live data versus training patterns, a fast reliability check.

Prerequisites

Your complete Week 1 constraint profile — budget ceiling and how firm it is, exact dates, number and type of travellers (including kids' ages), and trip purpose — plus your home airport. The more precise the profile, the sharper the matrix; vague inputs produce a vague matrix, and the prompt will say so. Ideally, run it on a model with live web access for current entry rules, flight routes, and seasonal data.

Required tools

A capable general-purpose AI model, ideally one with strong reasoning and live web access — current visa processing times, flight routes, and festival calendars are exactly the data that goes stale in training. Paid tiers, which typically offer stronger reasoning and browsing, will produce a more reliable matrix, though the structure works on any model. On a model without live data, treat every cell as a hypothesis to verify rather than a fact to book on.

Frequently asked questions

Isn't this overkill for a normal holiday?

For a cheap weekend, yes — use Variation 1. This prompt earns its length on trips where a wrong call is costly or hard to reverse: honeymoons, big group trips, month-long stays, anything with a firm non-refundable component. The disqualifier gate alone can save a trip that would otherwise fall apart late. Match the tool to the stakes.

The matrix has real numbers in it — are they accurate?

The composite and the cost index are structured judgments, not audited data, and a model without live access can be confidently wrong. That's why the prompt forces a verification list and a confidence flag on estimates. Use the matrix to shape the decision and to know exactly what to check, then confirm the decisive cells against official sources before you book.

What counts as a hard disqualifier?

Anything genuinely non-negotiable for you: entry processing longer than your available time, a weather window that's actively dangerous or miserable for your dates, or a true cost that breaks your ceiling. The point of screening these first is to avoid scoring — and falling for — a destination that a total score would rank highly but reality rules out.

How do I actually reuse it?

Save the completed prompt and its output. Next time, change only what's different — new dates, a new candidate, an adjusted budget — and re-run. Because the method is stated inside the prompt itself, the AI applies the same logic each time, so results stay comparable across runs. That consistency is the whole reason to invest in the structure once.

Can I combine it with the weighted approach from Variation 2?

Yes — tell it to use your Variation 2 weights when computing the composite in Step 3. That merges the reader-controlled weighting with the disqualifier gate and the verification discipline, giving you the most defensible version of all three. It's the natural end state once you're comfortable with both.

Recommended follow-up prompts

Week 3's airfare-strategy prompt, once the matrix names a winner and it's time to price the flights properly. A "verification sprint" prompt — feed the matrix's own verification list back in and ask the AI to draft the exact searches and official pages to check each item. And Week 4's lodging prompt, to carry the chosen destination forward into where-to-stay analysis without losing the reasoning that got you there.

Tags and categories

Tags:

travel planning, decision matrix, destination dossier, structured prompting, advanced prompts, disqualifier screening, reusable prompts Categories: Travel & Lifestyle, Advanced Prompts

Citations

NOT APPLICABLE — the prompt, its staged method, and the breakdown are original work. Rather than citing sources here, the prompt itself directs the reader to confirm outputs against primary sources: official government visa and travel-advisory pages, airline route maps, and cost-of-living references.

Which of the three should you use?

The three prompts are the same question asked with rising seriousness. The Fuzzy-Wish Shortlist is for the start of thinking — you have a feeling and a rough budget, and you want real places to react to in five minutes with zero setup. It's the right tool when you don't yet know what you want, because reacting to a concrete list is how most people discover their own preferences. Nothing about it is beneath an experienced planner; it's just fast, and speed is exactly what the earliest stage needs.

The Weighted Shortlist is for the moment the shortlist exists and the choice narrows to a few finalists that all seem fine. Its job is to make your priorities explicit and let you watch the ranking shift as you change them — and the lesson it teaches is that the "best" destination isn't a fixed fact but a function of what you weight. Reach for it when you can name your factors but haven't yet decided how much each one counts.

The Destination Dossier Matrix is for trips where being wrong is expensive. It adds two things the others don't: a disqualifier gate that removes impossible options before they seduce you, and a transparent, reusable scoring method you can defend to a travelling companion and re-run for years. It costs the most effort and returns the most rigour. Most readers will run Variation 1 on every trip, Variation 2 when a decision is close, and Variation 3 when the stakes justify it — and the three chain naturally, each one's output feeding the next. This isn't a ranking; it's a sequence, and where you enter depends on how far along and how high-stakes your trip already is.

TAGS:

Next
Next

The Defensible Shortlist: Picking a Destination Without the Dreamy Mess