A weekly project review is a maintenance pass over commitments and working context. Weekly is a useful default, not a rule; use a cadence that catches stale work before it becomes costly.
Review the project record
For each active project, reread the desired outcome and ask whether it still matters. Check that at least one next action is executable. Resolve tasks that are completed in reality but still open, and identify items waiting on another person or missing input.
Compare start dates and deadlines in the system that owns them. A review should surface external constraints without automatically moving every active task into Today.
Review the working material
Open or locate the current source file, draft, and relevant browser resources. Confirm links still work, files have not moved, and open windows show the correct version and account. Close unrelated or obsolete windows. A stale window assignment should be corrected rather than treated as evidence that the resource disappeared.
Decide the next status
Keep the project active with a clear next action, pause it with a review point, complete it after checking the delivered result, or remove it when the commitment no longer exists. Wallo can show a goal’s to-dos and assigned current windows during this review, but it does not schedule reviews, reopen missing resources, or archive goals automatically.