Weekly Review Templates in Obsidian

A personal knowledge management (PKM) system is only as powerful as the habits that sustain it. Without regular maintenance, even the most elegantly designed digital garden becomes overgrown and unusable. Weekly reviews are the essential maintenance ritual that prevents this drift, transforming a static collection of notes into a dynamic steering system for your work and life. In Obsidian, you can design this ritual to be intelligent and automatic, using templates and queries to surface exactly what you need to reflect on, ensuring your system—and you—stay on track.

The Purpose and Anatomy of a Weekly Review

A weekly review is a dedicated time to close out the past week and intentionally plan the upcoming one. Its core purpose is course-correction. It answers three fundamental questions: What happened? What did I learn? What comes next? This process prevents small oversights from snowballing into major project derailments and ensures your daily actions remain aligned with your larger goals.

In Obsidian, a weekly review isn't just a blank page for freeform journaling. It's a structured template that prompts specific reflections and, most powerfully, pulls relevant information from across your vault automatically. A robust template typically includes four key sections: a retrospective look at completed tasks and captured notes, a synthesis of key insights, a planning session for the week ahead, and a higher-level strategic check-in. This structure turns a vague intention into a repeatable, valuable process.

Designing Your Core Review Template

Your template is the engine of the habit. Start by creating a new note in your preferred weekly review folder (e.g., Periodic/Reviews/) and inserting a template. A basic but effective template structure might look like this:

## 🧭 Weekly Review for {{date:YYYY-MM-DD}}

### 1. Retrospective: What Happened?
**Completed Tasks:**
*<<A space for your Dataview query to list completed tasks>>*

**Key Daily Notes & Events:**
*<<A space for your Dataview query to summarize daily notes>>*

**What went well this week?**

**What was challenging?**

### 2. Synthesis: What Did I Learn?
**Key Insights & Notes Created:**
*<<A space for your Dataview query to surface new or modified notes>>*

**How does this connect to ongoing projects or interests?**

### 3. Planning: What Comes Next?
**Carry Over Tasks:**
*<<Manually list any unfinished important tasks>>*

**Top 3 Priorities for Next Week:**

**Weekly Calendar Preview:**
*<<Brief look at scheduled commitments>>*

### 4. Strategic Look-Ahead
**Am I working on the right things? (Alignment Check)**

**One small improvement for my systems:**

This template provides the scaffold. The magic—and the automation—comes from populating the first three sections with Dataview queries.

Automating Insight with Dataview Queries

Dataview is an Obsidian plugin that allows you to query your notes using a code-like syntax. Integrating it into your review template automates the gathering phase, letting you focus on thinking instead of hunting for information.

Here are essential queries to embed in your template:

1. Completed Tasks: This query surfaces tasks marked as done within the last 7 days, giving you a concrete record of accomplishment.

TASK FROM "" WHERE completion = date(this.file.name) - dur(7 days) AND completed SORT completed desc

1. Summary of Daily Notes: This query lists your daily notes for the past week, allowing you to quickly scan for events, meetings, or thoughts you captured.

LIST FROM "Daily" WHERE file.day >= date(this.file.name) - dur(7 days) SORT file.day desc

1. New or Modified Notes: This query helps identify new knowledge forming in your vault by showing notes created or significantly edited in the last week.

LIST FROM "" WHERE file.cday >= date(this.file.name) - dur(7 days) OR file.mday >= date(this.file.name) - dur(3 days) SORT file.mtime desc

To use these, you must name your weekly review note with an ISO date (e.g., 2024-05-27 Weekly Review.md). The query date(this.file.name) extracts that date, and dur(7 days) calculates the review period backward. You can customize the source folders (FROM "Daily") to match your vault's structure.

Building the Unbreakable Review Habit

The most perfect template is useless without consistent execution. Building the weekly review habit requires tying it to your schedule and making it frictionless.

First, schedule it. Block a recurring 60-90 minute appointment on your calendar, ideally at a calm transition point like Friday afternoon or Sunday evening. Treat this appointment as non-negotiable. Second, simplify the start. Use Obsidian's Templates or QuickAdd plugin to create a one-click button that generates your new weekly review note with all the Dataview queries already populated. The fewer steps between your intention and the action, the more likely you are to do it.

Finally, focus on the value, not just the completion. The goal isn't to fill out every box perfectly every week. Some weeks, the "Strategic Look-Ahead" section will be most critical; other weeks, simply reviewing completed tasks provides the momentum you need. The habit's power is in creating a weekly checkpoint where you, not your inbox or task list, are in control of deciding what's important.

Common Pitfalls

Overcomplicating the Template: It's easy to get lost in building the "ultimate" template with a dozen sections and complex queries. Pitfall: This creates friction and makes the review feel like a chore. Correction: Start with the simple 4-section template above. Only add a new section or query when you repeatedly find yourself wishing the information was there. Let your process evolve from need.

Neglecting the Reflection Prompts: The automated Dataview sections are powerful, but they are only data aggregation. Pitfall: Treating the review as just reading the query results and moving on. Correction: The real value is in manually answering the qualitative prompts like "What went well?" and "Am I working on the right things?" This is where insight and course-correction happen. Always spend at least 10-15 minutes on these reflective questions.

Failing to Act on the Output: A review that doesn't influence your upcoming week is merely an archival exercise. Pitfall: Creating a beautiful review note that is then closed and forgotten. Correction: Your "Top 3 Priorities for Next Week" must be transferred to your active task management system (whether in Obsidian or elsewhere). The "Carry Over Tasks" must be rescheduled. The review's output must become the input for your daily planning.

Summary

• Weekly reviews are a non-negotiable habit for maintaining an effective PKM system, serving as a regular course-correction ritual to align daily actions with broader goals.
• A structured template in Obsidian provides the necessary scaffold, typically containing sections for retrospective, synthesis, planning, and strategic reflection.
• Dataview queries automate the data-gathering phase, pulling in completed tasks, daily notes, and new insights automatically based on the note's date, letting you focus on analysis rather than collection.
• The habit is cemented by scheduling it and reducing friction, using plugins to create one-click review notes and protecting the time in your calendar.
• The highest value comes from manual reflection and action, using the aggregated data to answer strategic prompts and ensuring the review's conclusions directly inform your upcoming week's priorities.