Get AI summaries of any video or article — Sign up free
The Best Way to Manage Tasks and Projects in Notion thumbnail

The Best Way to Manage Tasks and Projects in Notion

Thomas Frank Explains·
5 min read

Based on Thomas Frank Explains's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Use the inbox checkbox as a capture buffer: tasks remain in Inbox until the checkbox is unchecked, then filters move them into the rest of the system.

Briefing

Notion’s task management setup can feel like a “white whale,” but the Ultimate Tasks template offers a structured system that makes recurring work, sub-tasks, inbox triage, and project tracking work together instead of fighting each other. The core idea is a single master task database (“all tasks”) that powers multiple filtered views—so tasks can be created quickly, then automatically appear in the right places based on due dates, status, priority, and project relationships.

The workflow starts with an inbox designed for capture. Tasks sit in the inbox until the “inbox” checkbox is unchecked, allowing users to dump items first, then fill in due dates, projects, and priority without losing track. A color-coded “state” field provides at-a-glance timing: red for overdue, green for due today, and blue for future tasks. For recurring tasks, the template uses a practical workaround: instead of relying on Notion’s native recurring behavior, it sets each task’s due date to the “next due date,” so completing a recurring item effectively advances it. This keeps the system compatible with Notion’s limitations while still producing a predictable cadence.

Sub-tasks are handled through a template-driven pattern. When creating a task “with sub tasks,” the task contains its own embedded sub-task database. Any sub-task created inside that embedded table automatically links back to its parent task, and small arrow markers in the state column reveal the hierarchy at a glance across views. The template also emphasizes responsiveness: list views are positioned as mobile-friendly, while table and Kanban views support richer desktop planning.

Daily planning is built into nearly every view via “daily tasks” notes that act like a scratch pad or whiteboard replacement. Users can plan the day or temporarily park items, then archive completed notes with an “archive” checkbox so they disappear from the system. Filtering then drives the next layer: the Today view shows tasks due today or earlier, while the Next seven days view expands the window to include everything due within a week.

For prioritization, a dedicated Kanban-style “priority view” assigns new tasks a default priority (medium) using a filter-based creation rule. Ordering on the board can be rearranged without breaking the underlying priority assignment, letting users sort high/medium/low while keeping new items consistent.

The most powerful piece is project management through a separate “projects” database linked to “all tasks.” Each task can relate to a project, so tasks automatically appear in both the project board and the personal planning views. Project boards support both classic state-based Kanban (to do/doing/done) and a tag-based board view that breaks large work into categories like design, copy, speed, and security. Creating a project uses a project template that auto-fills structure, icons, and linked databases—so new initiatives immediately slot into the system. The result is a unified Notion setup that replaces multiple task apps with one consistent set of views, rules, and relationships.

Cornell Notes

Ultimate Tasks is a Notion template built around one master database (“all tasks”) and many filtered views that keep task capture, planning, and project execution aligned. An inbox checkbox holds new items until they’re ready to move on, while a color-coded state field (overdue/today/future) gives quick timing signals. Recurring tasks are managed by updating due dates to a “next due date,” using a workaround that fits Notion’s constraints. Sub-tasks are created via a task template that embeds a sub-task database inside each parent task, with arrow markers showing the hierarchy. Projects live in a separate database linked to tasks, enabling project Kanban/tag boards while tasks still flow into Today and Next seven days planning.

How does the template prevent “inbox dumping” from turning into permanent clutter?

Tasks added to the inbox stay there only while the “inbox” checkbox remains checked. Once the checkbox is unchecked (and the task has a due date), the task disappears from the inbox view because the system’s filters treat inbox items as a separate state. This lets users capture quickly, then fill in due date, project, and priority without losing control of where tasks should live.

What’s the template’s approach to recurring tasks in Notion?

Recurring tasks use a due-date shifting method. When a recurrence interval is set, the task is treated as recurring and the “next due” guide drives the upcoming due date. Instead of relying on native recurring behavior, the template updates the due date to the next occurrence, so completing a recurring task effectively advances it. One-time tasks use a “done” checkbox/button to make them disappear from the active views.

How are sub-tasks implemented so they behave like real nested tasks across views?

Sub-tasks are created using a template called something like “task with sub tasks.” That template spawns a parent task that contains an embedded sub-task database. Any items created in that embedded database automatically become sub-tasks of the parent. In list/table/Kanban views, arrow markers in the state column indicate the task has sub-tasks, and opening the task reveals the embedded sub-task table.

What role do “daily tasks” notes play, and how do they avoid polluting the system?

Daily tasks notes act like a scratch pad or whiteboard inside Notion. They appear within most views (except the project view) so users can plan the day or park near-term items. An “archive” checkbox hides completed notes from essentially every view, keeping the main task system clean while still preserving daily planning history when needed.

How does the template ensure new tasks get a consistent priority automatically?

The priority view uses a filter-based creation rule: when the view is filtered by a property being “is not empty” (such as priority), new tasks created under that view inherit a default priority. The template sets new tasks to medium by ordering the priority options so medium is the top-listed choice. Users can then reorder cards on the Kanban board without changing the fact that new tasks start as medium.

How do projects connect to tasks without duplicating effort?

Projects live in a separate “projects” database, and tasks relate to projects via a relation property. When a task is created inside a project board, it automatically links to that project row, so it shows up in the project view and also flows into personal planning views like Today and Next seven days based on due dates. Project templates further streamline setup by auto-filling the linked structure when a new project is created.

Review Questions

  1. If a task is checked in the inbox view, what exact mechanism removes it from the inbox, and what additional condition must be satisfied for it to leave?
  2. Describe the template’s workaround for recurring tasks and explain how “next due” functions compared with one-time tasks.
  3. How does the template’s project relation model ensure a task appears in both project boards and day-planning views?

Key Points

  1. 1

    Use the inbox checkbox as a capture buffer: tasks remain in Inbox until the checkbox is unchecked, then filters move them into the rest of the system.

  2. 2

    Recurring tasks are handled by shifting due dates to a “next due date,” providing predictable recurrence despite Notion limitations.

  3. 3

    Sub-tasks are implemented via a parent-task template that embeds a sub-task database inside each task, with arrow markers signaling the hierarchy.

  4. 4

    Daily planning is integrated through “daily tasks” notes that appear across most views and can be hidden using an archive checkbox.

  5. 5

    Today and Next seven days views rely on due-date filters to control which tasks appear (today-or-earlier vs. within a week).

  6. 6

    A priority Kanban view assigns new tasks a default priority (medium) using filter-driven creation behavior.

  7. 7

    Projects are managed in a separate database linked to tasks, enabling project Kanban/tag boards while tasks still surface in daily planning views.

Highlights

The system’s backbone is one master “all tasks” database feeding multiple filtered views, so task data stays consistent while the interface changes.
Recurring work is made reliable by updating due dates to a “next due date,” effectively turning recurrence into a due-date workflow.
Sub-tasks become practical by embedding a sub-task database inside each parent task created from a dedicated template.
Project tracking scales by linking tasks to a separate “projects” database, then using both state-based and tag-based Kanban layouts.

Mentioned