The thesis, stated up front.

I have read more travel itineraries than I would care to admit, and the trend is bad. The same itinerary that fit on an index card in 2008 now lives in a Google Doc with twelve tabs, an attached Notion database, a Pinterest board for the aesthetic, and a shared Apple Note that no one updates. The trip itself does not get longer. The plan does. This article is the case for shrinking the plan back to two pages and treating everything else as either research (separate document, opened before the trip) or field notes (separate document, opened during the trip). Two pages is not a stylistic preference; it is the constraint that forces you to decide what the trip is actually about. Without that constraint, planning becomes an unbounded activity that fills available time without producing a plan.

What page one is for.

Page one is the geographic spine. Three columns, one row per location: city, nights, transit out. That is the entire page. No descriptions, no commentary, no aspirational lines about how you hope the morning in Lisbon will feel. The page is doing one job — it is telling you, and your traveling companions, where the body will be on each day of the trip, and how it will get to the next place. If page one cannot answer that question in 11-point type without scrolling, then the trip is overstuffed, and the constraint has just told you that. Listen to it. Cut a city. Add a night somewhere. Adjust the transit so the rail leg is not a four-hour connection that requires a dawn departure. Page one is a decision document. It is not a feeling document. The feeling documents go elsewhere.

I have watched smart people resist this. They want page one to also list the boutique hotel they are excited about, the lunch place near the station, the museum that closes at three on Tuesdays. Those things matter, but they do not belong on page one, because they are not load-bearing for the spine. Putting them on page one obscures the answer to the only question page one is supposed to answer (where will you be), and the cost is real. I have seen itineraries where the spine is buried under three paragraphs of restaurant notes, and the traveler shows up in Bologna having lost track of which night they are flying out — because the load-bearing information was not visible at a glance.

What page two is for.

Page two is the anchors. An anchor is anything that has a fixed time and a confirmation number. The dinner you booked four months ago. The timed-entry ticket to the Galleria Borghese. The single train per day that connects two of your cities. The one experience per stop that justifies your having gone to that stop in the first place — the cooking class, the studio visit, the morning walk with the guide. Anchors are operational. They tell you what cannot move. Everything else on the trip can flex around them, and most of the trip should flex, because flexing is where the good moments come from. The anchors give the trip its skeleton; the unstructured time is the muscle.

Note what is not on page two. Restaurants without reservations. Neighborhoods you want to see. Shops you read about in a Substack. Coffee places. Walking routes. None of this is on page two, because none of it is anchored, and adding it dilutes the page until it stops functioning as a constraint and starts functioning as a wish list. (A wish list is fine. I keep wish lists. They live in a separate file called field notes, and I open them only when I am in the city, never before.) Page two is for things you have already committed to. The discipline of writing only commitments on page two is what separates the plan from the dream.

The Google Doc with twelve tabs.

I want to address the most common objection directly. The traveler who has already invested fifteen hours in a maximalist Google Doc — twelve tabs, color coding, embedded maps, sub-tabs for restaurant alternates — feels strongly that this represents real planning. It does not. It represents research, which is a different activity. Research is collection. Planning is commitment. The maximalist doc is what you do when you are not yet ready to commit (the cities are still negotiable, the nights per stop have not been fixed, the airline tickets are unbought). It is a holding pattern. The two-page rule forces you out of the holding pattern, because to fill page one you have to decide which cities are in and which are out, and to fill page two you have to make the bookings that turn intentions into anchors.

This is the part that is uncomfortable. Most over-long itineraries are over-long because the traveler has not, in fact, decided. They are still researching. They feel prepared because the document is thick, but the document is thick because the decisions have not been made. The gap between feeling prepared and being prepared is exactly the gap between the twelve-tab doc and the two-page itinerary. You can be on the wrong side of that gap for a long time. The two-page rule is the move that gets you across it.

Notion templates and why they fail.

A brief detour, because the question comes up. Notion travel templates — the elaborate ones with database views and linked pages — fail for the same reason the Google Doc fails, and worse. The template's structure is generic. It assumes every trip has the same shape, the same set of fields, the same hierarchy of information. Trips do not have the same shape. A two-week Italy circuit does not need the same fields as a four-day Mexico City weekend, and forcing them into the same database produces a plan that fits the database rather than the trip. The two-page rule is the opposite move. The constraint is fixed (two pages), but the contents are entirely yours to choose. The page conforms to the trip, not the other way around.

The other failure mode of Notion templates is more subtle. They optimize for completeness, which feels like quality but is not. A complete database — every restaurant filled in, every neighborhood tagged, every transport option captured — produces a sense of mastery during planning that does not survive contact with the trip itself. On day three, when you are actually in Florence, you will not consult a Notion database with thirty-two filtered views. You will look at one document and decide what to do next. Make that document the right document. Two pages.

The concession.

Here is the counterargument I will grant. For a complex multi-country trip — six weeks, three continents, a dozen domestic flights — two pages is not enough to hold the spine, and pretending otherwise produces a page one in five-point type that no one can read. Fine. The rule still applies, recursively. Two pages for the master spine (regions, not cities, with the cross-region anchors). Then two pages per region as a sub-itinerary, each kept separate, opened only when you are in that region. The pattern scales. What does not scale is the impulse to put everything in one document. The discipline of separation is the durable part.

How to actually write it.

The mechanics are unglamorous. Open a document. Set print layout. Set the page count to two. Build page one as a three-column table — city, nights, transit out — and adjust the rows until they fit. Build page two as a list, organized by city, with the anchors and confirmation numbers. Print both. Read them as one document. If they do not reconcile (page two demands you be in Florence on a day page one has you in Rome), one of them is wrong. Fix it now. This is the moment the two-page rule earns its keep. The reconciliation step is the planning, in the active sense. Everything before it was preparation; everything after it is logistics. When the two pages reconcile, planning is done. Close the laptop.

I will say one more thing about the close-the-laptop part, because it is the part most people skip. The two-page rule has a second function beyond producing a clean plan. It tells you when planning is over. The marginal hour you spend reading the eleventh blog post about Lisbon, after the two pages reconcile, is not planning. It is consumption. There is nothing wrong with consumption, but it should not be confused with preparation. When the two pages are done, the plan is done. The rest is waiting for the trip to start.

Six questions, briefly answered.

Why two pages and not one?

One page collapses the where and the what into the same plane, which is how single-page itineraries become aspirational mood boards. Two forces a separation, and the constraint is the point.

What goes on page one?

City, nights, transit. Three columns. No commentary.

What goes on page two?

The anchors with confirmation numbers and the one experience per city. That is it.

What about the Google Doc with twelve tabs?

It is research, not an itinerary. Different objects, different purposes, different documents.

Does the rule work for long trips?

Yes, recursively. Two pages for the master spine, two pages per region for the sub-itineraries.

What about restaurants and neighborhoods?

Field notes. Separate document. Opened only when you are in the city.