Find working hours that overlap
A time that is convenient in one city can land at breakfast, late at night, or on the next calendar day somewhere else. Before choosing a recurring slot, ask where people work and what hours they can reasonably attend.
“Office hours” are only a rough starting point. Our planner highlights 09:00–17:00 on weekdays, but it cannot know local public holidays, school pickups, shift work, or someone’s personal schedule.
Always convert with the meeting date
Enter your meeting date into the converter before comparing cities. Today’s time difference might not be the difference on the day you meet. This is especially useful around seasonal clock changes.
Choose the city whose time you know first, enter the local time, and add the destination cities. Move through the day until you find a reasonable overlap.
Send a calendar invitation
A good invitation includes the full date, a named time zone, and a calendar entry. The calendar file from our converter contains UTC start and end instants for a 30-minute event. Calendar applications can display those instants in the recipient’s local zone.
The share link preserves your selected cities, date, time, and any repeated-hour choice. Send the link with context so recipients know what the appointment is for.
Recurring meetings across time zones
A repeating meeting anchored to one city may shift by an hour for colleagues elsewhere when clocks change. Choose which city’s local time should remain fixed, then check the effect on everyone after each seasonal transition.
When there is no fair overlap, rotate the inconvenience, shorten the synchronous session, or move the update into a written message. A thoughtful schedule makes participation easier.
Technical reference
Calendar interoperability follows RFC 5545: iCalendar. Local conversions use IANA time-zone rules supplied by the browser.