Run it at the end of the work week, after the week’s work is substantially complete.
I want to close the week with a clear record and a clean starting point for next week
When the work week is ending, use this workflow to review what actually happened, make an explicit decision about every open item, capture useful reflection, and prepare the next-week baseline.
Close the current week before opening the next.
When the work week is ending, use this workflow to review what actually happened, make an explicit decision about every open item, capture useful reflection, and prepare the next-week baseline. You’re done when the current log is closed and the next week has a trustworthy starting point.
Use any of these phrases to start this workflow.
close my weekend my weekwrap up the week
An active weekly log must exist and still be open. If no log exists, run the Week Planner first. Your day must also be closed before the Week Closer can run.
Resolve every open item deliberately.
The Week Closer works through the active weekly log priority by priority. It records progress, handles carry-over, restructure, or drop decisions, reviews the To-Do List without blocking closure, captures reflection, and locks the current log before creating the staging baseline for the next week. It leaves the week ready for the later Work OS Health Check and the next planning cycle.
One controlled close across the weekly record.
The weekly log is the working context. Workspace priority files supply durable outcomes and progress notes. The close and baseline templates define the records created. The workflow uses conversational review points so one priority is resolved before the next is shown. To-Do List items are reviewed as a queue and can carry forward without blocking the close.
Move from review to a clean next-week baseline.
- 01
Load and validate the active weekly log.
- 02
Review each priority and its open work one at a time.
- 03
Decide whether open work is carried as-is, restructured, or dropped, then review the To-Do List as a queue.
- 04
Capture reflection and new information.
- 05
Save the reflection and lock the current log as closed.
- 06
Write progress notes to the relevant workspace priority records and create the next-week baseline.
What gets closed, captured, and staged.
| Output | What happens | Where it goes |
|---|---|---|
| Closed weekly log | The reviewed work, decisions, reflection, and closure record are saved. | The current weekly log in Obsidian |
| Priority progress notes | Meaningful progress is recorded against the affected workspace priorities. | The relevant workspace priority records |
| Next-week baseline | Carried and restructured work is staged for the next planning cycle. | A new weekly-log baseline in Obsidian |
The next-week baseline is a starting point, not an approved plan. The Week Planner fills in the priorities and calendar blocks for the new week.
Verify closure before planning again.
The log must contain reflection before it is closed, and the baseline must be created only after closure. If an item is unresolved, the workflow pauses for a decision. The later Work OS Health Check can use the completed close as part of the wider weekly review. If saving fails, the log remains open and can be rerun safely. If you think of something after closing, add it to the next-week baseline in Obsidian rather than reopening the closed log.