Scheduling Across Time Zones: Find Overlapping Availability Without the Math
Scheduling across time zones is where simple meetings go to die. One person is in New York, one in London, one in Bangalore. Everyone has a booking link, but each page shows times in a different local zone, and somewhere between "your 9 a.m." and "my 2:30 p.m." someone ends up on a call at midnight.
Here's how to find overlapping availability across time zones without doing the offset math, and how to avoid the mistakes that catch even experienced remote teams.
Why time zone scheduling goes wrong
Offsets aren't whole hours
India is UTC+5:30. Nepal is UTC+5:45. Parts of Australia are half an hour off their neighbors. If your mental model is "add five hours," you'll be wrong by thirty minutes, which is exactly the length of the meeting.
Daylight saving time doesn't happen on the same day
The US and Europe change their clocks on different weekends, and much of the world doesn't change at all. For a few weeks in spring and about a week in fall, the gap between New York and London is four hours instead of five. A recurring meeting that worked last week can suddenly start an hour early for half the team.
Every booking page shows its own view
Calendly and Cal.com try to show times in the visitor's zone, but when you're comparing several pages, it's easy to lose track of which zone you're looking at, especially when one page has been set to a different zone manually.
The simple fix: compare in absolute time, display in yours
The reliable way to compare availability across time zones is to convert every open slot to the same absolute moment, find the intersection, and only then convert the results into the zone you care about. That's what CalOverlap does:
- It detects your time zone automatically from your browser and preselects it in a dropdown.
- It compares slots as exact moments in time, so a slot shown as 10:00 a.m. in New York and 3:00 p.m. in London counts as the same opening.
- It labels every result with the zone, including the correct abbreviation on each date. If the three-week window crosses a daylight saving change, slots before the change show EDT and slots after show EST.
Want the results in a colleague's time instead? Pick their zone from the dropdown and search again. The overlapping moments are the same; only the labels change.
Best practices for international meetings
- Announce times with the zone attached. "Tuesday 10:00 a.m. PT" is clear. "Tuesday at 10" is a bug report waiting to happen.
- Rotate the inconvenience. If there's no window that's comfortable for everyone, alternate who takes the early or late slot.
- Re-check recurring meetings around clock changes in March, April, October, and November.
- Use matching meeting lengths. Slots are matched on start times, so 30-minute event types on every link give you the most overlap. Our step-by-step guide has more tips.
Where this matters most
Distributed teams, founders talking to overseas investors, and recruiters lining up interviewers in several offices all hit this problem constantly. If you're in hiring, see our panel interview playbook; if you're coordinating a team that's split across tools as well as zones, read Beyond Calendly: team scheduling across platforms.
The bottom line
Time zones are a solved problem for computers and an unsolved one for people. Let the tool line up the absolute times, check that the dropdown shows the zone you want, and share the result with the zone attached.