ZoneMeetup
Plan a meeting across time zones
Start with the people’s local working day, then compare one shared instant. An offset alone is not enough to plan a recurring international meeting.
1. Use a date and named places
Add each participant’s city or an IANA identifier such as Europe/Paris. A country may contain several time zones; “US time” is not a usable reference. Abbreviations can be ambiguous. Enter the date before comparing clocks because daylight-saving changes can alter offsets.
2. Make work-hour assumptions explicit
The example schedule starts at 09:00 and ends at 17:00 with Saturday and Sunday off. Edit it for each person. Split shifts, overnight windows, custom sleep and date exceptions can change the result. An overnight shift belongs to its starting weekday; a date exception can replace that day’s schedule. Imported busy ICS overlays stay in this tab and have a stated coverage window.
The overlap count checks the entire meeting duration. A person who is free at the first minute but busy before the end is not fully available. Public-holiday calendars are a separate reference tool and are not silently applied to participants.
3. Read the whole date, not just the clock
At 12:00 in Kuwait on 15 January 2026, London is at 09:00. A one-hour call fits 09:00–17:00 work windows in both cities, if there are no other exclusions. In July London’s offset differs. Kathmandu provides another useful check: 12:00 there is 09:15 in Kuwait on that January date. The 45-minute offset must not be rounded away.
The matrix uses a shared elapsed-time axis. Check local-day rollover, start and end dates, and UTC offsets. The blue daytime band means approximate 07:00–22:00 local clock hours, not a sunrise calculation or a guarantee that someone is awake.
4. Recheck every recurring date
Choose whether a series follows the organizer’s local clock or a fixed UTC time. These are different promises across daylight-saving changes. Preview all occurrences; resolve repeated local times explicitly and move meetings that fall in skipped times. Monthly schedules do not silently move an invalid day to the end of the month.
ZoneMeetup’s recurring ICS contains the finite UTC starts shown in the preview. It does not continue indefinitely or update itself when governments change timezone rules. Recheck important future meetings and keep your browser/OS current.
5. Share only what recipients need
Read the disclosure beside each action. Plan links exclude personal participant labels and busy calendars, but include the visible public schedule configuration. Event titles are included only when chosen. A recipient can read a complete shared link. The meeting PDF summarizes local dates and times; it does not confirm attendance. Calendar-provider draft links open a draft for you to review, without automatically sending invitations.
When no shared hour is fair
Try a shorter meeting, compare another date, or rotate who takes the inconvenient slot. Asynchronous notes can be more respectful than a recurring overnight call. A mathematically available hour is not evidence that someone agreed to attend.
Use the exact-time converter, holiday and working-day reference, and timezone source diagnostics. Methods: IANA Time Zone Database and RFC 5545 calendar interchange.
A considered meeting setup
Start with your room, microphone settings and camera position before buying equipment. Our meeting equipment guide connects a small selection to practical meeting needs, with compatibility checks and clearly marked Amazon affiliate links. Using the planner and all its exports stays free.