Async project status meeting: agenda template, person-hours and escalation rule
Steffen Rosenögger, Founder of CapmePublished October 15, 2026
A filled-in agenda for a six-workstream review, the person-hour math (12 down to about 4.7 a week) and the rule for what still goes live.
In short
- In the ERP example, a one-hour review for twelve people costs 12 person-hours a week; a recorded round plus a 20-minute live slot for four costs about 4.7.
- Four kinds of item go live: a change to signed-off scope, budget or dates; a clash between workstreams; a red the owner cannot fix alone; a decision that cannot wait a week.
- Amber for the third week running counts as red.
A project status review is a regular meeting in which each workstream owner reports progress, risks and decisions needed against a plan the steering group signed off. German projects call it the Jour fixe, which Duden defines as a "meeting of a set group of people held regularly [on a particular day of the week]" (translated).
Run it as a recorded agenda: each owner records two to three minutes against the plan by Thursday noon, and each stakeholder watches only their chapters. A short Friday live slot stays for the four kinds of item in the escalation rule and is cancelled when there are none.
Which topics, owners and target lengths go on a project status review agenda?
A recorded status review agenda has one row per workstream, with owner, target length and who needs it most, below the project lead's intro. The example is fictional: a mid-sized company rolls out ERP with an outside partner.
| Topic | Owner | Target | Who needs it most |
|---|---|---|---|
| 0. Overall status, open escalations | Project lead | 2 min | Everyone, above all the steering group |
| 1. Finance processes | Head of accounting | 3 min | CFO, data migration |
| 2. Data migration | IT lead for the migration | 3 min | Finance, training, head of IT |
| 3. Interfaces to shop and warehouse | Lead developer | 3 min | Head of IT, testing |
| 4. Training and change | HR business partner | 2 min | Managing director, all owners |
| 5. Implementation partner | Internal vendor manager | 2 min | Partner's project lead, CFO |
| 6. Testing and go-live readiness | QA lead | 3 min | Steering group, all owners |
What should each workstream owner say in a two-minute status update?
Each owner covers the same four parts in the same order, for listeners who do not know the workstream's details.
- Status: green, amber or red, and one sentence on why.
- What changed against the plan: milestones reached or moved, with old and new date.
- Risks and dependencies: anything new, and which workstream it affects, by name.
- Decision needed: question, options, your recommendation and the date you need it by. Or "nothing to decide this week".
Training learns its date is shaky a week early. Sharing the screen for a number, such as the validation report, saves a paragraph of explaining.
Who clicks what in Capme during the ERP week, Monday to Friday?
In Capme Meetings, the project lead creates one meeting a week; any live slot runs in your usual call tool.
- Monday, project lead: clicks New meeting, sets the deadline to Thursday 12:00, adds six topics below her intro and lists the steering group and the partner's lead as audience.
- Tuesday to Thursday, owners: record in the browser from their link; nobody gets cut off at the target length.
- Wednesday, project lead: Capme does not remind speakers on its own, so she presses Remind everyone, which reaches only owners who have not recorded. Topic 6 goes to a deputy while the QA lead is on holiday.
- Thursday afternoon, project lead: watches all 18 minutes, records the intro and books the Friday slot if an item meets the escalation rule. Publish meeting warns that one video is missing; a placeholder shows until it arrives. In that dialog she sets one reminder, after 3, 7 or 14 days, for anyone not finished watching.
- Thursday evening, the CFO: enters the six-digit code from her email and, without joining the workspace, watches topics 0, 1 and 5 in seven minutes.
- Friday 9:00, project lead: as checked in Capme's code in October 2026, the page shows per person who watched (75% seen), partly watched, opened or never opened it, unless an admin chose totals only. Agree that setting with any works council first (video tools and the works council).
Videos stay in the EU on Solo and Team or in your own S3 bucket on Business and Enterprise (where your videos live); under Capme's pricing this review pays for seven speaker seats a month, and an eighth while a deputy without one stands in. Capme has no comments and no repeating meeting.
Is 4.7 person-hours a week a fair estimate for a twelve-person review?
About 4.7 person-hours a week is fair for the ERP review if the table's assumptions hold. The figure is our own calculation; swap in your project's numbers. To see the review beside your other standing meetings, add up your own meeting year.
| Who | Assumption | Person-minutes |
|---|---|---|
| Six owners | 10 min each: 3-minute target plus notes, setup, one retake | 60 |
| Project lead | 10 min setup, 5 min intro, 18 min watching | 33 |
| Everyone else on the list, owners included (11) | 10 min each: about four chapters of 2.6 min | 110 |
| Live slot | 4 people for 20 min (two deciders, two owners concerned) | 80 |
| Total | 283 person-minutes, or 203 without the live slot | about 4.7 h |
It leaves out written follow-up questions and assumes owners never get faster. At 20 minutes per recording the total is about 5.7 hours, still under half. It hides a cost in speed: a decision raised on Thursday is taken on Friday morning, where the old meeting took it in the same hour. For a budget holder, see the business case for async meetings.
When is a live review or a written status better than a recorded round?
The recorded round wins when several workstreams report to people who each need only part of it; the table covers the other cases.
| Situation | Live review | Recorded round + live slot | Written status only |
|---|---|---|---|
| Small project: three owners, four listeners | Wins: a 15-minute call | Loses: setup costs more | Works if nothing needs context |
| Every workstream green | Loses: an hour to hear "on plan" six times | Works, but the video adds little | Wins: three lines each |
| Crisis week, several reds | Wins: everyone decides together | Loses: hold the full live meeting | Loses |
| Direction or priorities in dispute | Wins | Loses: a recording cannot argue back | Loses |
| Steering group and partner outside the team | Loses: one hour that fits nobody's calendar | Wins: they watch from an email link | Works if they can open your tool |
We think the recorded round starts to pay from about five workstreams with someone from outside the team watching, because below that a 15-minute call is cheaper (which meetings can go async) and above it most listeners waste most of the hour. Keep one live steering review per phase gate or month anyway. If your status already lives in Jira or Confluence and the week is green, a line there beats a recording.
How should a project define red, amber and green?
A project should define red, amber and green (RAG) by what happens next, so the colour tells a stakeholder whether to act. Put the definitions in the project handbook.
| Colour | Means | What happens next |
|---|---|---|
| Green | On plan for scope, dates and budget | Nothing; a written line is enough |
| Amber | At risk; the owner can recover alone | The update gives the plan and when it works |
| Red | Milestone, budget or scope will be missed unless someone outside acts | Goes to the live slot automatically |
House rule: amber for the third week running counts as red. The colour forecasts the agreed plan, so a team working flat out on a slipping milestone is still amber or red.
Which items must go to the live slot?
Four kinds of item go to the live slot; everything else stays in the recorded round, with questions sent to the owner in writing, by email or team chat, since Capme has no comments.
- A change to scope, budget or a milestone date that the steering group signed off. Whoever approved the plan approves the change.
- A conflict between workstreams: two need the same people in one week, or one's delay moves another's dates.
- A red status the owner cannot resolve inside their own workstream.
- A decision by the partner or a steering member that cannot wait a week.
The live slot gets one line per escalated item, in the project lead's order, with only the deciders and the owners concerned, and without a notetaker unless all of them agree (AI notetaker or async meeting?). If three workstreams report red in the same week, the whole review goes live that week.
Before that week-five decision, count how many of the four Fridays the live slot met.
Run next week's status review as a recorded agenda
One topic per workstream, a Thursday deadline, the partner on the list.
Frequently asked questions
- What if a workstream owner misses the Thursday deadline?
- The project lead gives that workstream's status in the intro, and the late video replaces the placeholder once it arrives. House rule: a second missed deadline in a row counts as amber.
- Can the partner's project lead record their own update?
- Only if an admin gives them a speaker seat; speakers must be workspace members. Otherwise the internal vendor manager reports and the partner's lead watches free.