Asynchronous work: how a team runs on written updates, voice notes and recaps — with a weekly template (2026)

Asynchronous work is work that does not wait for a reply: each person posts the update, the question or the decision in writing, by a set time, and the others read and answer it when they are at their desk, not when it arrives. What stays live and what goes written, the four building blocks — the written update, the thread, the voice note and the recap of the one live call — a weekly template you can copy, three filled-in examples, where each piece lives in Teams, Zoom, Google Workspace and Slack, and how a channel keeps the whole week readable by each member in their own language.

The Mind.com Team

  • Asynchronous work does not wait for a reply. Updates, questions and decisions are written by a set time and read when the reader is free.
  • The writing has to land where the team reads. In Teams, Zoom, Google Workspace and Slack a call leaves one document, in the room's language.
  • InterMIND keeps the whole channel in each member's language, updates, voice notes and every recap, next to Teams or Slack rather than instead of them. Guests join free by link, no account; you pay only for active members.
Asynchronous work: how a team runs on written updates, voice notes and recaps — with a weekly template (2026)

Asynchronous work: how a team runs on written updates, voice notes and recaps — with a weekly template (2026)

Asynchronous work is work that does not wait for a reply. Each person posts what they finished, what they need and what they decided — in writing, by a set time — and the others read it and answer when they are at their desk, not the moment it arrives. The alternative, synchronous work, puts everyone in the same hour: a meeting, a call, a chat where the cursor blinks until someone types. A team that works asynchronously keeps a few of those hours and moves the rest into messages that have an author, a time and a thread.

This guide is the craft first — what stays live and what goes written, the four building blocks, a weekly template you can copy, three filled-in weeks — then the mechanics: where the written update, the voice note and the recap live in the tools your team already uses, and what happens to them a week later. Because the test of asynchronous work is not whether the meeting was cancelled. It is whether the person who was asleep when the decision was made can find it on Monday.

What asynchronous work is — and what it isn't

Two ways of working surround every team, and the mistake is to treat one as the rule and the other as a failure:

SynchronousAsynchronous
When it happensAt the same time, for everyone invitedWhen each person gets to it, inside an agreed window
What it is forA decision with a trade-off, a disagreement, a first meeting, bad newsStatus, plans, a question with one answer, a review, anything that is better after thinking
What it leaves behindWhat someone wrote down, or a recap if the tool writes oneThe message itself: who, when, and the replies under it
What it costsEveryone's hour at onceA few minutes per person, and a wait

Asynchronous work is not "no meetings", and it is not a chat that never sleeps. A chat where every message expects an answer in two minutes is a meeting that never ends; a team that cancels every call and decides nothing has not gone asynchronous, it has stopped deciding. The craft is a default: written first, live for the short list of things that need everyone's attention at once. The meeting cadence guide sorts a team's recurring meetings into the ones that survive that test and the ones that become a message.

The four building blocks

An asynchronous team runs on four kinds of message. Most teams already have three of them and lose the fourth.

  1. The written update, by a set time. One message per person, same shape every time, posted by an hour the team agreed — "by ten, your time". The set time is the deadline for writing, not for reading: the reader comes to it when their day allows. One message per person, not a form and not a shared document, because a message has an author, a timestamp and a place for replies. The weekly version is in how to improve team productivity; the daily one is the asynchronous stand-up.
  2. The thread, not the call. A question goes under the message it is about, so that the answer lands next to the problem and the rest of the channel stays readable. One answer closes it. A thread that reaches three replies without an answer is a call — a short one, between the two people in the thread, with the outcome typed back into the thread when it ends. That last step is what keeps the thread the record.
  3. The voice note. Some things are faster to say than to type: three sentences after a client call, a decision taken in a corridor, a status from the road. The rule that keeps a voice note asynchronous is that it must arrive as text. A recording the team has to listen to is a meeting nobody scheduled; a transcript is a message like any other — searched, quoted, answered in a thread.
  4. The recap of the one live call. The decisions a thread could not close go to a single live call a week, and the call ends with its decisions read back aloud and written down the same day, where the updates live — not in the organizer's notes. A decision that exists only in the memory of the people who were on the call is, for everyone else, a decision not taken. The decision log is the long-term shape of that habit.

Two rules hold the four together. A response window: replies inside four working hours during the team's overlap, next morning outside it, and one agreed signal — a phone call, the word urgent — for the rare thing that cannot wait. Without the window, every message is urgent, which is to say none is. A single home: the updates, the threads, the voice notes and the recap live in the same channel, in date order. A team whose updates are in a chat, whose decisions are in a document and whose recaps are in a mailbox has gone asynchronous in four places and can find nothing.

How to run a week asynchronously: before, during, after

Before the week: set the window, name the channel, write the first update yourself. Asynchronous work fails quietly when it is announced and not modelled. Put the response window and the set times in the team's norms, one paragraph; create the one channel; and post the first Monday plan yourself, in the template's shape, so the second person copies a message rather than a rule.

During the week: run the set times, not the chat. Monday opens with the plan: three outcomes for the week, each with an owner and a day. Each day, each person posts the three-line update by their set hour, typed or spoken. Questions go under the message they are about. The lead's job is not to answer everything — it is to close threads: an answer, a decision, or "this goes to Thursday". Thursday is the one live call, thirty minutes, for the short list the threads produced. Nothing else needs the calendar.

After the week: publish the weekly, and read last week's. Friday's weekly is each person's four lines — done, not done and why, next week, needs a decision — by four. The lead's reply is the one message that closes the week: the decisions taken, the ones still open with an owner and a date, and the one or two numbers the team watches. The following Monday's plan opens by naming what Friday left open. That loop, Friday to Monday, is what turns a channel full of updates into a team that does not repeat itself.

A weekly template for asynchronous work

[Team] — week of [date]
Window: replies within [four working hours] during [core hours, with time zone]; outside them, next morning. Urgent means [a phone call / the word URGENT in the first line].
Channel: [the one channel] — updates, threads, voice notes and recaps live here.

Monday — plan — [lead] — by [10:00]
Three outcomes for the week: [outcome — owner — day]. Carried from last week: [item — owner].

Daily — update — everyone — by [10:00, own time]
Finished since yesterday · will finish by tomorrow · blocked by. Three lines, or a voice note that says the same three things.

Threads — questions
Under the message they are about. One answer closes a thread; three replies without one become a call, and the call's outcome goes back into the thread.

Thursday — the one live call — [30 min] — [link]
Only what the threads did not close. Each item: decided / open / deferred to [date]. Read back aloud; recap the same day.

Friday — weekly — everyone — by [16:00]
Done · not done, and why · next week · needs a decision.

Open decisions: [item — owner — by when]

Three filled-in weeks

A product team across two offices — nine people, two hours apart

Window: four working hours, 10:00–16:00 CET; outside them, next morning. Urgent = phone.
Monday — plan — Ana — by 10:00 CET: ship the export behind a flag; close the two open bugs from support; decide the date for the pricing page.
Daily — update — everyone — by 10:00 own time: three lines; the two engineers on the road post voice notes.
Thursday — live, 30 min: the pricing date, which the thread could not settle; the flag naming, raised Tuesday with no answer.
Friday — weekly — everyone — by 16:00: four lines each; Ana closes with the decisions and the two numbers.

A delivery team and the client's team — two companies, one project

Sales agreed the contract; now the two teams settle the details. The client's project lead is in the project channel, not in a separate email thread.

Window: next morning, both sides; the client's lead is not expected to read evenings.
Monday — plan — Marta — by 10:00: the three deliverables due this week, each with an owner on our side and a reviewer on theirs.
Daily — update — our side only, by 10:00: finished, next, blocked by — "blocked by" usually names a question for the client, which goes into a thread the client's lead answers when her day allows.
Thursday — live, 45 min, both sides: the scope question from Tuesday's thread; the acceptance date. Recap to both teams the same day, and a copy to the client's project address.
Friday — weekly — Marta — by 16:00: one message the client reads on Monday morning — done, at risk, needs their decision.

A service team with field staff — a dispatcher and six installers

Window: installers reply between jobs; the dispatcher replies within the hour during the shift.
Daily — update — each installer, by 08:30: a voice note from the van — yesterday's jobs closed, today's first address, anything missing from the kit — which arrives as text the dispatcher reads at the desk.
Threads: a missing part is a thread under the installer's note; the dispatcher's answer is the part number and the time it will be there.
Thursday — live, 20 min: the two addresses nobody can get into; the schedule for next week.
Friday — weekly — dispatcher — by 16:00: jobs closed, jobs carried, what the team needs from procurement.

Notice what the three have in common: every message has a set time and an author, every question lives under what it is about, the one live call takes only what the threads could not close, and the week ends in writing. That is the whole craft. The shape of the Thursday call itself — the list, the time boxes, the read-back — is in the meeting agenda template, and what the team does with the people outside its payroll is in managing remote teams.

Where the update, the voice note and the recap live in the tools you already use

The written update needs only a chat where a message has an author and a time, and any of the four below has that. The other two building blocks are where the platforms differ: what a spoken update becomes, and what the one live call leaves behind for the people who were not on it. Documented behaviour only, from the vendors' own pages, checked November 2026:

PlatformA spoken updateWhat the live call leaves behind, and for whom
Microsoft TeamsA video or audio clip of up to a minute, sent to a one-on-one chat, a group chat or a channel; video clips have auto-generated captions, and the page does not state captions or a transcript for audio clipsA recap — recording, transcript, shared files, notes, agenda and follow-up tasks — after events that were recorded or transcribed; the intelligent recap with the AI summary is part of Teams Premium or a Microsoft 365 Copilot license, the AI summary is available for events transcribed in a supported language, and recap notifications, notes and content are not currently available for ad-hoc events
Zoom WorkplaceClips lets users record videos outside of meetings when an account owner or admin allows it; the length of a clip, where it lands and whether it is transcribed are not stated on the page citedA meeting summary with AI Companion, sent by email and posted to the meeting's group chat when chat access is enabled, for a licensed user on a paid Zoom Workplace plan; participants must be signed in during the meeting to receive it automatically, unauthenticated users do not receive the email, and a meeting in several languages is summarized in the language used by the majority of participants
Google WorkspaceA voice message in Google Chat, to a person or a group, from a computer, Android or iPhone; the receiver can open a transcript with View transcript; no length limit is stated, and the feature is not available on Chrome OSTake notes for me in Google Meet writes a Google Doc saved in the organizer's Drive, attached to the Calendar event and emailed to the organizer, shared with all invited guests, guests in the organization or hosts only, per the setting; it requires an eligible Workspace edition or Google AI plan, and "this feature supports one language at a time"
SlackAn audio or video clip of up to five minutes, in a channel or a direct message, on all plans and for members and guests; a transcript is generated when a person selects Generate transcript, and closed captions are available for video clipsA huddle has "a dedicated message thread to share notes, links, and files" and a canvas for meeting notes that stays in a tab of the conversation after the huddle; captions are currently only available in English and are not saved once the huddle ends; on the free plan a huddle holds two participants

Two things are the same across the four. A spoken update becomes text either on request, for video only, or not as stated; and the live call leaves one document or one summary, in the language the room used, for the people a host or an admin chose. None of the pages cited states that a reader gets any of it in a language of their own. What Teams and Meet offer inside the live call itself is documented in Teams live translation and Google Meet live translation; the third-party notetakers many teams add to the call, with their minute caps and language lists, are compared in Otter.ai alternatives. For a team in one office, in one language, with nobody outside the payroll in the channel, the table is the whole answer. The next section is one way the job gets done where it is not.

How an asynchronous week lives in one channel

InterMIND is a communication space where a team's meetings live in a channel, so the four building blocks have one home. The Monday plan is a message in the channel, pinned for the week. The daily update is a message under it or beside it, and a question about it is a reply that quotes the line it is about — the quoted block scrolls the reader to the original. The reaction row under a message is the asynchronous nod: 👀 means seen, ✅ means done, 🤔 means a question is coming. Thursday's call is the channel's own meeting, with a permanent link and a recurrence set once in Google Calendar or Outlook. And the history is the channel itself: Friday's weekly from three weeks ago is one search away.

The whole of it stays in each member's language. The chat is translated per reader — one person types in Portuguese, the colleague in Warsaw reads it in Polish and answers in Polish, and each side has the original one toggle away — so the update written at eight in Lisbon is read at ten in Warsaw as if it had been written there. A voice note is the microphone button in the channel composer, from the web or the phone app: up to ten minutes, transcribed within seconds, read by each teammate as text in their own language with a play button for the original, and searched, quoted and forwarded like any other message. An update from someone who cannot open the app — in a vehicle, on a ward, in a system that only sends email — lands in the channel through the channel's own email address, created by the host, under the sender's name and with attachments kept. During the Thursday call, the list of open decisions, posted as a note, goes on everyone's screen next to the video tiles with Share to conference: the sharer marks each item decided, open or deferred while the room watches, and every participant reads it in their own language.

When the call ends, the recap is written from the meeting itself: a summary and the action items with owners, each line keeping its timestamp. It arrives by email to each signed-in member, as a message in the channel and as a link in the calendar event, and every member reads it in their own language — the record is translated per reader, not written once in the language the call happened to use. Any member can edit it, every edit keeps author and revision history, and the channel keeps the recap of every past session, so the Thursday decision from last month is next to the Friday weekly that followed it. The host can add a recap copy to any address — a CRM inbox, the client's project address — so the outcome reaches the other company without anyone forwarding anything.

The membership rule of the second example maps onto two doors. A channel is members-only: the client's project lead, the contractor, the colleague in the other office who belongs in the team's week is added by email invitation onto a free account and reads the channel in their own language from then on — the same updates, the same threads, the same recaps. Someone who needs one call only — a supplier for one review, a candidate for one conversation — joins an ad-hoc meeting by link, from a phone, without an account and at no cost, hears the meeting live in their own language and gets nothing afterwards: the account is free, and it is what makes the record reachable. The host provides the space and, on a paid plan, pays only for the members active in the previous 28 days — joined a meeting, wrote in a chat, asked Mia. Channel participants from outside the team and meeting guests are free; a member on leave for a month keeps access and costs nothing that month, and the weeks they come back to are in the channel, in their language.

Asynchronous work as a craft survives every tool: somebody still has to post the plan on Monday, keep the update to three lines, close the threads and read the decisions back on Thursday. What does not have to survive is the second job — reconstructing the week afterwards, by hand, in one language, for a team that reads in several and for the people who were asleep when it happened.

FAQ

What is asynchronous work?

Asynchronous work is a way of working in which people do not need to be available at the same time: updates, questions and decisions are written down and posted by an agreed time, and each person reads and answers them inside an agreed window rather than the moment they arrive. Live meetings are kept for the short list of things that need everyone at once — a decision with a trade-off, a disagreement, a first meeting.

What is an example of asynchronous work?

A daily update posted by ten in each person's own time — finished, next, blocked by — read by the lead at their desk and answered in a thread; a voice note recorded after a client call that arrives as text; a design review done as comments over two days instead of a one-hour call; a weekly written by Friday afternoon that the other office reads on Monday morning. The three filled-in weeks above are examples of a whole week.

What is the difference between synchronous and asynchronous work?

Synchronous work happens at the same time for everyone involved — a meeting, a call, a live chat — and costs everyone's hour at once. Asynchronous work happens when each person gets to it, inside a window, and costs a few minutes per person plus a wait. Synchronous suits decisions with trade-offs and conflict; asynchronous suits status, plans, questions with one answer and anything that is better after thinking.

What are the benefits of asynchronous work?

Fewer interruptions, because a message waits and a meeting does not; a working day that fits each person's hours and time zone, so a team across offices does not meet at seven in the morning for one side; and a written record by default, because the update, the question and the answer are messages with an author and a time rather than words in a room. The cost is the wait, which is why a response window and a signal for the urgent are part of the method.

Is asynchronous work better than meetings?

For status, plans and single-answer questions, a written message is cheaper than a meeting and leaves a record. For a decision with a trade-off, a disagreement or bad news, a live call is faster and kinder than a forty-reply thread. A team that works well asynchronously is not a team without meetings; it is a team whose meetings take only what the threads could not close.

How do you run an asynchronous stand-up?

One message per person, by a set time, in one channel, with the same three parts in the same order — finished since yesterday, will finish by tomorrow, blocked by — a thread per blocker, the facilitator closing the list at the set time, and a live call on a fixed cadence for what the threads did not clear. The rules and a daily agenda are in the stand-up meeting guide.

What is an asynchronous work schedule?

A schedule that fixes when things are written rather than when people are present: a set time for the daily update, a set time for the weekly, a response window for replies, an overlap of a few core hours when the team is reachable live, and one fixed slot a week for the live call. Everything else is each person's own hours.


Sources: Microsoft — Record a video or audio clip in Microsoft Teams; Microsoft — Recap in Microsoft Teams; Zoom — Managing Zoom Clips; Zoom — Using Meeting Summary with AI Companion; Google — Send voice messages in Google Chat; Google Meet — "Take notes for me" in Google Meet; Slack — Record audio and video clips in Slack; Slack — Use huddles in Slack; checked November 2026. Vendors change plans, features and language lists over time; check their pages for the current state.

More in Meetings & recaps

All posts in Meetings & recaps
AI note taker for Google Meet: the ways to get notes from a Meet call, and what each leaves the team with (2026)
Meetings & recaps

AI note taker for Google Meet: the ways to get notes from a Meet call, and what each leaves the team with (2026)

An AI note taker for Google Meet is one of four things: Gemini's own Take notes for me, a notetaker bot that knocks and sits in the participant list, an app that records on your device with no bot, or a meeting room with the notetaker built in. Each one leaves something different behind the call — where the notes land, who receives them, which Workspace edition it needs, in which language they read, and what the guest who knocked walks away with. The four ways by the vendors' own documentation, a verdict table, and how to choose in 30 seconds.

The Mind.com Team

AI note taker for Microsoft Teams: the ways to get notes from a Teams meeting, and what each leaves the team with (2026)
Meetings & recaps

AI note taker for Microsoft Teams: the ways to get notes from a Teams meeting, and what each leaves the team with (2026)

An AI note taker for Microsoft Teams is one of four things: Teams' own Recap with Copilot or Facilitator, a notetaker bot that waits in the lobby and sits in the participant list, an app that records on your device with no bot, or a meeting room with the notetaker built in. Each one leaves something different behind the call — where the notes land, who receives them, in which language, and what the external attendee on the link gets. The four ways by the vendors' own documentation, a verdict table, and how to choose in 30 seconds.

The Mind.com Team

AI note taker for Zoom: the ways to get notes from a Zoom meeting, and what each leaves the team with (2026)
Meetings & recaps

AI note taker for Zoom: the ways to get notes from a Zoom meeting, and what each leaves the team with (2026)

An AI note taker for Zoom is one of four things: Zoom's own Meeting summary with AI Companion, a notetaker bot that sits in the participant list, an app that records on your device with no bot, or a meeting room with the notetaker built in. Each one leaves something different behind the call — where the notes land, who receives them, in which language, and what the guest on the link gets. The four ways by the vendors' own documentation, a verdict table, and how to choose in 30 seconds.

The Mind.com Team

Get new posts and product updates by email

One email a month with new posts and product updates. Unsubscribe anytime.