How to build a task manager in Notion (complete guide)

Notion is an excellent task manager and a magnificent trap. Excellent because your tasks live next to your notes, your projects and your documents instead of on a separate island. A trap because it lets you build whatever you want, and what almost everyone builds is a beautiful system they abandon after three weeks.

This guide is the minimal version that actually survives: what to build, what not to build, and how to keep maintenance from becoming the work itself.

Rule number one: one database, not ten

The foundational mistake is creating a task database per project, or per life area, or per client. It looks tidy and it's fatal: it forces you to decide where each task goes before you can even write it down, and to check several places to find out what you're doing today.

One single task database. Everything goes in there. Separation happens through properties and views, not through different databases. This is also what makes automated input possible: one destination to send everything to.

The properties you actually need

The temptation is to add fifteen properties. Filling them in is work, and maintenance work is what kills systems. These six cover 95% of cases:

Name — Title

The action, starting with a verb. "Call Marta about the contract", not "Marta contract". The verb forces it to be a concrete action rather than a vague topic, which is half the battle in GTD.

Status — Status

Three options, not eight:

• To do
• In progress
• Done

If you feel you need "Blocked", "In review" and "Waiting on someone else", ask yourself whether you'll genuinely keep them up to date. A status you don't update is worse than not having one.

Priority — Select

High / Medium / Low. No numeric levels, no P0–P4. The only job of this property is that when you open a list of twenty things, you know where to start.

Due date — Date

Only fill it in when a date genuinely exists. The habit of dating everything means that within two weeks you have fifteen overdue tasks in red, you stop looking at them, and the property loses all its value.

Project — Relation

Linked to your Projects database. This is the property that makes Notion worth it compared to a regular task app: from a project's page you see all its tasks without duplicating anything.

If you don't have a projects database yet, start with a simple Select and convert it later.

Created — Created time

Automatic, zero maintenance, and it powers the most useful thing of all: a "captured this week" view and a "hasn't been touched in 30 days" one. The second is your junk detector.

Optional, if you work in a team: Assignee (Person). Nothing else.

The views you'll really use

A database without views is a long list. Views are what turn it into a system. Build these four and resist the urge to build a fifth:

1. Today — Table or list. Filter: Status is not Done and (Due date is today or earlier or Priority is High). Sort: priority descending. This is your working screen, the one you leave open.

2. Inbox — Filter: Project is empty and Status is To do. Everything you captured without classifying. Emptying this view is your five-minute daily review.

3. By project — Board view grouped by Project, filtering out the done ones. For the weekly review: see at a glance which project has stalled.

4. Week — Calendar view by Due date. For things with real dates, and for spotting overloaded weeks before they land on you.

The real bottleneck: getting tasks in

Here's the problem no Notion template solves. Your system can be immaculate and still fail, because adding a task from your phone in Notion is slow. Open the app, wait for it to sync, find the database, "+ New", type, fill in properties. Close to a minute, and the mobile app makes it heavier going than desktop.

The outcome is predictable: when you're out of the house you write nothing down, and a task manager that only gets fed while you're sitting at a laptop doesn't reflect your actual life. It's exactly the failure of GTD's capture phase.

There are three ways to fix it, from least to most effective:

A home-screen widget. Notion offers a widget that opens the database directly. Saves a few seconds. Still requires typing.

Share to the widget from other apps. Useful for saving links, useless for your own thoughts.

Automated voice capture. You record an audio note wherever you are, the AI transcribes it, pulls out the actions and writes them into your database with the properties already set. The cost of capturing drops to five seconds and needs no hands.

That's MicTask: you send a voice note over Telegram and the tasks show up in whichever Notion database you choose — you can connect several and switch destination on the fly, say one for work and one for personal.

Five mistakes that make people quit the system

1. Over-designing before using it. Formulas, rollups, four related databases and a dashboard. Start with one table and six properties; only add what you genuinely miss in real use.
2. Never deleting. A list of 300 tasks where 200 no longer matter is a list you don't look at. In the weekly review, delete without mercy. If it hasn't moved in two months, you're not going to do it.
3. Confusing tasks with projects. "Redesign the website" isn't a task, it's a project. The task is "write the first draft of the homepage". If you can't start it in the next ten minutes, it isn't a task.
4. Using Notion as a calendar. Notion is bad at time management. Leave events in your calendar and actions in Notion.
5. Treating the system as permanent. Revisit it every few months: drop the property you never fill in, delete the view you never open.

The summary, ready to copy

• One task database, one project database.
• Six properties: Name, Status, Priority, Due date, Project, Created.
• Four views: Today, Inbox, By project, Week.
• Five minutes a day to empty the inbox, twenty minutes a week to clean up.
• And fix mobile capture, or none of the above will matter.

If you'd rather get tasks into Notion by talking instead of typing, try MicTask.