There is no standard 8-to-6 overlap. Someone joins early or late.
Riyadh and San Francisco sit on opposite ends of the clock — a 10-hour gap leaves no common business hours to work with. Lean on recorded updates, shared docs, and clear handoffs so the 10-hour gap doesn't stall progress between meetings. One seasonal catch: San Francisco springs forward and falls back, but Riyadh doesn't, so the gap changes by an hour for several months of the year.
| Local time | 12am | 1am | 2am | 3am | 4am | 5am | 6am | 7am | 8am | 9am | 10am | 11am | 12pm | 1pm | 2pm | 3pm | 4pm | 5pm | 6pm | 7pm | 8pm | 9pm | 10pm | 11pm |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Riyadh Asia/Riyadh | ||||||||||||||||||||||||
San Francisco America/Los Angeles |
London to New York is five hours apart, except for the five weeks a year when it isn't. Exact overlap windows for every US zone, the 2026 DST mismatch dates, and where to put the recurring sync. -
Most distributed teams either keep the daily standup and exclude someone, or kill it and lose the rhythm. There is a better third option. Here is how to redesign the daily standup so it works across nine time zones. -
The Philippines sits 12 to 16 hours ahead of the US and never changes its clocks. Exact overlap windows for every US coast, the tomorrow problem, and a rotation rule that works for product and BPO teams. -