If you've ever typed "does 9 AM work for everyone?" into a group chat and then spent ten minutes doing mental time zone arithmetic, you already know the problem: time zones aren't a fixed offset you can memorize once and reuse forever. They shift twice a year in most countries, they don't shift at all in others, and the person on the other end of your meeting invite is often doing the exact same confused math in reverse.
Why you can't just "add the hours"
The instinct is to treat a time zone like a constant -- "New York is 5 hours behind London, so 2 PM their time is 9 AM mine." That works for about half the year. The other half, the UK is on British Summer Time and the US East Coast is on Eastern Daylight Time, and the gap between them temporarily narrows to 4 hours because the two regions don't start and end daylight saving on the same date. India, by contrast, never observes daylight saving at all, so its offset from both New York and London keeps changing relative to each of them throughout the year even though India itself never moves its own clocks.
This is why a meeting time that worked fine in March can quietly shift by an hour in April, and why "just add 5 hours" is a rule that's right until it isn't.
Think in overlap windows, not single times
The more useful way to approach this isn't "what time is it for them" -- it's "which hours of the day are reasonable for everyone involved, at the same time." If you're coordinating three people across San Francisco, London, and Mumbai, you're not looking for a single magic hour; you're looking for the narrow band where none of their local clocks reads before roughly 7 AM or after 9 PM.
For some combinations, that window is comfortable -- a few hours in the late morning for one side land in the evening for another, with plenty of room either way. For others, especially when one person is roughly 12 hours offset from the rest, there may be no window at all where everyone is in normal waking hours, and the honest answer is that someone has to take an early or late call, or the meeting needs to rotate who absorbs the inconvenient slot each time.
The daylight saving trap
The most common scheduling mistake isn't bad math -- it's stale math. A recurring meeting set up in January using that month's offsets can land an hour off by July if the regions involved change their clocks on different schedules, or one changes and the other doesn't at all. If you have a standing weekly call with a distributed team, it's worth rechecking the actual local times a couple of times a year rather than assuming the original setup still holds.
A simple routine before you send the invite
- List every city involved, not just the time zone name -- "Pacific Time" and "Mountain Time" are each used by multiple places, and a vague label is where errors creep in.
- Check what each location's current local time actually is right now, rather than relying on what you remember its offset being.
- Line up a few candidate hours and see what each one translates to for every participant at once, rather than converting one pair at a time.
- If no slot is comfortable for everyone, say so explicitly and rotate the inconvenient slot, rather than defaulting to whichever region happens to be loudest in the planning thread.
Doing this by hand across more than two time zones gets error-prone fast, which is really a lookup problem, not a math problem worth being clever about.
The Meeting Planner lays out working hours for several time zones side by side so you can see the overlap at a glance instead of converting each one by hand, and the World Clock is a quick way to check what time it is somewhere right now before you even start picking candidate slots.