Travel Planning Rules

A trip plan built activity-by-activity from day one collapses the moment one booking changes — plan anchors first, then fill the gaps around them, so the whole itinerary doesn't need a rebuild every time one piece moves.

Anchor bookings first

• Lock the immovable pieces first: flights, hotel check-in/out dates, any pre-paid or time-fixed reservation (a show, a tour with limited slots, a restaurant that only takes one seating). These are the skeleton everything else hangs on.
• Don't book anything flexible (a museum visit, a casual meal, a walk through a neighborhood) before the anchors are set — flexible items should fill gaps between anchors, not compete with them for a time slot.
• Re-check anchor bookings against each other before adding anything else: does the hotel check-in time actually work with the flight arrival, is there enough transit time between two anchors on the same day. Catching a conflict here is cheap; catching it after building a full itinerary around it is not.

One plan document

• Keep exactly one document per trip with: dates, all confirmation numbers, all addresses (hotels, key venues), and the day-by-day skeleton. Scattered confirmation emails across a dozen threads is how a trip loses a reservation at the worst moment.
• Structure it day-by-day, not category-by-category — a "flights" section and a "hotels" section and an "activities" section forces you to reassemble the actual day yourself, exactly when you need it assembled for you (in transit, tired, on a phone).
• Update the single document immediately when anything changes — a flight time shift, a cancelled reservation. A plan document that's out of sync with reality is worse than no document, because it's trusted by default.

Realistic daily pacing

• Cap most days at 2–3 real anchors (a major sight, a meal reservation, a booked activity) — a day with six planned items looks efficient on paper and is unworkable in practice once you account for transit, lines, and being human.
• Account for actual transit time between activities using real distances, not straight-line optimism — "it's only 2km" ignores the terrain, the crowd, and the fact you're not walking at a commuter's pace on vacation.
• Build at least one deliberately unscheduled block per day, even short — a trip with zero slack turns any single delay (a late train, a long line) into a cascading failure across the rest of the day.
• Don't schedule a demanding day immediately after a long travel day (overnight flight, long drive) — arrival days should have a light plan by default, not the trip's most ambitious itinerary.

Buffer time

• Add buffer before anything time-fixed: a flight, a timed-entry ticket, a reservation. Buffer absorbs the transit delay, the line, the wrong-turn — without it, the first minor hiccup of the day cascades into missing something that can't be rebooked.
• Buffer connections between flights or trains more generously than the minimum legal connection time, especially for international connections or unfamiliar airports/stations — the minimum is a floor, not a plan.
• Leave a full buffer day with no anchors at all on trips longer than about a week, positioned mid-trip if possible — it absorbs whatever has gone wrong so far and prevents fatigue from compounding into the back half of the trip.

Packing by scenario, not by item count

• Build the packing list around the actual scenarios the trip contains (business meeting, hiking day, formal dinner, beach day), not a generic checklist copied from a template — a generic list both over-packs for scenarios that don't apply and misses ones that do.
• For each scenario, list the complete outfit/gear needed, then dedupe across scenarios afterward — this catches gaps (nothing for the one formal dinner) that a flat item-count list won't surface.
• Separate "pack" from "buy there" explicitly for anything bulky, restricted, or cheap to replace at the destination — deciding this in advance avoids both overpacking and last-minute scrambling.
• Reuse the same packing list structure across trips, but re-derive the scenario list per trip — the scenarios change every time even when the list format doesn't.

Offline copies

• Save offline (screenshot or downloaded PDF, not just an email you need signal to open) every: boarding pass, hotel confirmation with address, and the single plan document itself. Connectivity fails exactly when you need these most — border crossings, transit, unfamiliar areas.
• Keep a photo of key documents (passport info page, travel insurance card, any visa) stored offline and separately from the physical originals, so losing the physical document doesn't also mean losing the reference.
• Share the plan document (or at least dates and hotel addresses) with one person not on the trip — a completely undocumented itinerary with no outside visibility is a real risk, not just an inconvenience, if something goes wrong.