How to Manage Tasks and Projects Together in Notion
The relation between Tasks and Projects is the easy technical part. The harder question is scoping: when does something graduate from a task to its own project? Here's a simple test.
The relation between Tasks and Projects is the easy technical part — covered in our main tutorial in about ten minutes. The harder, ongoing question is scoping: when does something graduate from a task to a project of its own? Here’s a simple test.
The real question isn’t relations — it’s scoping
Once the Projects/Tasks relation exists, the structure itself doesn’t tell you where something belongs — that’s a judgment call your team makes dozens of times a week without necessarily realizing it. Get it wrong consistently, and your rollups quietly stop meaning what they’re supposed to mean.
A simple test
Ask three questions about the work in front of you:
- Does it involve more than one person’s distinct contribution? If yes, it’s likely a project.
- Does it have multiple genuinely different stages (design, build, review — not just a checklist of similar steps)? If yes, project.
- Will it take more than roughly a week? If yes, project.
Two or more “yes” answers: it deserves its own Project row, with its own Tasks related to it. Otherwise, it’s a Task — possibly with sub-tasks, covered in our hierarchy guide, if it has internal steps worth tracking separately.
Worked examples
| Work | Test result | Verdict |
|---|---|---|
| “Write and send the Q3 client update email” | 1 person, 1 stage, <1 day | Task |
| “Redesign the onboarding flow” | 3 people, 4 stages, 3 weeks | Project |
| “Fix the broken checkout button” | 1 person, 1 stage, <1 day | Task |
| “Migrate from Trello to Notion” | Whole team, several stages, 2+ weeks | Project |
How to apply this to existing work
How to Apply This to Existing Work
- 1
Scan your current Tasks database for outliers
Any task with more than 5–10 sub-steps, or spanning multiple weeks, is a candidate.
15 min
- 2
Apply the test from this guide
Multiple people? Multiple distinct stages? More than a week of work?
2 min per candidate
- 3
Promote qualifying tasks to their own Project row
Create the Project, relate existing sub-work to it as Tasks.
10 min each
- 4
Recheck your rollups
% Complete and Latest Deadline rollups should now reflect the corrected scope.
5 min
Need the sub-task mechanics too?
Once you’ve correctly scoped something as a task, breaking it into smaller steps is a separate feature — Notion’s native Sub-item property.
Scoping checklist
Scoping Checklist
- Nothing in the Tasks database spans more than roughly a week of total work
- Anything involving more than one person’s distinct contribution lives as a Project, not a single Task
- Recurring work uses a repeat pattern on a Task, not a new Project each cycle
- No Task has more than ~5–10 informal sub-steps buried in its description
Common mistakes
Common Mistakes
- Letting a task silently grow into a project. — A task’s checklist inside its description balloons to 15 items spanning three weeks and two people — at that point it’s a project pretending to be a task, and the % Complete rollup on its parent project stops meaning anything reliable.
- Creating a new Project for every small piece of work “to be safe.” — Inflates the Projects database with single-task “projects” that add overhead without adding clarity — the test in this guide cuts both ways.
- Not revisiting scope once work starts. — Initial scoping is a guess; checking in after the first week and re-scoping if needed costs little and prevents drift in either direction.
- Using sub-tasks (see our hierarchy guide) as a workaround instead of promoting to a real project. — Sub-tasks are for breaking down one task’s steps, not for hiding what is actually a multi-person, multi-week project inside a single Tasks row.
Free Notion Template
Projects + Tasks Starter Kit
The base relational structure this scoping guide assumes — duplicate it before applying the test above.
Template link placeholder — replace href with the live Notion “Duplicate” share link before publishing.
FAQ
What if a task keeps growing scope after it’s already created?
Convert it: create a new Project row, relate the original task (and any new sub-tasks) to it, and update the Assignee/Deadline fields at the project level. Takes a few minutes and prevents a bloated task from distorting your Tasks-level rollups.
Should recurring work (weekly reports, monthly reviews) be a Project or a Task?
Usually a recurring Task with a repeat/reschedule pattern, not a Project — it fails the multi-stage, multi-person test even though it repeats indefinitely.
Can a Task belong to more than one Project?
Technically yes if you allow multiple relations, but it usually signals the work should be split into two related tasks instead — shared ownership across projects gets confusing fast in rollup calculations.
Does this scoping question matter for a solo freelancer too?
Yes, arguably more — with no team to absorb ambiguity, an under-scoped project hiding inside a single task is exactly what makes billable-hours tracking and deadline estimates unreliable.
We turn workflows like this into a working Notion system in days, not months.
Find Your Solution