Asynchronous Meetings: What They Are and When You Can Skip the Call

An asynchronous meeting replaces a live call with written updates, recorded video or comments on a shared document that people add at different times before a set deadline. Unlike a live working meeting, where people decide or build together in real time, it doesn't need everyone online at once. Below: the differences, examples, pros and cons, when to switch, how to run one, and when a recording is enough.

What is an asynchronous meeting?

An asynchronous meeting is a meeting where participants contribute at different times — through written updates, recorded video or audio, or comments on a shared document — before a set deadline, instead of joining a live call. "Async meeting" is the everyday short name for the same thing.

It runs on asynchronous conferencing between teammates: messages, documents and recordings answered on each person's own schedule. An async meeting keeps a topic, an owner and an outcome, but swaps the end of the call for a deadline, such as "comments by Thursday noon ET."

Asynchronous meetings matter most in remote work and hybrid work, because distributed teams rarely share a convenient hour. Async-first teams make written and recorded updates the default, and a live call needs a reason; a job post that asks for experience in "async distributed teams" means exactly that.

What does "asynchronous" mean in simple terms?

"Asynchronous" means not happening at the same time. Dictionary.com gives that as its first sense: "not occurring at the same time." Email is the everyday example: you answer when it suits you, not the moment a message arrives. The opposite, synchronous, means happening at the same time.

Synchronous vs asynchronous meetings: what's the difference?

A synchronous meeting happens in real time — in a room, on a video call, or on the phone — while an asynchronous meeting spreads the same discussion over hours or days. In a synchronous, real-time meeting, everyone is present at once and answers come in seconds: that is real-time communication. Video conferencing, an in-person meeting and a conference call are all synchronous.

The channel alone doesn't set the type; the expected response time does. Instant messaging is synchronous when everyone in the chat answers within a minute, and asynchronous when replies can wait until tomorrow. A live webinar is synchronous; its recording, watched a week later, is asynchronous. Voicemail is a classic asynchronous channel.

In office slang, a "sync meeting" is narrower: a sync-up, a short team check-in.

Examples of asynchronous meetings

The most common async meetings are written standups, recorded video updates, document reviews with comments, async brainstorms on a shared board, and recorded presentations. Each one replaces a familiar live meeting and leaves its result in writing. The response windows are editorial suggestions, not a standard:

Written updates suit anything that fits in a few lines. A recorded video update suits anything people need to see; most are screencasts, screen recordings with voice-over. Document collaboration needs no new tool: a draft with comments and a due date is already an asynchronous meeting. Brainstorming works in writing too: collect every idea before anyone votes, so the first ideas don't steer the rest. Slack, Loom and Google Docs stand for tool types; any equivalent works.

Pros and cons of async meetings

Async meetings protect focus time and work across time zones, but they slow down decisions and lose the nonverbal cues and quick back-and-forth of a live conversation. The meetings they replace often weren't working anyway: in Atlassian's survey of 5,000 knowledge workers, meetings were ineffective 72% of the time.

Pros:

• Time zones. In Microsoft's Work Trend Index report Breaking down the infinite workday (June 2025), nearly a third of meetings span multiple time zones, and meetings after 8 p.m. are up 16% year over year. An asynchronous meeting has no 8 p.m. slot, which protects work-life balance; if burnout is a concern, move those late calls first.
• Deep work. Each recurring call you remove frees a block of focus time for deep work; to see the productivity effect, count your uninterrupted two-hour blocks per week before and after.
• Fewer hours on video. Stanford researcher Jeremy Bailenson links Zoom fatigue to nonverbal overload on video calls, an argument he notes still needs direct testing (Technology, Mind, and Behavior, 2021).
• Flexibility and time to think. People answer when it fits their day, and someone working in a second language can write a considered reply.

Cons:

• Slower decisions. A question two people could settle on a short call can take a day of replies.
• Lost nonverbal cues. Nobody sees a frown or hears hesitation, so short replies get misread.
• Lost context and isolation. Readers miss the side remarks behind an update, and some feel cut off from the team.
• Clarification loops. Follow-up questions pile up that a short conversation would end.

When should a meeting be asynchronous — and when should it stay live?

Make a meeting asynchronous when its goal is to inform, nothing is urgent, and one person would do most of the talking; keep it live when the group has to decide, create something together, or handle a sensitive conversation. Atlassian's Team Playbook play Think before you sync turns that decision-making into five questions:

1. Is it urgent? No: asynchronous. Yes: live.
2. What's the goal? To inform: asynchronous. To create, make a decision or unblock work: live.
3. How many people are involved? More than 8: asynchronous. Fewer than 8: live.
4. Will one person talk the whole time? Yes: asynchronous. No: live, possibly with an asynchronous part.
5. How complex is the topic? Not complex: asynchronous. Complex: live, possibly with an asynchronous part.

Some conversations stay live whatever the answers:

• One-on-one meetings, because trust builds on how things are said and on follow-up questions asked in the moment.
• Performance feedback and HR conversations, because the person needs to react and be heard right away.
• Conflicts and stuck problem-solving: after two rounds of written replies without progress, book a short call.

For recurring meetings, the decision usually looks like this:

How to run an asynchronous meeting

An async meeting needs the same things as a live one — an owner, an agenda, and an end — plus a written deadline and a clear rule for who makes the final call. Seven steps:

1. Name one owner who posts the question, chases late replies and closes the meeting.
2. Write the question or agenda in one place: one document or one channel post, not scattered messages.
3. Attach the pre-read (data, a draft or a recording) with its reading time. GitLab's handbook page on all-remote meetings asks for agendas 72 hours ahead, 24 hours at minimum, and notes that agendas shared that early make asynchronous participation efficient.
4. Set the reply format, such as "Approve, Approve with changes, or Object plus one reason." Written feedback on a draft goes in doc comments, next to the line in question.
5. Set a deadline with a time zone: "Thursday 12:00 p.m. ET," not "end of week."
6. Say who decides and what silence means: for example, the product lead decides Friday morning; no reply counts as no objection.
7. Close in writing, in the same place. Post the decision, owners and dates at the top of the doc and in the team wiki, so the documentation sits where people search for it.

A post that covers all seven steps:

Async meeting: pricing page copy for the November launch
Owner: [your name]
Question: Approve the new pricing page copy?
Pre-read: [link to the draft] (about 5 minutes)
How to reply: comment in the doc; end with Approve, Approve with changes, or Object + one reason
Deadline: Thursday 12:00 p.m. ET
Who decides: [product lead], Friday morning; no reply by the deadline = no objection
Outcome: posted at the top of this doc and in the team wiki

Can a recording replace attending the meeting?

Often, yes: a recorded meeting works as an asynchronous meeting for anyone who only needs to know what was decided and what they own, but not for anyone who needs to influence the decision. Use a record-once, catch-up-later setup:

• Live: only the people who decide or must debate.
• Everyone else: the recording, linked in the agenda within 12 hours as GitLab's handbook asks (same page as above), plus a searchable transcript and a short summary.
• A review window: when a meeting takes place outside some participants' time zones, the same page says to "consider confirming decisions and actions for 24-48 hours," so they can contribute asynchronously. Without that window, catching up means finding out you were overruled.

If you skipped the call, catch up in four steps:

1. Read the summary, decisions and open questions first.
2. Check the action items with your name, then the ones assigned to your team.
3. Ask the recording: "What did we decide about the launch date?" or "Did anyone mention my team?" Open the moment each answer points to.
4. Reply in the thread before the deadline: agree, object with a reason, or ask.

Catching up from a summary still loses tone of voice and people's reactions, the side conversations around the call, anything typed in the meeting chat (an audio recording holds only speech), and the chance to change a decision before it's made. Keep one-on-ones and contested decisions live.

Meetlens is a Chrome extension that lets you record a browser meeting in Google Meet, Zoom Web, Microsoft Teams Web or Webex without a bot joining the call. It captures the tab's audio (plus your microphone, if you allow it) and produces a transcript in 99+ languages with speaker labels, an AI report and tasks with owners and due dates. In General Meeting, the default report format, the Brief and Decisions cover step 1 and the Tasks block covers step 2. Whoever has the meeting in Meetlens can run step 3 in the AI chat over transcripts: add the meeting with Add context and ask. Answers link to the moments in the recording and often quote the exact words; check each one against the linked moment. Send the report to whoever skipped the call: paid plans export it as PDF, Markdown or TXT, and the Business plan adds a shared meeting library.

Meetlens records audio only, not video, the screen or the Zoom and Teams desktop apps, so it doesn't replace a recorded video update; import one as an MP4 file to get its transcript and report. No bot joins, so the platform shows no notice from Meetlens: announce the recording yourself, because some states require everyone's consent. California's Penal Code § 632, for example, bars recording a confidential communication without the consent of all parties.

What if the whole company needs the update, or someone simply missed the meeting?

Asynchronous all-hands and missed meetings

A company-wide update can run as an asynchronous all-hands: one live session, a recording for everyone else, and questions collected in writing before and after, answered in the same document. Attendance becomes optional, so nobody has to join at midnight to hear the news.

When one person simply missed a meeting, send them a short note with the decisions that affect them, their tasks and the recording: