How to Track Multiple Projects in One Notion Workspace
One project in Notion is easy. Six active projects at once is where most homegrown systems quietly break — here's the portfolio-level structure that keeps working past that point.
One project in Notion is easy. Six active projects at once is where most homegrown systems quietly break — usually because each project got its own separate page or database instead of staying as one row in a shared Projects database. Here’s the portfolio-level structure that keeps working past that point.
Where single-project tracking breaks down
A single project tracked in its own dedicated Notion page, with its own task list, works fine in isolation. The moment a second, third, and fourth active project join it — each in its own separate space — answering “what’s overdue across everything” or “which project is actually struggling” stops being possible without manually opening each one. The fix isn’t a new tool; it’s making sure every project is a row in one shared Projects database, not a separate silo.
Building the portfolio view
With every project already living as a row in one Projects database (per our main tutorial), add a Health indicator — either the % Complete rollup already covered there, or a simple manual Green/Amber/Red select if you want a more subjective read that accounts for factors a rollup can’t capture. Build a table view of Projects sorted by Health, worst-first, and that single view becomes your standing portfolio check.
A cross-project overdue view
Separately, build a Tasks view filtered to Due Date before today and Status not Done — with no Project filter applied. This single view surfaces every overdue item across every active project simultaneously, which is exactly the visibility that gets lost the moment projects live in separate silos.
Setup roadmap
Setup Roadmap
- 1
Confirm every project is a row in one Projects database
Not separate pages or separate databases per project — one database, many rows.
varies
- 2
Add a Health indicator
Either the % Complete rollup from our main tutorial, or a manual Green/Amber/Red select for subjective status.
10 min
- 3
Build a Projects table view sorted by Health
Struggling projects surface at the top automatically.
10 min
- 4
Build a cross-project overdue Tasks view
Filtered to Due Date before today, Status not Done — no Project filter.
10 min
- 5
Review the portfolio view weekly
A standing weekly habit, not a one-time setup.
10 min/week
Want the full dashboard, not just the portfolio panel?
This portfolio view pairs naturally with the My Tasks and Team Workload panels from our dashboard guide.
Launch checklist
Portfolio View Checklist
- All active projects live in one Projects database, not scattered across separate ones
- A Health indicator (rollup or manual select) exists on every project row
- A portfolio table view is sorted or filtered to surface at-risk projects first
- A cross-project overdue Tasks view exists, without a Project filter applied
- Someone owns reviewing the portfolio view on a weekly cadence
Common mistakes
Common Multi-Project Mistakes
- A separate Notion page (or database) per project. — Feels organized early on, but makes any cross-project view — “what’s overdue across everything” — impossible without manually checking each one.
- No shared Health or Status indicator. — Without a common field to sort or filter by, at-risk projects can only be found by opening each one individually.
- Treating the portfolio view as a one-time report instead of a living view. — Since it’s built from linked views, it updates automatically — the actual work is establishing the habit of checking it regularly, not rebuilding it.
- Letting the Projects database absorb unrelated content. — Meeting notes, ideas, and reference docs belong in their own database or wiki page — mixing them into Projects clutters the one view meant to stay scannable.
Free Notion Template
Multi-Project Portfolio View
The Starter Kit with a pre-built Health rollup and sorted portfolio table view.
Template link placeholder — replace href with the live Notion “Duplicate” share link before publishing.
FAQ
How many projects can one Notion workspace realistically handle?
The relational structure itself scales well past hundreds of projects — the practical limit is usually how many active projects a person can meaningfully track attention across, not a Notion technical limit.
Should each project get its own dedicated page, or just a database row?
Both — the Projects database row holds the structured data (status, deadline, rollups) and typically links out to a dedicated project page with notes, files, and context that don’t fit neatly into properties.
How do I see overdue tasks across every project at once, not project by project?
A single filtered Tasks view — filtered to Due Date is before today and Status isn’t Done — with no Project filter applied, pulls overdue items from every active project into one list.
What’s the difference between this and the dashboard guide?
This guide is specifically about the Projects-level portfolio view (health, status, overdue count per project). The dashboard guide covers a broader home page combining this with task-level and team-level panels.
We turn workflows like this into a working Notion system in days, not months.
Find Your Solution