Notion travel planner: how to set one up and when to move on

A Notion travel planner is a set of linked databases: one for places, one for the day-by-day plan, one for bookings and one for packing. Make one page for the trip, put the databases on it, and share it with the people coming. Notion is good at holding notes and lists together and at being shaped exactly how you want. It is slower to set up than a purpose-built planner, it is a lot to use on a phone in the street, and it does not do money or maps of a day.
Start with one page
Create a page for the trip and put four things on it:
- A short summary: dates, who is going, where you are staying.
- A database of places.
- A database or table of days.
- A bookings table.
Add packing and costs once the first four are in use. A common mistake is building twenty pages in a weekend and then never opening them. Start small and add what you actually need.
The places database
Each place is a row with properties:
- Name
- Type (sight, food, activity, stay)
- Area (neighbourhood or town)
- Status (idea, planned, booked, done)
- Link (map or website)
- Notes
Use a board view grouped by status for choosing, and a table view grouped by area for planning. The same data shows up two ways, which is Notion's real strength.
The days database
One row per day, with a date and a relation to the places you are going that day. In the day's page, list the order: morning, afternoon, evening. A relation means you tick places from the database rather than retyping them, so a change in one place updates everywhere.
If that sounds like more setup than you want, you can skip the relation and just use a page per day with a short list.
The bookings table
Type, provider, date, confirmation number, who it is under, cancellation deadline. You can attach a PDF or paste a screenshot to the row. Sort by the deadline.
Sharing with a group
Invite people to the page by email, or share a link. Decide who can edit and who can only comment. In a friend group, edit for everyone is fine if you agree not to restructure the databases without saying. Use comments on a row to ask questions, so the answer sits beside the thing.
One thing to check early: every person needs to open the page on their phone and find it easily. If three people cannot, the plan lives in one person's head again.
Offline and in the street
Notion works best with a connection. As of November 2026, Notion's help says you can mark a page "Available offline" in the desktop or mobile app, on each device, and that a downloaded database brings only its first rows with it. So mark the trip page and its databases on your phone, then test before you go: switch your phone to airplane mode, open the trip page and check that the days and bookings load. A planner that needs signal fails in exactly the places you need it. Travel offline lists what to save before you lose your connection.
What Notion is not
- A map. You can paste links, and some embeds work, but there is no map of a day's route that builds itself.
- A money tool. You can build a table of costs, but converting currencies and settling up fairly is up to you and your formulas.
- A quick tool. Adding an item on a phone takes a few taps more than in an app made for it.
None of that matters on a short trip with a couple of people. It matters when ten people are adding things from their phones across three countries.
Notion or something built for trips
Notion suits people who enjoy designing their own system, who already live in it for work or study, and who plan on a laptop. A trip planner suits people who want to start planning in a minute and carry the plan on a phone. Travel Life vs Notion compares them in more detail, and Travel Life vs a spreadsheet covers the other do-it-yourself option.
A minimal template to copy
If you want to start now, make one page with these headings and nothing more:
- Trip: dates, people, where you sleep
- Ideas: a list of places, one line each
- Plan: one heading per day, with three bullets
- Bookings: a table
- Packing: a checklist
You can turn any of these into a database later. Do that only when the list gets long enough to need filtering.
Keeping it from getting out of hand
Notion rewards restraint. Three rules help:
- One view per job. A board for choosing, a table for checking, a calendar for dates. More than three views of the same data means nobody knows which is current.
- One owner for the setup. Anyone can add a place; one person changes properties and templates.
- A weekly tidy. Five minutes to move finished items to "done" and delete duplicates, so the lists stay short enough to read.
Templates help here. If you plan often, make a trip template with your four databases already in place, and duplicate it for each new trip.
Before you go, open the trip page on every phone in the group and check that each person can find the days and bookings in under ten seconds.
What to do next
Create the trip page and add your first ten ideas. Share it with the people coming and ask each to add one. After a week, look at what you used and delete the rest. If the planner has become another thing to maintain, how to make a travel itinerary shows a lighter way to get to a plan.

