Weekly team update without a meeting: template and when to stay live
Steffen Rosenögger, Founder of CapmePublished October 26, 2026
Replace the weekly status meeting with a five-question update, written or recorded by Thursday noon. Template, example, hours saved, and when to stay live.
In short
- For a team of eight, our own calculation puts the weekly round at about 2.4 person-hours written and 4.2 recorded, against 8 for a 60-minute status meeting. Every input is stated and can be swapped for yours.
- Write by default and record when a result is easier to show than to describe. Keep the live meeting in a crisis week, and while a team or its lead is new.
- In Germany, per-person watch progress falls under the works council's co-determination. Capme's totals-only setting shows organisers counts without names.
It is Thursday, 12:00, and everyone on the team has posted five short answers: what moved toward our goals, what comes next, what is blocking me, what needs a decision, and whose work deserves a mention. That is a weekly team update: a short status update each person writes or records by a fixed deadline, and it can replace the weekly status meeting. Most weeks a written post in the team channel is enough. A recording of two to three minutes helps when there is something to show. The team lead reads or watches everything by Friday noon and meets live only with the people who have a decision open.
This guide is for one team lead and their own team. A review across several teams, with workstream owners and a steering group, follows other rules: see the async project status review.
Why replace the weekly status meeting?
A weekly status meeting mostly passes on information: one person reports, the others listen, and discussion is rare. Meetings like that work better async (the reasoning is in which meetings can go async), and they are what Capme Meetings is built for. Meeting cost in Germany by role prices the hour, and the meeting hours calculator adds up a year of your own standing meetings.
The other reason is the lead's own week. "Since 2022, Gallup finds manager engagement has dropped by nine points" (State of the Global Workplace 2026), and a written round hands the collecting of status back to the people who did the work.
What should a weekly team update include?
A weekly team update should include results, next priorities, blockers with a name and a date, open decisions and, if someone wants, a word of thanks. The list follows Gallup's Engagement Index Deutschland 2025: good managers "clarify expectations, set achievable goals together with their employees, set priorities, define responsibilities" (our translation) and show appreciation.
- What moved toward our goals this week? Name results. "Checkout flow live for 20% of new sign-ups" says more than "worked on onboarding".
- What is my focus next week? One to three items. Past three, it turns into a to-do list.
- What is blocking me, and who can unblock it by when? Name the person and the date.
- What needs a decision? Anything the person cannot decide alone. Only these points may need live time.
- Whose work do I want to mention? Optional, one sentence. In the update, the thanks reaches the whole team.
Weekly team update template to copy
Use it as a channel post, in a shared document or as the script for a recording. Below it is a fictional filled-in example.
The team lead sees at once that one decision is open (question 4) and that there is one dependency on marketing (question 3).
Should the weekly update be written, recorded, or kept live?
Write the weekly update by default, record it when a result is easier to show than to describe, and keep the live meeting in the situations at the bottom of this table.
| Situation | Best format | Why |
|---|---|---|
| Routine week, nothing to show | Written post | Fastest to read, easy to search later |
| Team of two or three | Short form, see below | The full template feels like paperwork |
| A result on screen: prototype, dashboard | Recording, 2 to 3 minutes | Showing is quicker than describing |
| Team spread over sites or time zones | Recording | A voice carries tone a post loses |
| An open decision that affects several people | Short live call, only those involved | It needs back and forth |
| Crisis week, plans change daily | Keep the live meeting | A Thursday deadline is too slow |
| New team or new lead, first weeks | Keep the live meeting | People read each other's posts better once they know each other |
For two or three people, keep questions 3 and 4, merge 1 and 2 into one line ("Done this week, next week") and skip 5 or say it in person. Keep the deadline, or the update drifts to Monday. For recordings, we found no independent research on the right length of a spoken work update, so three minutes is a rule of thumb.
How do you run the weekly update each week?
The week has one deadline and one optional slot: posts by Thursday 12:00, and a 30-minute call on Friday only if a decision is open.
| When | Who | What |
|---|---|---|
| Thursday, 12:00 | Everyone | Update is posted or recorded |
| Thursday 12:00 to Friday 12:00 | Everyone | Read or watch the others, ask in the team channel |
| Friday, 12:00 | Team lead | Collects the "needs a decision" points in one channel thread |
| Friday, 12:00 to 12:30 | Only those involved | Short live call, only if a decision is open |
A Thursday deadline leaves Friday to react, so nothing waits over the weekend. If your team's week ends on another day, or Friday is a no-meeting day, move every step by the same amount.
What goes wrong with a weekly update, and how do you avoid it?
In the first month, a weekly update usually goes wrong in one of three ways.
- Updates turn into activity reports. Question 1 asks for results, so push back gently when someone lists tasks.
- Decisions get made in a thread. A thread is fine for questions; a decision that affects others belongs in the Friday call or in a written note everyone sees.
- The live call creeps back to 60 minutes. Keep it to the open decisions, and cancel it when there are none.
How does a team lead run the recorded weekly update in Capme?
In Capme Meetings the recorded weekly update is one meeting with a deadline. As checked in our code in October 2026, the week runs like this:
- Monday: the lead clicks New meeting, adds one topic per person with that person as speaker and three minutes as the target, sets the deadline to Thursday 12:00 and adds anyone who only watches, such as the head of department, to the audience list (speakers are on it automatically). Speakers have to be workspace members.
- Until Thursday: each person records their topic in the browser, with camera, screen or both. Capme does not remind speakers on its own; Remind everyone reaches only those who have not recorded.
- Thursday, 12:00: the lead clicks Publish meeting, even with videos missing (they show as placeholders), and can switch on one reminder for people who have not finished watching. The shortest option is three days, so in a weekly round it arrives after Friday and only catches stragglers.
- Friday, 12:00: the team watches the chapters in order, and the lead sees for each person watched, partly watched, opened or not opened. Questions go to the team channel, since Capme has no comments.
In Germany, a system that shows who watched what is subject to co-determination by the works council under § 87(1) no. 6 BetrVG. An admin can switch the workspace to Totals only: organisers then see how many people finished, without names, and everyone still sees their own progress (what admins see). This describes the law and the product; it is not legal advice.
Capme has no repeating meeting, so each week is a new meeting and setting up the agenda takes a few minutes. Recordings are not transcribed, so a written post stays easier to search. Meetings come with Team, which stores videos in the EU and costs €12 per speaker a month plus VAT, from 3 speakers: €96 a month for a team of eight, against 8 person-hours of live meeting. Anyone who only watches is free.
Run next week's update as one meeting
Set it up on Monday with a Thursday deadline. Team is free for 14 days.
How do you roll out the weekly update in the first four weeks?
Run the first week in parallel: everyone posts by Thursday noon, and the live meeting still happens, cut down to the open decisions. In week two, cancel the meeting and keep only the Friday slot. Until week four, the lead replies to every update at least once, so people see the posts get read. Then ask the team whether every open decision was settled by Friday. If not, check question 4 first: every open decision needs the name of the person who decides.
Frequently asked questions
- What if someone misses the Thursday deadline?
- The round goes out at noon without them, and the lead asks once, directly. A late update still counts, and in Capme a late video is still accepted. If the same person misses several weeks in a row, raise it in a one-to-one.
- Should the team lead post an update too?
- Yes, first and in the same format. The lead's update adds what was decided last Friday and what the lead needs from the team this week.