Trip Planning Spreadsheet: A Template That Works, and When to Stop Using It

Ask a well-organized traveler how they keep a trip straight and a good number of them will say, slightly apologetically, "I have a spreadsheet." There is nothing to apologize for. A trip planning spreadsheet is free, it is already open in another tab, it does exactly what you tell it and nothing else, and anyone you send it to can read it without installing anything.

So this is not a post about why your spreadsheet is wrong. It is about what a good one contains, the four jobs it quietly does badly, and how to move a finished one into a real itinerary without retyping a single row.

The template: one row per booking, six columns

Most trip spreadsheets go wrong in the first five minutes, by being organized around days instead of bookings. A day is a lovely way to read a trip and a terrible way to store one, because a single booking often spans several days. The hotel, the rail pass, the car: each gets copied into three or four day blocks, and then the check-in time changes and you fix it in two of them. Now the sheet disagrees with itself, confidently.

Store one row per booking instead, and let sorting do the day-by-day work. Six columns cover almost every trip:

• Type. Flight, train, hotel, car, activity, meal. Six values, not thirty. This is what you filter on when you want to see just the flights.
• What. The human name. "BA 1476" or "Hotel Kastanie" or "Cooking class in Trastevere". Whatever you would say out loud.
• Starts. Date and time, in the local time of the place it happens, with the year written out.
• Ends. Same rule. Checkout for a hotel, arrival for a flight, drop-off for a car.
• Where. The full street address, not the neighborhood. "Via dei Cappellari 40, Rome" beats "near Campo de Fiori" when it is raining and your phone is at nine percent.
• Reference. The confirmation code, record locator, or booking number. The one string a desk agent will ask you for.

Two optional columns earn their keep. Cost and Paid by, if more than one person is spending money, because reconstructing that later from a card statement is how groups quietly lose track of a few hundred dollars. And Notes, for the detail that fits nowhere else: bring the printed voucher, the ferry leaves from the east dock.

That is the whole template. Sort by Starts and you have a chronological trip.

Two rules that keep it honest

• Pick one time zone rule and write it in the header row. A column of bare times spanning three countries is the most common way a spreadsheet trip goes wrong. Local time always, stated at the top, is the rule that survives a real trip.
• Put the year in every date. Confirmations routinely print "March 3" with no year attached. Copy that in and you will eventually sort a trip that crosses New Year into the wrong order, with January sitting eleven months before December. We wrote about why bare dates are so hard to read correctly, and a spreadsheet has the same problem with none of the repair logic.

The four jobs a spreadsheet does badly

A sheet is a storage format, and as storage it is excellent. Every one of these is a case where the storage is fine and the work happening around it is the real cost.

1. You are the parser

Every row is there because a person read a confirmation and retyped it. Twelve bookings is twenty-five minutes, plus a couple of transcription errors. The errors are the expensive part, because a mistyped departure time looks precisely as authoritative in a cell as a correct one.

2. Nothing in it knows that something changed

Airlines move departure times. Terminals get reassigned the week of the flight. A spreadsheet cannot tell you any of that, because it is a photograph of what was true when you typed it. The gap is widest on the day of travel, which is the day you are leaning on it hardest.

3. Collaboration degrades quietly

A shared sheet starts beautifully and drifts. One person owns it, everyone else reads it, and the two who booked their own flights forget to add them. Then somebody downloads a copy for the plane, and now two versions exist, and the wrong one is being read aloud at the rental counter.

4. It is close to unreadable on a phone

An eight-column grid is a desktop object. At a gate, in a moving queue, you are pinching sideways to find a confirmation code. Survivable, but not what you want when you are tired.

What to keep the spreadsheet for

Some things a sheet does better than any travel app, and we are not going to pretend otherwise.

• Comparing options before you book. Four flight combinations against three hotels, and the arithmetic of which pairing works. That is what a grid is for.
• Budget modeling. Formulas, exchange rates, a what-if column for the version with the nicer hotel. Keep all of it.
• Packing lists and pre-trip tasks. Fine forever. Genuinely.

The line is simple: a spreadsheet is excellent for deciding and mediocre for carrying. Once the bookings are confirmed, the sheet has done the job it is good at.

How to move a finished sheet into an itinerary

This takes about five minutes, and the whole point is that you do not retype anything.

• Export the sheet as CSV. In Google Sheets, File, then Download, then Comma-separated values. In Excel, Save As, then CSV. Petrel reads .csv and .tsv text exports rather than native .xlsx workbooks, so do the export step rather than uploading the workbook.
• Upload it. Drop the file on the Petrel home screen. CSV exports, calendar .ics files, PDFs, and photos all go in the same place, and you can drop several at once. One detail that trips people up: the email forwarding address accepts PDFs, photos, saved emails and calendar files, and not spreadsheets, so a CSV goes in by upload.
• Then forward the original confirmations too. This is the step people skip, and the one that pays. Your sheet holds only what you chose to type. The original emails and PDFs hold the seat numbers, the terminal, the baggage allowance, and the cancellation terms. Send them into the same trip and that detail comes back without you transcribing it.
• Read the day-by-day view once, carefully. Check the two things a hand-typed sheet gets wrong most often: a date that landed in the wrong year, and a time that was quietly in your home zone.

What you get on the other side

The reason to move is not tidiness. It is the handful of things a grid structurally cannot do:

• Any format in. Forwarded emails, PDFs that are secretly scanned images, screenshots from a group chat, photos of a paper voucher, and CSV exports. The input is a file rather than one provider's email template, so a small regional ferry operator works the same as a big airline.
• Live flight status inside the day it belongs to. Open the trip and the flight card carries the current status, the delay, the gate and terminal, and the baggage belt when the airline publishes it, sitting directly above the transfer and the check-in a delay would break. To be precise: Petrel shows status when you open the trip and does not push delay alerts to your phone today.
• Readable with no signal. Your plan opens offline, which is what you want at a foreign airport. Viewing works offline; editing needs a connection.
• Free collaborators, with cost splitting attached. Everyone traveling with you can see the plan and add their own bookings, and the costs settle to one number per person instead of a group chat that lasts until February.
• Receipts and a print-ready expense report. Attach the receipt when you pay, and get an itemized report at the end for reimbursement or for splitting.
• Share links and a recap. A public link for the person meeting you at arrivals, and an automatic recap email after the trip ends.

On privacy, plainly: Petrel does not connect to or scan your inbox, does not sell your data, and does not train AI on your bookings. You send it the confirmations you choose, and that is all it sees.

Being fair about the alternatives

TripIt has been doing email forwarding longer than almost anyone and is solid when confirmations arrive as clean text. Wanderlog is strong on discovery and mapping, a real part of planning that a spreadsheet handles awkwardly. Tripsy is a genuinely lovely piece of iOS design. All three are reasonable places for a spreadsheet to graduate to, and our notes on switching without retyping your trips apply to any of them. What we built Petrel around is the messy import: the screenshot, the scanned PDF, the voucher, the CSV somebody made in February. That is where a spreadsheet user has the most work to hand off.

Where to start

Keep the sheet for the deciding. Use it to compare, to budget, to argue about which hotel. Then, once the bookings are real, export it, upload it, forward the confirmations behind it, and stop being the parser.

You can do that on your next trip at https://petrelvoyage.com. The first trip is free, with no account and no credit card. If you would rather see the shape of the result first, we keep a set of example itineraries to read through, and a longer walkthrough of building a day-by-day plan.