What should a weekly review include?

A useful weekly review includes decisions required, important changes, blockers, commitments, risks, and a small set of next-week priorities.

How long should a weekly review be?

The document should be scannable in minutes. Live time should be spent on decisions and blockers rather than reading updates aloud.

Can AI prepare a weekly review?

Yes. AI can assemble approved updates, compare changes, flag missing owners, and draft the review. People should verify the evidence and make the decisions.

Weekly reviews

A weekly review that produces decisions

A weak weekly review collects updates. A useful one changes what happens next. The difference is the format.

Published 2026-08-18 · Updated 2026-08-18 · 5 min read

A practical weekly review structure for leaders who need decisions, owners, blockers, and follow-up from one recurring meeting.

Start with decisions, not updates

Ask what needs a call this week before asking what everyone did. Updates matter only when they change a decision, expose a blocker, or shift priority.

The first page of the review should list decisions needed, owner, deadline, and missing information. Keep status detail behind that.

Separate blocked work from slow work

A task is blocked when one person, decision, or dependency is stopping progress. Slow work is different. Treating both the same makes reviews noisy.

Have the assistant mark blockers with the person who can unblock them. If no owner is clear, that is the issue to resolve.

Close with a follow-up trail

The review should end with the next action, owner, date, and review point. If those fields are missing, the meeting created more ambiguity.

Bumblebee can keep that trail visible so the next review starts from open loops, not memory.

Use a stable one-page structure

Keep the order consistent: decisions needed, important changes, blockers, commitments, risks, and next-week priorities. A stable format makes change visible because people stop relearning the document every Friday.

Put links to detailed project data behind the review. The main page should contain only what changes a decision, priority, owner, or intervention.

Let the assistant prepare, not perform the meeting

An AI chief of staff can gather updates, compare this week with last week, identify missing owners, and draft the decision queue. That preparation should reduce reading time in the room.

The people in the review still resolve trade-offs, challenge the evidence, and make commitments. Let Bumblebee prepare the review and carry open items forward. People remain accountable for the decisions.