# Travel Research Brief Builder Prompt > A reusable text prompt that turns your own trip dates, budget and priorities into labeled options, open questions and a manual verification checklist. ## Install Copy the content below into your project: # Travel Research Brief Builder Prompt A reusable text prompt that turns your own trip dates, budget and priorities into labeled options, open questions and a manual verification checklist. ## 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](https://help.openai.com/en/articles/6825453-chatgpt-release-notes) · Reviewed 2026-10-04 Original TokRepo prompt · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Reference documents retain their own rights. --- # 旅行调研简报生成提示词 一段可复用的文字提示词,把你自己的出行日期、预算和优先级整理成带标签的备选方案、待确认问题和人工核对清单。 ## 开始使用 这是一段纯文字提示词。把它粘贴到任何能接收文字的普通 AI 聊天里即可,不需要终端、账户配置或 API。已查看来源;未做运行测试。 **粘贴前先准备好:** - 谁去、相关年龄或行动不便需求、以及出行缘由。 - 出发地、目的地或正在犹豫的短名单、最早出发日、最晚返回日、不能改的日期。 - 预算数字、币种、需要覆盖的内容,以及是否为硬性上限。 - 按顺序排列的优先级、绝对不能接受的情况、以及已经定好的事项。 **如何粘贴:** 复制本页附带的完整提示词文本,粘贴到聊天中,然后把你的回答分别写在六个输入标题下。某个标题不适用时,请写明“不适用”,不要默默留空。 **如何检查输出:** 回复应按顺序使用五个标题,为每个选项写出一项取舍,并且不把价格、时间、营业时间或可订状态当作事实陈述。问题应标注 [blocking] 或 [nice to know](阻碍项/了解即可)。最后一节应是你自己要去做的步骤。 ## 这段提示词的作用 你会得到一份调研简报草稿:用你的话重述行程、两到四个不同的行程形态及各自优化的取舍、按影响排序的待确认问题、指向来源类型的核对清单,以及人工下一步动作。它不会联系任何服务方,也不会预订任何东西。 ## 前提、权限与限制 - 只使用你粘贴的文字。聊天看不到订票网站、日历、邮件、账户、实时价格或可订状态,提示词也禁止声称看过。 - 如果有输入缺失,提示词要求把缺口列在“缺失或不明确”下,而不是猜测。 - 输出是调研草稿,不是确认信息。价格、班次、入场规则和营业时间必须在官方运营方、场馆或交通机构页面核实。 - 出行记录和预算属于个人信息,避免粘贴姓名、护照号或支付细节。 - 提示词不提供医疗、法律、移民或财务建议,只指向应查看的官方来源类型。 ## 常见问题 **助手能告诉我现在的价格或是否有空位吗?** 不能。它被要求绝不把价格、班次、可订状态、签证规则、天气或营业时间当作事实陈述,只能说明你需要核实什么。 **如果我的预算看起来撑不起我的优先级怎么办?** 提示词要求把它作为待确认问题提出,而不是下结论,并给出你应该测试的替代方案。 ## 来源与致谢 TokRepo 原创提示词,采用 CC BY 4.0 许可。为本页撰写;参考公告见 [ChatGPT release notes]()。提示词中的示例为虚构并已标注。已查看来源;未做运行测试。 ## 完整可复制提示词 # 旅行调研简报构建器(不预订) 你正在帮我为一次计划中的旅行准备一份调研简报。你只能依据我在下面粘贴的信息工作。你无法访问订票网站、日历、邮件、账户、实时价格或可订状态,并且不得声称检查过其中任何一项。你产出的所有内容都是草稿,需由我自己核实并采取行动。 ## 我的输入(我会把内容粘贴在每个标题下) 1. 行程目的与出行人:谁去、相关年龄或行动不便需求、以及出行缘由。 2. 固定约束:出发地、目的地(或正在犹豫的短名单)、最早出发日期、最晚返回日期、以及任何不能更改的硬性日期。 3. 预算:总额、币种、必须覆盖的内容(交通、住宿、餐饮、活动)。说明是否为硬性上限。 4. 优先级排序:例如低路途时间、低成本、安静的住宿、适合步行、美食、博物馆、自然。 5. 绝对不能接受的情况:会让某个选项被排除的因素。 6. 已经定好的事项:已安排的交通或住宿、已持有的通票、稍后加入的人。 如果某个标题缺失或不明确,不要用看似合理的猜测填补空白。把它列在“缺失或不明确”下,并继续处理已有的内容。 ## 需要产出什么 ### 1. 约束摘要 用我自己的说法简短重述我的行程:日期、路线、预算、优先级、绝对不能接受的情况。把你注意到的任何内部冲突(例如硬性预算看起来不太可能覆盖我陈述的优先级)作为问题标出,而不是下结论。 ### 2. 选项集合 提出两到四个符合所述约束的不同行程形态——例如不同街区、不同出行日、或更短与更长的版本。对每一个给出: - 一行标签,以及它优化的是哪项取舍。 - 它满足了我的哪些优先级,又牺牲了哪些。 - 它最敏感的特定约束(价格、可订状态、天气季节、开放日)。 - 在我相信它之前需要自己核实什么:说出确切事实,以及能确认它的来源类型(官方运营方网站、场馆页面、当地交通机构)。不要把价格、班次或可订状态陈述为事实。 ### 3. 待确认问题 一个编号列表,列出我在决定前应回答或核实的问题,按它们可能改变计划的程度排序。每个问题标注 [blocking] 或 [nice to know](阻碍项/了解即可)。 ### 4. 核实清单 对我认真考虑的每个选项,列出我在依赖它之前必须在官方来源确认的事实:日期、时间、入场规则、取消条款、无障碍设施,以及任何会在短时间内变化的费用。 ### 5. 我接下来做什么(人工步骤) 一个简短有序的动作列表,由我自己执行——例如打开官方网站、保存确认信息、向服务方提出具体问题。不要提出替你执行其中任何步骤、发送任何内容或进行预订。 ## 输出格式 按顺序使用上面的五个标题。保持便于快速浏览:短段落、项目符号、不要废话。表格不超过四列。仅用纯 Markdown。 ## 边界 - 绝不编造价格、班次、可订状态、签证或入境规则、天气或营业时间。 - 绝不声称浏览过、打过电话或实时检查过任何内容。 - 清楚区分“这是你可以去调研的计划”和“这是已确认的”。 - 如果我的预算或日期使某个选项不现实,把它作为需注意的顾虑说出,并给出我应该测试的替代方案。 - 不提供医疗、法律、移民或财务建议。改为指向应查看的官方来源类型。 ## 示例(虚构) 我可能会粘贴的输入: 目的:周末城市短途游,两名成人。 固定条件:从阿姆斯特丹飞,周五 18:00 后出发,周日晚返回,硬性日期为 3 月 14 日至 16 日。 预算:总计 600 欧元,硬性上限,覆盖交通、住宿、餐饮、一项付费景点。 优先级:1)短途飞行,2)市中心步行可达的住宿,3)好吃的,4)一座博物馆。 绝对不能接受:一次以上中转;住宿距市中心超过 40 分钟。 已决定事项:无。 你回答的预期形态: - 约束条件摘要,指出 600 欧元的硬性上限,并询问它是否必须覆盖两名出行者。 - 选项集合,例如“短途飞行、市中心住宿”对比“较长火车行程、较低住宿成本”,每个都写出取舍,以及敏感约束。 - 待确认问题:[blocking] 600 欧元是一个人的还是两人的?[blocking] 周五 20:00 之后还有哪些机场到市中心的接驳仍在运行? - 核对清单,列出官方交通和场馆页面,而不是具体时间或票价。 - 人工下一步:我自己打开官方网站并核实事实。 ## 回答前自检 1. 我是否只使用了所供输入,并列出缺口而不是猜测? 2. 每个选项是否都写出一项取舍和一项用户必须核实的事实? 3. 是否完全没有编造价格、时间或可订状态? 4. 下一步是否明确是用户的人工操作,不暗示我要预订、发送或核实? 5. 输出是否按指定的五个标题呈现,并且没有超出我范围的建议? 如果任何一项不达标,在返回简报前先修正。 ## 参考资料与复用 - [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes) · Reviewed 2026-10-04 TokRepo 原创提示词 · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)。参考资料保留各自原有权利。 --- Source: https://tokrepo.com/en/workflows/travel-research-brief-builder-prompt-358bf51f Author: Prompt Lab