Weekly Reviews In Notion — Master Level Life Alignment (Life OS)
Based on August Bradley's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Treat the weekly review as a scheduled, rigid ritual because it is the tactical layer that keeps daily execution aligned with higher aspirations.
Briefing
Weekly reviews sit at the center of a “life operating system” built in Notion: they convert long-term intentions into a short, repeatable weekly execution plan. The core claim is straightforward—without a weekly reset, projects and daily tasks drift out of alignment with higher goals, and the system stops producing the right outcomes. The weekly review is therefore treated as a non-negotiable scheduled ritual (typically 20–30 minutes) that keeps the “train on the track,” while also capturing lessons from the week so future planning improves.
The system separates responsibilities across review cycles. Weekly review is tactical: it aligns projects with the specific action items that must happen next. Monthly review is strategic: it checks whether projects are still the right vehicles for goal outcomes. Quarterly and annual reviews roll up learnings and results, but the weekly cadence is what prevents forgetting and mismatch—wins, disappointments, and insights are logged as they occur so they can later be summarized through database rollups.
In practice, the weekly review is designed for speed and consistency. The template avoids duplication across weekly, monthly, and quarterly sections by doing each “slice” of work only at the level where it belongs. It also relies heavily on rollups from daily tracking. Daily entries are already linked to the correct week, so metrics like workout counts, sleep ranges and averages, weight trends, and “percent of work completed” automatically populate the weekly review. That means the weekly session focuses on decisions and alignment rather than re-entering data.
The workflow begins with a visual and reflective setup: adding an image that represents the week (a moment, success, or meaningful event) to make recall vivid. Then comes a checklist-style reflection on guiding principles (a quick skim of core values), followed by accomplishments, disappointments, gratitude, and brief highs/lows and “what was learned.” The reflection is intentionally lightweight—questions are prompts, not essays—so the review stays manageable.
Next, the review moves into operational maintenance through “pillars, pipelines, and vaults.” Email gets processed to inbox zero (or intentionally deferred with starred/pinned items). Calendar follow-ups are checked across the past few weeks and the upcoming weeks. Pipeline work is updated in Notion kanban-style stages: completed content is marked published with dates and links, and “waiting on” items are revisited so stalled dependencies either get followed up (with due dates) or remain explicitly tracked.
Projects receive the most important check: every in-progress project must have at least one next action item, with due dates coming up in the next week or two. A rollup counts unfinished action items per project, acting as a quick diagnostic for whether more tasks need to be added or progress needs updating.
Finally, vaults handle cleanup and knowledge hygiene—clearing desktop/download clutter, deleting old screen captures, transferring high-value notes from tools like Evernote clipping, importing Kindle highlights into a book vault, and processing physical mail only during the weekly review. The payoff promised is reduced clutter, less worry, and daily clarity: when weekly and monthly reviews are done, the “today” view naturally surfaces the right priorities without constant rethinking. The next step in the broader system is monthly review, which shifts from tactical task alignment to strategic goal alignment.
Cornell Notes
Weekly reviews are the tactical engine of a Notion-based “Life OS.” They keep projects and daily action items aligned with higher-level goals by forcing a short weekly reset (about 20–30 minutes) and by logging outcomes and lessons as they happen. The weekly session stays efficient through two design choices: no duplication across weekly/monthly/quarterly sections, and heavy use of rollups from daily tracking already linked to each week. The review then processes execution details—email, calendar follow-ups, content pipelines, waiting-on dependencies, and especially ensuring every in-progress project has at least one next action with near-term due dates. Vault maintenance (cleanup and knowledge capture) finishes the loop so the system remains usable and clutter-free.
Why does the weekly review matter more than other review types for day-to-day effectiveness?
How does the system keep weekly reviews short enough to do consistently?
What does the weekly review require before moving into execution tasks?
How are stalled dependencies handled during the weekly review?
What is the key project-level requirement checked in the weekly review?
What does “vaults” maintenance accomplish at the end of the week?
Review Questions
- What specific mechanisms in the system prevent weekly reviews from becoming redundant or time-consuming?
- During the weekly review, how does the process ensure that every in-progress project has near-term momentum?
- Which rollup-based metrics from daily tracking feed into weekly reflection, and how do they influence next week’s focus?
Key Points
- 1
Treat the weekly review as a scheduled, rigid ritual because it is the tactical layer that keeps daily execution aligned with higher aspirations.
- 2
Use the system’s separation of responsibilities: weekly aligns projects to action items, monthly aligns goal outcomes to projects, and quarterly/annual roll up learnings.
- 3
Keep weekly reviews short by avoiding duplication across review cycles and by relying on rollups from daily tracking already linked to each week.
- 4
Process execution inputs during the weekly review—email toward inbox zero (or deliberate deferral), calendar follow-ups, and pipeline updates—so nothing silently slips.
- 5
Revisit “waiting on” dependencies and either extend the wait intentionally or assign a due date and move them back to active.
- 6
For every in-progress project, ensure at least one next action item exists with due dates coming up soon; use the unfinished-action rollup as a diagnostic.
- 7
Finish with vault maintenance (cleanup plus knowledge capture/import) so clutter doesn’t accumulate and high-value notes remain retrievable.