Finding an Hour That Works for Everyone
Scheduling across time zones is arithmetic that goes wrong quietly. Someone converts in their head, forgets that one country has already moved its clocks and the other has not, and a call lands an hour off, or at six in the morning for the person who said yes without checking.
This converter shows several zones at once against a single slider, with business hours marked, so the overlap is something you look at rather than something you calculate.
How to Plan a Meeting Across Zones
The tool answers a visual question: where do everyone’s working hours overlap?
- Add each participant’s time zone. Cities are easier to pick than UTC offsets and handle the daylight saving rules for you.
- Move the slider to sweep through the day. Every zone updates together, so you can see the whole set at once.
- Look for the window where all the zones show business hours. That overlap is the answer, and it is often narrower than people expect.
- Note the date as well as the time. A morning call in Europe can be the previous evening in the Americas, and the day is the part most often got wrong.
- Copy the schedule when you have a time, which produces the times for every zone in a form you can paste into an invitation.
Why Daylight Saving Breaks Mental Arithmetic
The offset between two places is not fixed. London and New York are usually five hours apart, but for two weeks in March and one week in autumn they are four, because the two countries change their clocks on different dates. A rule of thumb learned in January is wrong for part of the year, and nothing announces the change.
The southern hemisphere inverts the problem: when Europe springs forward, Australia is falling back, so the gap between London and Sydney swings by two hours rather than one. This tool relies on the browser’s own time zone database, which carries the real rules and historical changes, so it does not need a rule of thumb at all.
Common Business Zones
Standard and daylight offsets for the zones that appear most often in international scheduling.
| Zone | Standard | Daylight | Observes DST? |
|---|---|---|---|
| UTC | +0 | +0 | No |
| London (GMT/BST) | +0 | +1 | Yes |
| Central Europe (CET/CEST) | +1 | +2 | Yes |
| India (IST) | +5:30 | – | No |
| Singapore, Hong Kong | +8 | – | No |
| China (CST) | +8 | – | No, one zone nationwide |
| Korea, Japan (KST/JST) | +9 | – | No |
| Sydney (AEST/AEDT) | +10 | +11 | Yes, southern summer |
| US Eastern (EST/EDT) | −5 | −4 | Yes |
| US Pacific (PST/PDT) | −8 | −7 | Yes |
India, Iran and parts of Australia run on half-hour or quarter-hour offsets, which is why "add five hours" fails as a general rule. Much of Asia does not observe daylight saving at all, so the gap to Europe changes twice a year even though nothing changed locally.
Practical Habits for Scheduling
Writing the time zone into the invitation is the single most effective habit, and naming the city rather than the abbreviation is better still. CST is Central Standard Time in North America and China Standard Time in Asia, fourteen hours apart, and IST covers both India and Ireland. A city name is unambiguous in a way an abbreviation is not.
For recurring meetings, be aware that a series fixed in one participant’s zone will drift for everyone else twice a year. A weekly call at nine in London moves for the New York attendee in March and again in November. Agreeing which zone anchors the series prevents the quiet annual confusion.