Gantt charts in Notion: building a timeline view and where it falls short
Notion does not have a feature called a gantt chart. It has a timeline view, and for most of what small teams need from a gantt chart, the timeline does the job. Tasks appear as bars on a date axis, bars can be dragged, dependencies can be turned on, and the whole thing sits on top of the database the team is already using.
Where it gets interesting is the set of things the timeline is not designed to do, and the fact that most of those limits come from Notion's database model rather than from the timeline itself. Understanding that distinction saves a lot of time, because the workarounds people reach for tend to fight the model rather than work with it.
Building a timeline that actually plots something
The most common first problem is a timeline that renders an empty grid. Notion's timeline documentation states the cause directly: timelines only work if the database has at least one date property containing a range of dates. A single date is not enough, because a bar needs a start and an end.
The setup is short.
- Create a database, or open an existing one.
- Add a date property, then enable the end date option on it so each entry holds a range rather than a point.
- Click the plus next to the database view name and select Timeline.
- Fill in a date range on at least one entry so something appears.
From there the documentation describes the controls that matter for daily use. The time scale runs from hours up to years through a dropdown to the left of the Today button. Dragging the left or right edge of a bar changes the task's dates, with date indicators appearing as a guide. The Today button jumps back to the current day. A table can be shown to the left of the chart using the arrows on the left edge, so the full task list stays visible regardless of when items are scheduled.
Two settings worth changing immediately
Load limit. The documentation notes that the number of pages shown can be set under Layout, using the Load limit option. On a plan with a long history this is the difference between a timeline that opens quickly and one that does not.
Show timeline by. If the database has more than one date property, the timeline can be plotted by any of them, chosen under Layout in the Show timeline by option. The same page explains that start and end dates can either live in a single date property as a range, or be kept as two separate properties. Teams that track planned dates and actual dates separately can use this to switch the view between them, which is the closest thing Notion offers to a baseline comparison.
Property visibility is also worth setting once. The owner and status of a task are the two things people look for on a schedule, and both can be surfaced on the bars themselves rather than requiring a click.
Dependencies, and what happens when a date moves
This is the part that separates a chart from a plan. Notion's sub-items and dependencies documentation describes dependencies as a database setting rather than a timeline setting, which is an important detail: turning them on affects the database everywhere, not just in the timeline view.
Dependencies are enabled from the database settings under More settings, and the setup asks for a choice between three automatic date shifting behaviors:
- Shift only when dates overlap. Later tasks move only once their dates start to overlap the blocking task. The gap between tasks may shrink.
- Shift and maintain time between items. If task A blocks task B and A's due date moves forward one week, B moves forward one week too, preserving the gap.
- Do not automatically shift. Dates never move by themselves.
There is also an option controlling whether shifted items may start or end on weekends.
Which of the three to pick is a real decision rather than a default to accept. Automatic shifting keeps the plan internally consistent but means a single edit can rearrange work assigned to other people, sometimes without them noticing. No shifting keeps everything predictable and means the plan slowly becomes a record of what was once intended. Most small teams do better with shift and maintain time between items, plus an agreement that whoever moves a blocking task says so out loud.
Sub-items are the other structural feature worth knowing. They break a task into smaller pieces that can be assigned and tracked individually, and the documentation notes they are visible in all database views, displayed on the timeline either nested in a toggle or as a flattened list. This is Notion's answer to a work breakdown structure, and it works, although the timeline gets noisy quickly when every sub-item is plotted.
Where the timeline falls short
None of the following are bugs. They are consequences of building a schedule on a general purpose database, and they show up in a predictable order.
It plots dates, it does not schedule
A dedicated gantt tool treats a plan as a model to be solved. Set durations and dependencies, and the tool calculates dates and identifies which chain of tasks determines the end date. Notion works the other way around: dates are entered, and the chart displays them. Dependencies can shift dates after the fact, but there is no duration driven scheduling underneath.
For a team of five planning a quarter, this rarely matters. For anyone who needs to answer "if this task takes three days longer, what is the new end date, and which tasks now have no slack", the gap is real. Tools built specifically for scheduling advertise this as their core work. Instagantt's pricing page, for example, lists critical path analysis and baselines as plan features, which is a reasonable signal of what a dedicated scheduler treats as table stakes.
The free plan has a block ceiling for teams
This one surprises people because it has nothing to do with the timeline. Notion's pricing page explains that a free plan workspace used by one person can hold as many pages and blocks as wanted, while a free plan workspace with multiple members allows only a limited number of blocks before an upgrade is required. When that limit is reached, existing content can still be read, edited, and organized, but new content blocks cannot be added.
Since every paragraph, checkbox, and image in a task description is a block, a team that documents its work thoroughly consumes the allowance faster than one that writes short tasks. The same pricing page lists an external guest limit of 10 on the free plan, with unlimited guests on paid plans, which matters for teams that bring clients into a project.
Everything is a database decision
A timeline is a view of a database, which means its behavior is governed by properties, filters, and settings that live at the database level. That is powerful and it has a cost: someone has to own the structure. When a team sets up dependencies, sub-items, two date properties, and a set of filtered views, that configuration is invisible to everyone who was not there when it was built. A new person opening the timeline sees bars and has no idea why some tasks are missing, which is usually a filter nobody remembers setting.
Speed and mobile
A database with thousands of entries and many properties becomes noticeably slower to load, which is what the Load limit setting exists to mitigate. On a phone, a dense timeline is difficult to read regardless of the tool, and dragging a bar accurately on a small screen is harder than tapping a status.
How it compares with the alternatives
| Approach | Schedule view on the free tier | Dependencies shift dates | Main constraint |
|---|---|---|---|
| Notion timeline | Yes, timeline is a database view | Yes, three configurable settings | Block limit on free workspaces with multiple members |
| Asana | No, Timeline and Gantt start on Starter | Yes | Free Personal plan covers 2 users |
| Trello | No, Timeline on Premium and Enterprise | Via the view on paid plans | Not accessible on mobile devices |
| TeamGantt | No free tier, 14 day trial | Yes, scheduling is the core product | Basic from $24 per month, 150 tasks per project |
| GanttProject | Free desktop application | Yes | Built around one editor per file |
The details behind the table come from each vendor. Asana's pricing page lists list, board, and calendar views on the free Personal plan for 2 users, with Timeline and Gantt views on Starter at $10.99 per user per month billed annually. Atlassian's Timeline view documentation states the view is limited to Premium and Enterprise, with no current plans to bring it to free Workspaces, and that it is no longer accessible on mobile. TeamGantt's pricing page lists Basic from $24 per month with 2 projects, 1 manager, 10 collaborators, and 150 tasks per project. GanttProject is a free desktop application for Windows, macOS, and Linux that keeps data on the computer.
Read against that table, Notion's position is unusually good on one axis: the schedule view is available without paying, which is not true of most competitors. The trade is that it is a view of a document database rather than a scheduling engine, and the free tier's limit arrives through block count rather than seats or features. A side by side comparison is useful for teams that are weighing a move rather than an addition.
Deciding whether to keep planning in Notion
Three questions settle it for most teams.
Is the work already in Notion? If the tasks, specs, and notes live there, the timeline is close to free in effort terms, and moving to a dedicated tool means either migrating the documents or running two systems. That is usually a bad trade for a small team.
Does anyone need to answer scheduling questions rather than display questions? Displaying a plan is what a timeline does well. Calculating a plan, with slack and a critical path, is a different job.
How many people will edit, and how much do they write? A team of five that writes detailed task descriptions in a shared free workspace will meet the block limit, and the upgrade question arrives sooner than expected. Counting editors and reading the plan limits against that number is a five minute exercise that prevents a surprise.
Teams that answer yes, no, and small can stay where they are. Teams that need a board for daily flow, a calendar for deadlines, and a gantt view for planning, all reading the same cards without configuration work, are usually better served by a tool where those views ship together. The features overview sets out what that looks like in practice.
What to change first
Before adding anything, check the two settings that cause most of the complaints: confirm the date property holds a range rather than a single date, and pick the dependency shifting behavior deliberately instead of accepting the default. If after that the timeline still feels like a picture rather than a plan, compare it against a tool where the board, calendar, and gantt view are built in from the start, such as Pinateca.
Q1. Why is the Notion timeline empty?
Almost always because the date property holds a single date instead of a range. Notion's documentation states that timelines only plot items when the database has a date property containing a range of dates, so the end date option has to be enabled on that property.
Q2. Does Notion have real dependencies?
Yes. Dependencies are turned on in the database settings and offer three automatic date shifting behaviors: shift only when dates overlap, shift and maintain the time between items, or do not shift automatically, with an option to avoid weekends. The setting applies to the database, not just the timeline view.
Q3. Is the Notion timeline available on the free plan?
The timeline is a database view rather than a paid feature, so it is available without upgrading. The free plan's constraint comes from elsewhere: a free workspace with multiple members has a block limit, after which existing content can be read and edited but new blocks cannot be added.
Q4. Can a Notion timeline show a critical path?
Not as a built in calculation. The timeline plots dates that have been entered and can shift them through dependencies, but it does not calculate which chain of tasks determines the project end date. Dedicated scheduling tools list critical path analysis as a distinct feature for this reason.
Q5. How many tasks can a Notion timeline handle?
There is no published cap, but dense databases load more slowly, which is why the Load limit setting under Layout exists. As a practical matter, plans where each row is something one person can report on in a sentence stay readable, and plans that plot every sub-item usually do not.
