Obsidian Daily Note Template: Build a Daily Review System That Sticks

Daily notes in Obsidian are date-stamped Markdown files generated automatically by the built-in Daily Notes core plugin. By default, enabling Daily Notes gives you a blank file for each day. Useful to an extent — but a blank file puts all the work of structure on you, every morning.

A template changes this. Instead of an empty page, you open the day's note and find a pre-populated structure: prompts for priorities, a section for meetings or lectures, space for quick captures, and a section for an end-of-day review. The template does not write your notes for you. It removes the five-second decision about where things go, which is often enough friction to break a daily habit.

This kind of template has become a fixture in the PKM (personal knowledge management) community for a concrete reason: it connects short-term capture of daily events to the long-term knowledge stored in evergreen notes. A daily note for a specific date is not just a record of that day. It is the connective tissue linking that day's meetings, ideas, and reading to the permanent notes where those ideas live.

In Obsidian, the daily note functions as a daily hub. When you add [[wikilinks]] from the daily entry to specific topic notes, those evergreen notes gain backlinks that surface them more often and keep them connected to ongoing work. See our guide on obsidian notes for more on how the vault's linking system works.

The straightforward answer is consistency. A blank page invites different structures on different days — bullet lists one morning, prose the next, numbered priorities after that. After a month of inconsistency, searching through past daily notes takes longer than just remembering on your own.

A template enforces a single structure across every entry. When every daily note in your vault has the same sections in the same order, reviewing last week's entries takes seconds rather than minutes spent parsing unfamiliar formatting.

There is also a cognitive load argument. Research on habit formation consistently shows that reducing decision points at the start of a routine significantly increases follow-through rates. A template removes the decision entirely: open the daily note, fill in the sections, close it. The structure becomes the habit trigger.

For Obsidian users specifically, templates enable automatic linking. If your template includes a Linked Notes section with a prompt to add [[wikilinks]], you are more likely to connect the day's content to your existing vault. Without the prompt, linking daily entries to evergreen notes is easy to skip under time pressure. With the prompt, it becomes part of the routine rather than an optional extra.

Many Obsidian users find their vaults become genuinely useful only after adopting a consistent daily note structure. Notes that never get linked remain isolated files. A template that prompts for links each day gradually builds the network that makes Obsidian worth the setup effort.

There is no single correct answer — the right structure depends on how you use your vault. But experienced Obsidian users tend to converge on a consistent set of components that serve most workflows.

**Date header and navigation links** at the top give context and let you move to the previous or next entry without hunting through the file explorer. Templater can insert yesterday's and tomorrow's dates automatically using its date functions.

**A priorities block** with two or three prompts pushes you to state what matters before the day's noise takes over. Limit it to three items. A priorities list of ten is really a task list, and Obsidian is not a task manager.

**A notes section** for meetings, lectures, or reading sessions. A subheading for each event keeps the content scannable and gives you a named anchor you can link to from other notes.

**An inbox block** for quick captures during the day: ideas, links, observations, quotes that need a temporary home before being processed into proper notes. This is a frictionless dump, not a place for extended writing.

**A linked notes section** with a prompt to add [[wikilinks]] to the evergreen notes most relevant to today's activities. This is the section that turns daily capture into long-term knowledge.

**An end-of-day review** with three focused prompts: what did I learn, what needs to carry forward, and what went well. Three questions is enough. Five becomes a chore that gets skipped on busy days.

Obsidian's core Daily Notes plugin handles date-stamped file creation. Templater, a community plugin, adds dynamic content: auto-inserted dates, day-of-week labels, and JavaScript snippets for more complex automation. The core plugin is enough for a static template. Templater is worth the extra setup if you want navigation links or other dynamic content that changes based on the date.

To enable Daily Notes: open Settings, go to Core Plugins, and toggle Daily Notes on. Set the Date Format (YYYY-MM-DD is recommended for clean alphabetical sorting), the New File Location (a dedicated Daily Notes folder keeps entries out of the vault root), and the Template File (point it to your template note).

For Templater: install it from the Community Plugins browser, then open Templater settings, set the Template Folder path to match your templates folder, and enable the option to trigger Templater on new file creation. Set the trigger folder to your Daily Notes folder. From that point, every new daily note created in that folder automatically applies your template and runs any dynamic date functions.

The simplest effective setup is the core Daily Notes plugin with a fully static template — no Templater required. A static template saves the section structure and prompts. Dynamic date linking, which automatically inserts links to yesterday's and tomorrow's notes, requires Templater, but the base daily note habit works without it.

Test your setup by opening the command palette (Cmd or Ctrl + P) and running Daily Notes: Open today's daily note. If the template does not appear, check that the template file path in Settings matches the actual file location in your vault.

Here is a working daily note structure for Obsidian that covers the core components without demanding more than a few minutes of writing each day. The Templater syntax for dynamic date functions is noted where relevant — substitute plain text if you are using the core Daily Notes plugin without Templater.

At the top, a level-one heading with today's date in full text (Templater inserts this automatically with its date function), followed by navigation links to yesterday's and tomorrow's entries using relative date offsets. Under that, a Priorities heading with three empty bullet points.

Next, a Notes heading with a level-three subheading placeholder for the first scheduled meeting or lecture. During your morning review, duplicate the subheading format for any additional events.

Below Notes, an Inbox heading with an empty bullet point. This is where anything that arrives during the day lands until your weekly review moves items into proper evergreen notes.

A Linked Notes heading follows, containing a single prompt line with empty double brackets as a reminder to add at least one [[wikilink]] to an existing vault note before closing the entry.

The final heading is End of Day with three fixed prompts: What did I learn today? What carries forward to tomorrow? One thing that went well.

This structure takes roughly two minutes to fill in during a morning check-in and two minutes again at close of day. The Linked Notes section is the most important part. It is what turns daily capture into a connected knowledge base rather than a date-sorted archive of isolated text.

For templates covering other note-taking formats, our note-taking templates guide covers additional structures for lectures, meetings, and reading notes.

An obsidian daily note template handles text-based capture well. It falls short on content that is not primarily text: recordings from lectures and meetings, uploaded PDFs, audio files, and videos. Transcribing these manually into daily notes is time-consuming enough that most people skip it, which means that content never makes it into the vault.

Notelyn handles this gap. Record a lecture or meeting in Notelyn and it produces a full transcript, a structured summary, and a flashcard deck within a few minutes. The summary arrives in headed sections with key points extracted, the same format you would want in your daily note under the relevant session heading. You can paste it directly into the Notes section without manual reformatting.

For PDF-heavy workflows — research papers, textbook chapters, business reports — Notelyn's PDF import extracts key points and generates a structured summary you can drop into your daily notes or into a dedicated evergreen note for that source. See our PDF to notes guide for more on how that import process works.

The AI Q&A feature is useful during daily review: upload the day's lecture or meeting content, then ask specific questions rather than rereading the full transcript. Asking what the three main action items were from a planning session returns a direct answer instead of requiring you to skim through raw notes.

A practical combined workflow: process lecture recordings in Notelyn immediately after each session, paste the structured summary into the day's Obsidian daily note under the correct subheading, then add [[wikilinks]] to connect the summary to existing course or project notes. This gives you AI-powered transcription plus the linking and graph view that Notelyn does not provide on its own.

Daily note habits in Obsidian fail in a few predictable ways. Most of them have practical fixes.

**Overbuilt templates** are the most common failure mode. A template with twelve sections requires twenty minutes to fill in properly. Most days, you fill in two and feel behind on the rest. Start with four or five sections. Add more only after using the base template every day for at least two weeks.

**Not processing the inbox** means captures accumulate without becoming permanent notes. A weekly review of twenty minutes, at the same time each week, goes through inbox items from the past seven daily notes, moves the best ideas into proper evergreen notes, and links them into the vault. Without this step, the inbox becomes a dead end.

**Skipping the end-of-day review** is common when the day ends abruptly. Move the review to the following morning: instead of reflecting on last night, spend two minutes reviewing yesterday's entry before starting today's. The prompts are just as useful twelve hours later, and the habit is easier to anchor to a consistent morning routine.

**Not linking the daily notes to evergreen notes** wastes the main advantage of building in Obsidian. Every daily note without [[wikilinks]] is a dead end: it records something but does not connect it to anything. The Linked Notes section in your template is the prompt that prevents this from becoming a habit. Our how to link notes in Obsidian guide covers the mechanics in detail.

**Trying to be exhaustive rather than selective** is the last common mistake. Daily notes are not a complete record of your day — they are a filtered capture of what matters. If each day's entry runs longer than 500 words, it is probably too detailed to be useful as a navigational entry point into the rest of your vault.

Building a consistent daily note habit in Obsidian comes down to one thing: removing friction at the moment you open a new note. An obsidian daily note template removes the blank-page problem, makes the structure automatic, and gradually turns disconnected daily captures into a linked knowledge network.

Start with the structure described in this guide. Use it every day for two weeks before modifying anything. After two weeks, you will know which sections you actually fill in and which ones you skip. Cut the latter, or adapt them to fit how you actually work.

If you also deal with audio content — lectures, meetings, recorded calls — pair the daily note template with Notelyn to handle transcription. Notelyn turns recordings and PDFs into structured summaries that drop cleanly into your daily note sections, so the gap between what you hear and what your vault contains stops being a manual task.

For the broader question of how to structure your Obsidian vault around daily notes, see our obsidian notes guide. For linking those daily entries to your evergreen notes over time, our how to link notes in Obsidian guide covers every method from basic wikilinks to block references.

The daily note is the entry point, not the destination. Its job is to connect today's capture to everything you have already built. Get that connection working and the vault starts returning value. Skip it and you end up with a well-organized archive that nobody navigates.