Pro Task Manager In Notion Made Simple

A Notion task manager can be built around one core idea: treat each project as a parent record and each task as a child record, then use relations, rollups, and filters to automatically sort work by deadline and priority. The result is a clean workspace where projects and their subtasks stay linked, subtasks roll up key project signals, and “next actions” rise to the top without manual reshuffling.

The setup starts with a single tasks database that holds both projects (A–D) and subtasks (A1–A3, etc.). A relation property named “subtasks” (renamed to “project” in the tasks view) connects each subtask back to its parent project. Enabling “sync both ways” ensures the relationship populates correctly from either side, so selecting a subtask automatically associates it with the right project. Once the links are in place, the workflow focuses on making the hierarchy visually and operationally useful.

For nesting, one approach uses a formula-based “id” property: if the “project” relation is not empty (meaning the record is a subtask), the formula displays the parent project name plus the subtask name; otherwise it shows the project name alone. Sorting by this “id” groups each project with all its subtasks in one continuous block. A second visualization technique uses a formula “sticker” with emoji blocks to distinguish projects from subtasks, then hides the “project” property to reduce clutter.

Sorting and prioritization depend on two fields: “deadline” (date) and “priority” (select with High/Medium/Low). Deadlines are assigned to projects, while subtasks also receive priorities so the system can decide what to do first. To make sorting smarter, the build creates rollups on the tasks view: “project due” uses a relation to the parent project and calculates the earliest associated date, while “project priority” rolls up the parent project’s priority using “earliest”/priority logic. With these rollups available, sorting can be layered—first by project due date and project priority, then by subtask priority—so a high-priority subtask inside a high-priority project bubbles above lower-priority items.

To manage completion, a “done” checkbox is added. An “archive” view filters for subtasks where “project is not empty” and “done is unchecked,” effectively removing completed items from the active list and sending them to an archive-style area. A separate rollup called “progress” on the projects database calculates percent checked from the “done” status of subtasks, giving each project a live completion meter.

Finally, the system becomes scalable through templates. A “new project” template creates a page that automatically links and displays all subtasks whose “project” relation contains the template’s project name, and it applies a chosen emoji. The same structure turns a standard tasks list into a dashboard-friendly project tracker where hierarchy, sorting, and progress update automatically through relations and rollups rather than manual maintenance.