Build the pack from your booking data, not from a model's memory: paste the confirmed details into a prompt that produces an itinerary summary and a client checklist, add a pointer to the official source for each visa, health and insurance item with a "checked on" date, and run an accuracy check against the bookings before it is sent.
Printable travel checklists are generic lists of passport, tickets and insurance. A client needs a list for their own trip, with the documents that matter for those travellers and a record of where each rule was checked. The risky part is the rules. Entry, vaccination and insurance conditions depend on the traveller's passport and route and they change, so AI should structure the pack and never state a requirement.
Three kinds of content in a pack, and who supplies each
Every line in a client pack belongs to one of three kinds, and mixing them up is how wrong information gets into a PDF. Keep them apart in the prompt, in the sheet and in your head.
| Kind of content | Where it comes from | What AI does with it |
|---|---|---|
| Booking facts: flights, hotels, transfers, references, payment dates | Your booking system and the supplier confirmations | Formats them into a day-by-day summary and flags oddities; never fills a gap |
| Requirements: visas, passport rules, vaccinations, forms, insurance conditions | Official sources, read by a person, for this passport and route | Lays out the lookup sheet and the pointer lines; never states a rule |
| Advice: packing, local tips, what to do first on arrival | Your own knowledge and your suppliers | Drafts it in your voice for you to edit |
One data rule applies throughout. Use traveller codes (T1, T2, T3) and booking references in prompts, and keep full names, passport numbers, card details and medical information in your booking system. Names are merged in at the end. The tutorial on redacting personal data with AI before sharing covers the method, and it keeps the pack useful without handing a model more than it needs.
The checklist: eight groups, each item with why and how to verify
Print each group, or copy the tables into your own template. The first column is for a tick, and the last tells whoever checks the item what to open and what to record. Wherever it says "official source", record the page, the exact wording and the date, and never a summary from memory.
Names, passports and entry permissions
| Done | Item | Why it matters | How to verify |
|---|---|---|---|
| [ ] | Names on every booking match each passport exactly | Airlines can refuse boarding if the ticket name does not match, and corrections take time and sometimes money | Compare booked names with a photo of each passport data page the client sends |
| [ ] | Passport expiry against the trip dates | Some destinations require validity beyond the stay, and some ask for blank pages; the destination sets the rule | Calculate the dates in a spreadsheet, then compare with the destination's official entry page and record its wording |
| [ ] | Visa or electronic travel authorisation | Many destinations need approval before travel; the rule depends on the passport and the purpose of the trip | Destination's official government source for that passport; dated screenshot; the airline's check as a second source |
| [ ] | Every transit point | Transit countries can set their own rules, and a change of airport can need its own permission | Repeat the lookup for each transit, using the same sources |
| [ ] | Children travelling with one parent or none | Some destinations and airlines ask for extra papers | Destination's official page and the airline's policy, after you know the family's circumstances |
| [ ] | Driving licence and any permit for car hire | Hire firms and destinations set their own licence rules | The hire firm's terms and the destination's official page |
Health and vaccination
| Done | Item | Why it matters | How to verify |
|---|---|---|---|
| [ ] | Vaccination certificates required for entry | Some destinations ask for proof of yellow fever vaccination, and the destination decides what happens to a traveller who arrives without a valid certificate | Destination's official page, the client's national travel-health service, and the embassy or consulate; published lists can lag behind changes |
| [ ] | Recommended vaccinations and medicines | Health advice depends on the traveller, and you should not give it unless it is part of a licensed service | Tell the client to see a doctor or travel clinic early, and record that you told them and when |
| [ ] | Prescription medicines carried | Some destinations restrict certain medicines | Destination's official page or embassy; the client carries prescriptions and original packaging |
| [ ] | Health declarations or entry forms | Some destinations ask for a form before arrival | Official page; save the confirmation |
Insurance
| Done | Item | Why it matters | How to verify |
|---|---|---|---|
| [ ] | A policy exists, in the names of all travellers | Cover depends on the policy's details | Ask for the policy schedule; check names, dates and destination |
| [ ] | Medical conditions and activities declared | Cover can be affected by undeclared conditions or excluded activities such as skiing or diving | The client reads the wording and declares to the insurer; you record that you reminded them |
| [ ] | When cancellation cover starts | The start date varies by policy, so a late purchase may leave earlier risks uncovered | The policy wording or the insurer |
| [ ] | Emergency assistance number | It is the first call in a medical emergency | Copy it from the policy documents, never from AI; print it in the pack and ask the client to save it in their phone |
Money and payments
| Done | Item | Why it matters | How to verify |
|---|---|---|---|
| [ ] | Balance due dates, all suppliers | A missed final payment can cost the booking | Supplier invoices; the tutorial on tracking supplier payment deadlines covers the tracking |
| [ ] | What is payable at the destination | Hotels may charge local taxes or hold a deposit on arrival | The hotel's booking terms; list amounts only as the hotel states them |
| [ ] | Card needed for hire car or hotel deposit | Some providers require a card in the lead traveller's name | Supplier terms |
| [ ] | Backup payment method abroad | One declined card should not strand a family | Ask the client to check arrangements with their card provider |
Bookings and tickets
| Done | Item | Why it matters | How to verify |
|---|---|---|---|
| [ ] | Flights: names, dates, local times, airports, terminals, baggage allowance | Most pre-departure problems start here | The airline's own booking record |
| [ ] | Overnight flights show the arrival date | "Arrives next day" is the most commonly misread detail | Write both dates in full; check against the ticket |
| [ ] | Hotels: address, check-in time, reference, prepaid or pay at the property | A late arrival can need a heads-up to the hotel | Hotel confirmation |
| [ ] | Transfers and tours: pick-up point, time, supplier phone, voucher | It is the link most often missed after landing | Supplier confirmation |
| [ ] | Attachments open correctly on a phone | A voucher that will not open at a desk is no voucher | Open each PDF on a phone before sending |
Contacts and emergencies
| Done | Item | Why it matters | How to verify |
|---|---|---|---|
| [ ] | Your out-of-hours contact, and what counts as an emergency | Clients ring whoever they can reach | Test the number yourself |
| [ ] | Supplier emergency numbers (hotel, transfer, tour) | A driver who has not arrived needs a direct line | Supplier confirmations |
| [ ] | The client's emergency contact at home | You need someone to call if the client cannot be reached | Ask the client and note their consent to hold it |
| [ ] | Who to call first, by problem | The airline, the insurer, the embassy and you each handle different problems | One short paragraph in the pack that you wrote and checked |
Special needs and group details
| Done | Item | Why it matters | How to verify |
|---|---|---|---|
| [ ] | Mobility, dietary and medical needs passed to the suppliers | Telling only you is not the same as telling the hotel or the airline | Each supplier's confirmation mentions the need |
| [ ] | Celebrations such as a honeymoon or a birthday | The hotel cannot mark what it was never told | Hotel confirmation or an email reply |
| [ ] | Children's ages on each travel date | Child fares and room rules depend on age at the date of travel | Calculate the age on the outbound and return dates in a spreadsheet |
The countdown from 60 days to the day before
| When | What happens |
|---|---|
| 60 days before | Check passports against trip dates, run the requirements lookups, and remind clients about insurance and a travel clinic |
| 30 days before | Confirm final payments and due dates; chase any missing traveller details |
| 14 days before | Send the pack, with a version number and a date |
| 7 days before | Re-check every requirement line, and update the pack if anything changed |
| 2 days before | Check-in details, transfer confirmations and the first-day plan |
| The day before | A short message: emergency contact, where to meet, what to have in hand |
Official sources to point to, by question
The pack should say where to look, not what the answer is. These are the kinds of source to name, and what to record for each. The IATA Travel Centre is a traveller-facing lookup built on the Timatic database that airlines use. IATA's own material says rules and regulations change on a daily basis and that travellers are responsible for carrying the right documents, so treat it as a second source beside the destination's official page, and check its current terms before you rely on it.
| Question | Point the client to | Record in your sheet |
|---|---|---|
| Does this passport need a visa or authorisation? | The destination's official immigration or entry page, and the airline's document check | URL, exact wording, date, your initials |
| Is the passport valid for long enough? | The same official page; the arithmetic is yours | The rule as written, and the date calculation |
| Is a vaccination certificate required? | The destination's official page, the client's own travel-health service and a travel clinic; WHO and national health agencies note that yellow fever is the only disease named in the International Health Regulations for which proof of vaccination can be required at entry | Wording and date; whether a transit point has its own rule |
| What does the airline need at check-in? | The airline's own travel-documents page | URL and date |
| What does the policy cover? | The insurer's policy wording, read by the client | Policy number, assistance number, who is covered |
| Has anything changed since booking? | All of the above, again, about a week before departure | A second dated line, never an overwrite |
Prompts that build the pack from booking data
Three prompts do the structural work. The first turns booking data into an itinerary summary. Its rules are the important part: every gap is marked MISSING, and requirements are never stated.
You build a client itinerary summary from booking data. Use only the data
between the markers.
Rules:
- If a field is missing, write MISSING. Never guess times, terminals or references.
- Show every date in full (day, date, month). Mark overnight arrivals
"arrives next day".
- Use 24-hour local times and say they are local.
- Do not state visa, health, insurance or entry requirements. Write
"see requirements sheet".
- Output a table by day: date | what | local time | reference | notes.
- After the table, list "Things to check": tight connections, overnight
arrivals, late check-ins, balance due dates, anything MISSING.
=== BOOKING DATA START ===
Travellers: T1 adult, T2 adult, T3 child (9 on outbound), T4 child (12 on outbound)
Flight 1: [airline and number], Sat 12 Dec, dep 23:55 [airport A], arr Sun 13 Dec
07:10 [transit airport]
Flight 2: [airline and number], Sun 13 Dec, dep 09:05 [transit airport], arr 14:40 [airport B]
Hotel: [name], 13 Dec to 22 Dec, check-in from 15:00, ref [ref], breakfast included,
local tax payable at the hotel
Transfer: [supplier], 13 Dec, pick-up [time], ref MISSING
=== BOOKING DATA END ===An illustrative reply, trimmed, looks like this.
Day-by-day (all times local)
Sat 12 Dec | Flight 1 departs [airport A] | 23:55 | [ref] | Arrives next day
Sun 13 Dec | Flight 1 arrives [transit airport] | 07:10 | [ref] | Connection 1 h 55 min
Sun 13 Dec | Flight 2 departs, arrives [airport B] | 09:05 / 14:40 | [ref] |
Sun 13 Dec | Transfer to hotel | MISSING | MISSING | Pick-up time and reference missing
Sun 13 Dec | Hotel check-in from 15:00 | 15:00 | [ref] | Local tax payable at hotel
Things to check
- Transit connection is under two hours at a transit airport: confirm the minimum
connection and whether bags are checked through.
- Transfer pick-up time and reference are MISSING.
- Overnight flight: the arrival date differs from the departure date.The second prompt builds the lookup sheet, with the answer columns left blank on purpose. Its job is to make sure no traveller and no transit point is forgotten, and not to know the rules.
From the trip below, build a requirements lookup sheet: one row per traveller code
for each country entered or transited. Columns: traveller | passport issuer
(client to confirm) | country | reason for entry | question to answer (visa or
authorisation? passport validity rule? vaccination certificate? health or entry form?)
| official source | wording copied | checked on | checked by.
Leave the last four columns empty. Do not fill in any requirement.It returns a sheet like the one below, ready for a person to work through. The "official source", "wording copied" and "checked on" cells are the ones that get filled in, one row at a time.
| Traveller | Country | Question | Official source | Wording copied | Checked on |
|---|---|---|---|---|---|
| T1 | Transit country | Visa or authorisation for a connection of under two hours? | [blank] | [blank] | [blank] |
| T1 | Destination | Passport validity rule? | [blank] | [blank] | [blank] |
| T3 and T4 | Destination | Any extra papers for children? | [blank] | [blank] | [blank] |
The third prompt takes the verified sheet and the itinerary summary and drafts the cover email and a one-page "read this first" summary. The same pattern scales to larger parties, which the tutorial on group trip info packs and departure emails covers. At the quoting stage, the travel proposal template tutorial shows how similar booking data flows into a client-ready PDF.
Accuracy checks that catch the expensive mistakes
A pack goes out under your name, so check it with something other than the tool that wrote it. Five checks cover most of the damage.
- Compare the summary with the booking data. Give a second model, or the same model in a fresh chat, the booking data and the finished summary, and ask it to list mismatches only: dates, times, names, references, numbers of nights. A list that comes back empty is a good sign, not proof.
- Remove every requirement line with no source and no date. If a line says what a destination requires and has no URL, wording and date beside it, delete it. This is the check that stops a model's guess becoming a client's plan.
- Do the date arithmetic in a spreadsheet. Take passport expiry against the return date. If the official page says passports must be valid for a set number of months after the date you leave the destination, a formula such as
=EDATE(return_date, 6)gives the date the passport must outlast, and the sheet compares it with the expiry. Six months here is only an example of the kind of rule an official page may state. - Read the overnight and connection lines by eye. "Arrives next day", short connections and late check-ins are the lines models and people misread most.
- Have a second person skim the first ten packs. Two minutes each, looking only for anything that looks odd. After ten clean packs, switch to a sample.
The tutorial on what a travel agent must check before sending an AI itinerary goes deeper on supplier details and routing. Keep the checks in the same sheet as the lookups, so the date and the initials of whoever checked travel with the pack.
A filled-in pack for a family of four with one transit
Back to the family in the prompt: two adults and two children, an overnight outbound flight on Saturday 12 December, a transit connection the next morning, nine nights in one hotel, and a return on Tuesday 22 December. The pack carries these items, and none of them needs a model to invent anything.
- A one-page "read this first" sheet with the three actions: check the booked names against the passports, read the requirements sheet, send the insurance policy number and assistance number.
- The itinerary summary from the first prompt, with the transfer line still marked MISSING until the supplier confirms.
- The requirements sheet, with one row per traveller for the destination and the transit point, each filled in by a person from official sources and dated.
- The checklist groups that apply, with the ticks left blank for the client.
- A contacts page with your out-of-hours number and each supplier's emergency number.
One entry shows why the arithmetic belongs in a sheet. T1's passport expires on 2 March 2027, which is 70 days after the 22 December return. If the destination's official page asks for validity of six months beyond the date the family leaves, the sheet computes 22 June 2027, the check fails, and the client has months to renew instead of finding out at the airport. Had the model been asked "is this passport valid?", it might have said yes.
The time sums, using assumptions you should replace with your own timings: before, about two hours per booking to rekey details, write the email and check by eye, which is 36 hours a month at 18 bookings. After, about 40 minutes: 10 to export and tidy the booking data, 5 for the prompts, 15 for the official-source lookups and 10 for the checks. That is 12 hours a month, so 24 hours saved. The lookups do not shrink, because AI does not make reading an official page faster. It makes the rest of the work consistent, and that is where the gain comes from.
Sending the pack, and what to ask the client to confirm
A pack that no one reads protects nobody, so the cover email asks the client to do three specific things and says when. Here is a template, with placeholders for the details only you know.
Subject: Your travel pack for [destination], leaving [date]
Hi [first name],
Your pack is attached (version 1, [date]). It has your day-by-day summary, a
checklist and a requirements sheet. Three things need you before [date]:
1. Check each traveller's name against their passport. The pack lists the names
as booked.
2. Read the requirements sheet. Each line points to an official source and shows
when we checked it. Rules can change, so please check the linked page again in
the week before you travel.
3. Send us your travel insurance policy number and its emergency assistance number.
If anything looks wrong, reply and we will fix it and send version 2. Our
out-of-hours contact is [number].
[your name]Keep a record of what you sent: the pack version, the date and time, and the address it went to. When something changes, send a new version marked as replacing the old one, and ask the client to discard the earlier file. Two versions in circulation are how a family ends up at the wrong terminal.
How to tell the pack is doing its job
Count four things for the first 20 packs. How many client questions arrive after sending that the pack should have answered, such as "where do we meet the driver?". How many errors your checks caught before sending, and which check caught each. How long a pack takes, against your starting figure. And how many corrections you had to send after the pack went out. My own rule of thumb is to aim for no more than one corrected pack in twenty and to treat any wrong name on a ticket as a process failure to trace to its source, not a one-off. If the same kind of error keeps appearing, fix the prompt or the sheet column behind it, not the single pack.
Once the pack is steady, widen it carefully. Group trips need a rooming list and a shared departure email, which the group-pack tutorial covers. Repeat clients can have their traveller details saved in your booking system, so that each new pack starts with the passport expiry check. Nothing in the process asks a model to know a rule, and everything in it asks a person to read the right page on the right day and write down what it said.
Questions travel agents ask about document packs
Can AI tell me whether a client needs a visa?
No. Entry rules depend on the traveller's passport, the route, the purpose and the dates, and they change. Let AI list the questions to answer, then take the answer from the destination's official source for that passport, copy the wording into your requirements sheet and record the date. That record is what protects you.
How much personal data can I paste into an AI tool?
Use traveller codes (T1, T2) and booking references. Keep passport numbers, card details and medical information in your booking system and merge real names in afterwards. Use a business or API account where training on your content is off by default, and see the tutorial on redacting personal data before sharing.
Should the pack list recommended vaccinations?
Only as pointers. Say which official sources to read and tell clients to see a doctor or travel clinic in good time, then record that you told them. Health advice depends on the traveller, so do not write recommendations yourself unless giving that advice is part of your licensed service.
How often should I re-check entry requirements before departure?
At booking, about a week before departure, and whenever a destination or airline announces a change. IATA's own material says rules and regulations change on a daily basis, so a requirement you checked in September may be out of date in December. Log each check with the date, the source and your initials.
Further reads
- ChatGPT Prompts for Travel Agents: Delays, Cancellations, Refunds — What to send when plans change after the pack goes out.
- Travel Agency CRM: What a Small Agency Needs and Where AI Helps — Keep booking data in one place so packs build from it.
- Travel Agent Commission Tracking: Match Supplier Payments With AI — Match supplier payments once the trips are booked.
- ChatGPT Prompts for Travel Agents: 10 for Quotes and Follow-Ups — Prompts for the quotes that come before the pack.
- Best AI Tools for Travel Agents: Itineraries, Emails and Research — Tools that fit an agent's day, from research to emails.
- AI Chatbot for a Travel Agency: What to Collect Before Hand-Over — Collect traveller details before the hand-over.
- AI Marketing for Travel Agents: A Month of Posts and Emails — A four-week content calendar, a destination fact-check table, a supplier claims check and a four-email sequence for travel agents.
- Travel Agent Follow-Up Emails: Chase Silent Quotes With AI — A three-touch follow-up sequence for travel quotes that go quiet, with sample emails, timing by trip date, reply drafts and clear stop rules.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: IATA's Travel Centre, Timatic and Knowledge Hub pages (passport, visa and health requirement lookups; rules change on a daily basis; travellers are responsible for their documents); WHO's International Health Regulations country list and national health-agency guidance on yellow fever certificates (entry requirements vary and lists can lag); the author's illustrative timings and dates.