How to create a travel itinerary in Google Docs

By HankDevZ · Updated August 8, 2026

Google Docs is already on every device you own, it shares with one link, and it costs nothing — which is why so many trips get planned in one. This is the build guide: how to lay out a travel itinerary in Docs starting from an empty document, which settings to change before you start typing, and the one step almost every other guide leaves out.

If you would rather not type it out at all, the travel itinerary template for Google Docs covers the other route — build the plan elsewhere and paste a finished table in. This page assumes you are building it by hand.

Decide what each row holds before you open Docs

The mistake that costs the most time is inserting a table first and discovering on day three that it is missing a column. Adding one to a Docs table means widening every row you have already filled in. Settle the columns first.

A trip row needs seven fields:

Notice what is not in the table: the day number, the date and the day's title. Those are constant for every row beneath them, so repeating them in thirty cells wastes both space and typing. They belong in the heading above each table — which is also what makes step 2 work.

Building it, step by step

1. Set the page up first. File → Page setup → Landscape. Seven columns do not fit across a portrait page without the text wrapping into unreadable slivers. While you are there, drop the left and right margins to about 1.5 cm to buy back width. Docs also offers Pageless in the same dialog, which removes the page edges entirely and is genuinely nicer to scroll on a phone — but it also removes page breaks, so you lose the one-day-per-sheet printing in step 6. Choose based on whether this itinerary ends up on paper.
2. Give every day a real heading. Type the day line — Day 2 · Tuesday 13 October · Asakusa & Ueno — and set it to Format → Paragraph styles → Heading 1. Do not just bold it. Real headings populate the document outline, and View → Show outline then gives you a sidebar that jumps between days in one click. On a five-day trip that is the difference between navigating the plan and scrolling through it.
3. Insert the table under the heading. Insert → Table, then choose seven columns and one more row than you have stops that day. One table per day, not one giant table for the whole trip — a single table cannot be split by page breaks cleanly, and per-day tables let you add a stop to Tuesday without disturbing Wednesday.
4. Fill and pin the header row. Type the seven column names, bold them, then right-click inside that row and pin it as a header row so it repeats at the top of each printed page. Then drag the column borders: Time, Duration and Cost need almost nothing, while What, Where and Notes need everything you can give them. The longest note in the sample itinerary is 94 characters, which is roughly the width you should plan for.
5. Add the transit rows. This is the step most itinerary guides skip, and it is the one that changes the plan. Between two stops, insert a row and write how you get there: mode, route, minutes, fare. Leave the Time cell blank — the duration is the point. In the five-day sample this adds 7 rows across the trip, and those rows account for 359 minutes against 1,875 minutes of actual activity. That is 16.1% of all scheduled time spent moving. An itinerary without transit rows is not optimistic, it is wrong by about a sixth.
6. Break the pages. With the cursor at the end of each day, Insert → Break → Page break (Ctrl+Enter, or ⌘+Enter on a Mac). One day per sheet means you can carry a single page for the day you are actually having instead of the whole trip.
7. Write everything that is not a schedule underneath. This is where Docs earns its place. Booking references, the confirmation number for the rail pass, the clinic nearest the hotel, "the 07:12 is the only train that connects" — none of that fits in a cell, and all of it matters at 06:40. Insert → Checklist also gives you a genuine packing list with tickable boxes, which a spreadsheet column cannot do.
8. Export it. File → Download → PDF Document (.pdf). Do this the night before you fly. A PDF on your phone opens without a signal, without loading, and without Docs deciding to sync.

How much typing this actually is

Worth knowing before you commit an evening to it. The numbers below come from the five-day Tokyo sample built into this site's planner — a fairly ordinary city trip, not an extreme one.

It holds 30 rows: 23 activities plus those 7 transit legs, spread across the five days as 5, 8, 6, 6 and 5 rows. Laid out the way this guide describes — one table per day, seven columns, a header row on each — that is 35 rows and 245 cells, carrying roughly 2,110 characters of times, places, notes and prices.

Two details make it slower than 245 cells sounds. 13 of the 30 rows have no cost and 7 have no start time, but you still tab through every one of them. And none of that typing includes the research — the part where you find out the museum closes on Mondays.

Ten to fifteen minutes for a weekend. An afternoon for two weeks. That is the honest price of building it by hand, and for a lot of people it is fine — you learn the trip while you type it.

Three things that will bite you later

All three come from the same root: a Docs table looks like a spreadsheet and is not one.

• Nothing adds up. There is no SUM. In the sample, 17 of the 30 rows carry a cost and they total $231 — Day 4 alone is $63, because the Hakone trains are the expensive part. Change one fare and you re-add seventeen numbers by hand.
• Nothing sorts or filters. You cannot pull up "just the restaurants" or reorder a day after swapping two stops.
• Reordering is manual. Moving an activity from Tuesday to Wednesday is cut, insert row, paste, delete — for every change, in the week when trips change most.

The Google Docs template guide goes into all three properly, including which half of a trip plan genuinely belongs in a document.

If you would rather not type it twice

There is a shorter path to the same document, and it exists because the tedious part — structure, times, durations, per-day grouping — is exactly what software is good at.

Build the days in the free browser planner, click CSV, import that file into Google Sheets, then select the rows and paste them into your Doc. Docs converts a copied spreadsheet range into a real table, so you get the formatting without the transcription — and the schedule stays somewhere that can still total a budget. The Docs guide walks through that route, including why pasting the CSV file straight into a document does not work.

Either way, the thing worth carrying forward is the seven-column layout and the transit rows. Those are what make an itinerary honest about the day it is describing — and if you want the arithmetic behind that, how many activities fit in a day works it out from the same sample.

Frequently asked questions

Building it by hand is a perfectly good way to learn a trip. If you would rather skip the typing, open the free planner, build your days, then export.