Get AI summaries of any video or article — Sign up free
Huge NEW Notion Update! First Look at Recurring Tasks ✨ (calendar view tutorial) thumbnail

Huge NEW Notion Update! First Look at Recurring Tasks ✨ (calendar view tutorial)

Red Gregory·
5 min read

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

TL;DR

Notion’s recurring tasks generate new pages from templates on a schedule, but they populate “created time” rather than a true “date” field.

Briefing

Notion’s long-awaited “recurring tasks” feature turns templates into automatically generated daily/weekly/monthly/yearly task pages inside a calendar view—so recurring checklists can appear on the correct day without manually creating them. The core workflow is built around a key limitation: recurring pages can’t populate a true “date” property. Instead, Notion fills a “created time” timestamp when the recurring template generates, and the calendar can only reliably display that timestamp unless users add a workaround.

The tutorial starts from a blank database configured with a calendar view. A new database is created, a table view is added, and a “created time” property is included because it becomes the only dependable marker for when the recurring page was generated. A template (“new tasks for today”) is then built so each generated page contains a checklist (via a to-do block or a keyboard shortcut) plus an icon and title. When the template is set to repeat—daily, weekly, monthly, or yearly—Notion auto-populates the template on the specified cadence, but only for the day it’s generated. It does not pre-fill future occurrences into upcoming days.

In practice, the calendar view initially won’t show the recurring page on the expected date if the calendar is configured to display a date property, because recurring tasks don’t write to date fields. Switching the calendar layout to “show calendar by created time” makes the recurring entries appear on the correct day. The creator then highlights the annoyance: there’s no built-in way to populate a date property directly from the recurring template, and the “created time only” approach can be inconvenient.

To restore calendar behavior, a formula property is added. The formula checks whether a user-entered “date” property exists; if it does, the formula uses that date. If the date property is empty, the formula falls back to “created time.” With the calendar view switched to “show calendar by” this formula (configured to behave like a date), recurring tasks land on the right day while manually added tasks can also appear on user-chosen dates.

The workflow also includes practical usability tweaks. Entries can’t be created directly inside the calendar grid; new tasks must be added via the “new” button. To reduce friction, a “done” checkbox property is added and displayed through the calendar so tasks can be marked complete from the calendar view. The tutorial further demonstrates nesting: a separate task list database is connected to the calendar via a relation, and a linked database view inside each recurring day page filters tasks to only those tied to that specific day template. This creates a daily workspace where existing tasks can be pulled in, new tasks can be added, and the checklist grows over time.

Overall, recurring tasks provide the missing automation for daily planning, but the calendar/date limitation forces users to rely on “created time” plus a formula workaround if they want both recurring generation and manual date scheduling to coexist cleanly.

Cornell Notes

Notion’s recurring tasks feature generates new task pages from templates on a schedule (daily/weekly/monthly/yearly), and those pages appear in a calendar view. The catch is that recurring templates don’t populate a real “date” property; they only fill “created time” when the page is generated. By switching the calendar to use “created time,” recurring items show up on the correct day, but users who want manual date scheduling need a workaround. The tutorial builds a formula that uses a user-entered date when present, otherwise falling back to “created time,” then sets the calendar to display that formula as a date. This enables both automated recurring checklists and manually dated tasks in the same calendar.

How does Notion decide which day a recurring task page appears on in the calendar?

Recurring templates populate a “created time” timestamp when the page is generated. If the calendar view is configured to display a date property, the recurring page won’t appear as expected because recurring tasks don’t write into date fields. Setting the calendar layout to “show calendar by created time” makes the recurring page show up on the day it was created.

Why can’t recurring tasks pre-fill future occurrences, and what does that mean for planning?

The recurring setup generates entries only for the day they occur. Even if a template repeats on specific weekdays, Notion won’t automatically create pages for the week ahead. That means users must rely on the recurring generation timing rather than expecting future days to already contain the checklist.

What workaround restores manual calendar scheduling for tasks alongside recurring ones?

Create a formula property (e.g., “show in calendar”) that checks whether a user-entered “date” property is filled. If the date property is not empty, the formula returns that date; otherwise it returns “created time.” Then configure the calendar to “show calendar by” the formula so recurring pages use created time while manually added tasks use the chosen date.

What’s the limitation around adding tasks directly in the calendar grid?

Tasks can’t be created inside the calendar itself. Instead, users must create new task pages using the database’s “new” button, then set the date (or rely on created time for recurring entries). The calendar is used for viewing and quick actions like toggling completion.

How can users mark tasks complete without opening each page?

Add a “done” checkbox property to the database and ensure it’s visible in the calendar view (via the database menu’s properties visibility controls). With “done” shown, users can click checkboxes directly from the calendar for tasks that appear that day.

How does the tutorial nest a task list inside each recurring day page?

A separate task list database is connected to the calendar database using a relation property. Inside the recurring day template, a linked database view is added (linked view of the task list), filtered so it only shows tasks whose relation points to the current day template (matching the template’s title/relation value). This produces a daily page that pulls in relevant tasks and allows adding new ones.

Review Questions

  1. What property must be used for the calendar to reliably display recurring template pages, and why?
  2. How does the formula workaround decide between a manually set date and “created time”?
  3. What steps are required to show a “done” checkbox through the calendar view?

Key Points

  1. 1

    Notion’s recurring tasks generate new pages from templates on a schedule, but they populate “created time” rather than a true “date” field.

  2. 2

    Calendar views only show recurring entries correctly when configured to display “created time” (or a formula that uses it).

  3. 3

    Recurring tasks don’t pre-fill future days; they appear only on the day they’re generated.

  4. 4

    A formula property can combine manual scheduling and recurring generation by using a user-entered date when present and falling back to “created time” when empty.

  5. 5

    Tasks can’t be created directly inside the calendar grid; creation happens via the database “new” flow.

  6. 6

    A “done” checkbox can be surfaced in the calendar so completion can be toggled without opening each task page.

  7. 7

    Daily pages can pull in related tasks by linking a task list database and filtering the linked view to the current recurring day template.

Highlights

Recurring templates reliably stamp “created time,” and that timestamp is the anchor for calendar placement.
Because date fields don’t get populated by recurring templates, a formula fallback is the practical way to make calendars behave like true scheduled planners.
The calendar can be used for quick completion via a visible “done” checkbox, even though creation must happen outside the calendar grid.
Linked database views plus a relation filter let each recurring day page function like a personalized task inbox.

Topics

Mentioned