How to Schedule Meetings Across Time Zones
Use overlap windows, rotating fairness, daylight-saving checks, and async alternatives for global work.
Use overlap windows, rotating fairness, daylight-saving checks, and async alternatives for global work.
The fair time is an operating decision, not a conversion trick
Group scheduling adds preferences, required attendees, fairness, response delay, and time zones to ordinary availability. Decide whether the job needs a poll, collective host availability, pooled assignment, or recurrence before opening a grid of dates.
The fair time is a decision you make on purpose
There is rarely a time that is good for everyone. Pretending otherwise just hides who is paying. Decide the rule out loud: who takes the early slot, who takes the late one, and how it rotates.
Find the overlap the right way
- Use city-based zones. Store Europe/Berlin, not "+1". The offset changes twice a year; the city does not.
- Show local time to each person. Never make people convert in their head.
- Name the reference zone in the title when a group spans regions: "Weekly sync (14:00 UTC)".
Typical windows
| Regions | Usual best window (UTC) | Who pays |
|---|---|---|
| Europe and US East | 14:00 to 16:00 | Nobody, mostly |
| Europe and US West | 16:00 to 17:00 | Europe stays a little late |
| Europe and India | 08:00 to 11:00 | India ends the day in the slot |
| US and Asia-Pacific | 22:00 to 01:00 | Someone takes an evening; rotate it |
Recurring meetings and daylight saving
Europe and the US change their clocks on different dates. For a few weeks each spring and autumn, a fixed meeting drifts an hour for one side. A meeting stored against a city zone survives; one stored against an offset does not. Check the next transition date before you publish a series.
How to apply this guidance
Use one real meeting type, complete these actions in sequence, and record what changed.
Find overlap using city-based zones, not fixed offsets.
Rotate recurring burden and document the rotation.
Choose asynchronous work when no humane overlap exists.
Test the core scheduling flow
Create a booking page or group poll, then complete it in a separate browser session.
Measure meetings held outside local working hours
The primary signal for this guide is meetings held outside local working hours. Pair it with time to confirmation, completion, reschedule rate, attendance, organizer intervention, and the intended meeting outcome. Segment results by meeting type and participant context so one high-volume workflow does not hide another's failure.
Questions about schedule across time zones
How do I schedule a meeting across time zones?
Let each participant see their own local time, store a full IANA zone rather than an offset, and state the reference zone in the meeting title when the group spans regions.
What is the best time for a global meeting?
Usually 14:00–16:00 UTC, which is afternoon in Europe and morning on the US east coast. Asia-Pacific rarely fits without someone taking an evening, which is why rotation matters.
Why do recurring meetings drift by an hour?
Daylight-saving transitions happen on different dates in different hemispheres. A meeting fixed to a stored zone survives them; one fixed to an offset does not.
