Async standup: run a daily standup without the meeting

A live standup works well when everyone sits in the same room. It works less well when half the team is asleep, or in deep work, or on a different continent. An async standup keeps what the standup was for and drops the call.

This guide covers how to run one: the questions, the timing, time zones, what leaders should do with the answers, and how to handle blockers.

What an async standup is

An async standup is a daily update that people write when it suits them, instead of speaking at a set time. Everyone answers the same short questions. Everyone reads the answers when they are ready.

The goal has not changed. The team should know who is working on what, and what is in the way. Only the way of getting there is different.

The questions to ask

Keep the list short. Three questions are enough:

1. What did you do yesterday?
2. What will you do today?
3. Is anything blocking you?

Some tips for making them work:

• Ask per project. If people work on several things, a single answer turns into a vague paragraph. One short answer per project is easier to write and to read.
• Make blockers optional. A forced answer produces “no blockers” typed on autopilot. An optional box keeps the answers real.
• Link the first two. The plan someone wrote yesterday is the answer they owe today. Reading the two together tells you more than either alone.

You can add one more optional question: how sure are you that today’s plan gets done? Three answers are enough (on track, at risk, won’t make it), plus a place to say what would help.

When to post

Pick a rule that is easy to remember. A good one is: post your update at the start of your own workday.

That sounds obvious, but it fixes most problems:

• Nobody is asked to be online at an odd hour.
• The plan is written before the day fills up.
• Readers in other time zones find fresh updates when their own day begins.

Avoid a hard deadline for the whole team. A single “by 9:30 sharp” is just a meeting in disguise.

Time zones

Time zones are the reason many teams go async, and they cause two common problems.

The weekend problem. If you write on Friday and the next update is on Monday, a calendar-based reading says you missed two days. Do not do that. Compare an update to the previous update, not to yesterday’s date. Friday’s plan is answered on Monday.

The overlap problem. If your team shares only an hour or two, protect that hour for talking, not for status. The written update has already told people what they need to know. Use the call for the things that need a conversation.

What leaders do with the answers

An async standup only works if someone reads the answers. Here is what that means in practice.

• Read them once a day. Five minutes, at a regular time. Skim for blockers and risk first.
• Reply to blockers the same day. A blocker that sits for a day is a blocker the team learns to stop mentioning.
• Connect people. If one person is stuck and another wrote that they have room, say so. That small introduction is often the best use of a leader’s morning.
• Ask questions in the open. If something is unclear, reply under the update. Others learn from the answer.
• Do not turn answers into a score. The update is a conversation starter. If people feel graded, they will write what looks good instead of what is true.

Handling blockers

Blockers are the most valuable part of the update, and the easiest to lose.

Make it easy to write one. The box should be right there with the other answers, not a separate form.

Make it visible. A blocker that is buried in a long update gets missed. Pull blockers and “needs help” items into one place that leaders look at every morning.

Make it safe. People name blockers when the response is help, not blame. The first few replies set the tone for everything after.

And make it specific. “Waiting on design” is vague. “Need the final checkout mockup to finish the form” tells the reader exactly what would help.

Do you still need a meeting?

Sometimes, yes. A short call is still the right tool for a real discussion, a decision with trade-offs, or a conversation that is not going well in writing. The async standup does not replace those. It removes the meeting whose only purpose was to read out updates.

A simple test: if a meeting can be replaced by everyone reading the same page, it should be.

Where DailyPulse fits

You can run an async standup in a shared document or a chat thread, and many teams start there. The weak spot is usually the same: answers get lost, blockers get buried, and nobody can see the week at a glance.

DailyPulse is built for this routine. Each person posts a short check-in with a plan per project, an optional blocker, and an optional confidence. The Today board shows who is at risk or blocked and who has room to help. Each person also gets an AI insight on their own check-in, written for them and not for their manager.

DailyPulse is invite-only for now. If you would like to try it with your team, talk to us at hello@dailypulse.ai. If you have already been invited, open the app at app.dailypulse.ai.