Home / Software Tutorials

How to Use Notion for Project Management: Projects and Tasks as One Linked System

Colleagues discussing a project around a whiteboard in a modern office.

Photo: Yan Krukau / Pexels

Start with your situation, not the template gallery

Notion project management fails in two directions: teams that build a gorgeous system nobody updates, and teams that use Notion as a shared document folder and call it project management. The working middle is a specific build: two databases, related together, run by a cadence. This guide builds that, with one worked project, and then spends as much time on the cadence as on the schema, because the cadence is the part the template gallery cannot sell you.

Your situationYour honest starting pointWhat this guide gives you
Solo or pair, projects in your headBuild both databases, skip sprintsThe linked system at personal scale
Small team, first real systemFull build, adopt the weekly cadence firstProject visibility without a new tool to buy
Team migrating from a board toolRead the limits section before migratingAn honest map of what Notion does worse
You run repeating delivery cyclesFull build plus the sprint sectionSprints as filtered views, not new boards
You only need personal tasksLighter build existsThe general Notion guide dashboard is enough

Step 1: The Projects database

Create a database called Projects: Name, Status (select: Scoping, Active, Paused, Shipped, Archived), Owner (person), Dates (date range for start to target ship), and Goal (text, one sentence: what done looks like). Every project gets a page, and the page holds the brief: background, scope, what is explicitly out of scope, decisions log, and links. The brief matters because tasks without a brief drift; when a task argument starts, the project page is where the answer lives.

Interactive tool

Project System Checklist

Check off each step as you finish it. Your progress stays on this page.

0 of 9 complete

0% done

Step 2: The Tasks database, related to Projects

Create Tasks: Name, Project (Relation to Projects), Assignee (person), Status (select: Inbox, Next, In progress, In review, Done), Due (date), Priority (select), and Estimate (number, in hours or points, pick one and never mix). Add the rollup that makes managers happy: on Projects, a Rollup over Tasks counting total, and a second counting Done, and a formula dividing them into a completion percentage. Every project now reports its own progress, and a portfolio view of Projects sorted by that percentage is a status meeting on a page.

Relations are the whole game. If you skipped relations in your earlier Notion use, the general guide teaches them on a personal task list; here they carry a team's work.

Step 3: Sub-tasks and dependencies, honestly

Enable sub-items on the Tasks database (in the database options) so a task can nest children: "Launch landing page" carries "Write copy", "Design hero", "Build form". Use sub-tasks for work that shares one owner and one deadline; promote to a sibling task when the owner or date differs, or your board fills with collapsed rows nobody opens.

Dependencies in Notion are a Relation property from Tasks to itself, usually named Blocked by. Be honest about what this is: a record, not an engine. Notion will not stop you starting a blocked task, will not auto-shift dates when a predecessor slips, and will not draw you a critical path. The discipline is manual: the weekly review reads the Blocked by column. Teams that need enforced dependencies and automatic scheduling should keep a dedicated project tool for that layer; the comparison in Notion vs Asana grades exactly that trade.

Step 4: Views, sprints, and the project dashboard

On Tasks, build the views the cadence uses. Board by Status for the team's daily glance. My tasks: filtered to Assignee equals current user, sorted by Due, the view each person bookmarks. This sprint: sprints in Notion are a Select property (Sprint 12, Sprint 13) plus a filtered view, or a date-range filter on Due; either works, and the select is easier to close out and archive. Calendar by Due, which can also feed the Notion Calendar app for time blocking.

Each project page gets linked views of its own tasks: board, timeline (use the Timeline view grouped by the project's date range for a Gantt-like picture), and a decisions section. One database, many lenses, no copies: the same discipline as every good Notion build.

The worked project: a website launch in six weeks

A four-person team launches a marketing site. Projects gets one row, goal sentence written, dates set. Tasks gets 23 items across the sub-task pattern: content (6), design (5), build (8), launch checks (4). Two dependencies are real: Build form is blocked by Finalize fields, and Announce is blocked by QA pass. Sprint 1 takes content and design; Sprint 2 takes build and launch. The completion rollup reads 0 percent, then 35 after Sprint 1 closes, then 100 at launch. Nothing about this required a template; it required the relation in step 2 and twenty minutes of honest task writing at kickoff, which is the actual work of project management that tools only store.

Step 5: The cadence that runs the system

  • Daily, per person, two minutes: open My tasks. Move what you finished, pull what is next, flag blocks in the task's comments the moment they appear, not at the next meeting.
  • Weekly, team, thirty minutes: open the Board and the Projects portfolio view. Read completion percentages, read the Blocked by column out loud, re-date what slipped with reasons in the project decisions log, and close the sprint if it is sprint end: archive done tasks' sprint tag, set the next sprint's filter.
  • At project close: a short retro page linked from the project, three sections (worked, did not, change next time), then Status to Shipped and the project archived out of active views. The retro is where the system compounds; skip it and every project repeats the last project's lessons at full price.

Sharing, guests, and what it costs

Project work means people outside the workspace: clients, contractors, freelancers. Share the individual project page with guests rather than adding them as members, and remember guests on many pages can cost as much as members on some plans. Notion Plus lists at $10 per user per month billed annually, and Business at $20, when we checked Notion's pricing page on November 18, 2026; Business adds private teamspaces and richer guest and history features that multi-team setups eventually want. Price the seats after the system works, not before: a pilot project on free or Plus teaches you the real seat count. The life organization guide shows the same two-database pattern running a personal life, and the school guide runs it for classes and assessments.

The honest limits

No native time tracking; estimates are planning numbers, and actuals need a tracker or a manual property. No workload view that warns when one person holds nine due dates and another holds one; the weekly review's eyes do that job. Notifications are weaker than dedicated tools, so the cadence carries communication that software would automate elsewhere. Automations exist (buttons, database automations on paid plans) and handle status nudges and template creation, but they do not turn Notion into a workflow engine. Within those limits, the system's strengths are real: the brief, the tasks, the decisions, and the docs live in one place, which is the thing teams actually lose in other tools. If the limits are the story for your team, our Notion alternatives grades the exits by job.

Rolling it out without a big-bang migration

Do not migrate your team's history. Start with the next project: build the two databases, run the pilot project through one full cycle with the cadence, and let the team feel the rollups and the My tasks view before judging. Keep the old tool read-only during the pilot so nobody straddles two systems for the same work, which is the migration pattern that actually kills adoption. After the pilot's retro, adjust the properties (every team wants one field you did not predict and wants to delete two you did), save the databases as the team's template, and only then bring a second project in. Historical projects stay where they are, linked from a single archive page. A month after the pilot, the question answers itself: the team either reaches for the system or it does not, and no amount of imported history would have changed that verdict.

Related guides

Frequently asked questions

Can Notion really handle project management for a team?

Yes, for small and mid-sized teams whose work is mostly knowledge work with documents attached. The two-database build in this guide, projects related to tasks with rollups, covers planning, assignment, status, and reporting. What it does not cover is enforced dependencies, automatic rescheduling, workload balancing, and time tracking; teams that live on those features need a dedicated project tool, possibly beside Notion rather than instead of it.

How do sprints work in Notion?

A sprint is a label plus a filter. Add a Sprint select property to Tasks, tag the tasks committed to the sprint, and save a view filtered to that sprint. At sprint end, review the board, carry unfinished tasks to the next sprint tag deliberately, and archive the old view. There is no built-in sprint ceremony; the weekly cadence in this guide supplies it.

How do I show project progress without status meetings?

Use rollups. On the Projects database, roll up the related Tasks twice: once counting all, once counting those with Status Done, and divide in a formula for a completion percentage. A gallery or table view of Projects sorted by that number is a portfolio status page that updates itself as the team moves tasks.

What is the difference between this and the Trello project guide?

Shape of work. Notion suits projects where the brief, documents, and decisions are as important as the task list, and where you want custom properties and rollups. Trello suits projects where the work is a flow of cards through stages and the team wants the board to be the whole interface. Many teams run both: Notion for the project home, Trello for a delivery board, which the Trello guide covers.

Do clients and contractors need paid seats?

Guests can view and comment on shared pages without being members, and the limits and costs depend on your plan and how many guests accumulate. The practical rule is to share project pages with guests, review the guest list monthly, and convert regular collaborators to members when the guest math stops making sense. Check the current guest policy on Notion's pricing page before a big rollout, since plan terms change.

How do I stop the system from going stale?

The cadence, not the tooling. Stale systems are updated by nobody because updating was nobody's ritual. The daily two-minute personal pass and the weekly thirty-minute team review in this guide are the maintenance contract; a team that will not hold the weekly review should choose a simpler tool, because no schema survives an absent cadence.

Photo credits: Yan Krukau (Pexels). Photos are served from this site; follow the credit to the library page for the original.