2026-10-09 · 9 min read
A free vacation planner template built around seven blocks — trip overview, transport, lodging, day-by-day plan, budget, packing, and notes — tested against the structures used by Canva, Jotform, and 101 Planners, plus a worked Lisbon example and a business-travel variant.
Most of Cusco's points of interest run on one bundled ticket system, not pay-as-you-go gates. Here's what the Boleto Turístico covers, what it leaves out, and how to pace the altitude.
Resonance ranks London first, Time Out ranks Porto second, Travel + Leisure's readers pick Florence. None of them are wrong — they're measuring different things. Here's how to build a shortlist from all three, plus what July actually costs in heat and crowds.
By Clara Mendes, Fortrip's travel planning editor, who has rebuilt this seven-block structure across road trips through the Mountain West and city itineraries in Lisbon, Tokyo, and Porto. More of her itinerary breakdowns and planning write-ups are archived on Fortrip's blog.
Compared against templates from Canva, Jotform, and 101 Planners, plus the generic Google Sheets and Word formats that circulate on travel forums, to find the structure that recurs across all of them.
A template with twelve empty columns looks thorough on a laptop screen and becomes impractical on a phone in an airport line. Our working rule, after comparing the templates above: if a block takes longer to fill in than it takes to order a coffee, it stops getting used after the first day. That's an editorial heuristic from testing these formats on actual trips, not a measured statistic — but it's the design constraint that separates a template people keep updating from one they abandon.
Readers searching for a vacation planner template, a trip schedule template, or a sample trip itinerary are almost all asking for the same structure, just under different names. The seven blocks below are the ones that show up — in some order, under some label — across Canva, Jotform, and 101 Planners closely enough to treat as a reasonable default.
| Block | What goes in it | Why it matters |
|---|---|---|
| Trip overview | Dates, destination, number of travelers, emergency contact, passport or ID numbers | Fill this in first; it's the block you need if a document gets lost. The U.S. State Department's international travel guidance recommends carrying copies of ID and passport numbers separately from the originals — this block is where that copy lives digitally. |
| Transportation legs | One row per leg: carrier, confirmation number, departure time, arrival time, terminal | A rebooked flight means editing one row, not rewriting a paragraph |
| Accommodation | Check-in/check-out times, address, booking reference, cancellation deadline | Keeps every detail in one line instead of scrolling back through a confirmation email at 11 p.m. |
| Day-by-day plan | Morning, afternoon, evening rows, each with time, activity, location | Three short rows per day read better on a phone than one long paragraph that turns into a wall of text by day four |
| Budget tracker | Planned cost and actual cost, adjacent columns, per category | Overspending shows up the day it happens, not on the flight home |
| Packing list | Grouped by category (documents, electronics, clothing, toiletries) with checkboxes | Works better on its own tab so it doesn't clutter the daily plan |
| Notes | One catch-all row per day for hours, reservations, cancellation windows | Covers things like "museum closed Mondays" before you're standing outside a locked door |
The day-by-day block is the one most templates get wrong, usually by collapsing all three day-parts into a single free-text cell. Splitting morning, afternoon, and evening into separate rows is a small change that keeps the whole sheet legible past day three. Once the blocks are filled in, running the plan through an itinerary validator catches opening-hours and travel-time conflicts before they turn into a locked gate at 9 a.m.
The times below are illustrative, meant to show how the day-by-day block fills in — not live booking confirmations. Always check current hours directly, for instance on the Jerónimos Monastery site, before building a real schedule around them. Time-of-day labels are used consistently here (Morning, Midday, Afternoon, Evening), with any specific clock times moved into the Note column rather than mixed into the Time column.
| Day | Time | Activity | Location | Note |
|---|---|---|---|---|
| 1 | Midday | Arrival | Humberto Delgado Airport | Flight lands around 11:40; check-in target by mid-afternoon at an Alfama guesthouse |
| 1 | Evening | Dinner | Mouraria | Reservation suggested |
| 2 | Morning | Jerónimos Monastery | Belém | Confirm opening hours before the visit |
| 2 | Afternoon | Tram 28 ride | Graça | — |
| 2 | Evening | Fado show | Alfama | Many venues close reservations a few hours before showtime; confirm directly with the venue |
| 3 | Morning | Train to Sintra, then Pena Palace | Rossio station / Sintra | Train departs around 09:15 |
| 3 | Afternoon | Quinta da Regaleira | Sintra | Return train in the early evening |
| 4 | Morning | LX Factory market | Alcântara | Free block |
| 4 | Midday | Checkout | Alfama guesthouse | Target around 11:00 |
| 4 | Afternoon | Airport transfer | — | Build in buffer ahead of departure |
The same seven blocks scale to ten days or three weeks — only the row count in the day-by-day table changes, not the structure. If you'd rather have this scaffolding generated around real opening hours and transit times instead of typed row by row, the AI trip planner builds the same table from a destination and date range.
A business travel itinerary template needs different fields, not just a different title. Swap out the sightseeing blocks rather than bolting extra rows onto a vacation template.
| Vacation block | Business replacement |
|---|---|
| Day-by-day sightseeing | Meeting blocks: time, attendee names, room or video link, objective |
| Budget per category | Expense line with a cost center or project code column, so the sheet doubles as a reimbursement reference |
| Restaurant reservation list | Client contact list: name, title, phone, preferred meeting location |
| (no equivalent) | Time zone listed next to every meeting time, when the trip crosses more than one zone |
The time zone column deserves its own line: on a multi-city work trip, it's the single field most likely to prevent a missed call, since a meeting block without it reads the same whether it's local time or the time zone three stops back.
| Tool | Use it when |
|---|---|
| Wanderlog / TripIt | A trip has enough bookings — roughly half a dozen or more confirmation emails — that automatic parsing saves real re-typing. Both tools are built around forwarding booking emails to an address that assembles the itinerary automatically, which is the reason to pick either one once a trip has more than a few reservations. |
| Google Sheets | The itinerary needs to be shared with someone who won't download an app, or printed at a hotel business center the night before a flight |
| ClickUp | Several travelers are coordinating assigned tasks — booking a car, confirming a restaurant, picking up tickets — rather than reading a shared schedule |
| Citymapper / Maps.me | Day-to-day navigation inside a city, as an addition to the itinerary document, not a replacement for it |
None of these tools replace the table above. They either generate it automatically from forwarded bookings or help navigate once it's built.
Canva, Jotform, and 101 Planners offer drag-and-drop templates that export to PDF directly, useful when design matters as much as content — a trip printed as a keepsake, or shared with a group.
The faster route for most people: build the table in Google Docs or Word, then use File → Download → PDF. One day per printed page, on A4 or 8.5x11, was the default across the three drag-and-drop sites reviewed here — Canva, Jotform, and 101 Planners — and it matches how people actually reference the document while traveling, one day at a time, not the whole trip at once.
Before filling in any day-by-day rows, cluster every planned stop on a map and group nearby ones into the same two-to-four day block. Date-sequencing a trip before grouping it geographically is what causes zigzag routes.
A Southwest road trip clustered correctly runs Las Vegas → Zion → Bryce Canyon → Grand Canyon South Rim → Sedona, each leg a manageable drive, instead of backtracking across the same highway twice because stops were added in the order they were thought of rather than the order they sit on a map.
For round-the-world itineraries, group by continent first, then by sub-region, and only then assign specific dates. This geographic-first step is what separates a usable "usa road trip planner" or "round the world trip planner" from a list of cities with no route logic between them.
Fortrip's planning flow builds this grouping step in by default, so the day-by-day blocks above come out clustered by distance rather than needing to be re-sorted by hand. For details on what's included if you'd rather have the tool generate the table than build it from scratch, see pricing.
What are the seven blocks in a vacation planner template? It comes down to what a document needs to survive a real trip: identifying details up front (trip overview), a leg-by-leg transport log, lodging references, a day split into three short time blocks instead of one paragraph, a side-by-side budget column, a packing list kept off the daily tab, and a notes row for the kind of hour-specific detail — a Monday closure, a 24-hour cancellation window — that otherwise gets forgotten until you're standing in front of it.
Should I use a spreadsheet or a travel app to plan my trip? The deciding factor is booking volume, not personal preference for apps versus sheets. Past roughly six confirmation emails, auto-parsing tools stop being a novelty and start saving real re-typing. Below that threshold, a shared Sheet or Word doc that doesn't require anyone to install something is usually the faster path, especially when a parent or a printer at a hotel desk is involved.
How do I turn my itinerary into a PDF? If the table already exists in Docs or Word, exporting it is a one-step File → Download → PDF action. The drag-and-drop templates from Canva, Jotform, or 101 Planners are worth the extra setup time only when the document itself needs to look designed — for a keepsake or a group hand-out — rather than just function as a reference.
How is a business travel itinerary different from a vacation itinerary? The swap isn't cosmetic. Sightseeing rows become meeting blocks with attendees and an objective field, the budget tracker picks up a cost-center column so it can double as an expense reference, and a time zone field sits next to every meeting time once the trip crosses more than one zone — the single addition most likely to prevent a missed call.
How many stops should I plan per day? Three is the practical ceiling for a single day's rows — morning, afternoon, evening — before the entry turns into a paragraph that's hard to scan on a phone. For longer trips, the harder constraint is sequencing: group stops by geography into two-to-four day clusters first, then assign dates, or the route ends up zigzagging regardless of how many rows are used per day.
It comes down to what a document needs to survive a real trip: identifying details up front (trip overview), a leg-by-leg transport log, lodging references, a day split into three short time blocks instead of one paragraph, a side-by-side budget column, a packing list kept off the daily tab, and a notes row for the kind of hour-specific detail — a Monday closure, a 24-hour cancellation window — that otherwise gets forgotten until you're standing in front of it.
The deciding factor is booking volume, not personal preference for apps versus sheets. Past roughly six confirmation emails, auto-parsing tools stop being a novelty and start saving real re-typing. Below that threshold, a shared Sheet or Word doc that doesn't require anyone to install something is usually the faster path, especially when a parent or a printer at a hotel desk is involved.
If the table already exists in Docs or Word, exporting it is a one-step File → Download → PDF action. The drag-and-drop templates from Canva, Jotform, or 101 Planners are worth the extra setup time only when the document itself needs to look designed — for a keepsake or a group hand-out — rather than just function as a reference.
The swap isn't cosmetic. Sightseeing rows become meeting blocks with attendees and an objective field, the budget tracker picks up a cost-center column so it can double as an expense reference, and a time zone field sits next to every meeting time once the trip crosses more than one zone — the single addition most likely to prevent a missed call.
Three is the practical ceiling for a single day's rows — morning, afternoon, evening — before the entry turns into a paragraph that's hard to scan on a phone. For longer trips, the harder constraint is sequencing: group stops by geography into two-to-four day clusters first, then assign dates, or the route ends up zigzagging regardless of how many rows are used per day.

Sketch a brief. We come back with an itinerary that reads like a recommendation, not a checklist — and tell you what we’d change about it.
Try planning free