Recurring Tasks in Notion + Self Referencing Filter (New Feature)
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.
Use a “do date” (planned execution date) as the recurring task driver, not a hard deadline with consequences.
Briefing
Recurring tasks in Notion can be handled without built-in automation by leaning on a simple scheduling habit: use due dates (not “due dates do dates” confusion) as the system of record for when work is intended to happen, then “roll” the task forward after completion. In this workflow, active tasks live in an Action Item database with a “do date” field—meaning the date the task is planned for, not the deadline with consequences. A calendar view then becomes a weekly planning outline, showing what’s scheduled across upcoming days so users can avoid overbooking and quickly see what’s coming.
For a straightforward recurring item like “create TPS reports every Thursday,” the method is to set the task’s due date to the next occurrence and optionally set a priority or reminder status (including optional scheduled time). When Thursday arrives and the work is done, the user doesn’t check a “done” box to finish the task permanently; instead, they update the due date to the next cycle (next Thursday, next month, etc.). Notion’s date picker makes this quick: open the calendar, choose the next occurrence, and the task reappears in the correct future day’s view. The core payoff is that recurring work becomes a repeatable daily action—complete the task, then bump the date—so nothing gets forgotten.
The transcript also distinguishes when this “bump the due date” approach is insufficient: tasks that take hours (e.g., a 3–4 hour TPS report on the third Friday) may need to be visible far in advance so planning can account for time blocks. In those cases, the alternative approach is to pre-schedule multiple instances. The user creates the task for the next occurrence, then duplicates it repeatedly to cover the next six months or year, adjusting the date each time. This produces a calendar that clearly communicates future time commitments, helping prevent scheduling meetings in the wrong half of the day.
A second update addresses a different recurring pain point: self-referencing filters inside Notion templates for projects, goal outcomes, and action items. Previously, when creating a new project from a template, filters that were supposed to reference “the project you’re currently in” couldn’t be set to the newly created project; they had to be left blank and then manually filled in after the project was created. The improvement comes from a new option in the template’s filter configuration that allows the filter to reference the template itself relative to the newly created page. By selecting the template name in the filter (rather than an existing project), the relational links resolve automatically when a new project is created from that template. As a result, the project-specific views—projects filtered to themselves, goal outcomes tied to the project, and action items filtered to the project—work immediately without three manual adjustments.
Together, the workflow turns recurring tasks into a predictable “roll the date” operation and turns template-based project setup into a one-click process—small mechanics that reduce friction and make planning and execution more reliable.
Cornell Notes
The system handles recurring tasks in Notion by treating the “do date” as the planned execution date and using the calendar view as the weekly schedule. After completing a recurring task, the user simply bumps the due date to the next occurrence instead of relying on a built-in recurrence feature. For long tasks that must be visible months ahead, the workflow pre-creates multiple duplicated instances (e.g., every third Friday) and sets each one’s date so future time blocks are clear. A separate template update fixes self-referencing database filters by letting filters point to the template itself, so newly created projects automatically populate project-specific views without manual filter edits. The combined effect is fewer missed tasks and less template setup work.
Why does the workflow rely on “do dates” instead of deadlines, and how does that change recurring task handling?
How does a simple weekly recurring task work step-by-step in this system?
When should the workflow switch from “bump the due date” to pre-scheduling duplicates?
How does pre-scheduling work for a monthly pattern like “every third Friday”?
What problem existed with self-referencing filters in project templates, and what changed?
How does the updated template filter selection prevent manual post-setup edits?
Review Questions
- In this workflow, what specific action replaces checking a “done” checkbox for recurring tasks, and why does it work?
- What criteria would make you choose pre-scheduled duplicates over rolling a single recurring task forward?
- How does referencing the template name in a self-referencing filter change what relational links resolve to when creating a new project?
Key Points
- 1
Use a “do date” (planned execution date) as the recurring task driver, not a hard deadline with consequences.
- 2
For simple recurring tasks, complete the task and then roll the due date forward to the next occurrence instead of marking it done permanently.
- 3
For long recurring tasks that affect calendar planning, pre-schedule multiple duplicated instances across upcoming months or a full year.
- 4
Leverage Notion’s calendar view to prevent overbooking by making future time commitments visible.
- 5
Update self-referencing database filters in templates by selecting the template itself as the relative reference, so new projects populate correctly without manual filter edits.
- 6
When templates are used by teams, relative template-based filters reduce onboarding friction and prevent missed setup steps.