Running Standups Across Timezones: 3 Proven Approaches for Distributed Teams
The daily standup works great in an office. Fifteen minutes, everyone in a room or on one call, and you walk away knowing what your teammates are doing. It also works fine when the whole team shares a timezone.
Then your backend engineer is in Bangalore, your designer is in Berlin, your PM is in New York, and your frontend devs are split between São Paulo and San Francisco. Now that 15-minute call is somebody's 6am or somebody's 9pm, every day. Here is what teams actually do instead.
Why traditional standups break down
The spread between US Pacific and India Standard Time is 13.5 hours. There is no slot inside that window that lands during reasonable working hours for everyone. You can't schedule your way out of it.
Say you pick 10am Eastern. That's 7am Pacific, which is early but survivable. It's 4pm in Berlin, which is fine. And it's 8:30pm in Bangalore, which means your engineer is choosing between standup and dinner with their family. Every single day. Flip it and pick 10am in Bangalore, and now it's midnight in San Francisco.
The format assumes everyone is awake at the same time. Once that stops being true, you have three real choices: rotate the inconvenience, drop the live meeting entirely, or split the difference.
Option 1: Rotating standup times
Move the meeting around on a schedule so the same people aren't always the ones getting up early or staying up late. One common rotation:
- Week 1: 9am ET, which catches the Americas and Europe
- Week 2: 9am CET, which catches Europe and Asia
- Week 3: 9am IST, which catches Asia and the Americas in the early morning
- Then repeat
The appeal is fairness. Everyone takes a turn at the awkward hour instead of one timezone eating it forever, and you keep some real-time face time on the calendar. It holds up for smaller teams, roughly 5 to 8 people.
The downside is that nobody remembers what week it is. "Wait, when is standup this week?" becomes a recurring Slack message. Someone is still up early or staying late on any given week, and the whole thing falls apart once you have more than three or four timezone clusters to juggle.
Rotating works best for teams with two or three clusters that genuinely want the live interaction and can live with the occasional bad hour.
Option 2: Fully async standups
Drop the live meeting and replace it with a written post. Everyone writes their update in a dedicated Slack channel during their own morning, whenever that morning happens to be.
The questions are the same ones a live standup asks:
- What did I get done yesterday?
- What am I working on today?
- Is anything blocking me?
Plenty of teams add a line for things the rest of the team should know (out tomorrow, a PR that needs eyes) and sometimes a quick emoji to signal how the week is going.
Getting it to actually work takes a few habits. Create one channel, #standup or #daily-update, and keep side conversations out of the main thread. Ask people to post within the first hour of their workday, which keeps updates trickling in across the whole global day instead of bunching up. Give everyone the same template, because a consistent format you can skim beats a beautifully written paragraph that's laid out differently every time. And make reading the channel part of the routine, not optional. A post nobody reads is wasted effort. A thumbs-up reaction is enough to signal "I saw this." When someone flags a blocker, don't let it sit until tomorrow's posts. Jump into a thread or DM right then.
What you get: no scheduling fight, a searchable written record you can point back to weeks later, and updates that respect everyone's hours equally because nobody has to be awake for anyone else. What you give up: the loose, in-the-moment conversation a live call produces. It's also easy to coast on autopilot and write the same three lines without really engaging, and a blocker posted at the wrong hour might wait longer for a reply than it would in a live meeting.
This is the right call for teams across four or more timezones, teams bigger than eight people, or honestly anyone who'd rather sleep than wake up for a ritual.
Option 3: The hybrid approach
This is where most teams that have done distributed work for a while end up. Daily async updates, plus one live call a week.
Monday through Thursday, people post written updates in Slack during their own mornings. Then on Friday, or whatever day fits, you get on a video call during the hours when enough of the team overlaps. That call is your standing slot for demos, planning, and the casual conversation that text never quite captures.
The weekly call isn't a standup, and you shouldn't run it like one. Use it for quick demos of what shipped that week, for hashing out the blockers that async couldn't untangle, for the five minutes of small talk at the start that keeps people feeling like a team, and for getting on the same page about next week.
The reason this holds together: the daily posts cover the part of a standup that's about sharing information, and the weekly call covers the part that's about people knowing each other. Those two jobs have completely different timezone requirements, and a single daily meeting can't serve both well. If your team is spread wide, rotate the weekly call's time too, but do it monthly. Rotating it weekly just brings back the confusion you were trying to avoid.
Making times clear
Whatever you pick, one rule doesn't change: when you mention a time, leave no room for guessing. "Friday sync at 10am" guarantees the exact confusion you're trying to kill.
Write the timezone every time. "Friday sync at 10am ET / 7am PT / 4pm CET / 8:30pm IST" takes two extra seconds and saves a round of "wait, my 10am or yours?"
Or let software do it. In Slack, Timely converts any time you mention so each person reads it in their own timezone. You type "sync at 10am ET," and your teammate in Berlin sees that it's 4:00:00 PM Central European Time, without either of you doing the math.
A template to get started
Moving from live standups to async? Drop this in your #standup channel and tell people to copy it:
Update — [Date]
Done: Shipped the onboarding flow redesign, reviewed 2 PRs
Today: Starting API integration for the new payments provider
Blockers: Waiting on design approval for the settings page
FYI: Out Thursday afternoon for a dentist appointment
Keep it short. Three to five lines is plenty. If it's taking more than two minutes to write, you're overthinking it.
So which one
There's no single right answer here, and anyone who tells you there is hasn't run a team across eight timezones. There is one reliable wrong answer, though: assuming a meeting format built for one room will work unchanged for a team scattered across half the planet.
Match the approach to your team's size, spread, and how it likes to work. If you're not sure, start async. Adding a weekly call later is easy. Killing a daily meeting after it's calcified into habit is a fight.
And include the timezone. Always.
For the broader framework behind async-first work, read Async-First Communication for Remote Teams. To understand the full cost of timezone confusion before it compounds, see The Hidden Cost of Timezone Ambiguity.
Eliminate Timezone Confusion From Your Standups
Timely converts every time reference in Slack to each person's local timezone automatically — so "sync at 10am ET" is always clear, no matter where your team is.