How to Schedule Meetings Across Time Zones

Most cross-timezone scheduling is not a scheduling problem; it is a politeness problem. Someone picks a time that suits headquarters, sends the invite, and assumes the remote colleagues on the other side of the world will manage. That approach quietly builds resentment and burnout on exactly the teams that most need trust. This guide reframes scheduling as an engineering task: draw everyone's working hours on a grid, find the overlap, and rotate the edge-of-day burden instead of dumping it on the same people. By the end you will have a repeatable method, the math behind the worst-case gaps, and the daylight-saving trap that catches even careful teams.

What 6am and 10pm calls actually do to you

It is tempting to call an early or late meeting "fine" because one meeting is only an hour. The evidence says otherwise. Scheduling sources including City Clock, Kumospace, Cash Nomads and eume converge on the warning that calls scheduled at 6 a.m. or 10 p.m. land on the edges of a normal waking day, disrupting sleep and circadian rhythm. A single 6 a.m. call means waking before dawn, skipping a normal breakfast, and working through a morning you never actually arrived at. A regular 10 p.m. call means eating dinner with one eye on the laptop and going to bed wired.

There is also a fairness dimension that is rarely spoken aloud: the HQ team treats 10 a.m. as a respectful time, while the same meeting is 10 p.m. for the remote team. The people setting the clock never feel the cost. Over months, this produces exactly the burnout pattern researchers flag: remote workers on the wrong side of the schedule quietly disengage, and the company mistakes it for low motivation. The fix is structural, not motivational, and it starts by treating no-ones's 6 a.m. as acceptable unless the burden is shared.

The US East to India 9.5-hour gap

Some pairs of cities have almost no good window, and it helps to know which ones you are dealing with. Analysis from Globalmetrics, Wisemonk and WorldClock.lol highlights the classic US East Coast to India gap of about 9.5 hours. Translate it: when it is a comfortable mid-morning in New York, it is late evening in India. When it is a normal working morning in India, it is the middle of the night in New York.

This is the "second shift" problem. The Indian team never attends a US-timezone meeting during their own normal hours; they attend after their workday ends. The failure mode, documented in a widely circulated engineering post-mortem, is a senior remote engineer who finally left because every meeting was scheduled in headquarters time. The lesson is not that the US-India pairing is impossible. It is that it has no win-win window, so the only fair move is to accept that one side will take an awkward slot, and make sure the awkward slot rotates between the regions rather than always landing on India. For a live view of this exact grid, the Cross-Timezone Meeting Finder pre-loads a San Francisco, London and Sydney example that makes the no-overlap problem obvious at a glance.

The four-step overlap grid

Here is the repeatable method. It takes ten minutes and removes the guesswork from future scheduling.

1. List the people and their cities. For each person, write the city and its time zone, not a raw offset, because offsets change with daylight saving.
2. Draw each person's acceptable band. Use a reasonable default such as 8 a.m. to 6 p.m. local, and let night owls or early birds adjust their own band. The band is their human boundary, not a suggestion.
3. Find the intersection. On a 24-hour grid, shade the hours that fall inside everyone's band. Where the shaded regions overlap is your candidate window.
4. Pick the center of the overlap. Choose a time that sits in the middle of the overlap for everyone, not the edge. A window that is 8 a.m. for one person and 5 p.m. for another is worse than one that lands at 10 a.m. and 2 p.m.

When the overlap is one hour or less, that is information, not a problem to bulldoze through. It tells you that this meeting should be short, asynchronous, or scheduled with rotation. The grid makes the invisible visible: instead of arguing about whether a time is "reasonable," you look at the shaded overlap and decide together. If you track how often you and your colleagues land in after-hours meetings, our after-hours meeting load report helps you gather the data before you raise it with your manager.

Rotate the burden, don't dump it on one person

No global team has a perfect window all year. Most of the time there is a small overlap, and some meetings will require one region to take an early slot and another to take a late slot. The fair system is explicit rotation. This week, the US side takes the 7 a.m. call; next week, the Asia side takes the 8 p.m. call; the week after, the window shifts so Europe carries the awkward time.

Rotation works for three reasons. It spreads the cost so no single person's sleep pays for the whole team. It builds empathy: the people who choose the times experience what the awkward slot actually feels like. And it removes the quiet assumption that remote colleagues exist on HQ time. When you set up a recurring meeting, say the rotation out loud in the invite note so everyone can see the schedule. If protecting the off-work side of this boundary is the harder part, the OOO boundary planner helps you mark the blocks that should never receive a cross-timezone call, and gives you a copy-ready note to align expectations with your team.

The daylight-saving drift trap

Even a perfect grid breaks twice a year if you ignore daylight saving time. A note on time-zone pitfalls from VClock.pro describes the classic failure: a recurring meeting scheduled with a fixed offset drifts by an hour when one region switches to or from daylight saving, and nobody notices until someone misses a call at the wrong time. Because not every country switches on the same weekend, two regions that were perfectly aligned in March can be off by an hour in November.

The defense is to think in time zones, never in offsets. Store a meeting as "10 a.m. Eastern" rather than as a fixed number of hours from UTC, and re-verify every recurring cross-timezone meeting in the weeks around the spring and autumn transitions. A quick check that your calendar shows the right local time for every participant is a ten-minute task that prevents a missed all-hands. Combined with the overlap grid and the rotation rule, this closes the loop: you stop guessing, stop burning out the remote team, and stop letting the clock run your evenings.

When a meeting should simply not exist

The most underused scheduling skill is canceling the meeting. Once the grid shows that a cross-timezone call forces someone onto a 6 a.m. or 10 p.m. slot every week, the right answer is often not to rotate the pain forever but to ask whether the meeting needs live attendance at all. Decisions that could be a written update, a threaded question, or a short async message should not burn an evening on either side. Teams that are honest about this discover that a surprising number of their recurring global calls survive as habit, not necessity.

A practical rule: if the meeting is mostly status updates, make it asynchronous. If it genuinely needs discussion, use the overlap grid and rotate the awkward slot. And if the overlap is nearly empty, record the key session, share notes, and rely on a decision log so the person who could not reasonably wake at dawn still sees what was decided. This is the same principle that keeps remote voices visible in hybrid meetings: the people who cannot physically or temporally be present should not lose information because the room decided to proceed without them. The office-day guide pairs naturally with this, because aligning team anchor days reduces the number of global syncs you need in the first place.

Frequently asked questions