What is async communication? Examples, benefits and how to do it well
By Harsh Rawat · · 7 min read
Async communication is how most good remote work gets done. Instead of pulling everyone into a meeting, you send a message, a document or a short video, and people respond when they’re ready. This guide explains what it means, when it works better than a meeting, and how to do it well.

Quick answer: async (asynchronous) communication is any message that doesn’t need a reply right away. You send it when it suits you, and the other person reads, watches and answers when it suits them. Email, recorded video updates, shared documents and comments are async. Meetings, phone calls and live chats are sync (synchronous): everyone has to be there at the same time.
Async vs sync communication
| Async | Sync | |
|---|---|---|
| Examples | Email, recorded videos, documents, comments, project boards | Meetings, video calls, phone calls, live chat |
| When people respond | When it suits them, often within hours | Right away |
| Best for | Updates, reviews, feedback, decisions that can wait a day | Urgent problems, brainstorming, sensitive conversations |
| Downside | Slower back-and-forth; needs clear writing | Interrupts focus; hard across time zones |
| Leaves a record | Yes, by default | Only if someone takes notes or records it |
Examples of async communication at work
- A video walkthrough instead of a meeting. Record 2 minutes showing a design, a bug or a finished feature, and send the link.
- A written stand-up. Each person posts what they did, what’s next and what’s blocking them, instead of a daily call.
- Comments on a document. People review a proposal in the doc itself, on their own time.
- Code review. Developers leave comments on a pull request instead of reviewing it together live.
- A client update. A short recording of this week’s progress, which the client watches whenever they open their inbox.
Why teams switch to async
- Fewer interruptions. People get long stretches of focused work instead of a day broken up by calls.
- Time zones stop mattering. Nobody has to join a meeting at 11 pm to give a five-minute update.
- Better thinking. People answer after they’ve thought it through, not on the spot.
- A record by default. Decisions and explanations stay findable, so new teammates can catch up on their own.
GitLab, a company that works fully remotely, makes async its default and documents how in its public handbook on asynchronous communication. It’s one of the most thorough guides on the subject.
When a meeting is still better
Async is a default, not a rule. Switch to a live call when:
- Something is urgent, or broken right now.
- A thread has gone back and forth three times without getting anywhere.
- You’re brainstorming, or making a big decision with many opinions.
- The conversation is sensitive, like feedback on someone’s work or a difficult client issue.
- You’re meeting someone for the first time and building trust.
How freelancers use async communication
I freelanced for five years, and clients wanted small updates all the time: a change I’d made, a bug I’d fixed, where the project stood today. The choice was usually between booking a call for a two-minute update or writing a message so long it was nearly an article.
A short screen recording fixed both problems. The client sees exactly what changed, hears why, and watches it when it suits them. I keep my focus, and there’s a record of what we agreed. These are the updates I’d send async:
- Daily or weekly progress: what’s done, what’s next, what I need from them.
- Design and website reviews: walk through the page and explain each decision.
- Handover: how to edit the site, where things live, what to do if something breaks.
- Bug reports: show the problem happening instead of describing it.
How to do async communication well
- Give full context. Write or record as if the reader knows nothing about the last conversation. Link the doc, the design or the ticket.
- Lead with the ask. Start with what you need: a decision, feedback, or nothing (just an update).
- Set a reply-by time. “Can you reply by Thursday?” stops async from turning into waiting forever.
- Keep videos short. Two to five minutes, one topic each. If it needs twenty minutes, it might need a meeting.
- Show, don’t describe. A screen recording beats three paragraphs explaining where to click.
- Agree on response times. For example: messages within a working day, urgent things by phone.
A simple async stand-up
Post this at the same time each day, in writing or as a one-minute video:
- Done: what I finished since yesterday
- Next: what I’m working on today
- Blocked: anything I need from someone, and by when
Tools for async communication
- Writing: email, threaded chat in Slack or Teams, shared documents like Google Docs or Notion.
- Project tracking: boards and issue trackers like Trello, Linear or Jira, where status updates live next to the work.
- Video: screen recorders that give you a link to share, so you can show instead of write.
For video, I built Showthrough, a Chrome extension that records your screen, camera and voice and copies the link the moment you stop. There’s no limit on the number of videos or their length, and viewers can comment at the exact moment they’re asking about. If you’re comparing options, see the screen recorders we compare.
Questions people ask
What is async communication?
Async (asynchronous) communication is any message that doesn't need a reply right away. You send it when it suits you, and the other person reads, watches and answers when it suits them. Email, recorded videos, shared documents and comments are all async.
What is an example of async communication?
A 2-minute screen recording that walks a client through changes to their website, sent as a link instead of booking a call. Others are a written daily stand-up, comments on a shared document, or a code review left on a pull request.
What is the difference between sync and async communication?
Sync communication happens live, with everyone present at the same time, like meetings and phone calls. Async communication happens on each person's own schedule, like email, recorded videos and documents.
Is Slack async or sync?
It can be either. Slack works as async communication when people reply in threads on their own schedule, and as sync communication when everyone is expected to answer within minutes.
When should you not use async communication?
Use a live call for urgent problems, for anything that has gone back and forth without progress, for sensitive conversations, and for getting to know someone new.
How do you run an async stand-up?
Each person posts a short written or video update at the same time each day: what they did, what they're doing next, and anything blocking them. Others read it when they start work and reply only where something needs a decision.