The Predictable Failure Modes
Cross-timezone scheduling breaks down in three common ways. First: assuming everyone understands the time without a zone marker. '3 PM on Thursday' means different things to someone in London than to someone in Chicago. Second: always scheduling at the organizer's preferred time without considering the other party's work hours. Third: not accounting for daylight saving time transitions, which shift the hour difference between zones twice per year.
Tools and Practices That Help
- Always include the timezone when communicating meeting times in writing — '2 PM EST / 7 PM GMT.'
- Use World Time Buddy or similar tools to visualize overlap windows before sending an invite.
- Enable Google Calendar's secondary timezone and world clock before scheduling cross-zone meetings.
- For recurring cross-zone meetings, document whether they adjust for daylight saving or stay fixed.
- When time zones make overlap difficult, explore async alternatives before defaulting to someone's off-hours.
Finding Overlap Windows
For common timezone pairs, overlap windows exist but require checking. US East Coast and Western Europe have a two-to-three hour window in the morning EST / early afternoon CET. US West Coast and East Asia have almost no natural overlap and require one party to take a genuinely inconvenient time.
For the latter case, honestly evaluating whether the meeting needs to be synchronous is worth doing. If the content could flow asynchronously, the synchronous alternative imposes a real cost on someone's workday or evening that could be avoided.
When asking someone to attend a meeting at an inconvenient hour, acknowledge it explicitly in the invite. The acknowledgment signals awareness and respect — it does not change the time, but it changes the experience of the request.
Establishing a Cross-Timezone Meeting Norm
Teams that regularly meet across zones benefit from an agreed-upon norm: a specific overlap window designated as the team's synchronous hours, a rotation policy for inconvenient time slots, and a clear threshold for when meetings should become async instead. For related guidance on the async side of this, see our guide on scheduling for async teams.
How Schedule Calendar helps
Schedule Calendar displays events in your local time based on your Google Calendar timezone setting. For distributed team members receiving invites from organizers in different zones, the popup shows the correct local time for each event without manual conversion. Before scheduling a cross-zone meeting, a quick popup check tells you your own availability clearly, which is the starting point for any timezone scheduling conversation.
Frequently asked questions
Use a visual time zone tool like World Time Buddy to identify windows where all participants fall within reasonable business hours. Create the event in Google Calendar at your local time — it automatically converts for all attendees. Include the time in multiple zones in the event description or invite message. Always specify the timezone when communicating meeting times in writing.
Identify each location's typical business hours, then find the overlap. US East Coast and Europe (CET) have a two to three hour window mid-morning EST. US West Coast and Asia have almost no natural overlap and require one party to take an off-hours slot. Tools like World Time Buddy, Every Time Zone, and Google Calendar's world clock sidebar help visualize these overlaps without manual calculation.
Always include the time zone, and consider including the meeting time in each attendee's local zone for important meetings: '2 PM EST / 7 PM GMT / 3 AM JST.' For recurring meetings, include the time zone that the meeting is anchored to — relevant for daylight saving adjustments. Avoid time zone abbreviations alone (PST, CST) as they are sometimes ambiguous internationally.
Google Calendar stores events in the creator's time zone and adjusts for daylight saving based on that zone's rules. For attendees in zones with different daylight saving dates (notably US and Europe, which change on different weekends), this means the overlap window shifts temporarily. Document the expected time shift in the recurring meeting's description so attendees know when to expect changes.
Not necessarily, but it requires acknowledgment. When you schedule a meeting that falls outside a participant's standard business hours, note it explicitly: 'I know this is outside your normal hours — I appreciate you joining.' Rotate who takes the inconvenient slot for recurring meetings. And genuinely evaluate whether the meeting could be async before asking someone to attend at 7 AM or 9 PM.
Google Calendar supports displaying two time zones simultaneously in the day and week views — your primary zone and one secondary zone. The world clock feature, accessible in Settings, can show additional zones as a sidebar list. There is no strict limit on the number of zones in the world clock, though displaying more than four or five becomes visually dense.