As someone who’s obsessed with organizing, I find traveling is the one thing I don’t want to over-plan for myself. I want to enjoy it and just go with the flow.
And by “go with the flow,” I mean the itinerary. The packing list, emergency contacts, and other practical details? That’s a different story. I guess I’m an EA for a reason. 😂
When I plan a trip for someone else, I start with a few questions.
- What do they need to know before leaving?
- What will they look for after landing?
- How can I organize the details so they don’t have to keep asking?
That’s the idea behind this portfolio project: a Google Sheets travel planner for Alex, a fictional executive flying from New York to Seoul for two business meetings. Explore the travel planner demo here.
The traveler, bookings, and payments are all simulated. I built it as a template, so the same structure can be customized for any traveler.
Thinking about what happens in between
I start with the main parts of the trip: flights, accommodation, and the daily itinerary. Then I look at what happens between them.
A flight’s arrival time isn’t the time someone is ready for a meeting. Alex’s flight lands at 5:30 PM, but after allowing time for immigration, baggage, and the ride into the city, his planned hotel arrival is 8:30 PM. So the next day is a protected recovery day with no meetings, and both meetings happen on Thursday, after he’s had time to rest.
The time difference adds another detail. For this itinerary, Seoul is 14 hours ahead of New York, so a flight that leaves on Monday lands on Tuesday. It also means Alex’s 2 PM partnership meeting happens at midnight in New York. Instead of a late-night call, the NYC team gets a written recap.
The schedule has to make sense for the person following it. Having enough time to get somewhere matters just as much as knowing where to go.
Built to be reused
The file has 12 tabs, and each one has a clear purpose:
- Start Here: the traveler’s preferences, trip summary, and contingency plans for a flight delay, a cancelled meeting, or an emergency.
- Schedule: the itinerary, flight details, and meeting briefs.
- Preparation: a pre-travel checklist, a reservation tracker, and a packing list.
- Reference: a time zone guide, emergency contacts, apps to download before departure, the budget, and sources.
Hopefully the traveler never needs the emergency details, but they should be easy to find if they do.
The checklist is color-coded by owner: one color for Alex, one for me, and one for tasks we share. At a glance, you can see who needs to do what, whether it’s Alex testing his eSIM or me confirming a transfer. Nobody has to ask, “Is this on me or on you?”
The reservation tracker lists every booking with its change and cancellation terms. The checklist even schedules a check before the free-cancellation windows close, so there’s time to catch a problem while it’s still cheap to fix.
Because every tab has a clear purpose, the whole file works as a template. For the next trip, I keep the structure, swap in the new traveler’s details, and adjust the tabs to what they need.
It depends on the traveler
Every traveler is different. Some want every detail laid out. Others only want the essentials. Someone might prefer a certain flight time, need specific food options, or want more breathing room between meetings.
For this demo, I gave Alex a specific set of preferences and built the schedule around them. He prefers window seats and a quiet hotel room, avoids seafood as a food preference, and wants a recovery day with no late work calls. Those details shaped the whole schedule.
For a real trip, that’s why I ask first. The template gives me the structure, and the traveler’s answers shape the rest.
Takeaway: Plan for the person, not just the trip.