How to Schedule Meetings Across Time Zones (Without Headaches)
If your team spans New York, Berlin, and Singapore, you've felt the pain: someone is always joining at 7 a.m. or 10 p.m. Scheduling across time zones is the defining logistics problem of remote work. Done well, it becomes a superpower — a "follow the sun" workflow. Done poorly, it breeds resentment and burnout. Here's how to get it right.
Find the Golden Overlap Hours
Every set of locations has a window where working hours overlap. The art is finding it and protecting it. Some common overlaps:
| Locations | Golden overlap |
|---|---|
| US East Coast + Western Europe | 9 a.m.–12 p.m. ET = 3–6 p.m. CET (plentiful) |
| Western Europe + East Asia | 8–10 a.m. CET = 3–5 p.m. CST (narrow but workable) |
| US West Coast + East Asia | 4–6 p.m. PT = 8–10 a.m. JST next day (tight) |
| US + Europe + East Asia | Essentially none — rotate or go async |
The key insight: an overlap of just two hours is enough for a daily standup and a weekly sync. You don't need eight shared hours — you need one good one, used deliberately.
Go Async-First
The best distributed teams treat meetings as the last resort, not the default. Async-first practices include:
- Written standups: Post updates in a shared channel instead of a daily call.
- Recorded video: Tools like Loom let you present a design or demo that teammates watch in their own morning.
- Decision documents: Propose decisions in writing with a comment deadline, so every time zone gets an equal voice.
- Clear handoffs: End your day with a note about what's ready for the next region to pick up.
Async work respects time zones by design: nobody has to be awake at the same moment for work to move forward.
Use the Right Tools
Mental math across zones is where errors — and missed meetings — come from. Rely on tools instead:
- A world clock showing your teammates' cities side by side, so "is it reasonable to ping Ana now?" is answered at a glance.
- Calendar apps that auto-convert invitations to each recipient's local time (Google Calendar and Outlook both do this — always send invites, never just a time in chat).
- Scheduling links (Calendly-style) that display your availability in the booker's time zone.
One golden rule: always include the time zone when you write a time in text. "Let's meet at 3" is meaningless across borders; "3 p.m. CET / 9 a.m. ET" is clear. Better yet, anchor to UTC for anything technical.
Etiquette for Distributed Teams
Scheduling across zones is ultimately about fairness. A few norms that healthy global teams adopt:
- Rotate the pain: If a meeting is early for one region and late for another, alternate who gets the bad slot each week. No team should permanently absorb the 10 p.m. call.
- Beware DST season: Twice a year, daylight saving transitions shift offsets by an hour — and the US and EU switch on different dates. Recurring meetings silently drift. Audit them in March and October.
- Respect local Fridays and Mondays: A Friday afternoon call in San Francisco is Saturday morning in Sydney.
- Record everything: People will miss meetings; make sure they can catch up without a second meeting.
- Set response-time expectations: "Replies within 24 hours" beats implicit demands for instant answers at someone else's midnight.
A Simple Workflow That Works
Put it together: maintain a shared world clock of team locations, define a two-hour overlap window and guard it fiercely, default to async for everything else, rotate inconvenient slots, and double-check recurring meetings when DST changes. Do these five things and time zones stop being a headache — they become round-the-clock momentum.
Key Takeaways
- Identify the golden overlap hours for your team and protect them for live meetings.
- Default to async communication; use meetings sparingly and record them.
- Always state time zones explicitly, and send calendar invites that auto-convert.
- Rotate inconvenient slots and audit recurring meetings during DST transitions.