Okay so I just spent like three days rebuilding my entire Notion planner setup because my old system was honestly a mess, and I figured out some stuff that actually works.
Starting with the Basic Structure
First thing you gotta do is forget about trying to make it look pretty right away. I wasted probably two hours on aesthetics when I should’ve been thinking about what I actually needed to track. Start with three core databases and you can add more later if you need them:
- Tasks database (obviously)
- Projects database
- Calendar database for time-blocking
The tasks database is where everything lives. Create it as a full-page database, not inline, because you’re gonna be filtering and viewing it in like six different ways. My properties setup looks like this:
- Status (select): Not Started, In Progress, Waiting On, Done
- Priority (select): Urgent, High, Medium, Low, Someday
- Due Date (date)
- Project (relation to Projects database)
- Energy Level (select): High Energy, Medium, Low Energy, Mindless
- Time Estimate (select): 15min, 30min, 1hr, 2hr, 3hr+
That energy level thing changed everything for me by the way. I added it after reading this productivity article while my dog was at the groomer and I was killing time at a coffee shop. Now when I’m tired at 3pm I can filter for “Low Energy” tasks instead of staring at “write quarterly report” and feeling like garbage about myself.
The Project Database Setup
Projects database is simpler but connected to everything. Properties I use:
- Status (select): Active, On Hold, Completed, Archived
- Start Date and End Date
- Related Tasks (relation back to Tasks)
- Notes (text area for goals, links, whatever)
The relation between Projects and Tasks is crucial. When you create a task, you link it to a project, and then in your project page you can see all related tasks automatically. Took me forever to figure out how relations worked but once you get it, it’s like… oh, that’s why everyone uses Notion.
Views That Actually Matter
Here’s where Notion gets powerful but also where people get overwhelmed and give up. You need multiple views of the same data. In my Tasks database I have:
Daily View – This is a table view filtered by:
- Due date is today OR
- Due date is before today (shows overdue stuff)
- Status is not Done
Sort by priority, then by time estimate. Every morning I open this view and that’s my day.
Weekly View – Board view grouped by due date. I set it to show the next 7 days as columns. You can drag tasks between days which is super satisfying when you’re rescheduling stuff. Filter out anything that’s Done or has no due date.
By Project View – Board view grouped by Project. Shows you what’s on your plate for each active project. I filter this to only show Active projects and tasks that aren’t Done.
Quick Capture View – Table view with minimal properties visible. Just the task name, priority, and due date. This is what I use when I’m in a meeting and need to jot something down fast without all the other fields staring at me.
Wait I forgot to mention – for the board views, you gotta set up your groups manually the first time. Click the three dots, go to Group settings, and you can choose what columns show up and in what order.
Templates for Recurring Setups
Notion’s template feature is weirdly hidden but super useful. Inside your Tasks database, click the dropdown arrow next to “New” and you’ll see “New template.”
I created templates for:
Weekly Review Template – This isn’t a task, it’s actually a page template. Every Sunday I create a new page using this template. It has sections for:
- What got done this week (I literally copy-paste completed tasks)
- What didn’t get done and why
- Top 3 priorities for next week
- Stuff to delegate or delete
Client Project Template – In my Projects database, I have a template that auto-fills certain properties and includes a standard page structure with sections for client info, deliverables, timeline, meeting notes. Saves me probably 15 minutes every time I start a new client project.
Content Creation Template – Specific to my work but you could adapt this. Has fields for topic, target platform, draft status, publish date. The page template includes sections for outline, resources, and final copy.
Oh and another thing – you can set default properties in templates. So my content template automatically sets Status to “Not Started” and Energy Level to “High Energy” because writing always requires my brain to be actually functioning.
The Calendar Database Thing
This is gonna sound extra but having a separate Calendar database for time-blocking changed how I work. It’s different from the tasks database because it’s about TIME SLOTS, not tasks.
Create a new database with these properties:
- Date (date property with time enabled – this is important)
- Type (select): Deep Work, Meetings, Admin, Break, Personal
- Related Task (relation to Tasks database)
Then create a calendar view. Now you can block out time and link those blocks to actual tasks. I know it seems redundant but here’s why it works – your tasks database shows WHAT needs to be done, your calendar database shows WHEN you’re doing it.
I usually time-block on Sunday evening for the week ahead. Takes like 20 minutes. I look at my Weekly View in tasks, then create calendar blocks for when I’ll actually do them.
Workflows That Actually Stick
Having templates is useless if you don’t have a routine for using them. My daily workflow looks like:
Morning (with coffee, before I check email):
- Open Daily View
- Look at today’s calendar blocks
- Adjust if needed based on how I’m feeling
- Pick my “Most Important Task” and put a star emoji next to it
Throughout the day:
- New tasks go into Quick Capture View immediately
- I don’t organize them right away, just get them out of my head
- Check off tasks as I complete them (very satisfying)
End of day (this takes 5 minutes max):
- Go through Quick Capture View and properly categorize anything I dumped there
- Add projects, energy levels, time estimates
- Move anything I didn’t finish to tomorrow or later in the week
- Look at tomorrow’s Daily View so I’m not surprised in the morning
Sunday evening:
- Weekly review using my template
- Time-block the week ahead in Calendar database
- Check Project View to make sure nothing’s falling through cracks
Database Relations for Power Users
Once you’re comfortable with the basics, database relations are where Notion becomes actually powerful. I added two more databases to my setup:
Areas of Responsibility – This is like… life categories. Work, Health, Home, Relationships, Creative Projects, whatever matters to you. My Projects database has a relation to Areas, so every project belongs to an area.
Resources – Where I keep article links, templates I’ve downloaded, tools I use, reference materials. My Projects can link to relevant resources.
The magic happens when you create rollups. In my Projects database, I have a rollup that counts how many tasks are linked to each project. In my Areas database, I have a rollup showing how many active projects are in each area. Gives me a bird’s eye view of where my energy is actually going.
My client last week was like “I feel like I never have time for personal stuff” and when we looked at her Areas rollup, she had 8 active work projects and zero personal ones. Sometimes you need the data to see what’s obvious.
Mobile Workflow Adjustments
Notion mobile is… fine. Not great, but fine. I adjusted my workflow for phone use:
Create a “Mobile Dashboard” page that’s just links to your most-used views. I have mine set as:
- Quick Capture View (for adding tasks on the go)
- Today’s calendar blocks
- Weekly View
You can favorite this page so it’s easy to access. The mobile app’s navigation is kind of annoying so having a dashboard helps.
Also, turn on offline mode in settings if you haven’t. Nothing worse than trying to add a task on the subway and realizing you have no service and Notion won’t load.
Common Mistakes I Made So You Don’t Have To
Too many properties – I started with like 12 properties per task and never filled them out. Stick to what you’ll actually use. You can always add more later.
Too many databases – I had separate databases for work tasks, personal tasks, and someday tasks. Nightmare to manage. One tasks database with good filtering is way better.
Trying to make it Instagram-worthy – I spent hours finding the perfect cover images and icons. Nobody cares. Your planner is a tool, not a showpiece. Make it functional first, pretty later if you have time.
Not using templates – I was manually creating the same page structures over and over like a chump. Templates save so much time.
Ignoring the mobile experience – I built this beautiful desktop setup and then never used it because I’m on my phone half the time. Test your setup on mobile.
Integration Stuff Worth Knowing
Notion doesn’t integrate with everything but here’s what works:
Google Calendar – You can embed your Google Calendar in a Notion page. Not two-way sync, just viewing, but still helpful. I have mine embedded in my weekly planning page.
Zapier/Make – If you wanna get fancy, you can automate stuff. I have a Zap that creates a task in Notion whenever I star an email in Gmail. Probably overkill for most people but I like it.
Web Clipper – The Notion Web Clipper extension is actually good. When I find an article I wanna read, I clip it to my Resources database with tags. Way better than bookmarking and never looking at it again.
Maintaining Your System
The thing about Notion is it requires maintenance. Every few weeks I do a deeper review:
- Archive completed projects
- Delete tasks that are never gonna happen (be honest with yourself)
- Review my Areas to see if anything’s being neglected
- Check if my templates need updating
- Clean up my Resources database because it gets messy
I schedule this as a recurring task for the last Sunday of each month. Takes about 30 minutes and keeps everything from becoming chaos.
The reality is your system will evolve. My setup now looks nothing like it did six months ago. That’s fine. The point isn’t to build the perfect system, it’s to build something that works for you right now. Adjust as you go.



