How to Set Up a Project Management System in Notion in 30 Minutes
🔍 Want the best deal? Check current prices and availability.
Compare Prices →When you buy through links on our site, we may earn a commission.
How to Set Up a Project Management System in Notion in 30 Minutes
Most people who try Notion for project management end up with a beautiful mess. They build a dashboard, add eleven databases, watch three hours of YouTube tutorials, and then abandon the whole thing two weeks later when a real deadline shows up.
The problem usually isn't Notion. It's the scope. A project management system needs three things to work: a place to track projects, a place to track tasks, and a way to see what's due this week. That's it. Everything else is decoration you can add later, once the system has survived its first month.
So here's the plan: 30 minutes, two databases, a handful of views, and one template. No plugins, no paid templates, no elaborate PARA-method scaffolding. Just a system you'll actually open on Monday morning.
I've built this exact setup for freelancers, two-person agencies, and marketing teams of about a dozen people. It works at all three sizes. Let's go.
What You'll End Up With
Before we start clicking, here's the target:
- A Projects database where each project has an owner, a status, a deadline, and a linked set of tasks
- A Tasks database where every task belongs to a project and has a due date and priority
- Five views that answer the questions you actually ask during a work week: What am I doing today? What's overdue? What's coming up? What's the status of each project? What's on the calendar?*
- A project template so new projects take 20 seconds to spin up instead of 10 minutes
- A couple of automations so you stop manually changing statuses
What you won't get: time tracking, resource allocation charts, or a replacement for your accounting software. Notion isn't built for those, and pretending otherwise is how people end up disappointed.
Before You Start (3 minutes)
Three quick decisions. Write them down before you open Notion, because deciding mid-build is how a 30-minute setup turns into a 3-hour one.
1. Pick your status values. Keep it to four or five. Something like: Not Started → In Progress → In Review → Done. Maybe "Blocked" if your work genuinely stalls. If you find yourself wanting eight statuses, you probably want tags instead.
2. Decide who's using this. Just you? Then skip the owner property and save yourself a field. A team of five? Add "Owner" and be strict about it — unassigned tasks are the single biggest failure mode in shared Notion setups.
3. Pick one place for it. Don't scatter projects across your personal and team workspaces. One top-level page called "Projects" or "Work," everything lives under it. Future you will be grateful.
You'll also need a Notion account. The Free plan covers everything in this tutorial for a solo user — unlimited pages and blocks, though file uploads are capped at 5 MB per file and page history only goes back 7 days. If you're adding teammates or want longer version history, the Plus plan is the usual step up. Check Notion ->
Step 1: Create the Projects Database (5 minutes)
Create a new page in your sidebar. Call it Projects. Type /database and choose Database — Inline (or "Table view" depending on your Notion version). You now have an empty table with a Name column.
Rename the database to "Projects" by clicking its title. Then add these properties:
| Property | Type | Options / Notes |
|---|---|---|
| Name | Title | The project name. Keep it short — "Q1 Newsletter Relaunch," not a sentence. |
| Status | Status (or Select) | Not Started, In Progress, In Review, Done |
| Owner | Person | Skip if you're flying solo |
| Deadline | Date | Turn on "End date" only if projects genuinely have ranges |
| Priority | Select | High, Medium, Low — or P0/P1/P2 if you prefer |
| Progress | Formula | Optional; see below |
| Tasks | Relation | We'll connect this in Step 2 |
A note on the Status property type: Notion's dedicated "Status" type (as opposed to a plain Select) groups your options into To-do, In progress, and Complete categories. That grouping is what powers the board view columns and lets Notion calculate completion percentages later. Use it if your workspace has it; a Select works fine otherwise.
On the Progress formula: it's tempting to build a formula that counts completed tasks and divides by total. It's also the single most common place people get stuck, because the relation needs to be two-way and the formula needs to handle empty states. If you're on a 30-minute budget, skip it. Add it in week two when you know the system is sticking.
Delete the default empty rows and add two or three real projects — real ones, not "Project A." You want to test the system against actual work.
Step 2: Build the Tasks Database (7 minutes)
Create a second page in your sidebar called Tasks, and again add an inline database. This is the workhorse. Properties:
| Property | Type | Options / Notes |
|---|---|---|
| Name | Title | The task itself, starting with a verb |
| Status | Status | To Do, Doing, Blocked, Done |
| Project | Relation | Points to the Projects database |
| Assignee | Person | Skip for solo use |
| Due | Date | The single most important field |
| Priority | Select | High, Medium, Low |
| Notes | Text | Optional context |
Now the important part — the relation. Click the "Project" property, choose Relation, and select your Projects database. Notion will offer to create a matching relation on the Projects side. Say yes. That's what gives each project page its own list of tasks without you building anything else.
Two settings to check while you're in there:
- Limit to one project per task. In the relation settings, set it to "Limit to 1 page." Multi-project tasks sound useful and are almost always a mess in practice.
- Show on Projects as a property, not a page. This keeps the Projects table readable instead of cluttered.
If you want subtasks, add a self-referencing relation on Tasks (a relation pointing back to Tasks) and name it "Parent task." Don't do this on day one unless your work genuinely has three levels. Most task lists don't.
Step 3: Set Up the Views That Do the Work (5 minutes)
This is where Notion earns its keep. A database without views is just a spreadsheet with worse ergonomics. Add these five, in this order.
View 1 — "This Week" (Table). Filter: Due date is on or before "Today + 7 days," and Status is not Done. Sort by Due date ascending. This is your default working view. Pin it.
View 2 — "Overdue" (Table). Filter: Due date is before today, Status is not Done. Sort ascending. Check this every morning. It should be empty most days.
View 3 — "Board" (Board view). Group by Status. This is the view you show in standups. Add a filter for the current project if you're reviewing one thing at a time.
View 4 — "Calendar" (Calendar view). Show by Due date. Useful for spotting the weeks where three deadlines land on the same Thursday — which is always the week you also have a dentist appointment.
View 5 — "By Project" (Table, grouped). Group by Project, collapse all groups. This gives you a one-screen overview of what's in flight across every project without opening each one.
The key trick: these are all views of the same database. You're not duplicating data. Change a task's status in the board view and it updates in the table, the calendar, and the project page. That's the whole point of the relational setup, and it's why Notion beats a folder full of separate lists.
Step 4: Build a Project Template (4 minutes)
Templates are where Notion saves the most time, and most people never set them up. Here's the version worth building.
Go to your Projects database, click the dropdown next to the blue New button, and choose + New template. Name it "Standard Project."
Inside the template body, add:
- A one-line objective statement (what does "done" mean for this project?)
- A Key results section with three bullets
- A linked view of the Tasks database, filtered to this project. To do this, type
/linkedand select Tasks, then set the filter to "Project contains [the current project]." Notion will offer a "filter by current page" option — use that, so the view adapts automatically to whichever project you're on. - A Meeting notes section
- A Decisions log section — a simple bulleted list where you record what was decided and when. This one saves arguments later.
Now when you create a project, you pick "Standard Project" and get all of that instantly. Twenty seconds instead of ten minutes.
Step 5: Build a Dashboard (3 minutes)
Create a page called Work Dashboard and pin it to the top of your sidebar. Inside, add linked views:
- Tasks filtered to "Due this week," sorted by date
- Tasks filtered to "Overdue"
- Projects filtered to "In Progress," sorted by deadline
- A quick-links section with your most-used pages
This is the page you open first. Everything you need to decide what to do today is on one screen. Don't add more than four blocks — a dashboard you have to scroll is a dashboard you stop opening.
Step 6: Add Two Automations (3 minutes)
Notion's built-in automations live in the database's ... menu under Automations. Two are worth setting up immediately:
1. Auto-set completion date. When Status changes to Done, set a "Completed on" date property to today. Takes 30 seconds and gives you a real record of when things actually finished — useful when someone asks why a project took six weeks.
2. Recurring task reset. For tasks that repeat (weekly reports, invoice runs), create a "Recurring" checkbox property and an automation that, when Status changes to Done and Recurring is checked, creates a new task with the due date pushed forward a week. It's not as clean as a dedicated recurring-task tool, but it works.
One honest caveat: automations are capped on the Free plan, and the limits are more generous on paid tiers. If you're running a lot of recurring work, this is one of the few places where the upgrade genuinely pays for itself. Check Notion ->
Notion vs. the Alternatives: What It Actually Costs
If you're deciding whether Notion is the right home for this system at all, here's how the pricing stacks up against the tools people usually compare it to. Prices are per user per month, billed annually, and they change — check the vendor pages before you commit.
| Tool | Free plan | Entry paid tier | Mid tier | Best for | Where Notion wins / loses |
|---|---|---|---|---|---|
| Notion | Yes — unlimited pages, 5 MB file cap, 7-day history | Plus, ~$10 | Business, ~$15 | Docs + tasks in one place | Wins on flexibility and cost per feature. Loses on native time tracking and granular permissions below Business. |
| Asana | Yes, |
🔍 Want the best deal? Check current prices and availability.
Compare Prices →