Notion Basics: How to Use Template Blocks and Database Templates

Template blocks in Notion let users generate repeatable pages and checklists with a single click—turning tedious, multi-step workflows into one-button operations. The core payoff is speed and consistency: instead of rebuilding the same structure (to-dos, publishing checklists, team dashboards) every time, a template block spawns a fresh copy of the content whenever it’s needed.

A template block behaves like a clickable “factory” for blocks. After inserting a template block (via the /template command), users name it and then place the desired blocks inside. Clicking the template later creates a copy of those blocks as a new page or checklist instance. The transcript walks through simple examples like generating a new to-do item repeatedly, then scales up to a full checklist (e.g., a grocery list) configured inside the template via “Configure template.” It also highlights a powerful twist: templates can include database blocks. By embedding a database inside a template block, users can generate databases that themselves contain templates.

The workflow becomes even more powerful when combined with database templates. Inside a database (such as a video project tracker), users can create “New templates” that define default properties and starter content for new rows. When an instance is created, the template’s content and properties are copied into the new row, while the template remains unchanged. The transcript emphasizes that properties set before spawning a template aren’t erased—so users can prefill fields and still get the template’s checklist or structure.

A key operational detail is how spawning behaves depending on whether a row is empty. Rows that already contain content typically only offer “spawn from a template” when empty. To work around this, the transcript describes a practical trick: cut selected blocks (Command X) to clear the row, spawn from the template to restore the template instance, then paste the saved blocks back in. This supports a common real-world flow—collecting raw ideas first, then later applying the template structure.

The transcript also shows how templates can pull from a centralized knowledge base. Instead of duplicating a frequently updated “master filming checklist” into every new project, users can link to a wiki page from within a template. Two approaches are demonstrated: one button creates a link to the wiki page, while another button creates a copy of the checklist content. To prevent links from pointing to the wrong instance, the transcript uses a URL hard-coding technique by appending “?” to a pasted link so the link stays anchored to the master page.

Finally, it distinguishes template blocks from “shared templates” (like Ultimate Tasks) distributed via duplication permissions. Shared templates are published so others can duplicate pages into their own workspaces, using Notion’s share settings (including “allow duplicate as template”). The overall message is clear: template blocks and database templates together turn Notion into a scalable system for checklists, project creation, and team workflows—especially when paired with centralized wiki links and reusable templates.