An async standup replaces the daily meeting with written or recorded updates that each person posts on their own schedule, usually before a fixed cut-off. Teammates read or watch them when convenient, raise blockers in the thread, and only meet live when something needs a real conversation. Done well, it gives back the daily 15 minutes, works across time zones, and leaves a searchable record. Done badly, it becomes a channel nobody reads.
This guide covers the format, the questions, text versus video, the norms that keep it alive, and how to tell whether it is working.
Why teams move the standup out of the calendar
A live standup has three hidden costs. It interrupts focus at the same moment for everyone. It forces a time that suits one time zone and penalizes the others. And it produces no record: the person who missed it has to ask around.
Need to show the blocker instead of describing it? A short screen recording can make async standups clearer when text alone is too vague. Record a quick demo
The Scrum Guide does not require a meeting format. It describes the Daily Scrum as a 15-minute event for inspecting progress toward the Sprint Goal and planning the next day, and says developers can “select whatever structure and techniques they want” as long as it stays focused on the goal and produces an actionable plan. An async standup is one of those structures. It keeps the purpose and drops the synchronized time slot.
Live vs text vs video standups
| Live meeting | Text update (bot or thread) | Short video update | |
|---|---|---|---|
| Time zones | One slot for everyone | Posts any time before a cut-off | Posts any time before a cut-off |
| Reading cost | 15+ minutes, whole team | Seconds to skim | 1–3 minutes per person, or skim the transcript |
| Nuance and tone | High | Low | High |
| Showing work | Screen share, live | Links and screenshots | Screen recording with narration |
| Record afterwards | None unless someone takes notes | Searchable thread | Searchable transcript and link |
| Best for | Hard problems, team bonding | Routine status, large teams | Demos, design decisions, complex blockers |
Most teams that stick with async use a mix: a text check-in by default, and a short video when the update is easier to show than to describe.
The format: cadence, cut-off and channel
- Cadence. Daily works for teams shipping together on one goal. Teams with longer-running work often do better with three updates a week, or a daily text line plus a weekly video recap.
- Cut-off. Pick a deadline in the earliest relevant time zone, such as 10:00 for the team’s “morning.” Updates posted after it lose most of their value, because blockers surface too late.
- One place. A dedicated channel or thread per day. Never scatter updates across DMs.
- An owner. Someone, often the lead or a rotating facilitator, reads every update the same day and follows up on blockers. Without an owner, async standups decay within weeks.
Template questions that produce useful updates
The classic three questions still work, phrased toward outcomes rather than activity:
- What moved forward since my last update? Link the pull request, document, or ticket.
- What am I focusing on next? One or two items, not a to-do list.
- What is blocking me or at risk? Name the person or decision needed.
Optional prompts worth rotating in weekly: “What did you learn that others should know?” and “What would you like feedback on?” Keep the core questions identical every day. Predictable structure is what makes updates skimmable.
Text bots: when they are enough
Standup bots post the questions to each person at a set time and collect the answers into a channel. Geekbot, for example, runs standups in Slack and Microsoft Teams, is free for teams of up to ten users, and charges $2.50 per participant per month on its Basic plan. Slack itself can ask the questions with Workflow Builder, its no-code automation tool.
Text is the right default when updates are routine and the team is large. Its weakness is nuance: “auth refactor is tricky” tells you almost nothing about whether to worry.
Video updates: when showing beats telling
A one- to three-minute screen recording is better when the update is visual or the blocker is hard to describe: a UI change, a failing test, a design trade-off, a customer call you want to summarize. Slack’s built-in clips let you record audio, video, or screen into a channel. A dedicated recorder adds a transcript, search, and a stable link you can reference later.
Guidelines for video updates:
- Start with the headline: “Billing page is ready for review; one open question about refunds.”
- Show, don’t tour. Open only the screen that proves the point.
- Keep it under three minutes; split anything longer.
- Post the link with one line of text so people can decide whether to watch.
How Chairkick fits an async standup
Chairkick records your screen, camera, and microphone in the browser with nothing to install, and gives you a share link when you stop. For standup-style updates, a few features do the heavy lifting:
- A written recap from each video. Chairkick can turn a recording into a Recap: a short summary with what was covered, numbers mentioned, action items, and next steps. Every line is editable. Copy it as text into Slack or email, or share the page, so teammates who will not watch still get the update.
- Transcripts, chapters and action items on every processed recording, so viewers can skim or jump to the part they need.
- A shared workspace library. Workspace admins can set new recordings to be shared with the workspace automatically, and restrict links so only signed-in workspace members can open them. Viewer seats are free.
- Folders. Keep a workspace folder per team or project so a week of updates lives in one place.
- Comments and reactions on each recording for quick replies without a meeting.
New workspaces get a 14-day Pro trial without a card; Pro then costs $9 per recorder per month. See pricing, or try the browser recorder with your next update.
Norms that keep async standups alive
- Post before the cut-off, every time. Consistency matters more than eloquence.
- Reply to blockers within the same working day. If nobody responds, people stop flagging them.
- Escalate to live when a thread passes three back-and-forths. Async is for updates, not debates.
- Keep one live touchpoint. A weekly call or demo protects relationships that pure async erodes.
- Celebrate in the thread. Visible reactions are what make people feel read.
Pitfalls to avoid
- Status theater. Long lists of tasks nobody needs. Ask for outcomes and blockers only.
- Write-only channels. If the lead is not reading, the team will notice and stop writing.
- Video for everything. Five three-minute videos a day is 15 minutes of viewing. That is the meeting again. Default to text and use video when it saves explanation.
- No decision log. When a thread produces a decision, write it down where the team keeps decisions, not only in the standup channel.
How to tell whether it is working
After two to four weeks, check three signals: do blockers get resolved faster than before, are people posting by the cut-off, and did anyone ask to bring the meeting back? If updates are late or unread, shorten the template and recommit to the owner role before abandoning the format.
For more on recording clear explanations, see how to make a tutorial video and Loom vs Scribe: video or written guide.
FAQ
What is an async standup? A daily or regular status check where each teammate posts a written or recorded update on their own schedule instead of joining a live meeting.
How long should an async standup update be? A few lines of text, or a video under three minutes. If it needs more, it is probably a separate conversation.
Are async standups compatible with Scrum? Yes. The Scrum Guide lets developers choose the Daily Scrum’s structure as long as it inspects progress toward the Sprint Goal and produces a plan.
Should standups be text or video? Text by default; video when the update is visual or a blocker is hard to explain in writing.
Do we still need meetings? Keep at least one live touchpoint per week for discussion, planning, and team connection.
Sources
Checked October 4, 2026: The 2020 Scrum Guide (Daily Scrum), Geekbot pricing, and Slack’s announcement of clips, huddles and Workflow Builder updates.