By 
To make a Notion database template repeat, open the dropdown beside New, select ••• beside the template, and open Repeat. Choose its frequency, start date, and creation time. A repeating database template creates a new copy on that schedule; it does not reset the task you finished last week.
I recommend this approach for a weekly report, meeting agenda, or review checklist that needs a separate record for each occurrence. If the next task should wait until the previous one is complete, choose a completion-based recurring task workflow instead.
Prepare the template before switching on Repeat
Before creating or editing the template, use a database you are allowed to edit and check that it is unlocked. Thomas Frank’s database-template guide identifies unlocking as a prerequisite. If those controls are unavailable, ask the database owner to enable the appropriate access before continuing.
Open the database where the new tasks should live. In the dropdown beside New, choose + New template. Give it a recognizable name, such as Weekly review, then add its default properties and page content. For an existing template, use ••• → Edit in the same menu. These are the paths in Notion's template setup instructions.
Use the template for what stays the same. In an educational weekly-review example, that might mean three unchecked checklist items: review open work, identify blocked tasks, and choose next week's priorities. The observations and decisions belong in each generated page, not in the master template.
| Field or content | Template choice | Reason |
|---|---|---|
| Status | Your starting status, such as To do | A fresh occurrence should arrive as unfinished work. |
| Owner | The person responsible for every review | Keep a fixed owner only if that assignment really repeats. |
| Client or Project relation | Blank, unless every occurrence belongs to the same record | A template relation is an existing page reference, not an instruction to find the right client later. |
| Due date | Blank for this simple setup; assign the occurrence's deadline when reviewing it | The creation schedule and the task's deadline are separate decisions. |
| Page body | Stable prompts and unchecked checklist items | Each occurrence needs space for its own answers. |
The relation deserves a close look. Notion warns that a relation filled into a template is inherited by every page created from it. A fixed parent project can be useful; a client that changes from week to week should stay blank. Templates are also specific to the database where you create them, so check that you are editing the right database's template.
Set the frequency and first creation time
- Return to the database's New dropdown. On a smaller screen, Notion may show + instead.
- Find the intended template and select its ••• menu.
- Open the dropdown beside Repeat.
- Choose daily, weekly, monthly, or yearly recurrence. Set the interval, start date, and time for the new page to be created.
- Save the repeat settings, then reopen the template's Repeat settings to check the rule you have set.
The current setup reference covers the interval, start date, and time. Notion's fuller guide also describes Custom schedules, including every three days, Tuesday and Thursday each week, or every two months.
For a dated educational example, choose Monday, November 16, 2026 at 9 a.m. as the first creation, then repeat every week. November 23 and November 30 are the next two intended Mondays. If you instead choose every two weeks, the second intended creation is November 30, not November 23.
| Decision | Weekly-review example | Reader check |
|---|---|---|
| Template and database | Weekly review in Tasks | Reopen Repeat beside this template in the correct database. |
| Interval | Every week | Do not confuse this with every two weeks. |
| First creation | November 16, 2026 at 9 a.m. | Record the intended date and time before it occurs. |
| Deadline | Due date remains blank in this simple template | Assign the occurrence's deadline separately; it is not supplied by the creation rule. |
For a team in several time zones, agree which local time “9 a.m.” means and record that expectation with the rule. After the first scheduled creation, compare the new page's Created time with the intended date and time before relying on the schedule.
Keep creation time separate from due date
Repeat answers “When should this database page be created?” A Date property answers “When is this task due?” Do not treat the scheduled creation time as proof that the new page has the deadline you intended.
The simple setup above leaves Due date blank on purpose. When a weekly-review page appears, assign its deadline as part of the review. If your task views require a populated Due date, include a separate view that can show new pages with no deadline; otherwise you can miss the task before you assign one. Notion documents view filters as rules that show or hide pages by their property values.
For an automatically recorded creation timestamp, use Created time. It is auto-generated and not editable, which makes it useful for distinguishing repeated pages with the same title. It still describes creation, not a promised completion deadline.
Check the first scheduled page
After the first expected creation time, look in the destination database. Start with a view that has no filters, then find the new page by title and Created time. Creating a page manually from the template can help you inspect its content, but it does not confirm that the scheduled path ran.
Open the generated page and compare it with your intended defaults: correct starting Status, owner, client or project relation, date values, and unchecked checklist. A new weekly-review page should contain prompts ready to answer, not last week's completed observations.
If the page exists there but is missing from your usual task list, inspect that view's filters. In particular, a repeating page's Created by value is Notion automation. A filter that admits only pages created by you can hide it. Check Status, owner, relation, and Due date filters as well before creating another copy.
| Observation | Check before changing anything | Action and expected change |
|---|---|---|
| Page exists in an unfiltered view but not the work queue | Compare Status, owner, relation, Due date and Created by against the queue's filters. | Correct the intended filter or page value. A generated page should become visible when it meets that queue's criteria; do not create another copy merely to make it appear. |
| No occurrence found in the destination database | Confirm the expected time has passed, then inspect this template's Repeat state, interval, start date and time. | Correct the mismatched rule and record the next expected creation. A manual template copy checks content, not scheduled creation. |
| Page exists but inherited the wrong client or completed checklist | Open the master template's Edit view and inspect fixed values and content. | Correct future defaults there; repair this occurrence separately. Do not expect a schedule change to rewrite its content. |
If the expected page is still absent after those checks, keep the record of the template, database and intended time when seeking help. Do not delete and rebuild a working task database as a first diagnostic step. Distinguish “page wasn't created” from “page was created but my view hides it.”
Edit the master template or stop future repeats
To change the recurring checklist or default properties, open New → ••• beside the template → Edit. To change the timing, return to that template's Repeat settings. Inspect the next generated page after either change.
You can edit an individual page created from a template, but that is a change to that occurrence. Correct the master template when the default is wrong, then review existing tasks separately rather than expecting them to be repaired.
To keep the template while stopping scheduled creation, turn Repeat off in its template options. I would choose that before deleting the template when the checklist may be useful again. Notion also permits deleting the template; make that choice only when you no longer need the reusable starting page.
Two limits to check before expanding the setup
First, a scheduled template copy will not start a second database automation. Notion explicitly says that a recurring template automation does not trigger a database automation. If you expected an automation to assign properties after creation, put stable defaults in the template or redesign that step using a supported trigger. The template-to-automation troubleshooting guide covers that separate decision.
Second, nested templates have limits. You cannot nest a template within a template that recurs daily; nesting is supported for weekly, monthly, or yearly recurrence, with a maximum of three levels per database template. A repeated project page is therefore not a reason to assume that any depth of recurring subtask structure will work. Start with the single page you need and expand only when its contents and schedule are clear.
