Notion for project management: where it works and where it strains
A small team usually arrives at Notion project tracking the same way. The wiki is already in Notion, meeting notes are in Notion, and someone builds a task database next to them because it is right there. For a few weeks it works well. Then the questions start: why does the timeline look different for everyone, why did a task sit in "In progress" for a month without anyone noticing, and why is the free plan suddenly asking for an upgrade.
The short answer: Notion tracks projects well when the person who built the system keeps maintaining it and the team already lives in Notion for documents. It strains when the tracker has to be the single source of truth for people who do not open Notion every day, or when the shape of the database keeps drifting because anyone can add a property. The rest of this article shows how the built-in tracker actually works, what each plan costs as of October 8, 2026, the specific points where teams report friction, and how to decide whether to tighten the setup or move tracking somewhere else.
How Notion project tracking is built
Notion does not have a fixed project module. Tracking is built from databases, and the official help guide on projects and tasks describes three starting templates in the app's template picker:
- To-do list: a single database for simple task management, aimed at one-off projects or personal lists.
- Projects & tasks: two separate databases that are related to each other. Projects are the parent, and each task should relate to a single project.
- Projects, tasks & sprints: adds a third database so tasks can be placed into time-boxed sprints, which the guide positions for engineering teams.
The guide notes that the Projects and Tasks template is only available inside the Notion app, from Templates in the sidebar, not from the web template gallery.
In the two-database setup, projects carry properties such as status, people, related tasks, and a completion percentage. Tasks carry assignee, due date, and status. Progress is calculated from completed tasks: the completion property counts finished tasks per project and shows the result as a progress bar.
Views do the rest. The projects database ships with an "Active" kanban view that hides anything not marked Planning or In progress, a "Mine" view filtered to whoever is logged in, an "All" table for bulk edits, and a "Timeline" view that lays projects out by start and end date so overlapping commitments are visible. The tasks database adds "By project" and a "People" view grouped by assignee.
This is a sensible starting kit. The important detail is that every one of these pieces is editable by the team. Anyone with edit access can rename a status, add a property, or change a filter. That flexibility is the reason people choose Notion, and it is also the root of most of the strain described further down.
What each Notion plan gives a project team
Prices below were checked on Notion's pricing page on October 8, 2026, in US dollars per member per month.
| Plan | Billed monthly | Billed yearly | What matters for project tracking |
|---|---|---|---|
| Free | $0 | $0 | Collaborative blocks limited once there are 2+ members, 10 guests, 7-day page history, 1 chart, button-only automations |
| Plus | $12 | $10 | Unlimited blocks, unlimited guests, 30-day page history, unlimited charts, custom database automations |
| Business | $24 | $20 | Adds Notion Agent and AI Meeting Notes, SAML SSO, private teamspaces, granular database permissions, 90-day page history |
| Enterprise | Custom | Custom | Adds SCIM provisioning, audit log, advanced security controls, unlimited page history |
A few rows deserve attention for anyone tracking projects.
The Free plan is built for individuals. The pricing page labels it "for individuals to organize personal projects and life", and its pages and blocks row reads "unlimited for individuals, limited for 2+ members". A team of four building a shared tracker will hit the block limit; the page does not publish the exact number, so it is worth testing before committing.
Subtasks and dependencies are database features on every plan. The Free plan description lists "databases including subtasks, dependencies, custom properties and more". Linking tasks so one waits on another is not a paid upgrade.
Automations change at Plus. Free gets button-based automations only. Plus adds database automations that can set status, assignee, and property values automatically. For a tracker, that is the difference between a person remembering to move a card and a rule that does it.
Row-level permissions arrive at Business. Granular database permissions let a collaborator work in a database without seeing the whole thing, limited to rows where they are assigned. Without it, giving a contractor access to the task database means giving access to every task in it.
For a team of eight on yearly billing, that is $960 a year on Plus or $1,920 on Business. Many teams already pay for Plus or Business for documents, so the tracker comes at no extra cost. That is a real advantage and a fair reason to stay.
Where Notion project tracking works well
There are teams for whom moving project tracking out of Notion would be a mistake.
The documents are the work
When most of a project is writing, such as a content calendar, a product spec, a research plan, or a client proposal, the task and the document are the same object. Notion lets a database row open into a full page with headings, embeds, and comments. A separate tracking tool would hold a title and a link back to Notion, which adds a step without adding anything.
One person owns the system
Notion trackers stay healthy when someone treats the database like a product: they decide which properties exist, prune the ones nobody fills in, and fix views when they drift. In teams where that person exists and has the time, the flexibility pays off because the system grows with the team rather than against it.
The team already opens Notion every day
A tracker is only accurate if people update it. If the team already starts the day in Notion for meeting notes and docs, updating a status on the way past is cheap. The tracker benefits from habits that already exist.
The work is a list, not a schedule
Kanban by status, a "Mine" view, and a due date cover most small-team work. If the team rarely needs to see how one late task pushes three others, the built-in views are enough.
Where it starts to strain
The friction points below come up repeatedly in community threads about Notion as a project tool. None of them mean Notion is broken. They describe what happens when a flexible database is asked to behave like a fixed process.
The structure drifts
Because anyone with edit rights can add properties, a tracker that started with five fields often has fifteen after a few months, several of them half-filled. Filters that once caught every open task now miss the ones using a new status name. The fix is governance, not features: someone has to say no to new fields. When that person is busy, drift is the default.
Views are personal, but they look shared
People build their own filtered views and then discuss "the board" in a meeting, each looking at something slightly different. A project lead who asks "what is late?" gets three answers depending on whose view is on screen.
Timeline is a view, not a plan
The Timeline view shows items by start and end date, and dependencies can be linked. What a team does not get by default is a plan that reacts to change in a way everyone sees the same. When one date moves, someone still has to look at what else should move. For a team that reschedules weekly, that review is the job, and it is easy to skip.
Updates depend on visiting Notion
People who live in chat or email rarely open a database to change a status. The tracker slowly becomes a record of what was true at the last meeting. Automations on Plus help with consequences of a change, but they cannot make someone report a change they never entered.
Guests and contractors
On Free there is a 10-guest limit. On Plus and above guests are unlimited, but without Business-level row permissions, an external collaborator who can see the task database sees all of it. Teams handle this by building separate databases for outside partners, which then have to be kept in sync by hand.
Tighten the Notion setup first, or move tracking out
Most teams should try tightening before switching. Changing tools has a cost, and many of the problems above are habits that would follow the team anywhere.
Steps to tighten a Notion tracker
- Freeze the schema. Agree on the properties the tracker needs, typically status, assignee, due date, project, and priority. Remove or archive the rest. Restrict who can edit database properties.
- Define status values in writing. Write down what "In progress" and "Blocked" mean and when to use each. Keep the list short.
- Create one shared view for meetings. Name it clearly, for example "Weekly review", and use only that view when the team discusses status.
- Use automations where the plan allows. On Plus or above, set a rule so that a task moved to Done stamps a completion date, or a new task in a project gets a default assignee.
- Review dependencies weekly. Put a 15-minute slot on the calendar to look at the Timeline view and move dependent dates. Make it someone's job.
If after a month the tracker is still out of date, the problem is likely that the team does not open Notion for status, not that the database is poorly built.
Signs it is time to move tracking out
- Status updates come in chat, and someone copies them into Notion.
- The team needs a schedule view that everyone sees the same way, and dependencies are reviewed by hand.
- External partners need access to their tasks only, and the workspace is not on Business.
- The person who owned the tracker has left or has no time to maintain it.
Comparing Notion with a dedicated board tool
When tracking does move, it usually moves to a dedicated project management tool while documents stay in Notion. The two play different roles, and keeping both is common.
| Notion | Dedicated board tool | |
|---|---|---|
| Structure | Built from databases; the team designs it | Fixed board types; the team fills them |
| Best at | Documents and tasks in one page | Status, schedule, and ownership at a glance |
| Schedule view | Timeline view with linkable dependencies | Varies by tool; Gantt view often built in |
| Where updates happen | Inside Notion pages and databases | On cards, often with chat or comments attached |
| Cost model | Per member; most features gated by plan | Varies by tool; some gate by features, others by team size or board count |
The cost model row matters more than it looks. Some tools charge by feature tier, so Gantt charts or automations sit on a paid plan. Others keep every feature on every plan and charge only for team size and the number of boards. For a small team, the second model means the free tier is a full test of how the tool will work at scale. The features page lists the board types such tools typically include, from kanban and Gantt to calendar and timetable boards, and the pricing page shows a model where everything is free for up to 5 people and 10 boards, with $4 per user a month on yearly billing after that.
A detailed side-by-side of Notion and a board-based tool, including what each does not do, is on the Notion comparison page. It also covers the case where staying with Notion is the better choice.
What to change first
Start by freezing the tracker's properties and agreeing on one shared view for the weekly review; that alone fixes most drift. If status still lives in chat a month later, keep documents in Notion and move day-to-day tracking to a board tool such as Pinateca, which is free for small teams to test without a feature cap.
Q1. Is Notion's free plan enough for team project tracking?
It is designed mainly for individuals. Notion's pricing page lists collaborative blocks as limited once a workspace has two or more members, allows 10 guests, keeps 7 days of page history, and offers button-only automations. A small team can test a tracker on Free, but most teams sharing one database will need Plus.
Q2. Does Notion support task dependencies?
Yes. The pricing page lists subtasks and dependencies as database features, including on the Free plan. Dependencies can be linked between tasks, and Notion's projects page presents the timeline view as the place to see how projects fit together. Moving dependent dates when one task slips is still something the team has to review.
Q3. How much does Notion cost for a small team in 2026?
As checked on October 8, 2026, Plus is $10 per member a month billed yearly or $12 billed monthly, and Business is $20 yearly or $24 monthly. For eight people on yearly billing, that is $960 a year on Plus and $1,920 on Business. Enterprise pricing is custom.
Q4. Can contractors see only their own tasks in Notion?
Granular database permissions, which limit a collaborator to rows where they are assigned, are listed on the Business plan and above. On Plus, a guest with access to a task database can see the whole database, so teams often create a separate database for external partners.
Q5. Should documents and tasks stay in the same tool?
If most of the work is writing, keeping them together in Notion is usually simpler. If the team needs a shared schedule and updates arrive mainly through chat, many teams keep documents in Notion and track tasks in a dedicated board tool, linking between the two.