2026-09-24 · 8 min read
A working itinerary format template needs five columns, not a fancy design. Here's the structure that survives past day one, the Google Maps stop limit most planning guides skip, and when to hand the route to an app instead.
By Elena Voss, Fortrip's travel-logistics editor. Elena has built and revised multi-day trip spreadsheets for road trips, business travel, and flight-heavy itineraries, and cross-checked the Google Maps stop limit against Google's own support and developer documentation.
A working itinerary format template needs five columns: Date, Time, Activity/Stop, Location/Address, Notes. Color coding, cover pages, a Cost tab — those are optional depending on the trip. Two things break most itineraries after the fact: a format that's missing a field you need mid-trip, and a driving route that runs into a limit nobody mentioned when you were building it. This piece covers both, because on a road trip they're the same document — the spreadsheet holds the plan, and the map link has to execute the driving day around a cap Google doesn't advertise.
Five columns show up in every reusable itinerary that survives past the first day:
Share
Google's standard consumer driving-directions interface allows 9 stops plus a start and end point, for 10 locations total in a single route, according to Google's own support documentation, and the same ceiling is reflected in Google's separate Directions API documentation for the underlying routing engine.
A spreadsheet is built for shared editing, offline access, and revision history across a multi-day or multi-week trip. A route-planning app is built for live traffic recalculation and generating a driving route you can hand to someone as a single link. They solve different problems, not the same one.
Only if you're splitting expenses with someone else and want a running daily tally. A solo leisure trip usually doesn't need it.

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 freeA printed Japan guide book still earns its spot in a carry-on, but no edition can tell you that Japan just cleared 40 million annual visitors for the first time, or that JR Pass math shifted after the October 2023 price rise. Here's how the major series compare, and what to verify against official sources before you buy one.
Notre-Dame reopened in December 2024, the Louvre now requires timed booking in practice, and Versailles deserves more than a half-day. Here's what's actually true about Paris right now, landmark by landmark.
| Column | Purpose | Example entry |
|---|---|---|
| Date | Which day this row belongs to | June 14 |
| Time | Start time for the stop | 9:30 AM |
| Activity/Stop | What you're doing or where you're going | Uffizi Gallery |
| Location/Address | The address, or a pasted maps link | Piazzale degli Uffizi 6, Florence |
| Notes | Confirmation numbers, parking instructions, timing caveats | Timed-entry ticket — arrive 15 min early |
(Sample row for illustration only — not an actual booking or confirmation.)
Skip one of these and you end up rebuilding the sheet mid-trip.
Notes is the column people leave blank and then regret. Confirmation numbers, parking instructions, and "call ahead before 6pm" reminders need to live in that row, next to the stop they apply to, not in a separate notes app you'll forget to check while standing at a locked gate.
For a weekend trip, one long list works fine. Past four days, split it into one tab per day. Scrolling through 40 rows on a phone screen to find Tuesday's dinner reservation is slower than tapping a tab. If you'd rather generate that day-by-day skeleton than build it by hand, Fortrip's AI trip planner drafts the structure first and lets you edit it like any spreadsheet afterward.
The five core columns cover most trips, but three specific types need extra fields, and generic templates built primarily for leisure travel often leave at least one of them out.
The base five columns are enough. Add a Cost column only if you're splitting expenses with someone else and need a running tally by day.
Add a Purpose/Meeting column describing why each stop exists, and a Contact field — name, phone, company — next to each entry. This is the piece most generic vacation templates skip, since they're built for leisure trips first.
Three fields a road trip sheet doesn't need: Confirmation Code, Terminal/Gate, and Layover time, each in its own column. When a connection gets delayed, you're updating one cell, not rewriting the whole row.
If you want a second opinion on a route before you commit to it, running a multi-stop route through an itinerary validator catches timing conflicts a static sheet won't flag on its own.
Google's own support documentation describes the exact ceiling: a standard driving-directions route accepts 9 stops plus a start and final destination, for 10 total locations in one link (Google Maps Help). That phrasing — 9 stops plus a start and end point — is Google's own description of the limit, not a rounded estimate. Google's separate Directions API documentation, written for developers rather than the consumer app, corroborates the same underlying waypoint ceiling on the routing engine both interfaces rely on, which is useful confirmation this isn't a bug specific to the mobile or desktop app.
Add an 11th stop and there's no clear error message. Reports from people building long multi-stop road trips consistently describe the same behavior: the app simply declines or drops the addition rather than explaining why, which is likely why the number circulates as something discovered by trial and error rather than a figure Google states upfront in the interface itself.
Two ways around it:
If building that sheet from scratch feels like more setup than the trip warrants, Fortrip's AI trip planner can generate the day-by-day structure for you. To compare plans for longer or multi-stop trips, see the pricing page, and read other itinerary-format breakdowns on the blog.
Google's standard consumer driving-directions interface allows 9 stops plus a start and end point, for 10 locations total in a single route, according to Google's own support documentation, and the same ceiling is reflected in Google's separate Directions API documentation for the underlying routing engine.
A spreadsheet is built for shared editing, offline access, and revision history across a multi-day or multi-week trip. A route-planning app is built for live traffic recalculation and generating a driving route you can hand to someone as a single link. They solve different problems, not the same one.
Only if you're splitting expenses with someone else and want a running daily tally. A solo leisure trip usually doesn't need it.