Time-zone planning has a technical part and a human part. The technical part is finding the correct local time on a specific date. The human part is choosing a time that does not routinely push someone into an unreasonable early morning or late evening. A useful planner should help with both.
Start with a named city and a date
Use a city or IANA time-zone name instead of an abbreviation alone. Abbreviations can be ambiguous and can change seasonally. “Tuesday 14:00 in Athens” is clearer than “Tuesday 14:00 EET,” especially near a daylight-saving transition.
Find a reasonable overlap
A simple first pass is to compare a 09:00–17:00 local working window in both cities. That will not suit every team, but it makes the trade-off visible. If the overlap is short or absent, rotate inconvenient meeting times so the same person is not always carrying the burden.
Check daylight saving time twice
Some places change clocks; some do not; and they do not all change on the same date. A recurring time that works in March may shift in April. Review recurring meetings around local daylight-saving changes and state the city/time zone in calendar invitations.
Confirm with people, not only a calculator
A calculator can show a current offset. It cannot know school runs, caring responsibilities, local holidays, or individual preferences. Offer two options where possible and record the chosen city/time zone in the meeting invite.
Meeting-planning note
Use the live time-zone planner to compare the current time between two cities. The page explains its current-offset and working-hours assumptions.
Read our methodology, sources, and editorial policy. Spot an error? Contact the site.