Skip to content
Tutorials Center
My learning

Topics

Lesson 31 of 36 ยท Workflows and Systems

A Task Management System

Design a Notion task system: a Tasks database with status, priority and due dates, views for Today, Upcoming and Board, plus capture, clarify and review habits.

Tasks are the most common thing people build in Notion, and the most common thing they abandon. The difference is rarely fancy features. A good task system does three things: it makes capture instant, it makes today's list obvious, and it makes review a habit.

Notion is not available on this site, so this lesson describes the setup in the app, with labelled JavaScript stand-ins for the logic of sorting and planning.

Capture, clarify, organize, review

A simple loop, inspired by the Getting Things Done approach:

  1. Capture every task into one Inbox without thinking about structure.
  2. Clarify each item: what is the next physical action? Does it take under two minutes? Is it a task or a project?
  3. Organize by giving it a status, date and project.
  4. Review weekly.

The Tasks database

Create one database called Tasks with these properties:

Property Type Purpose
Name Title A clear action starting with a verb
Status Status Inbox, Next, In progress, Waiting, Done
Priority Select High, Medium, Low
Due Date Optional deadline
Project Relation Link to the Projects database
Estimate Number Minutes or points
Done on Date Filled by a button or automation

Keep it small. Extra properties that you never fill become clutter.

Views that do the work

One database, several views:

  • Inbox: Status is Inbox, newest first. This is where you triage.
  • Today: Status is Next or In progress and Due is today or earlier (use the "relative to today" filter option), sorted by Priority.
  • Upcoming: Due is in the next 7 days, grouped by Due week.
  • Board: a Board view grouped by Status for drag and drop.
  • By project: grouped by Project.
  • Done: Status is Done, sorted by Done on, descending.

Embed linked views of Today and Inbox on your Home page so the first screen you see is the action list.

Stand-in: the Today logic

This is not Notion; it replays the filter and sort of the Today view on a small list.

JS Stand-in: build the Today view

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Notice that overdue items appear too: due <= today is what keeps tasks from quietly disappearing.

Recurring tasks

Chores repeat: pay bills, water plants. Notion has two approaches:

  • A recurring database template that creates a new task on a schedule. This works well for "every Monday" or "first of the month".
  • A button on the task that, when pressed, marks it done and creates the next instance with a new due date.

Choose the recurring template for fixed schedules and the button for "X days after I finish", which cannot be known in advance.

Stand-in: next due date

The "after I finish" case is arithmetic. This stand-in computes the next due date for different intervals (UTC dates, so it is stable).

JS Stand-in: next occurrence

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Habits that make it stick

  • One inbox. If tasks live in five places, you will trust none.
  • Write the next action. "Mom" is not a task; "Call mom to confirm Sunday" is.
  • Limit Today. More than five to seven items is a wish list. Move extra items to Upcoming.
  • Close the loop. Mark done immediately; your Done view becomes a reward and a record.
  • Weekly review. Clear the Inbox, check Waiting items, and set next week's Today candidates.

Pin a quick-add. Add a button or use Notion's mobile and web clipper and share sheet so new items land in the Inbox in two taps. The capture step is where most systems fail.

Check your understanding

Quick check ยท 3 questions

of 3 answered You scored / 3 ยท perfect!

  1. 1. Why does the Today view use "Due is today or earlier"?

    Including earlier dates keeps overdue tasks in front of you.
  2. 2. Which is a good task name?

    A clear next action starts with a verb and says what to do.
  3. 3. How would you handle a chore that repeats 14 days after you finish it?

    A button can mark the task done and create the next instance relative to completion.

Summary

  • Run a capture, clarify, organize, review loop.
  • One Tasks database with Status, Priority, Due and a Project relation is enough.
  • Build views for Inbox, Today, Upcoming and Board instead of separate databases.
  • Use recurring templates for schedules and buttons for "after I finish".

Next: Meeting Notes and OKRs