Every time carries a time zone.
Admin and money
Build a travel admin checklist from a booking
Extract every deadline, document, dependency and buffer from a booking confirmation, then assign an owner and a latest-start date.
You are turning a booking confirmation into an admin checklist.
Inputs:
- Booking or itinerary: [BOOKING]
- Travellers and documents: [TRAVELLERS]
- Who handles each task: [OWNERS]
Extract and organise:
1. Every date and time with its time zone. Convert to [HOME_TZ] and [DEST_TZ] and label which is which.
2. Every deadline: check-in, cancellation, document submission, insurance activation, prescription refill, renewal, address registration.
3. Every dependency: what must happen before what. Put the chain in order, not just the tasks.
4. A buffer for each connection, appointment and immigration step. State the buffer in hours.
5. A table with: task, deadline, owner, dependency, latest start date, source, risk if missed.
6. The five tasks most likely to be forgotten, and the one that would cost the most to fix late.
Rules:
- Do not give immigration, tax or medical advice. Flag the question and the authority to ask.
- Do not assume a document exists because it usually does. Mark "confirm" where the input is silent.
- Use exact dates and times. "The day before" is not a deadline.
- Keep the time zone on every time. A 23:55 departure is a different day in another zone.
| Variable | What to put there |
|---|---|
[BOOKING] | The confirmation text, including the small print. Cancellation windows and check-in cut-offs are usually there. |
[TRAVELLERS] | Who is travelling and which documents they hold. Do not paste passport numbers; “passport valid to 2029-04” is enough. |
[OWNERS] | Who does what. A checklist with no owner is a list of good intentions. |
[HOME_TZ] | The time zone you plan in. The prompt keeps it separate from the destination time zone. |
[DEST_TZ] | The destination time zone. Connections and check-ins are usually quoted in local time. |
Run it
How to use this template
Paste the full confirmation, not the summary email. The cancellation window is in the part nobody reads.
Fill the owner for every task before you run the prompt. If you leave it blank, the model will invent a “you”.
Put the dependencies in order and check the chain backwards from the departure date.
Put the checklist in the calendar with the latest-start dates, not the deadlines.
Checks
Guardrails before you trust the output
Every task has an owner and a latest-start date.
Missing documents are marked “confirm”, not assumed.
The checklist contains no immigration or medical advice.
Adapt
Variations worth keeping
If the trip has multiple cities
Add a leg-by-leg table and a separate column for the entry rule on each border. Do not assume the rule that applies to the first entry applies to the second.
If someone else is travelling on the same booking
Add a per-traveller column for documents and tasks. Shared bookings hide individual deadlines.
Why this works
A booking confirmation is a legal and logistical document disguised as an email receipt. It contains cancellation windows, check-in cut-offs, baggage rules and sometimes a transit visa warning. Most people read the dates and skip the conditions.
The prompt does the boring part: it turns conditions into tasks, tasks into deadlines, and deadlines into latest-start dates. The last step is the one that matters. A deadline tells you when it is too late; a latest-start date tells you when to begin.
What good looks like
The dependency chain should be visible. “Book the appointment” comes before “collect the document”, which comes before “submit the application”. If the checklist is a flat list sorted by date, ask for the chain.
Time zones are not pedantry. A flight that leaves at 00:20 is often listed on the previous day in the booking system. Put both zones on every time and check the date.
Adapt it to your work
For a long stay, add a column for the permit or registration step and the office that handles it. For a work trip, add a line for the client's time zone and the first meeting after arrival. For a family, add school and childcare deadlines, which often run on a different calendar.
Failure modes
- The model assumes a visa is not needed. It cannot know. Add “state the question and the authority; do not answer it”.
- The buffer is zero. Ask for a buffer in hours and reject “sufficient”. A 45-minute connection is not a plan.
- The checklist has no owner. Every task needs a name, even if the name is “me”.
Related templates
This page is part of the free library.
The prompt is also in the Markdown mirror at
/prompts/booking-admin-checklist.md. If the scenario is close but not right, send the gap to the help desk with the output you expected.
Found a gap in the library?
Send the scenario, the prompt that failed, or the harness change that broke your setup. The help desk takes questions and corrections from humans and agents, and every accepted fix updates the page date.