How to Run Meetings Across Time Zones

Why time zones make meetings hard

A meeting only works when everyone can actually attend at a reasonable hour. Across two or three time zones that's manageable; across a global team it quickly becomes a zero-sum problem, where any time that suits one region pushes another to the edge of their day. Handled badly, the same people always take the awkward calls — and resentment and burnout follow.

Find the overlap window first

Before picking a time, map everyone's working hours in a single reference zone and look for where they intersect. That shared band — the overlap window — is the only humane place to put a synchronous meeting. The wider your team is spread, the narrower it gets, which is exactly why distributed teams should protect it for the conversations that genuinely need to be live.

• Agree on one reference time zone (UTC is the common neutral choice) so no one mis-converts.
• Use a scheduler that shows the proposed time in each attendee's local clock.
• Treat the overlap window as scarce — don't fill it with status updates that could be written.

Coordinating across U.S. time zones

Even a U.S.-only team isn't on one clock. The continental United States spans four zones — Eastern, Central, Mountain, and Pacific — so a 9 a.m. start on the East Coast is 6 a.m. on the West Coast, before you add Alaska and Hawaii. If you need a quick reference for which states sit in which zone when scheduling, this map of U.S. time zones lays out the boundaries clearly. Aim for late morning Pacific / early afternoon Eastern to keep a coast-to-coast call inside everyone's normal hours.

When there's no overlap: rotate and record

For teams spanning, say, San Francisco and Singapore, there may be no comfortable shared hour at all. Fairness then means sharing the inconvenience rather than eliminating it:

• Rotate meeting times so the same region isn't always taking the early-morning or late-night slot.
• Record every session and post notes, so anyone who can't attend live isn't penalized.
• Keep a written decision log so the outcome doesn't live only in someone's memory of a call.

Default to async for everything that can be

The most reliable fix for time-zone pain is to need fewer synchronous meetings in the first place. Status updates, FYIs, and most decisions work better as written threads people pick up during their own day. Our guide on async communication vs meetings covers when to go async and when a live meeting still earns its place.

Run an async standup

The classic example is the daily standup. Instead of forcing a synchronized call, each person posts a short written update to a shared channel at the start of their own workday. It removes the time-zone problem completely, leaves a searchable trail, and usually costs less than a live call — see the standup cost calculator to compare.

Quick reference: common overlap by region pair

Region pair	Approx. gap	Best shared window
US East ↔ US West	3 hours	Late morning Pacific
US East ↔ London	5 hours	Morning Eastern / afternoon London
London ↔ India	4.5–5.5 hours	Early afternoon London
US West ↔ Central Europe	8–9 hours	Very early Pacific / late afternoon CET
US West ↔ Singapore	15–16 hours	Rotate; lean async

For broader remote-team tactics, see our remote meeting guide and inclusive meetings guide.