Which meetings can go async? A one-question test and 9 meeting types sorted

A Monday team meeting: 40 minutes of status on three projects, then 20 minutes on who gets the extra developer. Only the 20 need the room. A meeting can go async when its job is to pass information on: status updates, project reviews, announcements and demos. It should stay live when people have to agree on something they see differently, when the topic is personal, or when nobody can say yet what the question is. If it has to produce "everyone knows X", record it. If it has to produce "we agree on X", meet.

An async meeting has the parts of a normal meeting (an agenda, speakers, a result, a date by which it is done) but no shared time slot. Each speaker records their part when it suits them, the others watch when it suits them, and questions go back in writing, for example in the team channel. The meeting ends at a deadline instead of at 10:30.

Unlike an email thread, it has an agenda and an end. Capme Meetings is built on that shape.

Nobody has measured how many meetings in Germany could go async, but employees have a clear opinion about their own calendars. In February 2025 the market research firm bilendi surveyed 1,040 employees in Germany for the HR software vendor HR WORKS, which calls the survey representative. Respondents had 4.4 meetings a week on average and considered 2.9 of them dispensable. They spent 4.7 hours a week in meetings and counted 3.2 of those hours as wasted, and 26% felt their own attendance was not needed.

"Dispensable" is a self-report, so it overstates the case a little: some of those meetings matter to someone other than the person asked. It still shows where to look first. 2.6 of the 4.4 weekly meetings were internal, and internal meetings are the ones a team can change on its own.

The ifo Institute measured 24.9% of employees working at least partly from home in August 2026, and 35.1% in services. The guide to async communication for remote teams covers which channel such a team should use for what.

Whether a meeting runs async or sync depends on whether it passes information on or has to produce agreement. Media Synchronicity Theory, set out by Alan Dennis, Robert Fuller and Joseph Valacich in MIS Quarterly in 2008, calls these conveyance and convergence. Its abstract puts the rule in two sentences: "For conveyance processes, use of media supporting lower synchronicity should result in better communication performance. For convergence processes, use of media supporting higher synchronicity should result in better communication performance."

A recording lets each viewer go back over the material. A live conversation surfaces a misunderstanding within seconds.

Meetings work well async when most of their minutes pass information on. The last two rows are where async loses:

What each speaker covers comes from the five-question weekly update. Setting it up in Capme Meetings takes the organiser five steps:

As checked in Capme's code in October 2026, the watch reminder goes out once per meeting, only to people on the audience list who have not finished. An admin can switch the workspace to totals only: then nobody sees who has watched what, and everyone still sees their own progress.

Capme has no comments or threads, so questions go to your team channel, and it does not transcribe or summarise recordings. It is a meeting platform for the meetings where few speak and many listen, and it is neither a call tool nor an AI notetaker. Videos are stored on EU hosting, or in your own S3 bucket on Business and Enterprise.

Five kinds of meeting should stay live:

If you need the answer from the room before you can say the next sentence, the meeting should be live.

Async slows decisions down when a team treats it as "reply whenever". Every async round needs a firm deadline, and a disagreement still open at the deadline goes to a short live call within one working day, with only the people involved. The updates are already done, so that call can take 15 minutes. In a live hour, an open decision competes with the status reports and can slip a week.

If a team needs quick answers several times a day, recordings with a deadline are the wrong tool. A call or a chat message is faster.

The Monday meeting from the audit, one hour with seven people, costs 420 person-minutes (7 x 60). Our own calculation for the same content run async: three speakers spend 10 minutes each preparing and recording a 3-minute update (30), all seven watch 9 minutes of video (63), and the developer question goes to a 15-minute call with three people (45). That is 138 person-minutes, about a third of the hour. The result depends on a recorded update being shorter than a spoken one, because nobody waits for a screen share or repeats for latecomers. At 6 minutes per update it is 30 + 126 + 45 = 201 person-minutes, still under half.

Try your own numbers with the meeting cost formula, the calculator or costs per role in Germany. For finance, the business case for async meetings puts it on one page.

To replace a meeting with an async one, change one recurring meeting for four weeks. We think the weekly team update is the one to try first, because it is almost all information and it repeats every week, so four weeks give you four rounds to compare. The meeting hours calculator lists your own standing meetings by cost.

Once a few meetings have moved, the freed hours are scattered across the week. A no meeting day pools them; set it up after you have sorted your meetings.