How to Schedule Meetings Across Time Zones

The arithmetic is only one part of international scheduling. A reliable plan also uses the correct date, respects local working limits, avoids ambiguous labels and shares the burden when no comfortable overlap exists.

1. Collect cities and actual availability

Ask for each participant's city or IANA time-zone name and their usable local hours. “CST” is not enough: abbreviations can be ambiguous, and “9 to 5” may not reflect flexible work, school pickup or local practice.

2. Choose the meeting date first

Offsets can change with daylight-saving rules. A conversion made for today can be wrong for next month. Enter the intended date in the Terbit Meeting Planner, then add each city.

3. Compare the same instant across every city

Scan the full day instead of testing one guess at a time. Watch both the hour and calendar date: a Tuesday afternoon in California may be Wednesday morning in Asia. If you already have one candidate, use the Time Zone Converter to check its local equivalents.

4. Apply a fairness rule

When there is no shared daytime window, define what the team considers “extended but acceptable” and rotate the inconvenience. For example, alternate a US-morning/Asia-evening meeting with a US-evening/Asia-morning meeting. Record the rotation so the same office does not inherit every early or late call.

5. Put unambiguous details in the invitation

• Use a calendar event with a named time zone, not a time pasted into plain text alone.
• Include the weekday and date, especially when participants are on different dates.
• Write “noon” or “midnight” carefully; for deadlines, use 11:59 PM or 12:01 AM when the intended date could be misunderstood.
• State the expected duration and whether the series will shift after DST changes.

NIST notes that 12 AM and 12 PM can be ambiguous and recommends clearer wording around noon and midnight in its times-of-day guidance.

Example: a three-city team

Suppose colleagues are in London, Riyadh and Singapore. Start with each person's real availability, then compare the selected date. London may change between standard time and summer time; Riyadh and Singapore keep stable offsets. A recurring slot therefore needs another check when London's clocks change.

Limits to remember

A time-zone tool cannot know holidays, leave, religious observance, commuting patterns or personal availability. Treat working-hour indicators as a filter, then confirm with the people involved. For the especially difficult US–Asia pairing, see our dated US–Asia meeting guide.

Source for changing civil-time rules

The IANA Time Zone Database tracks the history of local time and is periodically updated for political changes. Keep operating systems current and reconfirm important future meetings close to the date.