Time-Zone Communication
3 exercises — communicate meeting times, availability, and scheduling across multiple timezones clearly.
0 / 3 completed
Timezone communication rules
- Always anchor in UTC — "14:00 UTC" is unambiguous; "2pm" is not
- Pre-calculate local times — never make teammates do the math
- Name the overlap window — the hours when everyone can meet synchronously
- Declare response SLAs — "I respond within 8h" eliminates anxiety when you're offline
- Offer async alternatives — recording, notes, written agenda for off-hours attendees
1 / 3
You're sending a meeting invitation to team members in Warsaw (UTC+1), New York (UTC-5), and Singapore (UTC+8). The meeting is at 09:00 UTC. Which invitation text handles timezones correctly?
Option B is a professional timezone-aware meeting invitation:
Required elements in cross-timezone invitations:
1. UTC as the anchor time — neutral reference all can convert from
2. Pre-calculated local times — recipients shouldn't have to do math ("10:00 Warsaw / 04:00 NY / 17:00 Singapore")
3. Acknowledging inconvenient times — "04:00 is very early for NY" shows awareness and respect
4. Async alternative offer — recording option for off-hours participants is inclusive practice
5. Agenda — necessary for time-zone scheduling especially; let people decide if attendance is worth the hour
Meeting scheduling tools that help:
• worldtimebuddy.com — visual timezone overlap tool
• Every Time Zone (everytimezone.com) — quick reference
• Calendar apps: when you set a recurring meeting, set it in UTC to avoid DST drift issues
DST warning: "10am every Monday" will shift by 1 hour twice yearly for parts of your team. UTC times don't drift. Always anchor in UTC for international teams.
Required elements in cross-timezone invitations:
1. UTC as the anchor time — neutral reference all can convert from
2. Pre-calculated local times — recipients shouldn't have to do math ("10:00 Warsaw / 04:00 NY / 17:00 Singapore")
3. Acknowledging inconvenient times — "04:00 is very early for NY" shows awareness and respect
4. Async alternative offer — recording option for off-hours participants is inclusive practice
5. Agenda — necessary for time-zone scheduling especially; let people decide if attendance is worth the hour
Meeting scheduling tools that help:
• worldtimebuddy.com — visual timezone overlap tool
• Every Time Zone (everytimezone.com) — quick reference
• Calendar apps: when you set a recurring meeting, set it in UTC to avoid DST drift issues
DST warning: "10am every Monday" will shift by 1 hour twice yearly for parts of your team. UTC times don't drift. Always anchor in UTC for international teams.