An async standup is a written daily check-in posted to a shared channel instead of a live call. Each person answers three prompts: yesterday, today and blockers. People post by a deadline set in their own morning, so nobody has to be online together, yet the whole team can read the same thread and respond.
The daily call is the default ritual for a reason: it forces alignment and surfaces problems. But on a team spread across time zones, that call always lands badly for someone. The async version keeps the value and drops the cost, if you run it deliberately rather than just telling people to "post an update".
What goes in an async standup?
Keep the format to three lines. Anything more and people stop reading; anything less and the blocker disappears.
- Yesterday. What you finished or genuinely moved forward. One or two bullets, not a diary.
- Today. What you plan to do next. This is a commitment, not a wish list.
- Blockers. Anything stopping you, or anyone you are waiting on. This line matters most; it is the only part that usually needs a human reply.
Pin the template at the top of the channel so the structure is identical every day. Consistent shape makes the thread scannable: a reader can skip every "today" line and read only "blockers" in ten seconds.
Where should the standup live?
Use one dedicated channel, not a thread that gets buried under chat. A single channel gives you a clean, chronological record: anyone joining mid-week can scroll back and see exactly what happened. Keep replies and discussion in threads off each post so the main column stays a readable list of updates.
When is the posting deadline?
This is where async standups quietly fail. A single global deadline, say 9:00 AM UTC, lands at breakfast for London, before dawn for New York and after work for Sydney. Half the team posts stale updates or skips entirely. This is the norm rather than the exception: in Buffer's 2023 State of Remote Work report, 74% of respondents said their company operates across multiple time zones, so a single fixed deadline almost always lands badly for someone.
Set the deadline relative to each person's morning instead. The simplest rule: post within the first hour of your own working day. To make that workable you need to see, at a glance, where each teammate is in their day. That is exactly what Atlas shows: pin each person, see their current local time, and watch the shaded working hours so you know whose morning is starting right now.
Everyone uses the same three-line template, but each person's cut-off is their own local morning. If you still need a short live overlap for blockers, find the one window everyone is awake first; here is how to run a daily standup across time zones.
How do you surface blockers fast?
A blocker that waits a full day for a reply costs you a day. The fix is ownership, not hope.
- Make blockers loud. A heading, a flag emoji, or a separate line that is impossible to miss while scanning.
- Name a triager. One person whose job, once their day begins, is to read every post and respond to each blocker within the hour, either resolving it in a reply or escalating to a quick live chat.
- Tag the unblocker. If you are waiting on someone, @-mention them in your blocker line so it lands in their notifications, not just the channel.
Most days no live conversation is needed. On the days it is, the blocker line is the trigger, and you only pull in the two people who actually need to talk.
How do you keep accountability without a call?
People worry that without the social pressure of a call, updates dry up. In practice the written record is a stronger accountability tool, because it is permanent and visible.
- The thread is the proof. A skipped day is obvious to everyone, which is far more motivating than a manager noticing privately.
- Today vs yesterday is self-correcting. If yesterday's plan and yesterday's results keep diverging, it shows in the log without anyone having to chase.
- Reactions count as acknowledgement. A simple emoji on each update tells the poster their note was read, which keeps people writing them.
Async standup vs the live call
Neither is strictly better; they trade different things. A quick comparison:
| Async (written) | Live call | |
|---|---|---|
| Time-zone fairness | High — post in your own morning | Low — bad hour for someone |
| Written record | Permanent, searchable | None unless noted |
| Speed of blocker reply | Within the hour, with a triager | Immediate, but only once a day |
| Social connection | Lower | Higher |
| Focus interruption | None — read when ready | Fixed slot in everyone's day |
A common middle path: run the written standup daily and keep one short live call a week, scheduled in the one window where everyone overlaps, for the human side that text cannot carry.
Putting it together
A good async standup is three lines, one channel, a deadline in each person's local morning, and one named person watching for blockers. Get those four right and you keep every benefit of the daily call without asking anyone to join it at 6:00 AM. To pick the deadline and any weekly overlap with confidence, see where everyone actually is in their day with Atlas.
Frequently asked
What is an async standup?
What three questions should an async standup answer?
When should the async standup deadline be?
How do you surface blockers quickly without a call?
Stop doing timezone math
Atlas finds the time everyone's awake and adds it to your calendar in one tap.
One-time purchase, yours forever.