Scheduling Across Three or More Time Zones Without Anyone Taking a 3am Call
With two time zones you find the overlap. With three there often is not one, and the job changes from finding a good time to distributing the cost fairly.
By Nishanth Narayanan · 2026-08-06 · 7 min read
Accept that there may be no good answer
Take a team split between San Francisco, London and Bengaluru. A 9 to 6 day in each gives you London to Bengaluru overlap in the London morning, London to San Francisco overlap in the London late afternoon, and San Francisco to Bengaluru overlap at no point whatsoever.
There is no hour where all three are inside normal working hours. Not a narrow one, none. Any all hands meeting for that team costs at least one location its evening or its early morning, permanently.
Recognising this early changes the conversation productively. The question stops being "when can we all meet" and becomes "how often do we genuinely need all three in a room, and who pays for it".
The method
Convert everything to UTC first. Trying to hold three local times in your head is where mistakes come from. Write each person's acceptable window as a UTC range and the problem becomes visible arithmetic. Bengaluru 09:00 to 18:00 is 03:30 to 12:30 UTC. London 09:00 to 18:00 is 08:00 to 17:00 UTC in winter. San Francisco 09:00 to 18:00 is 17:00 to 02:00 UTC.
Look for the intersection. Bengaluru and London intersect from 08:00 to 12:30 UTC. London and San Francisco intersect from 17:00 to 17:00 UTC, which is to say a single instant in winter. All three intersect nowhere.
Then widen deliberately, not accidentally. Decide what an acceptable stretch is: perhaps people will take a call an hour before or after their normal day, but not three. Widening Bengaluru to 20:00 local and San Francisco to 08:00 local gives you a genuine, if uncomfortable, common slot around 15:30 UTC, which is 21:00 in Bengaluru, 16:30 in London and 08:30 in San Francisco.
Distribute the cost
Once you know somebody has to pay, the remaining decision is who and how often.
Rotate. If the meeting is weekly, alternate between a slot that is hard for Asia and one that is hard for the Americas. It doubles the number of awkward slots but halves each person's share, and it visibly signals that the inconvenience is shared rather than assigned by seniority.
Shrink the room. Most meetings that span three zones do not need everyone. Two zone meetings almost always have a comfortable slot. Splitting into two overlapping conversations with one person bridging is usually better than one call nobody can attend properly.
Record and summarise. If a location is genuinely unable to attend, a recording plus a short written summary of decisions is a reasonable substitute for attendance, but only if decisions are actually written down. A recording alone asks someone to spend an hour recovering ten minutes of information.
Use the handoff instead
The strongest version of multi zone work barely meets at all. If Bengaluru finishes as San Francisco starts, that is not a scheduling failure, it is a relay. Work handed over at the end of one day and picked up at the start of another moves roughly twice as fast as work that waits for a shared meeting.
What makes this work is the quality of the handoff note, not the tooling. A useful one says what was done, what is blocked, what decision is needed and by when. A useless one says "pushed some changes". The discipline is the entire trick.
Watch the day boundary
The error people make most often with three or more zones is not the hour, it is the date. When it is 21:00 on Tuesday in Bengaluru it is 08:30 on Tuesday in San Francisco, but when it is 08:00 on Tuesday in Bengaluru it is 19:30 on Monday in San Francisco. A recurring invitation described as "Tuesdays" means two different days depending on where you read it.
Always state the date alongside the time for anything crossing more than about eight hours of offset. Our meeting planner shows a day badge on each city row at its local midnight, so a slot that is tomorrow for someone is obvious before you send the invitation rather than after.
Frequently asked questions
How do I find a meeting time for three time zones?
Convert each participant's acceptable working window into UTC, then look for an intersection. If none exists, widen each window by a fixed, agreed amount rather than ad hoc, and rotate which region absorbs the inconvenience.
Is there any time that works for San Francisco, London and India?
Not within normal working hours for all three. Around 15:30 UTC is the least bad compromise, landing at 21:00 in Bengaluru, 16:30 in London and 08:30 in San Francisco, which means the Indian side gives up their evening.
What is the most common mistake when scheduling across many zones?
Getting the date wrong rather than the hour. Across a large offset, the same instant falls on different calendar days, so a meeting described only by a weekday name means different things in different places.
About the author
Nishanth Narayanan builds and maintains GlobalTimeTools from Coimbatore, India. He works with distributed teams across Indian, European and US time zones, which is where most of these questions came from.