Notion at Work: Master the Timeline View

Notion’s new Timeline view turns database items into a chronological, Gantt-style display—complete with start/end date handling—so teams can spot scheduling overlaps and capacity issues at a glance. The feature is built for databases where each item spans time, such as project tasks, event series, or any sequence of work that has both a beginning and an ending. Timeline view sits alongside other database formats (table, list, calendar, board, gallery), but it adds a linear visual layer that makes duration and sequencing easier to understand than a standard spreadsheet-like layout.

The walkthrough starts with the basics of how to set up a timeline. A database item needs a date range: either a single date property that includes both a start and an end, or two separate properties—one for start and one for end. When creating a timeline view, users choose which date property (or which pair of start/end properties) determines where each item lands on the timeline. From there, sorting controls the “waterfall” order: sorting by the start date produces a chronological flow, while sorting by other properties (like owner) can group items in ways that support different planning questions.

Timeline customization goes beyond placement. Users can decide which properties appear in the table alongside the timeline and which show up directly on the timeline bars. That includes practical fields like task names, assignees (shown as headshots), and completion checkboxes. Notably, the bars aren’t just visual: users can interact with checkbox properties directly on the timeline, and they can drag bars from one date to another—updating the underlying date values.

A second example demonstrates why timeline views matter for real-world event planning. Using a PGA tournaments dataset, the setup splits start and end dates into separate properties and links each tournament to a separate winners database via a relation field. That relationship lets the timeline display winner information with visual cues (like the winner’s icon and headshot) pulled from the related database. The result is a timeline that functions like a compact event dashboard—useful for tracking seasons, conferences, or any multi-day series.

The session also highlights two other recent Notion updates. First, database page “hidden properties” let users hide specific properties inside individual item pages—either always, or only when they contain no value—cleaning up item views when certain fields are only needed for calculations or timeline logic. Second, child pages now inherit parent sharing settings but can be tightened: a parent can remain publicly shared while a child page can be restricted, addressing a limitation where sharing could previously only be loosened, not tightened.

In Q&A, the timeline is framed less as a data-entry tool and more as a visualization and capacity-planning tool—especially when items overlap in time. Users also raise common feature requests, including more dynamic date dependencies and more flexible title/ID generation, but the core message remains: timeline view is designed for anything that spans time and benefits from seeing sequencing, overlap, and duration in one place.