Get AI summaries of any video or article — Sign up free
Notion Task Lists & "Do Dates" (Viewer Q&A) thumbnail

Notion Task Lists & "Do Dates" (Viewer Q&A)

August Bradley·
5 min read

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

TL;DR

Use “do dates” for planned action on a specific day, reserving “due dates” for hard deadlines.

Briefing

A practical “do date” system in Notion is presented as the fix for tasks that don’t yet have hard deadlines—while also preventing the psychological weight of endless, undated lists. The core rule: anything truly important gets a scheduled “do date” (not a “due date” for a hard deadline), which forces deliberate attention on a specific day. If a task keeps getting pushed out repeatedly, that pattern becomes feedback that the task may be less important than first assumed, and it should be deleted or demoted rather than endlessly rescheduled.

The distinction matters because “do dates” are designed for planning and review, not emergency urgency. A do date is the day someone intends to take action on a task—whether that action is completing it, reevaluating it, or rescheduling it further out. The system treats repeated rescheduling as a signal: if time never opens up, the task’s priority likely isn’t strong enough to justify occupying schedule space. Letting time slip can reduce the task’s perceived urgency, and the method encourages users to make a conscious decision—do it, delete it, or kick it down with a new do date—so tasks don’t fall through the cracks.

To handle tasks that can be done “any day” (like reading an article, calling a friend, or washing a car), the system adds a separate “ongoing low priority” list for discretionary time. This list acts as a rolling queue of items that are worth remembering but not time-critical. It’s intentionally bounded to avoid turning into an unmanageable backlog. For example, the reading workflow can pull from Pocket, but the highest-priority items can be surfaced as bullet points so they don’t get buried in a long saved list. The same approach applies to YouTube “watch later” videos and books: these sources can feed the low-priority list, but the list must stay short enough to remain actionable.

When spare time is limited, the system still keeps the “today action items” dashboard as the center of day-to-day execution. The low-priority list is positioned as a supplement for moments that open up, not a replacement for scheduled work. If someone has frequent downtime and wants more variety, the method suggests expanding the low-priority area with categories and reviewing it on a weekly (and sometimes monthly) cadence—while still capturing new ideas quickly in an inbox-like place.

The method also addresses operational reality: if the day gets derailed, tasks can be dragged to the next day or next week in the calendar view for reconsideration. But the system insists that the real discipline is making deliberate trade-offs between what was scheduled and what pulls attention away. Finally, for longer-term efforts, tasks can be attached to projects and the project can be placed on hold so they don’t clutter the task database with constant do dates; when the project is activated, the tasks become live again. The overall message is that do dates create accountability and prevent forgetting, while low-priority lists provide a controlled outlet for flexible, discretionary work.

Cornell Notes

The system distinguishes “do dates” from hard “due dates.” A do date is the planned day to take action on a task—complete it, reevaluate it, or reschedule it—so important items never get forgotten. If a task keeps getting bumped repeatedly, that pattern is treated as evidence the task may not be important enough to keep occupying schedule space, prompting deletion or demotion. For tasks that can happen anytime, an “ongoing low priority” list provides a rolling queue for discretionary time, drawing from sources like Pocket and YouTube watch later but staying short to remain usable. When days derail, tasks can be dragged to the next day/week; when projects are on hold, tasks can be kept out of the active schedule until the project is reactivated.

What’s the practical difference between a “do date” and a “due date,” and why does it change how tasks are managed?

A “due date” is reserved for hard deadlines. A “do date” is the day someone plans to take action on a task—either completing it or performing a deliberate next step like reevaluating and rescheduling it. That planning function is the point: do dates ensure deliberate consideration at a specific time so tasks don’t fall through the cracks, even when there’s no emergency deadline.

Why does repeated rescheduling of a task become a decision tool rather than just a scheduling nuisance?

When a task keeps getting pushed out because there’s never time, the system treats that as feedback about priority. The method frames the pattern as a cue that the task may not be important enough to justify schedule space. Over time, the initial urgency can fade, making deletion or demotion more appropriate than endless bumping.

How does the system handle tasks that are flexible—things that can be done any day of the week?

Flexible tasks go into an “ongoing low priority” list for discretionary time. These items are meant to be reviewed when spare moments appear, not to demand attention on a specific day. If an item later proves important enough, it can be assigned a do date; otherwise it stays in the rolling list.

What prevents the low-priority list from turning into an overwhelming backlog?

The system emphasizes keeping the list short and actionable. For reading, Pocket can store many articles, but the highest-priority ones can be surfaced as bullet points so they don’t get buried. During weekly review, items that no longer matter can be deleted (while still keeping them in Pocket if they might be revisited later).

What’s the system’s approach when a scheduled day goes off track?

If tasks don’t get done because the day is derailed, they can be reassigned by dragging them to the next day or next week in the calendar view for reconsideration. The key discipline is making deliberate trade-offs—deciding what to stick with versus what derails attention—rather than getting pushed off course without evaluating the cost.

How do projects reduce schedule clutter from tasks that aren’t ready to be scheduled?

Tasks that belong to longer-term efforts can be attached to a project instead of being kept as active do-dated items. If the project is placed on hold, those tasks don’t clutter the task database with constant do dates. When the project is activated again, the tasks become live scheduled items.

Review Questions

  1. How would you decide whether a task should receive a do date versus live in the ongoing low priority list?
  2. What signals would make you delete a task rather than keep pushing its do date forward?
  3. How would you use projects on hold to prevent too many scheduled items from accumulating?

Key Points

  1. 1

    Use “do dates” for planned action on a specific day, reserving “due dates” for hard deadlines.

  2. 2

    Treat repeated rescheduling as priority feedback; if a task keeps getting bumped, consider deleting or demoting it.

  3. 3

    Keep flexible, anytime tasks in an “ongoing low priority” list for discretionary time, not in the main scheduled queue.

  4. 4

    Bound low-priority lists so they stay actionable; surface only the highest-priority items from sources like Pocket and YouTube watch later.

  5. 5

    When days derail, drag tasks to the next day/week for deliberate reconsideration rather than letting them vanish.

  6. 6

    Attach not-yet-ready work to projects and put projects on hold to prevent constant do-date clutter in the active task list.

  7. 7

    Use weekly review to prune low-priority items that no longer matter and to keep the system psychologically light.

Highlights

A do date is a planning mechanism: it forces deliberate consideration even when there’s no hard deadline.
Endlessly bumping a task becomes a diagnostic signal—time slip can reveal the task isn’t as important as first thought.
The ongoing low priority list is a controlled outlet for discretionary tasks, but it must stay short to remain usable.
If a day derails, tasks can be dragged forward; the real discipline is choosing what to stick with.
Projects on hold keep unscheduled work out of the active do-date queue until it’s time to activate.

Topics