Scheduling Meetings Across Time Zones — A Practical Guide

If you’ve ever sent a calendar invite “for 3 PM” without specifying a time zone, you’ve made everyone’s day a little harder. After running a distributed team for 6 years, here’s the playbook I wish I’d had on day one.

Rule 1: Always specify the city, not the abbreviation

“3 PM EST” is ambiguous half the year — because half the year, the U.S. East Coast is on EDT, not EST. Saying “3 PM New York time” or “3 PM ET” is unambiguous regardless of season.

For Central time, the safest phrasing is “3 PM Chicago time” or “3 PM CT”. Avoid “CDT” or “CST” unless you really mean to fix the season — most of the time you mean “current Central wall-clock time”.

Rule 2: Anchor on UTC for global teams

If your team spans 6+ time zones, write times in UTC. Slack and most calendar tools auto-convert to local for each viewer. UTC has no DST; it never moves; nobody can be confused.

Sync standup: 14:00 UTC daily

Rule 3: Use the “fairness rotator”

If your team has a US (Chicago) and India (Mumbai) office, every recurring meeting has a built-in 10.5-hour gap. Either:

• Pick a slot that works for both (early morning Chicago = evening Mumbai), but always pick the same slot — don’t make people guess.
• Or alternate: month one is “early morning Chicago”, month two is “early morning Mumbai”.

Rule 4: Beware the DST traps

Twice a year, the time difference between the U.S. and Europe (or Australia, or Brazil…) shifts because countries enter and exit DST on different dates. The common pitfalls:

• Mid-March: U.S. springs forward 2-3 weeks before Europe. For ~3 weeks, EU times are 5 hours ahead of EDT instead of the usual 6.
• Late October: Europe falls back ~1 week before the U.S. For that week, EU times are 5 hours ahead of EDT again.
• Australia and Brazil are reversed — their DST is in our winter.

Rule 5: Know which countries don’t observe DST

If you work with India, China, Japan, Singapore, the Philippines, the UAE, Russia, Turkey, Iceland or Argentina — none of them observe DST. The offset to those countries shifts twice a year only because the U.S. side changes.

Tools that actually help

• time.is for a quick “what time is X in Y” check
• everytimezone.com for visualizing 5+ teams at once
• cdttimenow.com (👋 us) for U.S. Central anchoring

That’s it. Nothing fancy — just be explicit, anchor on UTC for global, and respect that DST is the source of 90% of cross-team scheduling pain.