Notion Sub-Tasks and Task Hierarchy Explained

Sub-tasks aren’t a workaround — they’re a native Notion property (Sub-item / Parent item), built for exactly this. Here’s how to set it up, how to roll up progress to the parent automatically, and when a sub-task is actually the wrong tool for the job.

A native feature, not a workaround

Unlike the dependency tracking in our dependencies guide, which requires manually building a self-relation, Notion’s Sub-item feature comes with dedicated UI — an “Add sub-item” button directly inside any task page, and automatic indented display. Under the hood it’s still a self-relation on the same Tasks database, just with a purpose-built interface on top.

Three sub-items under one parent task, with a rollup calculating % complete automatically — the same rollup pattern as the Projects-level structure, one level down.

Setting up sub-items

Open any task, and inside the page click “Add sub-item.” Notion creates the Sub-item/Parent item relation the first time you use it — no property setup required in advance. Add sub-items for steps that only make sense in the context of their parent task, not anything that needs its own independent deadline or assignee.

The parent-level rollup

Add a Rollup property on Tasks: Relation = Sub-item, Property = Status, Calculate = Percent per group, filtered to Done. Now any parent task with sub-items shows live progress — the exact same pattern as the Projects-level % Complete rollup in our main tutorial, just applied one level down.

When a sub-task is the wrong tool

If a step needs its own deadline, its own assignee distinct from the parent, or needs to show up independently on a Kanban board filtered by Status, it’s better modeled as a sibling Task related to the same Project — not buried as a sub-item. Sub-items work best for steps that are genuinely just “parts of one task,” not independently-managed work.

Not sure if something belongs as a task, sub-task, or its own project?

See the full scoping test for deciding between a task and a project — sub-tasks are one level below that decision.

Read the scoping guide →

Setup roadmap

Setup Roadmap

1

Open any task in your Tasks database

Sub-items work at the database level, no new property setup required to start.

1 min
2

Click “Add sub-item” inside the task page

Notion creates the Sub-item/Parent item relation automatically on first use.

2 min
3

Add sub-items for genuinely dependent, non-independent steps

Not for anything that needs its own deadline or assignee.

varies
4

Add a % Complete rollup on the parent

Relation: Sub-item, Property: Status, Calculate: Percent per group, filtered to Done.

10 min
5

Review depth periodically

If a sub-item chain is nesting 3+ levels deep, consider promoting the deepest layer to its own Task.

ongoing

Launch checklist

Sub-Task Launch Checklist

Sub-items are used for steps with no independent deadline or assignee need
A % Complete rollup exists on parent tasks with sub-items, mirroring the Projects-level pattern
Nesting is kept to 1–2 levels; deeper chains get promoted to their own Task
Anything needing its own filter, deadline, or assignee is a sibling Task, not a buried sub-item

Common mistakes

Common Sub-Task Mistakes

Using sub-items for work that needs its own deadline. — Sub-items inherit visibility from their parent in most views — if a step genuinely needs independent tracking, it should be a Task in its own right, related to the same Project.
Nesting sub-items 4+ levels deep. — Technically supported, practically unmanageable — if you’re several levels deep, the bottom layer is very likely a project pretending to be a checklist item.
No rollup on the parent task. — Without it, “how much of this task is actually done” requires opening it and eyeballing the sub-item list manually every time.
Confusing this with the Projects-to-Tasks relation from the main tutorial. — That’s a two-database relation for scoping whole projects; sub-items are a same-database, single-task breakdown — different tool for a different level of granularity.

Free Notion Template

Sub-Task Ready Tasks Database

The Starter Kit with a pre-built parent-task % Complete rollup for sub-items.

Duplicate This Template →

Template link placeholder — replace href with the live Notion “Duplicate” share link before publishing.

FAQ

Is Sub-item a separate property type, or the same as a regular Relation?

Under the hood it’s a self-relation (Tasks related to Tasks), but Notion exposes it with dedicated Sub-item/Parent item UI — indented display, and a one-click “Add sub-item” button — that a manually-built self-relation doesn’t have automatically.

Can a sub-item have its own sub-items?

Yes, Notion supports nested sub-items several levels deep, though beyond 2 levels most teams find it harder to track than promoting the deeper item to its own Task or Project.

Does the parent task’s rollup update automatically as sub-items complete?

Yes, once you add a % Complete rollup on the parent referencing the Sub-item relation’s Status field, exactly like the Projects-level rollup in our main tutorial, just one level down.

When should I use a sub-task instead of just… another task?

When the steps are only meaningful in the context of their parent and nobody would ever need to assign, filter, or deadline them independently. If a step needs its own due date distinct from the parent, it’s arguably fine as its own Task related to the same Project instead.