A weekly task review helps a remote team stay aligned without turning the meeting into a long round of status updates. The most effective format combines a short asynchronous update with a focused 30–45-minute conversation about priorities, blockers, and decisions.
Recommended weekly workflow
1. Collect asynchronous updates
Ask each team member to post an update by a consistent deadline, ideally several hours before the meeting. Use this structure:
Weekly update template
- Completed: Tasks or outcomes finished since the last review
- In progress: Current work, expected completion date, and confidence level
- Blocked or at risk: What is preventing progress and what help is needed
- Next priorities: The two or three most important tasks for the coming week
- Decisions needed: Questions requiring approval or team input
- Capacity: Available, fully allocated, or overloaded
- Key learning: Optional insight, customer feedback, or process improvement
Encourage outcome-focused updates. “Published the onboarding guide” is more useful than “Worked on documentation.”
2. Review and prepare
Before the meeting, the team lead should:
- Identify overdue or stalled tasks
- Flag dependencies between team members
- Group related blockers and decisions
- Note any mismatch between priorities and team capacity
- Move routine status information out of the live agenda
- Assign an owner to every issue that needs follow-through
A shared task board should be the source of truth. Each active task should have an owner, status, due date, and clear next step.
30-minute meeting agenda
0–3 minutes: Context and wins
Recognize important completions and briefly restate the team’s current goal.
3–10 minutes: Priority check
Confirm whether this week’s priorities still support the team’s goals. Address new requests or changes in urgency.
10–22 minutes: Blockers, risks, and dependencies
Discuss only items that require coordination, assistance, or a decision. Avoid reading updates aloud.
22–27 minutes: Capacity and ownership
Reassign work where necessary and confirm that workloads are realistic.
27–30 minutes: Decisions and commitments
Summarize what was decided, who owns each action, and when it is due.
If a topic needs deeper discussion, assign a smaller follow-up session rather than extending the review for everyone.
Facilitator script
“Please review the written updates before we begin. Today we’ll focus on changes in priority, blockers, dependencies, and decisions. Our main outcomes are to confirm the coming week’s priorities and leave every open issue with an owner and due date.”
At the end:
“This week, our top priorities are [priority 1], [priority 2], and [priority 3]. The decisions made today were [decision summary]. Action items are recorded with owners and due dates. Any corrections should be added to the task board by [deadline].”
Weekly review record
Use a concise summary rather than full meeting minutes:
WEEK OF: [Date]
TOP PRIORITIES
- [Priority and desired outcome]
- [Priority and desired outcome]
- [Priority and desired outcome]
COMPLETED
- [Outcome]
- [Outcome]
BLOCKERS AND RISKS
- [Issue] — Owner: [Role] — Next step: [Action] — Due: [Date]
DECISIONS
- [Decision and brief rationale]
ACTION ITEMS
- [Action] — Owner: [Role] — Due: [Date]
- [Action] — Owner: [Role] — Due: [Date]
CAPACITY CONCERNS
- [Concern and adjustment]
PARKING LOT
- [Topic requiring separate discussion]
Ground rules for remote teams
Keep updates visible across time zones, document decisions immediately, and avoid treating online presence as evidence of productivity. Judge progress by agreed outcomes. Cancel the live meeting when there are no blockers, priority changes, or decisions to discuss; the asynchronous review can stand on its own. Once a month, spend five minutes checking whether the process is useful and remove any fields or agenda items the team no longer uses.