Start here

This is a plain-text prompt. You paste it into any ordinary AI chat that accepts text (for example a general chat assistant). No terminal, account setup or API is needed. Source reviewed; runtime not tested.

What to have ready before you paste:

• Who is going, ages or mobility needs if relevant, and the occasion.
• Origin, destination or a short list you are choosing between, earliest departure and latest return date, any hard dates.
• Budget figure, currency, what it must cover, and whether it is a hard ceiling.
• Priorities in order, deal-breakers, and anything already booked or owned.

How to paste: copy the full prompt text supplied with this page, paste it into the chat, then paste your own answers under each of the six input headings. If a heading does not apply, write that it does not apply rather than leaving it silently blank.

How to check the output: the reply should use the five headings in order, name a trade-off for every option, and list no prices, times, opening hours or availability as facts. Questions should be marked [blocking] or [nice to know]. The final section should be steps you take yourself.

What this prompt does

You get a draft research brief: a restatement of your trip, two to four distinct trip shapes with the trade-off each one optimizes, ordered open questions, a verification checklist pointing at source types, and manual next actions. It never contacts providers and never books anything.

Prerequisites, permissions and limits

• Only the text you paste is used. The chat cannot see booking sites, calendars, email, accounts, live prices or availability, and the prompt forbids claiming it does.
• If an input is missing, the prompt asks the assistant to list it under "Missing or unclear" instead of guessing.
• Output is a research draft, not confirmation. Prices, schedules, entry rules and hours must be checked on official operator, venue or transit pages.
• Travel history and budget may be personal; avoid pasting names, passport numbers or payment details.
• The prompt gives no medical, legal, immigration or financial advice; it points to official source types instead.

FAQ

Can the assistant tell me the current price or whether something is available? No. It is instructed to never state prices, schedules, availability, visa rules, weather or opening hours as fact, and to say what you must verify instead.

What if my budget looks too small for my priorities? The prompt asks for that to be raised as a flagged question, not a verdict, with the alternative you should test.

Attribution

Original TokRepo prompt, licensed CC BY 4.0. Written for this page; see the reference announcement ChatGPT release notes. The worked example inside the prompt is fictional and labelled as such. Source reviewed; runtime not tested.

Complete reusable prompt

Travel Research Brief Builder (No Bookings)

You are helping me prepare a research brief for a trip I am planning. You are working only from the information I paste below. You do not have access to booking sites, calendars, email, accounts, live prices or availability, and you must not claim to check any of them. Everything you produce is a draft for me to verify and act on myself.

My inputs (I will paste these under each heading)

1. Trip purpose and travelers: who is going, ages or mobility needs if relevant, and the occasion.
2. Fixed constraints: origin, destination (or a short list I am choosing between), earliest departure date, latest return date, and any hard dates I cannot move.
3. Budget: total figure, currency, and what it must cover (transport, lodging, food, activities). State if it is a hard ceiling.
4. Priorities ranked: e.g. low travel time, low cost, quiet accommodation, walkability, food, museums, nature.
5. Deal-breakers: things that would rule an option out.
6. Anything already decided: transport or lodging already arranged, passes owned, people joining later.

If a heading is missing or unclear, do not fill the gap with a plausible guess. List it under "Missing or unclear" and continue with what is present.

What to produce

1. Constraint summary

A short restatement of my trip in my own terms: dates, route, budget, priorities, deal-breakers. Flag any internal conflict you noticed (for example, a hard budget that looks unlikely to cover my stated priorities) as a question, not a verdict.

2. Option set

Propose two to four distinct trip shapes that fit the stated constraints — for example different neighborhoods, travel days, or a shorter versus longer version. For each one give:

• A one-line label and the trade-off it optimizes for.
• Which of my priorities it serves and which it compromises.
• The specific constraint it is most sensitive to (price, availability, weather season, opening days).
• What I would need to check myself before trusting it: name the exact fact and the kind of source that would confirm it (official operator site, venue page, local transit authority). Do not state a price, schedule or availability as fact.

3. Open questions

A numbered list of the questions I should answer or verify before deciding, ordered by how much they could change the plan. Mark each as [blocking] or [nice to know].

4. Verification checklist

For each option I am seriously considering, list the facts I must confirm on official sources before I rely on it: dates, hours, entry rules, cancellation terms, accessibility, and any fee that changes at short notice.

5. What I do next (manual steps)

A short ordered list of actions I take myself — for example opening the official site, saving a confirmation, asking a specific question to a provider. Do not offer to perform any of these steps, send anything, or make reservations.

Output format

Use the five headings above in order. Keep it scannable: short paragraphs, bullet points, no filler. No tables wider than four columns. Plain Markdown only.

Boundaries

• Never invent prices, schedules, availability, visa or entry rules, weather, or opening hours.
• Never claim to have browsed, called, or checked anything live.
• Distinguish clearly between "this is a plan you can research" and "this is confirmed."
• If my budget or dates make an option unrealistic, say so as a flagged concern and give the alternative I should test.
• Do not give medical, legal, immigration or financial advice. Point me to the official source type instead.

Worked example (fictional)

Input I might paste: Purpose: weekend city break, two adults. Fixed: fly from Amsterdam, leave Friday after 18:00, back Sunday night, hard dates 14–16 March. Budget: 600 EUR total, hard ceiling, covers transport, lodging, food, one paid attraction. Priorities: 1) short flight, 2) central walkable lodging, 3) good food, 4) one museum. Deal-breakers: more than one transfer; lodging over 40 minutes from center. Already decided: none.

Expected shape of your answer:

• Constraint summary noting the hard EUR 600 ceiling and asking whether it must cover both travelers.
• Option set such as "Short-hop city with central stay" versus "Longer train trip, lower lodging cost," each with the trade-off, and the sensitive constraint.
• Open questions: [blocking] Is the 600 EUR for one person or both? [blocking] Which airport-to-center transfers still run after 20:00 on a Friday?
• Verification checklist naming official transit and venue pages, not specific times or fares.
• Manual next steps: I open the official sites and check the facts myself.

Self-check before you answer

1. Did I use only the supplied inputs, and list gaps instead of guessing?
2. Does every option name a trade-off and a fact the user must verify?
3. Are there zero invented prices, times, or availability claims?
4. Are the next steps clearly manual actions for the user, with no implied booking, sending or checking on my part?
5. Is the output in the five specified headings and free of advice outside my scope? If any item fails, fix it before returning the brief.

References and reuse

• ChatGPT release notes · Reviewed 2026-10-04

Original TokRepo prompt · CC BY 4.0. Reference documents retain their own rights.