How to schedule across time zones and avoid date and DST mistakes
The biggest cross-time-zone risk is not being one hour off—it is believing everyone is discussing the same calendar day. Establish one reference zone, then collect the times when each person can attend in full.
Collect cities or named time zones, not only UTC offsets
Record each participant’s city or IANA time zone, such as Asia/Taipei, Europe/London, or America/Los_Angeles. A note such as “UTC-8” can become wrong when daylight saving time begins. Some regions change offsets during the year; others do not.
Choose one reference zone and repeat it in the invitation
Use the organizer’s location or the primary team’s zone as the meeting time zone. Togethr displays all dates and times in that reference zone and does not automatically convert the grid for each participant. Write a clear note such as “All options are shown in Taipei time,” and ask participants to convert before submitting.
Check for previous-day and next-day changes
Tuesday morning in Taipei may still be Monday evening in the Americas. Friday evening in California may already be Saturday in Asia. Every conversion should include the weekday and date, not only the clock time. If a candidate window crosses midnight, split it into clearly labeled dates.
Watch the weeks when daylight saving time changes
The United States and Europe do not always change clocks on the same weekend, and Southern Hemisphere seasons run in the opposite direction. For meetings near a transition, recalculate with named city zones instead of reusing last month’s offset. Recurring meetings deserve a fresh reminder before every clock change.
Find acceptable hours before searching for a perfect time
A group spanning Asia, Europe, and the Americas may have no option inside everyone’s normal workday. Agree on boundaries first—for example, no earlier than 7:00 and no later than 22:00 locally—then collect availability inside them. For long discussions, consider two shorter sessions or replace part of the meeting with an asynchronous document.
Rotate inconvenient hours for recurring meetings
If the same region always wakes early or stays late, participation quality will decline. Alternate between two windows—one favoring Asia and Europe, another favoring Europe and the Americas—or record the session and accept asynchronous input. Fairness does not mean every meeting is equally convenient; it means the burden does not permanently fall on one group.
Confirm the result in at least two local zones
The final message should include the reference zone and the local dates and times for major participant regions. Check the time-zone field before saving the event. An .ics file helps calendars convert automatically, but the written invitation should still name the zone so forwarded text and screenshots retain their context.
Example invitation
“Please reply by Thursday, July 23 at 20:00 Asia/Taipei. Every option in the grid uses Taipei time; participants in Los Angeles should note that some choices fall on the previous calendar day. The meeting is 60 minutes, so select every option you can attend in full.”
Next step
Create a cross-time-zone meeting and state the reference zone in the description. If group size is the main challenge, read the group scheduling guide as well.