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.

A complete London, Riyadh and Singapore example

Consider a 45-minute meeting on 6 November 2026. For this example, all three colleagues have agreed availability from 9:00 AM to 6:00 PM locally. London is on UTC+0, Riyadh on UTC+3 and Singapore on UTC+8. Their common window is 9:00–10:00 AM in London, noon–1:00 PM in Riyadh and 5:00–6:00 PM in Singapore. Starting at 9:00 AM London fits; starting at 9:30 AM would finish at 6:15 PM Singapore and exceed the agreed limit. This is why a planner must evaluate the whole meeting duration. These hours are assumptions for the example, not a statement about local business practice.

Make the invitation understandable without mental arithmetic

For that example, an invitation could say: Friday, 6 November 2026, 09:00–09:45 London, 12:00–12:45 Riyadh, 17:00–17:45 Singapore. Include the calendar invitation as the primary event record and the written equivalents as a cross-check. Add the purpose, expected decision, meeting link and one owner for questions. If the meeting is rescheduled, update the original event rather than sending an unrelated message with a new time. Participants may otherwise keep two different appointments. Never describe an international event only as “tomorrow morning”; tomorrow depends on the reader's location and the time they open the message.

Choose the anchor for a recurring series

A recurring event needs an explicit rule. An event anchored to 9:00 AM London should follow London's seasonal clock changes; an event anchored to a fixed UTC instant should retain that instant while some local readings move. Those are different business requirements. Ask which one matters before creating the series. For a customer office-hours call, the customer's local time may be the appropriate anchor. For a global operational handover, a fixed UTC reference might be more useful. Record the chosen rule in the description, then inspect calendar occurrences on both sides of the next seasonal transition instead of assuming the software made the intended choice.

Plan the discussion as well as the time slot

Not every invited person needs to attend every minute. Identify the decision maker, essential contributors and people who only need the result. Send background material early enough for each region to read during its own working day. Put the shared decision near the start of the meeting rather than after a long status report. When the overlap is only 30 minutes, reduce the agenda instead of silently extending the call. Assign an owner and due date to every follow-up. A carefully converted time is wasted if the meeting produces no recorded outcome or repeatedly requires people to join outside their agreed availability.

Handle changes without creating duplicate calendar records

When a participant travels, confirm which location they will actually be in on the meeting date. Their home office zone may remain in an email signature even after they move. If the organizer changes, verify that the new organizer preserves the intended anchor zone and recurrence rule. For a cancelled occurrence, cancel that occurrence explicitly. For an entire series, replace or edit the series deliberately and tell participants which record remains authoritative. Calendar products behave differently, so inspect the saved result rather than relying on a button label alone. Ask a colleague in another zone to confirm the first changed occurrence before extending the series for months.

Common scheduling questions

Should we invite everyone using UTC?

UTC is useful as a shared reference, but many participants work from local calendars. Supply both a named event zone and readable local equivalents where confusion is likely. A timestamp without a date remains incomplete even when it includes UTC.

What if there is no shared working-hour window?

Reduce attendance, use written decisions, or agree an occasional rotating early or late slot. A tool cannot decide which personal constraints should be overridden. Get agreement instead of treating a green working-hours indicator as consent.

How far ahead should we reconfirm?

Review important events when participants, venues or clock rules change, and again close to the event. For a long-running series, schedule a review around relevant DST transitions. Keep the original decision about the reference zone visible so a later correction does not accidentally change the business requirement.

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.