Run a Useful Weekly Review with LifeOS

Weekly reviews often fail because you try to remember the whole week from scratch. LifeOS works better when tasks, daily notes, and theme tags have already captured the evidence.

Week view: review tasks and time at the weekly level

Start with completed work

Open your weekly note or weekly review note. Pull up completed tasks from the task view or review them from daily notes.

Do not only count tasks. Look for three things:

  1. Which tasks actually moved goals forward?
  2. Which tasks were reactive or administrative?
  3. Which tasks repeated, suggesting a system problem?

Review active projects

Open this week's active theme notes and check whether each project moved forward.

Use a compact format:

## Project Progress

### User Feedback Report

- Progress: finished classification and first findings.
- Risk: mobile data is missing the latest one-week sample.
- Next week: add data on Monday, send review version on Tuesday.

### Website Update

- Progress: completed the feature overview on the homepage.
- Risk: English illustrations need another text review.
- Next week: run one mobile screenshot pass.

This keeps the review grounded in projects instead of feelings.

Check the calendar

If you use Calendar Pro, review the week view. It is usually more honest than memory.

Look for:

  • Whether deep work had real blocks of time.
  • Whether meetings took your best hours.
  • Whether urgent tasks kept leaking into evenings.
  • Which tasks were repeatedly postponed.

Weekly calendar: review where your time went

Re-decide unfinished tasks

Do not move every unfinished task to next week. Decide again:

TypeAction
Still importantSchedule it on a date or time block
Unclear goalMove it back to the project theme and clarify it
No longer importantDelete or archive it
Waiting on someoneWrite who it is waiting for and when to follow up

A clean task system makes next week easier to start.

Write next week's plan

End with three sections:

## Next Week Focus

1. Finish the review version of the user feedback report.
2. Publish the updated documentation entry.
3. Close the LifeOS plugin feedback loop.

## Not Doing Next Week

- No large refactors.
- No new documentation pages until the beginner path is fixed.

## Confirm Early

- Confirm feedback metric definitions on Monday.
- Schedule an English site copy review on Wednesday.

The most useful part is often "not doing". It protects attention.

Tip

If you are new to LifeOS, keep the weekly review under 20 minutes: review completed tasks, review projects, handle unfinished tasks, and write three priorities for next week.