Complete Guide to Scheduling Meetings Across Time Zones
Scheduling a meeting with participants in Tokyo, London, New York, and São Paulo is not a math problem — it's a fairness problem. Most time zone tools show you what time it is elsewhere. They don't tell you who is being asked to wake up at 4 AM, or whose family dinner is being interrupted. This guide explains how to use the fairness score, handle DST transitions, rotate meeting burdens, and choose the right tool for your team's geography.
Why Fairness Matters More Than Convenience
Circadian disruption research (Harvard Medical School, Czeisler et al.) shows that even single-night sleep loss reduces cognitive performance by 15–30%. That's why our algorithm penalizes sleep hours 3× more than early/late hours: the person who joins at 03:00 is not just inconvenienced — they're meaningfully impaired the next day.
When to Use This Tool vs. Alternatives
| Tool | Best For | Limitation | Our Advantage |
|---|---|---|---|
| WorldTimeBuddy | Quick glance at 3–4 cities | No fairness scoring; static display | Visual burden heatmap |
| TimeAndDate | Exact time conversion | No DST conflict detection | Auto-detects DST gaps/overlaps |
| Calendly | 1-on-1 scheduling | Assumes everyone shares your working hours | Multi-party fairness optimization |
| Spacetime.am | Team dashboard | No calculation; just visualization | Calculates optimal windows |
| EveryTimeZone | Simple UTC reference | No participant-specific analysis | Per-person burden analysis |
Use this tool when: you have 3+ participants across 3+ time zones, you meet regularly (weekly standups, sprint planning), or you want to rotate who takes the early/late slots. Use simple converters for one-off calls between two people.
Interactive Scenarios
How to Handle DST Transitions (The Most Common Mistake)
- Spring-forward gap: clocks jump 02:00 → 03:00. Meetings 02:00–03:00 don't exist. Tool flags and suggests next valid time.
- Fall-back overlap: clocks fall 02:00 → 01:00. Hour 01:00–02:00 happens twice. Tool uses UTC anchors to avoid ambiguity.
- Southern Hemisphere offset: Sydney enters DST October, New York exits November. Gap shifts by 2 hours for 2–4 weeks. Tool auto-adjusts weekly.
- Countries that abolished DST: Russia 2014, Turkey 2016, Morocco suspends during Ramadan. Tool uses IANA tzdb with weekly updates.
The Fairness Algorithm: How Scores Are Calculated
- Working hours (09:00–17:00 local): Weight = 1.0
- Acceptable (07:00–09:00, 17:00–21:00): Weight = 0.6
- Sleep (22:00–07:00): Weight = 0.0
- Deep night (00:00–05:00): Weight = −0.5
Formula: Fairness Score = sum(weights) / participants. A 4-person meeting where 3 are in working hours and 1 is in sleep hours scores 75%, not 85%, because the sleep penalty drags the average down — that one person's cost is higher than the others' benefit.
Rotating Schedules: The Long-Term Fix
For a 6-person London/New York/Singapore team meeting weekly, a 3-week rotation distributes the early-and-late burden roughly equally across a quarter. The rotation generator is DST-aware, exports directly to calendar invites, and sends email alerts when a previously fair time becomes unfair due to seasonal clock changes.
Cultural Working Hours: Not Everyone Works 9-to-5
- Middle East: Sunday–Thursday work week, Friday prayer hours blocked.
- Spain/Italy: Siesta-aware (14:00–17:00 lower weight).
- Japan: Later start (10:00) common; overtime culture means 18:00+ still acceptable.
- India: Staggered shifts (09:00 and 11:00 starts common in tech).
These adjustments change the heatmap colors and fairness scores without requiring manual time-zone math.
When to Go Async Instead
- Split into two sessions (APAC + EMEA, Americas + EMEA).
- Record the meeting for async viewing with timestamped chapters.
- Use Loom or Slack huddles for under-15-minute updates.
- Rotate the "async sacrifice" — one person watches the recording each week.
The tool includes an Async Threshold setting. If no time scores above your threshold (e.g., 80%), it automatically suggests async alternatives.
API for Power Users
The REST API returns JSON with local times per participant, UTC anchors, fairness scores, DST warnings, and rotation schedules — ideal for Slack bots, HR systems, calendar apps, and project management tools. Free tier allows 100 requests/day; see API documentation for parameters and citation policy.