Weekly review template for small teams: decisions and follow-ups

Opitor · 17 September 2026

USE IT WITH YOUR TEAM

Free weekly review template

Download the blank worksheet or fill it in below. No account needed. Your edits stay in this page and disappear when you leave.

Download blank template (.txt)

Fill in and copy the template

Your worksheet

SMALL TEAM WEEKLY REVIEW
Opitor | https://opitor.com/guides/weekly-review-without-a-meeting
Copy and adapt this worksheet for your team. No Opitor account is needed.

Week ending:
Prepared by:

1. PROMISES STILL OPEN
What did I tell another person I would deliver?
Deliverable | Promised to | Original date | Done / open / dropped

2. BLOCKERS
What is waiting, and what single action would move it?
Item | Waiting on | Next action | Person taking that action | Follow-up date

3. NEXT SEVEN DAYS
What must be finished, by whom, and how will we know it is done?
Deliverable | One owner | Due date and time zone | Done means

4. QUARTERLY GOAL CHECK
Which current goal does this week's work support?
What should we stop or defer because it does not support that goal?

5. WRITE BACK THE DECISIONS
[ ] Update changed dates in the team's existing task list.
[ ] Send the next action to the person who owns it.
[ ] Tell anyone affected by a missed or dropped promise.
[ ] Schedule a conversation only for a decision that needs discussion.

ONE THING TO FINISH NEXT WEEK:

Next review date:

Keep private client or employee details out of any copy you share publicly.

A weekly review for a team of 3–10 people should leave you with three things: an accurate list of open promises, decisions on blocked work, and agreed dates for the next week. Start with the commitments made in chat and your task list. Each person can prepare a written update before you decide which issues need a conversation.

Use the free worksheet above to collect the review. You can edit, copy or download it without an Opitor account. Keep the team’s existing task list as the record of ownership and deadlines, then use the worksheet to identify what needs to change.

Prepare the review in 15 minutes

Fifteen minutes is a suggested starting point for each person’s preparation, not a measured result or a promise that every decision will be resolved in that time.

Find the promises — three minutes. Open the shared task list and the chat threads where you agreed to deliver something. Capture any commitment still living only in a message with the message-to-task tool. Check for an existing task before creating one.
Close or reconsider them — four minutes. Mark completed work done and link the result. For unfinished work, choose: keep the date, propose a new date, request a decision, or drop the work. Record who needs to agree to a change.
Check the next seven days — four minutes. Look for tasks due together and work that depends on a pending decision. If the plan does not fit, propose what to defer. A later date stays a proposal until the affected people accept it.
Write the requests — four minutes. For each unresolved item, name the decision needed, who can make it, when an answer is needed and who will follow up. Copy agreed changes back into the task list.

A review is ready to share when another person can tell what you need from them and by when. “Still waiting” needs a next action.

Turn each blocker into a decision request

Use this structure in the worksheet’s blockers or decisions section:

Task: [deliverable and task link]

Decision needed: [specific question or options]

Decision maker: [one person]

Answer needed by: [date, time and time zone]

If no answer: [who follows up, when, and what work remains blocked]

After agreement: [task owner updates the task and informs affected people]

For example: “Leon, choose homepage option A or B by Tuesday at 12:00 Bangkok time. Maya will follow up then if there is no answer. The launch date remains unconfirmed until you choose.” This gives the team a visible next step without treating silence as approval.

Worked example: a five-person design team

This is an illustrative scenario, not an Opitor customer result. On Friday, Maya checks a sent proposal, an unapproved website preview and a launch checklist that depends on the approval.

Commitment	Review decision	Owner and next action	Follow-up point
Send the client proposal	Done; the task still needs closing	Maya links the sent proposal and closes it	Friday, before sharing the review
Get a choice between two website previews	Approval needed	Leon chooses A or B; Maya sends the request	Tuesday, 12:00 Bangkok time; Maya checks for the answer
Finish the launch checklist by Wednesday	Proposed move to Thursday, subject to approval	Maya asks the launch owner to confirm the impact	Tuesday, 15:00 Bangkok time; keep the change pending until accepted

The proposal can close immediately. The other two rows remain open decisions. When Leon chooses a preview, Maya records the choice, checks the launch owner’s response and updates the agreed deadline. If the answer does not arrive, she follows up at the stated time and flags the launch dependency.

Choose one place for the team’s weekly updates and agree when decision requests should receive a reply. In a team across time zones, write the zone next to that deadline. A compact update from the example could read:

Done: Proposal sent; result linked in the task.

Decision needed: Leon to choose preview A or B by Tuesday, 12:00 Bangkok time. Maya will follow up then.

Date change proposed: Launch checklist Thursday instead of Wednesday. Launch owner to confirm by Tuesday, 15:00 Bangkok time.

Next: Update the checklist date after both decisions are agreed.

Share enough context for the decision. Keep private notes and unrelated client details out of the update, and check that recipients can access the linked work.

When to have a conversation

Meet when a written request exposes a disagreement, a sensitive issue or several dependent choices that need discussion. Invite the people who can resolve it, bring the specific options and finish by recording the choice, owner and date in the task list.

If a request receives no answer, follow the escalation path the team agreed on. Repeatedly blocked work may need a change in who can decide. Repeatedly moved dates may need less planned work. The worksheet helps make those patterns visible; it cannot make the decision for the team.

Close the review on Monday

Check that each decision from Friday is either reflected in a task or still has a named person and follow-up date. Do not silently carry the same unresolved paragraph into another week.

After two reviews, check whether you found a missed promise in time to act, resolved a blocker, or warned someone before a deadline changed. Keep fields that help those decisions and shorten fields that repeat the task list. For Monday planning and daily follow-up, use the weekly planning template.

Where Opitor fits

Opitor is an AI-native operating system for small companies, where every person gets their own AI chief of staff. It is designed around messages, todos, deadlines and quarterly goals. Access is currently by invitation through the waitlist. This worksheet works independently of the product.

Read the Opitor FAQ for the invitation process and product details.

Updated 2026-09-28