Move through schedule, decisions, costs, field evidence, and next actions in one calm rhythm.
Review exceptions, not every record
A useful weekly review is short because the project system already holds routine details. The meeting focuses on decisions that are late, scope that changed, costs that moved, work that lacks evidence, and handoffs without an owner.
Use the same operating sequence
Move from client and design decisions to schedule, procurement, field constraints, financial change, punch, and the next seven days. A consistent sequence makes missing information easier to notice.
- Decisions due before they affect the schedule.
- Committed dates without confirmed ownership.
- Estimate or invoice changes since the last review.
- Open issues without current field evidence.
- Client updates that should be published this week.
Finish with named next actions
Every exception should leave the review with one owner, one due date, and the project context needed to act. Avoid meeting notes that create a second system beside the project record.