Google Calendar Travel Itinerary Template: Copy and Import a Trip
A travel calendar becomes useful when it tells you what cannot move: the train you booked, the museum entry you paid for, the time you need to leave for the airport. Fill every spare hour and it starts working against you.
This Google Calendar travel itinerary template gives you a small, editable CSV to copy, plus a method for keeping bookings separate from ideas. It is designed for a short trip within one destination time zone. For flights across time zones, add the events individually and check both ends carefully.
Start here: copy the CSV below into a plain-text file, replace the sample dates and details, and test it in a separate trip calendar. These are fictional planning blocks, not reservations, opening hours or a complete sightseeing route.
A copyable travel planner calendar template
The example uses May 14–16, 2027. Change every date before importing. Dates are written as month/day/year. Keep the English column headings and commas exactly as shown, and retain quotation marks around descriptions or locations containing commas.
Subject,Start Date,Start Time,End Date,End Time,All Day Event,Description,Location,Private Trip overview,05/14/2027,,05/14/2027,,True,"Arrival day; keep the evening flexible",Destination city,True Arrival and hotel transfer,05/14/2027,2:00 PM,05/14/2027,4:00 PM,False,"Replace with actual arrival and transfer details",Arrival terminal,True Hotel check-in,05/14/2027,4:00 PM,05/14/2027,4:30 PM,False,"Confirm check-in time with the property",Hotel name and address,True Booked visit,05/15/2027,10:00 AM,05/15/2027,12:00 PM,False,"Placeholder only; replace with confirmed entry time",Venue address,True Lunch and open afternoon,05/15/2027,12:00 PM,05/15/2027,3:00 PM,False,"Flexible block; shorten or remove as needed",Nearby neighborhood,True Leave for departure terminal,05/16/2027,9:00 AM,05/16/2027,10:30 AM,False,"Illustrative buffer; calculate your own required arrival time",Hotel to terminal,True
Save the file as trip-calendar.csv, rather than .txt. A code editor or plain-text editor is enough. If you prepare it in a spreadsheet, export the finished tab as comma-separated CSV and inspect the downloaded file before importing.
The Private field is included for the example, but it is not a substitute for checking calendar sharing permissions. Keep passport numbers, payment details and entry codes out of descriptions. Use a booking reference only where everyone with access should see it.
How to import your itinerary into Google Calendar
On a computer, open Google Calendar and its Settings. Choose Import & Export, select your .csv file, choose the destination calendar and click Import. Google also accepts ICS files. Its official import guide lists the accepted fields; Subject and Start Date are required.
Use a separate calendar named for the trip so you can review it without mixing sample entries into work appointments. Import a short test file first. Confirm the date, time and location of a known event before adding the rest.
Importing is a one-time copy, not an ongoing connection to your planning sheet. Editing your source document later does not update the imported events. Guests and conference details are not carried over by event imports.
Use three kinds of calendar blocks
| Block | What belongs in it | How firmly to treat it |
|---|---|---|
| Confirmed | Paid entry, train departure, booked tour | Keep the real start time and source link |
| Movement | Hotel transfer, station approach, walking between areas | Protect enough time to reach the next booking |
| Flexible | Lunch, neighborhood wandering, optional viewpoint | Move or remove without disrupting the day |
Put a status word at the start of a title if you need clarity: “BOOKED — museum,” “TRANSFER — hotel to station,” or “IDEA — riverside walk.” A beautiful calendar is less valuable than one that makes the difference obvious.
Do not color an unbooked attraction as though it were confirmed. If you have not bought the ticket, write that in the description. Include the official page you still need to check and the person responsible for doing it.
Build the day around one anchor
Choose one visit that gives the day its shape. If a museum is the priority, keep the morning for that and place lunch nearby. Avoid a second paid timed entry immediately afterward unless you are comfortable leaving the first early.
A useful description has four short lines: confirmation status, address or meeting point, source link and next action. Long research notes belong in your itinerary document. Your calendar should let you answer “where next?” on a small phone screen.
For a multi-day route, map the places before assigning times. Our Google Maps travel planner guide explains day layers and the handoff to navigation. The map catches the cross-city detour that a neat calendar can hide.
Protect the time around a booking
An entry time is not the moment to leave the hotel. Work backward: required arrival time, journey, station exits, walking and a margin for delays. Keep that movement visible as a separate block if missing the booking would be costly.
For departure day, start with the airline or operator's current instructions and your specific terminal. The 90-minute transfer block in the sample is deliberately arbitrary. It is not advice about how early to arrive at an airport, a border crossing or a railway station.
Arrival day deserves the same restraint. A late flight, luggage collection or a room that is not ready can move the whole afternoon. Put the essential transfer in the calendar and keep the first evening easy to cancel.
Time zones: check before trusting the clock
CSV's basic date and time columns do not give you a separate time-zone field. For this single-zone template, check the destination calendar's time-zone settings and inspect the imported result. Google's import troubleshooting guide recommends matching source and Calendar time zones when events appear at the wrong time.
For an overnight flight, do not copy the departure date into the arrival field automatically. Check the date on the booking confirmation, then set each endpoint using its local airport time. A two-hour clock difference is not necessarily a two-hour flight.
Near a daylight-saving change, inspect the actual travel date rather than assuming today's offset will still apply. If the itinerary crosses several zones, enter transport events individually with explicit time-zone settings instead of stretching this simple CSV into a job it was not designed to do.
Keep changes from turning into conflicting plans
Choose one place for the current schedule. If that is Google Calendar, update the actual event when a booking changes. If the master remains a spreadsheet, mark the calendar as a convenience copy and review both before travel.
Avoid repeatedly importing the whole trip as your normal update method. Inspect existing events first, then edit the entries that changed. If an import reports zero processed events, check whether the first import already succeeded before trying again.
For a group trip, decide who can edit and who only needs to view. Tell companions when an essential booking changes; do not assume a silent calendar edit will be noticed. Review notification settings for important events after import instead of assuming the CSV supplied useful reminders.
If the CSV import fails
- Check that the extension really is .csv and that fields use commas, not semicolons.
- Keep the English headings and one event per row.
- Put double quotation marks around any field containing a comma.
- Review dates, end times and the selected destination calendar.
- Check the official troubleshooting page before repeatedly importing.
If you only have three bookings, manual entry may be quicker than fixing a file. The CSV becomes helpful when the trip has enough structured events to justify the setup.
What should stay outside the calendar?
Keep your packing list, cost forecast and long shortlist elsewhere. Calendar entries are poor places for 25 restaurants you might visit. Use our editable day-by-day itinerary layouts for the full plan, then move only the confirmed anchors and useful movement blocks here.
A good final check is to hide the flexible events. Can you still see every essential journey and booking? Then show everything again. If the day has no room for a queue, lunch or a change of mind, remove an optional block.
Editorial note: this is an original DIY CSV template checked for column structure, not a hosted calendar or a claim of live import testing. Written by the Amicly team. Official Google instructions reviewed 26 October 2026; interfaces may change.
Comments
Post a Comment