GUIDE · Updated 2026-09-19

Every distributed team knows the ritual: someone proposes "3 pm my time?", three people convert it wrong, and the thread grows to eleven replies. Scheduling across time zones is a solved problem — it just needs a method instead of arithmetic in the dark. Here is the one that works.

Step 1: Find the true overlap

Write down each participant's comfortable hours — say 9:00 am to 6:00 pm local — and intersect them. London + New York leaves a generous 5-hour window (2:00–7:00 pm London). London + Singapore leaves 2 hours (9:00–11:00 am London). London + New York + Singapore leaves… nothing comfortable at all, which is itself the answer: some meetings should not exist as meetings (see step 4).

Step 2: Name the sacrifice

When the overlap is thin, someone is taking the bad slot — a 7:00 am start or a 9:00 pm finish. The single biggest fairness failure in global teams is that the same office takes it every week, usually the one furthest from headquarters. Say it out loud in the invite: "This one is early for Singapore." Naming the cost is what makes rotation (step 3) happen.

Step 3: Rotate the pain

For any recurring meeting across 7+ hours of spread, alternate who stays late and who wakes early — odd weeks favor Asia, even weeks favor America, or rotate through three anchors. A simple fairness test: over a quarter, count how many out-of-hours attendances each region logged. If one region holds 80% of them, the schedule is broken regardless of how "convenient" it feels at HQ.

Step 4: Downgrade to async when the window is empty

A meeting with no humane overlap is a document in disguise. Status updates, decisions with clear options, and reviews all survive the conversion: write it up, set a 24-hour comment window, and reserve live calls for the discussions that genuinely need interruption and tone — conflict, brainstorming, bad news.

Step 5: Communicate times like a professional

Three habits kill conversion errors: always state the city with the time ("14:00 London / 9:00 New York"), never say "EST" when you mean "whatever New York is doing this month" (half the year it is EDT), and for anything written down, add the date — a Tuesday evening call in California is already Wednesday in Manila.

Quick answers

What's the best default meeting time for US–Europe? Late European afternoon: 4:00 pm London = 11:00 am New York = 8:00 am San Francisco.
US–Asia? There is no good slot — rotate between US evening (Asia morning) and US early morning (Asia evening).
How far ahead should invites go out? One week minimum across 3+ zones; time ambushes convert terribly.

Tools for this route