How to run a daily standup when your team is in 4 time zones

The daily standup was built for a room. Everyone stands, speaks for a minute, and sits down. Move that team across four time zones and the room disappears: by the time Sydney finishes the day, San Francisco has barely started it. You can keep dragging people into calls at 6am or 10pm, or you can change the format to fit the geography.

Why a live daily standup breaks across four zones

With two close zones, a shared hour is easy. With four spread zones, the working days barely touch. A team across, say, San Francisco, London, Bengaluru and Sydney might share only a sliver of overlap, and often none at all. Forcing a live standup into that gap means someone is always doing it before breakfast or after dinner. That cost compounds every single day, and the people who pay it are usually the most distant ones, who then quietly drift to the edge of the team.

The deeper problem is that a daily live meeting treats synchronous time as free. Across four zones it is the scarcest resource you have. Spend it on the wrong thing and you have nothing left for the conversations that genuinely need voices.

The fix: an async written standup

Replace the meeting with a written update that each person posts in a shared channel at the start of their own working day. No one waits for anyone. The whole team reads a complete set of updates when they come online, in their own morning, wherever that falls. The appetite for this is already there: in Buffer's 2023 State of Remote Work, 37% of remote workers said they would prefer to work in a mostly or fully asynchronous way.

Keep every update to three short lines:

1. Did — what you finished since your last update.
2. Doing — what you are picking up next.
3. Blockers — what is in your way, and who can clear it.

The blocker line is the one that earns its keep. Tag the specific person who can unblock you and link the ticket. Because they read it in their own morning, they can act on it before you are even awake, so a blocker that used to cost a full day of waiting for the next call now clears overnight.

Keep one short live sync, but earn it

Async does not mean never talking. It means talking on purpose. Find the hour when all four working days overlap, even partially, and book one short live sync there two or three times a week. Protect that window for the things text handles badly: decisions with trade-offs, debugging something together, planning, and the plain human contact that keeps a distributed team feeling like a team.

If you are unsure where that overlap sits, map each person's working hours against a fair window before you pick a slot. We cover the method in finding your team's overlap window, and the same principle drives Atlas: pin each person on the map, and it shows the moment everyone is actually awake.

Async standup vs live standup, at a glance

The two are not rivals. The written standup carries the daily status; the occasional live sync carries the conversations. Used together they cover what a single daily meeting never could across four zones.

Making the habit stick

A few small rules keep an async standup from decaying:

• One channel, one thread per day. Everything in one place, easy to scan, easy to search later.
• A soft deadline, not a hard one. "Within two hours of starting" respects every zone; "by 9am" punishes most of them.
• Read before you post. Catching up on others' updates first turns a list of monologues into a conversation.
• Let people skip a quiet day. "Nothing new, still on the migration" is a valid update. Forced filler trains people to ignore the channel.

Done well, the async standup is not a downgrade from the live one. It is faster to read than a meeting is to attend, it leaves a record you can search, and it treats every time zone as equal. The half-hour everyone used to lose to a badly timed call goes back into the actual work. For the deeper case on the format, see our guide to async standups.