Two years ago in Porto, I watched a couple in the train station miss the regional service to the Douro Valley because they were scrolling through a 14-tab Notion planner trying to remember which platform they needed. The information was in there somewhere. It just wasn’t anywhere they could glance at it with a backpack on and a train leaving in ninety seconds.
That’s the problem with most travel planning. People build elaborate digital cathedrals and then can’t find the door. After a decade of organizing my own trips and helping friends format theirs, I’ve landed on a single, boring-but-reliable solution: a tourist travel itinerary template that fits on one printed page per leg of the trip, lives in your travel wallet, and never needs a signal or a battery.
This post walks through the exact format, a fully worked example you can copy, and the mistakes that quietly ruin otherwise good plans.
Why one page beats the mega-planner
I love a detailed planning doc. I build them too. But there’s a difference between the planning artifact (where you research and decide) and the execution artifact (what you actually use on the ground). Most people only build the first and then drag a phone full of it through a foreign train station.
A one-page itinerary forces ruthless prioritization. If it doesn’t fit, it isn’t load-bearing for that day. That constraint is the feature, not the bug.
Here’s the honest trade-off:
| Format | Best for | Falls apart when |
|---|---|---|
| Multi-tab digital planner (Notion, Google Sheets) | Research, group collaboration, comparing hotels | You’re offline, rushed, or hands are full |
| One-page printed sheet (per leg) | On-the-ground execution, fast glances, no battery | Plans change hourly and you need live edits |
| Phone notes app | Quick reference, links | Glare, dead battery, doom-scrolling, accidental edits |
| Dedicated app (TripIt, Wanderlog) | Auto-importing confirmations | Roaming costs, app fatigue, over-notification |
My actual workflow uses two of these: I research in a Google Sheet, then I export the decisions into the one-page format and print it. The sheet is the kitchen. The page is the plate.
The anatomy of the one-page itinerary
The whole template is built around the idea that you’ll glance at it, not read it. Every section earns its place by answering a question you’ll have at a specific, predictable moment.
Use one page per base location (the city or town you’re sleeping in), not per calendar day. A 10-day trip across three cities = three pages. This keeps day-trips and logistics grouped where they actually live.
Each page has six blocks:
1. The header strip
One line, top of the page:
LISBON · Nights 1–4 · Apr 12–15 · Hotel: Lisbon Story GH (Rua dos Fanqueiros 24)
That’s your anchor. The hotel address is here because it’s the one thing you’ll show a taxi driver or type into a maps app most often. Don’t bury it.
2. The “arrival logistics” box
This solves the worst-feeling moment of any trip: stepping off a plane or train into a new city with no plan. Three lines:
- How I get from the station/airport to the bed, with the specific option and rough cost.
- What time check-in is and what to do if I arrive early.
- Local SIM / wifi plan if relevant.
Example: Airport → Aeroporto metro (red line) → change at Alameda to green line → Rossio. ~€1.80, 25 min. Bag drop available before 3pm check-in. And critically, a fallback for the worst case: if you land after roughly 1am, the metro has stopped — the Aerobus line 1 runs into the small hours toward the city center, and Bolt/Uber are usually quick from the rank outside arrivals (~€12–15). Write the late-night option down even if your flight is scheduled for midday; flights slip.
3. The day-by-day grid (the heart)
This is the part people overcomplicate. Resist hour-by-hour scheduling — it makes you feel like you failed by 10am. Instead, use three time blocks per day: morning, afternoon, evening. One or two anchors per block, max.
DAY 1 (Sat)
AM Alfama wander + São Jorge Castle (buy ticket online, ~€15)
PM Lunch Time Out Market → tram 28 (board early, ~11am crowds)
EVE Fado dinner, Bairro Alto (Mesa de Frades — book ahead by phone
or Instagram DM, late seating, arrive 8:30)
Anchors, not minute-by-minute. The gaps are where the trip actually happens.
4. The “must-book / time-sensitive” callout
A boxed list, visually separated, of anything with a clock attached: timed-entry tickets, restaurant reservations, a train you’ve already paid for. This is the stuff that costs money or causes panic if missed.
5. Quick reference footer
Tiny font, bottom of the page:
- Emergency number (112 in the EU)
- Your hotel’s phone
- One backup restaurant near the hotel (for the night a plan collapses)
- A note like “Sundays: many shops closed, museums free until 2pm”
6. Budget tracker (optional, right margin)
A skinny column with a rough daily spend target and three blank lines to pencil in actuals. If you’re trying to hit a budget, writing “€85 / day” where you’ll see it does more than any app notification.
A fully worked example: 4 days in Lisbon
Here’s a complete one-page Lisbon plan in the actual format. Costs are rough 2024-era ballparks — verify before you go, but they’re realistic for planning.
LISBON · Nights 1–4 · Hotel: Lisbon Story GH, Rua dos Fanqueiros 24
ARRIVAL: Airport → Metro red line → Alameda → green line → Rossio (€1.80, ~25 min). Late arrival (after ~1am, metro closed): Aerobus 1 to center, or Bolt/Uber ~€12–15. Check-in 3pm, bag drop OK earlier.
MUST-BOOK (do before trip):
– São Jorge Castle timed ticket (~€15)
– Belém: Jerónimos Monastery online ticket (~€12, skip the 45-min line)
– Pastéis de Belém — no booking, but go before 10am or after 5pm
– Day-trip: Sintra train (no reservation, Rossio→Sintra, ~€2.40 each way)
– Mesa de Frades fado dinner (book ahead; small room, one late seating)
| Day | AM | PM | EVE |
|---|---|---|---|
| 1 Sat | Alfama + São Jorge Castle | Time Out Market lunch, tram 28 | Fado, Bairro Alto |
| 2 Sun | Belém (monastery, pastéis, tower) | LX Factory — Sunday market (the reason to do Belém today) | Cais do Sodré dinner |
| 3 Mon | SINTRA day trip (Pena Palace + Quinta da Regaleira) | back ~5pm | Rest / Príncipe Real |
| 4 Tue | Gulbenkian Museum | Last-minute shopping, Rua Augusta | Sunset Miradouro da Senhora do Monte |
SINTRA NOTES: Catch 8:30am train (Pena gets mobbed by 11). Bus 434 loop or walk uphill (~30 min, steep). Buy Pena ticket online. Budget the whole day — don’t try to add Cascais unless you skip Regaleira.
FOOTER: Emergency 112 · Hotel +351 21 xxx xxxx · Backup dinner: A Merendeira (near hotel, late hours) · Sun: museums often free until 2pm.
BUDGET: Target €90/day food+sights. ___ / ___ / ___ / ___
That’s it. Everything you need for four days on one sheet. Notice the LX Factory entry: it’s pinned to Sunday on purpose, because that’s when the open-air market under the bridge runs — schedule it any other day and you get a quieter, half-empty version of the same place. That’s exactly the kind of detail a one-pager should carry: not “visit LX Factory,” but why this day.
Notice too what’s not there: no GPS coordinates, no opening hours for every site, no “Plan B options 1 through 5.” If I need that depth, it’s in the planning sheet I left at the hotel.
Insider tips a beginner wouldn’t know
Print two copies and split them up. One in your day bag, one in your luggage. If a bag gets stolen or lost, you’re not starting from zero. This sounds paranoid until it happens once.
Put the day of the week next to the date, always. “Day 3” means nothing when you’re tired. “Mon” instantly tells you the Picasso Museum is closed, the market’s quieter, and the restaurant you wanted needs no reservation. Half your logistics are downstream of which day it is.
Write transit in the direction you’ll travel it. Don’t note “Rossio–Sintra line.” Note “Rossio → Sintra, platform 4-ish, 8:30am.” You read it under pressure; make it match the moment.
Leave one block fully empty per city. Label it OPEN. The best afternoon of my Lisbon trip was an unplanned three hours in a Graça café because the schedule had room. An over-stuffed page guarantees you’ll either fall behind or never sit still.
Use a fixed icon for “costs money / pre-paid.” A simple € or ★ next to timed tickets means your eye finds the panic-items instantly. On the morning of a timed entry, you scan for the symbol, not the prose.
Anchor day-trips to the early train, not the activity. The single biggest determinant of whether Sintra, Cinque Terre, or a Tokyo-to-Nikko day works is what time you leave. Put the departure time in bold and let everything else flow from it.
Match your paper to your wallet. I print on A5 (half a sheet) or fold A4 into a passport-sized travel wallet. If it doesn’t physically fit where you’ll keep it, you won’t carry it, and an itinerary you don’t carry is decoration.
Common mistakes (the non-obvious ones)
Scheduling by the hour. “9:00 castle, 10:30 market, 11:45 tram.” You will be 40 minutes behind by lunch and feel like the day is broken. Travel runs on blocks, not appointments. Reserve exact times only for things with actual tickets attached.
Packing every meal with a reservation. Two booked dinners across four nights is plenty. Over-reserving locks you into neighborhoods far from wherever you actually end up at 7pm, and you’ll eat worse, not better. Leave room to follow a good smell.
Listing opening hours for everything. It bloats the page and goes stale. Instead, only flag the exceptions — the place that closes Mondays, the museum with a weird lunch break. Assume normal hours; annotate the surprises.
Putting day-trips on their own page. A day-trip belongs on the page of the city you sleep in, because that’s where the train station, the left-luggage, and your bed are. Separating it creates orphaned logistics.
No “collapse plan.” Trips go sideways — rain, a stomach bug, a closed attraction. The footer’s backup restaurant and the OPEN block are your shock absorbers. Plans without slack don’t survive contact with reality.
Confusing the planning doc with the field doc. This is the meta-mistake that causes all the others. Your 30-tab research file is great — for the couch. The thing in your pocket needs to be smaller than you think.
How to actually build and print it
You don’t need fancy tools. The format is just a one-page table — here’s the exact structure to recreate in Google Docs (the easiest path) or any spreadsheet:
- Row 1 — header strip: a single merged cell with
CITY · Nights · Dates · Hotel + address. - Row 2 — arrival box: one cell, three short lines (transit-to-bed, check-in time, late-night fallback).
- Row 3 — must-book callout: a bordered cell, bulleted list, each pre-paid or timed item prefixed with
€or★. - Rows 4+ — the day grid: a four-column table (
Day | AM | PM | EVE), one row per day, one or two anchors per cell. - Footer cell: emergency number, hotel phone, backup restaurant, day-of-week exceptions.
- Optional right margin: a skinny one-column budget tracker with blank actuals.
My actual setup is the spreadsheet version: I build the research in Google Sheets, then keep one tidy tab formatted exactly as above — research and field doc in one file, two faces. I print just that tab.
Print settings that matter: Set scaling to “Fit to page,” uncheck headers/footers (you don’t need the URL printed), and use “black and white” if your hostel printer is moody. Save the final as a PDF on your phone too — belt and suspenders, so you have it offline even if the paper gets soaked.
When to not use one page
Honesty time. The one-page format is wrong for a few situations:
- Slow travel / one base for two weeks. If you’re posted up in Oaxaca for a fortnight with loose plans, a page of structure is overkill. A short list of “things to maybe do” beats a grid.
- Complex group logistics. Six people, separate flights, shared rentals — you need a collaborative live document, and the printout is just a summary.
- Heavily reservation-driven trips (think a Japan rail itinerary with seat reservations on six shinkansen). You’ll still want the printed page, but it’ll lean almost entirely on the must-book box, and you may need one page per day, not per city.
Use the one-pager when your trip has real movement and real anchors. Lean on a list when it doesn’t.
Your actionable takeaway
Open a blank Google Doc right now. Make a one-page table with the six blocks above: header strip, arrival logistics, a morning/afternoon/evening grid, a boxed must-book list, a quick-reference footer, and an optional budget column. Fill it for your first city only — don’t try to do the whole trip tonight.
Then print it on A5, fold it into your wallet, and notice how much lighter your planning brain feels when the load-bearing details are on paper instead of buried under fourteen tabs. Build the rest of the pages the same way, one base location at a time — whether your trip is a Lisbon long-weekend, a Tokyo-and-day-trips week, or a multi-stop South America loop, the format holds. The mechanics are identical everywhere; only the anchors change.
The trip you can hold in your hand is the one you actually enjoy living. Build the first page tonight, and you’ll never go back to scrolling through tabs on a station platform with a train pulling away.
