A Notion database template gives new entries a consistent starting structure. Use it for a recurring meeting agenda or a repeatable project briefing, then fill in the details that change. Start with one useful template rather than a library nobody maintains.
Table of Contents
Build the structure before the template
Use database properties for details you want to filter or sort: a meeting date, an owner and a status. Keep the discussion itself inside the page. Notion has Date, Person and Status property types; Date can include a time and reminder. Created time is automatic and cannot be edited, so it is different from an appointment date. Property types and date settings.
Illustrative example: a small consultancy holds a weekly delivery review. Its database records the meeting date and facilitator; the page contains the agenda, decisions and actions. Start with the information someone needs to prepare. Remove fields that nobody uses when deciding what to do next.
Create and use the database template
Open the dropdown beside New in the database and select + New template. Name the template and add its page content and property defaults. For the review, add headings for preparation, decisions and follow-up; leave changing details as prompts. Database template instructions.
Create a new page and choose the saved template, then give the entry its own title and replace the prompts. Templates belong to their particular database; they are not automatically available across the workspace. Keep the name specific enough that a colleague can select the right structure.
Choose the project relation deliberately
A Relation property connects pages in different databases. For example, relate a meeting entry to its project page instead of copying the project description into every agenda. Relations are one-way by default; you can enable a corresponding relation in the other database. A relation can allow one page or multiple pages. Relations and their settings.
Leave the relation blank in a general-purpose template. Notion warns that a populated template relation will point new entries to the same existing page or pages. Set a fixed project only when every entry created from that template should belong to it.
For the consultancy, a project-specific review template may deliberately use a fixed project. A shared weekly-review template should prompt the facilitator to choose. Rehearse with two different projects and inspect the resulting relations before asking the team to use it.
Give the team a practical view
Views display the same database in different ways. A calendar uses a Date property; a table can make owners and statuses easy to compare. Each view has its own settings, including property visibility, filters and sorts. Create a view for upcoming meetings and a separate view for completed reviews. Views, filters and sorts.
If an entry seems missing, inspect an unfiltered view before creating another copy. Our Trello card templates guide covers another approach to repeatable work when your team prefers cards.
Repeat only what should happen on a schedule
For recurring entries, open the template menu and choose Repeat. Repeating database templates can generate entries on daily, weekly, monthly or yearly schedules, with an interval and chosen start date and time. Use this for a regular meeting agenda, then inspect the first generated page and adjust its actual meeting details. Repeating template guide.
A generated agenda is preparation, not evidence that the meeting happened. Assign someone to review it and remove or mark cancelled sessions appropriately. If you need recurring task deadlines rather than meeting-note pages, see our ClickUp recurring tasks guide.
Understand automation and access limits
Do not build a notification chain on the assumption that a recurring template triggers a database automation. Notion explicitly says it does not. Database automations generally require a paid plan and full database access to create, edit or delete; Free has limited Slack-notification and existing-template exceptions. Check the intended trigger before upgrading. Database automation rules.
For contributors who should update entries without redesigning the database, consider Can edit content. This allows page creation, editing and property-value changes, but prevents changes to database structure, views, filters and sorts. Review the actual sharing settings rather than assuming that an uncluttered view limits access. Sharing and permission levels.
Check the template with a harmless sample
Before rollout, create two sample entries and check their titles, dates, owners and relation values. Confirm that each agenda starts with empty decisions and unfinished actions. Ask a colleague to find and update a sample with their normal access. Keep an unfiltered view available to diagnose missing entries, and nominate a template owner to revise prompts when the meeting changes.
Sources reviewed 10 October 2026 against official Notion documentation. Examples and rehearsal checks are illustrative recommendations, not reported product tests.
