Get AI summaries of any video or article — Sign up free
The Ultimate Notion To Do List (free notion template setup for students) thumbnail

The Ultimate Notion To Do List (free notion template setup for students)

Priscilla Xu·
5 min read

Based on Priscilla Xu's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Capture every loose thought or task into an inbox immediately to prevent forgetting caused by short-term memory limits.

Briefing

A “messy brain” problem has a practical fix: capture every loose thought and task immediately, then route it through a structured workflow so nothing relies on memory. The core claim is that short-term memory fades in about 20 seconds, so ideas and obligations must be dumped into an external “inbox” system right away—or they get forgotten and resurface later as missed calls, appointments, and unfinished work.

From there, each item gets clarified into a next step. Tasks are sorted by whether they’re actionable. Actionable items are decided based on whether the person should do them personally or delegate them; non-actionable items are stored for later. Non-actionable entries split into two buckets: trash (things that no longer matter and can be deleted) and reference (materials to read, watch, or consume later). The system’s purpose is to create “task knockouts” that move work forward toward goals, while keeping the mind clear enough to process rather than memorize.

The transcript then lays out how to add context so tasks become usable, not just recorded. Each actionable item can include properties such as location, required tools, involved people, due date, and urgency. In Notion, the workflow uses tags and properties to attach that context, then routes tasks into different views based on time and status. A calendar view filters out completed items so day-specific and time-specific commitments stay visible. A “do now” table filters for tasks due today, while other tables filter by due within the week or by project/area.

Projects and areas of responsibility provide the horizontal/vertical structure. A project is defined as something requiring more than one action and able to be completed within a year. Next actions sit under projects as the concrete steps that keep progress moving. Areas of focus act like responsibility lanes—such as family, health, social life, or vacation—each containing projects with due dates. The “vertical” rule is to keep tasks in the right lane; for example, studying a test chapter should not drift into a vacation pile.

Several supporting lists handle uncertainty and coordination: a “Someday/Maybe” list for long-term ideas or bucket-list items, and a “Waiting For” list for tasks dependent on other people’s schedules (e.g., waiting for a friend to confirm a meetup). The system also emphasizes regular review. Daily reflection checks how the system is being used, while weekly review keeps tasks, projects, and bucket-list items current and feeds next week’s inventory of actions.

Finally, the transcript frames execution as “engage and start the fight,” using GTD’s five-step loop: capture, clarify, organize, reflect, and engage. When choosing what to do now, four factors guide decisions—context, energy, priority, and time available. The workflow can be planned in advance, but it also accommodates interruptions by handling tasks “as they come” when real life changes the schedule.

The overall message is not that the system must be perfect immediately; mastery takes time. The suggested progression moves from day-to-day clarity, to integrating the system into ongoing project management, and eventually to scaling up toward longer-term goals and life purpose—so productivity doesn’t turn into an endless hamster-wheel.

Cornell Notes

The workflow centers on GTD-style productivity: capture everything immediately into an inbox, clarify what each item is, organize it with context, reflect regularly, and then choose what to do now. Because short-term memory lasts only about 20 seconds, tasks and ideas must be externalized or they’ll be forgotten. Actionable items get a next step (do it now, delegate it, or define the next action), while non-actionable items go to either trash or reference. Projects are multi-step outcomes completed within a year, supported by next actions filtered by date and project properties in Notion. Weekly and daily reviews keep the system current and help turn “Someday/Maybe” and waiting items into actionable work when the timing is right.

Why does “capture” come first, and what problem is it meant to solve?

Capture means dumping any thoughts or tasks into an external inbox right away. The transcript ties this to memory limits: short-term memory holds information for only about 20 seconds, so anything not processed into long-term memory gets forgotten. The practical payoff is fewer missed obligations—like forgetting a call—because tasks don’t rely on mental recall.

How should a task be clarified once it’s captured?

Each item gets two core checks: (1) Is it actionable or not? If actionable, decide whether the person should do it or delegate it. If not actionable, decide how to store it: trash for items that no longer matter, or reference for materials to consume later (e.g., reading, watching, or keeping restaurant/movie ideas for future use).

What does “context” mean in this Notion setup, and why does it matter?

Context turns a task into something you can execute under real conditions. The transcript lists properties such as location, required tools, involved people, due date, and urgency. In Notion, tags and properties attach this context to each task, making it easier to filter and pick the right work at the right time.

How are projects, next actions, and time-based views organized?

A project is defined as an outcome requiring more than one action and finishable within a year. Next actions are the concrete steps under each project. Notion views then filter tasks by date and project/area properties: a “do now” table shows items due today; a calendar view shows time-specific tasks; other filtered views handle due within the week and project/area groupings.

What roles do “Someday/Maybe” and “Waiting For” play?

“Someday/Maybe” stores bucket-list or long-term ideas when timing isn’t clear yet—useful for ideas that may later spark into a real project. “Waiting For” tracks tasks dependent on other people’s responses or schedules, such as waiting for a friend to confirm a meetup time; the item stays visible until the dependency resolves.

How does the system decide what to do right now?

Execution uses four factors: context, energy available, priority, and time available. The transcript also allows a second approach—doing tasks as they appear during the day—because life interrupts plans (like a text arriving during dinner). The goal is balance: handle spontaneous needs without letting them fully derail control over priorities.

Review Questions

  1. What criteria determine whether an inbox item goes to “do,” “delegate,” “trash,” or “reference”?
  2. How do the definitions of “project” and “next action” affect how tasks are filtered and completed?
  3. What daily and weekly review activities keep the system accurate, and how do they feed future actions?

Key Points

  1. 1

    Capture every loose thought or task into an inbox immediately to prevent forgetting caused by short-term memory limits.

  2. 2

    Clarify each item by asking whether it’s actionable; then decide between doing it, delegating it, or storing it.

  3. 3

    Route non-actionable items into trash (delete) or reference (keep for later consumption).

  4. 4

    Add task context using properties like location, tools, people, due date, and urgency so tasks are executable.

  5. 5

    Use Notion views to filter tasks by time (calendar, due today, due this week) and by project/area.

  6. 6

    Define projects as multi-step outcomes completed within a year, and manage them through next actions.

  7. 7

    Choose “what to do now” using context, energy, priority, and time available, while still accommodating real-life interruptions.

Highlights

Capture first: ideas and tasks must leave the mind and enter an inbox immediately, because short-term memory fades in about 20 seconds.
Actionable vs. non-actionable is the decision fork; non-actionable items split into trash or reference.
Projects are multi-step and year-bounded; next actions are the concrete steps that keep progress moving.
Weekly review turns “Someday/Maybe” and other stored items into a refreshed pipeline of next actions.
Execution balances planned work with “as it comes” interruptions using context, energy, priority, and time.

Topics