Back to blog
Standups & Status

Standup across Time Zones

5 min read
standup across time zonesasync standupdistributed teamstime zonesoverlap hours

The short version

  • When a team spans four time zones, a single live standup always lands at a bad hour for someone, so make the standup written by default.
  • Keep any live time only for the small overlap window, and use it for decisions, not readouts.
  • The real problem across time zones is not the meeting. It is the waiting: a question asked while its owner sleeps stalls the work for hours.
  • StandIn answers questions from what you wrote down while you are off, in your words, and never guesses, so the answer does not have to wait for morning.

To run a standup across four time zones, make it written by default and drop the daily live call, because any single meeting time will land in someone's evening or early morning. Reserve live time for the short window when hours overlap, and spend that window on decisions, not on reading status out loud.

But the standup format is the small part of this. When your team is spread across the clock, the thing that actually slows you down is not the meeting slot. It is the waiting: a question asked in Amsterdam at 9 a.m. that only Tokyo can answer, sitting untouched until Tokyo wakes up. Fix the meeting and that waiting is still there.

Make the standup written by default

Across four time zones, a live daily standup is a tax you charge the same people every day. Someone always dials in tired or stays late. Written by default removes that. Each person posts a short note on their own schedule, and everyone reads it when their day starts.

Keep the note tight so it survives, using a three-prompt written standup format: what moved, what is blocked, and what the next person needs to know. That third line matters most across time zones, because the "next person" is often literally the next zone waking up. For the shape of that handoff, see the end-of-day handoff template.

Use the overlap window for decisions only

Four zones usually leaves a thin band where at least some people are awake together. That overlap is your most expensive hour, so do not waste it on a readout that writing already handled. Spend it on the things that genuinely need people at once.

  • Decisions that are stuck: choices where a thread has gone in circles and needs live resolution.
  • Ambiguity that needs a human: the "wait, what do we actually mean by this" moments that writing keeps missing.
  • Nothing that a note could carry: if it can be written, write it and give the overlap back.

Protecting that window is its own skill; the overlap hours post goes deeper, and working across time zones on an engineering team covers the wider setup.

The real problem is the waiting

Here is what a perfect async standup still cannot solve. You can write flawless notes and still lose hours, because the notes answer once and then go quiet. The instant someone needs a detail the note did not include, they are back to waiting for its author to wake up.

Sarah logs off in Tokyo after posting a clean update. Alex starts his day in Amsterdam, reads it, and hits a question it did not cover. He types it out, and it sits. Eight hours later Sarah answers, and only then does the work move. Nobody did anything wrong. The format did its job. The waiting is baked into the time-zone gap itself, and more or better standups do not touch it. This is the same drag the timezone tax post puts a name to.

Keep answers flowing while people sleep

The only real fix for the waiting is to make answers available when the person who has them is off. Not a guess, not a summary someone might have to walk back, but the actual answer that person already recorded, handed over on demand.

That is what StandIn does, and why it is not a standup tool at all. It answers questions on your behalf from what you wrote down, your brief and the team's record. Alex asks where the migration stands and gets Sarah's answer, in her words, while she sleeps, instead of losing the day to the gap. When the record does not hold the answer, StandIn says so plainly rather than inventing one, so nobody acts on a made-up detail across a time zone where they cannot double-check. See why bots fail for why that honesty is the point, and the daily standup question for whether you need the meeting at all.

Common Questions

How do you run standup across multiple time zones?

Make it written by default so nobody takes a bad-hour call, and reserve any live time for the overlap window and for decisions only. Keep each note short enough to finish and read fast.

What is the best time for a standup across four time zones?

Usually none, which is the point. Any single time punishes the same people daily. Use async for the status and save the overlap hour for choices that need everyone present.

Does StandIn schedule a standup across time zones?

No. StandIn does not schedule or run standups. It answers questions from what you already wrote down while you are off, so answers arrive across the gap, and when the record has no answer, it says so instead of guessing.

Running a standup across four time zones is mostly about admitting the meeting was never the hard part. The hard part is that a question asked while its owner sleeps used to cost you a full day. Make the standup written, guard the overlap for real decisions, and let your work keep answering when you are off, from your brief, in your words, without guessing. See how teams work across time zones.

Get async handoff insights in your inbox

One email per week. No spam. Unsubscribe anytime.

Ready to retire your daily standup?

Distributed teams use StandIn to start every shift with full context, no standup required. Engineers publish a 60-second brief. The next shift wakes up knowing exactly what to work on.

You might also like