How to Schedule Meetings Across Time Zones Without Making Anyone Suffer

Nearly every distributed organization makes the same scheduling mistakes. The most common is defaulting to the headquarters time zone — usually because the CEO is there, or because the company was founded there. This feels efficient in the moment: "We always meet at 9 AM Pacific." But this systematically punishes everyone outside that zone. Your London team attends 5 PM meetings. Your Singapore team logs in at 1-2 AM. This approach optimizes for one geography at the expense of everyone else.

The second pitfall is the "convenient for me" trap. Individual managers and project leads schedule meetings for their own time zones without considering the broader impact. Your engineering manager schedules daily standups at 9 AM Pacific because that's when they're most alert. Your product manager schedules retrospectives at 3 PM UTC because that fits their calendar. No single meeting is unreasonable, but the cumulative effect is chaos. Someone in Tokyo is attending four or five meetings between 10 PM and 2 AM every week, and no one has a shared view of the total burden.

The third pitfall is assuming there's a "perfect time" that works for everyone. When you have geographic spread greater than 8-10 hours, there literally isn't a time slot where everyone is in golden hours. Many organizations waste weeks searching for the impossible and end up demoralized. The search for perfection becomes an excuse for never standardizing the process at all.

A fourth mistake is rigid inflexibility. Some organizations attempt to solve timezone problems by saying "every meeting must rotate," but then they rotate so frequently that no one knows when to show up, or the rotation pattern is so chaotic that it creates constant calendar friction. A well-designed timezone strategy needs structure and predictability.

Begin by understanding exactly where your team is distributed. Don't estimate. Use actual timezone data from your HR or team management system. For each team or functional group, list the time zones represented and how many people are in each zone. You'll likely discover that your "globally distributed" company actually has clusters: maybe 60% in US/Europe, 25% in Asia, and 15% scattered elsewhere. Or perhaps you have two equally-sized clusters (US and Europe) and a smaller Asia contingent.

Next, calculate the timezone spread. If your earliest person is in San Francisco (UTC-8) and your latest is in Singapore (UTC+8), your spread is 16 hours. If your spread is more than 10-12 hours, there is no single time that works for everyone in golden hours. This is a critical realization because it changes your strategy from "find the perfect time" to "manage the distribution of pain fairly."

Finally, identify which meetings are actually truly global. You probably have some all-hands meetings that include everyone, some team meetings that include only a subset of geographies, and many small team meetings that are entirely contained within one timezone. Your strategy should be different for each category. You might tolerate higher sacrifice scores for rare all-hands meetings (quarterly is bearable; weekly is not) while keeping regular team meetings within reasonable hours.

An overlap window is a period where the majority of your team is in reasonable waking hours (ideally between 8 AM and 6 PM in their local time). Identify these windows explicitly. For a US-Europe split, there's usually a 2-3 hour window in the morning (Eastern time) that catches both coasts. For a US-Asia split, you might have a narrow window early morning Pacific, or there might not be any true overlap window at all.

Once you've identified overlap windows, you now know your constraints. If you have only a 2-hour overlap window and six meetings that must include everyone, that's impossible. You'll need to either: 1) split some meetings into regional cohorts and summarize later, 2) accept that one geography will have some out-of-hours meetings, or 3) reduce the number of global meetings. This constraint-based thinking is more useful than searching for the impossible perfect time.

For teams without any overlap window (truly extreme spreads like San Francisco to Tokyo), accept that synchronous global meetings will always have pain. Your strategy shifts to: schedule them rarely, keep them short, rotate the pain, and default to async. Maybe your all-hands is quarterly instead of monthly. Maybe your global sync is 30 minutes instead of 2 hours. Maybe sensitive discussions happen async with video recordings.

If you have geographic spread, rotation is not optional — it's how you ensure fairness. Design a rotation pattern that is predictable and minimizes total sacrifice. For a three-timezone organization with recurring meetings, you might use a three-week rotation: Week 1 is Pacific time (favors US West Coast), Week 2 is UTC (favors Europe), Week 3 is early morning Pacific (favors Asia). Everyone knows the pattern in advance. Everyone gets "their" convenient slot once every three weeks, and the pain is distributed.

The rotation pattern should be longer than people intuitively expect. A daily rotation (different time every single day) sounds fair but creates chaos and meeting fatigue. People can't remember when they're supposed to be on the call. A weekly rotation is more predictable. For non-recurring meetings, you can be more flexible, but recurring meetings absolutely need a standard, published rotation pattern.

Communicate the rotation clearly. Many organizations publish a "meeting matrix" that shows which meetings rotate on which schedule. This takes the guesswork and negotiation out of meeting planning. Instead of managers arguing about times, they check the matrix and propose three time slots. Everyone knows where to find the information.

A final note on rotation: some meetings don't need to be for everyone at the same time. A monthly all-hands can happen on the same day at two different times: 8 AM Pacific for the Americas and Europe, then the same meeting again at 5 PM Pacific for Asia and EMEA. This doubles the communication lift but eliminates the pain entirely for that meeting. Many organizations find this trade-off worthwhile for their most important communication events.

Beyond rotation, you need a way to evaluate trade-offs when meetings must be scheduled or when exceptions occur. This is where sacrifice scores become practical. A simple scoring system might be: Golden hours (10 AM-4 PM local) = 1 point. Early morning (7-10 AM) = 3 points. Late afternoon (4-7 PM) = 2 points. Evening (7-11 PM) = 5 points. Night (11 PM-7 AM) = 9 points. Duration and recurrence multipliers apply.

When someone proposes a meeting time, calculate the total sacrifice for all participants. If one proposed time scores 50 points and an alternative scores 95 points, you have concrete information that the first option is better. This framework transforms "I think this time is better" into "this time is provably less painful." Many organizations that implement sacrifice scoring discover they can have brief, data-driven conversations instead of lengthy negotiations.

Some modern scheduling tools now calculate this automatically. You propose a time, the tool shows you the sacrifice score for all participants, and you can instantly see if there's a better option. Even if you don't use a tool, a simple spreadsheet calculation (person × hour of day × multipliers) gives you the data you need.

Here's a radical thought: maybe the problem isn't finding the perfect meeting time. Maybe the problem is too many meetings. Many organizations that successfully manage distributed teams have discovered that the real solution is going async-first. This doesn't mean zero synchronous meetings, but it means asking "is this meeting necessary?" much more seriously than single-timezone companies do.

A status update meeting in a single timezone might be fine as a synchronous ritual. In a distributed company, that same meeting is expensive. Does it need to be synchronous? Could it be a written update that people read asynchronously and respond with questions in Slack? Could it be a Loom video that people watch at their convenience? Could async really replace this synchronous time?

Organizations that shift to async-first for 70-80% of their meetings report higher engagement, better meeting quality (fewer people half-attending from their commute), and dramatically higher team satisfaction in distributed settings. The timezone problem becomes smaller when you have fewer meetings to coordinate.

Document your timezone strategy clearly. Write it down. Share it. Make it part of your meeting culture. "We rotate our all-hands meetings," "We keep team standups within Pacific time," "We ask: is this synchronous, or can it be async?" These clear policies prevent constant re-negotiation.

Use tools that support your strategy. Calendar software that shows participants' local times helps prevent mistakes. Meeting schedulers that calculate overlap windows save time. Tools that calculate sacrifice scores make trade-offs visible. None of these are strictly necessary, but they make execution much easier.

Finally, measure and iterate. Quarterly, ask your team: "Which meetings feel hard to attend due to timezone? Which could go async?" Collect this feedback and adjust. Maybe you discover that your Asia team is consistently in pain at one particular meeting, and rotating it is worth the disruption it creates in other timezones. Or maybe you shift something to async and discover that people actually prefer it.