Guide · scheduling
How to pick a meeting time across time zones that people actually accept
“Can we do 3 p.m. my time?” is the sentence that starts most scheduling arguments. The fix is not a better memory of offsets — it is a repeatable method that makes the trade-off visible before anyone agrees to it.
In this guide
1. One instant, many clocks
A meeting happens at a single instant. Everything else — “9 a.m.”, “14:00”, “after lunch” — is a local reading of that instant, and the reading changes with the city. Almost every scheduling mistake comes from treating one of those readings as the event.
So the first move is to stop negotiating in local times and start negotiating in a shared reference. Pick the zone you will quote: usually the zone of the person who has the fewest options, or simply the organiser's zone. Every proposal after that is “the instant that reads 09:00 in New York,” and each participant converts once, not on every reply.
Offsets are also not constants. A city's offset can change twice a year, and occasionally for good, when a government changes its rules. Any method that relies on remembering “Berlin is +1” will be wrong for a few weeks each year. Read the offset from a time zone database at the moment you schedule — that is what your operating system and this site's planner both do.
2. Find the real overlap
Write down each participant's working window in their own zone (not everyone is 9–5) and convert those windows into the reference zone. The overlap is the intersection. Do it per person and you get a table like this — the sample team is in New York, London, Berlin and Singapore, on a November date when New York is on UTC−5, London UTC+0, Berlin UTC+1 and Singapore UTC+8:
| Instant (New York) | London | Berlin | Singapore | Verdict |
|---|---|---|---|---|
| 09:00–09:45 | 14:00 | 15:00 | 22:00 | US + Europe at work; Singapore late evening |
| 10:30–11:15 | 15:30 | 16:30 | 23:30 | Europe still at work; Singapore about to sleep |
| 12:00–12:45 | 17:00 | 18:00 | 01:00 next day | London on the edge, Berlin done, Singapore asleep |
| 08:00–08:45 | 13:00 | 14:00 | 21:00 | Best compromise for a four-zone team |
Two things are worth noticing. First, the “obvious” 9 a.m. New York slot already pushes Singapore to 22:00 — technically awake, practically after dinner. Second, moving one hour earlier (08:00 New York) buys Singapore a 21:00 start at the cost of an earlier morning in the US. That is the shape of almost every cross-zone decision: an hour moved from one end of the chain appears at the other.
When you have more than three cities the arithmetic stops being reliable by hand, because the answer depends on every participant's own working window. That is the case for a tool that scores all 96 quarter-hour start times rather than eyeballing a clock grid.
3. Check the day, not only the hour
Three day-level checks catch most of the meetings that get accepted and then quietly resented:
- Weekends. A Friday 22:00 in Singapore is Saturday 01:00 — and a Saturday call is not a working-hours call, whatever the clock arithmetic says. Treat weekend days as personal time when you score a slot.
- Friday evenings and Monday mornings. Even inside working hours, a Friday 17:00 in one zone is the end of a week; the same call on Tuesday costs less goodwill for the same information.
- Local holidays. Time zone tools do not know that 3 October is a German public holiday or that Lunar New Year closes offices in Singapore and Seoul for several days. Keep the team's holidays somewhere you actually look before sending the invite.
A useful habit: when you find a good slot, check the next day's date in every city, not just the clock. A call that crosses midnight for someone is almost never a call they will join with full attention.
4. Decide who takes the awkward hour
Distributed teams rarely have a slot where everyone is inside 9–5. The honest move is to choose who is outside it — and to make that choice rotate. A team that always asks the same region to join at 23:00 is teaching that region that its evenings are not protected.
Two rules work well in practice:
- Protect the night, trade the edges. An 07:00 start or a 20:00 finish is a real cost but a manageable one; 02:00 is not. Prefer slots where the worst-off participant is at the edge of their day rather than in the middle of their sleep.
- Rotate by meeting, not by person. If the weekly sync always lands at 22:00 Singapore, move it to 07:00 Singapore next month (which is an evening slot in Europe), or record one meeting and alternate which region attends live.
Write the rotation into the calendar description — “this quarter the Asia-Pacific team takes the early slot” — so the next person who books a follow-up can see the history instead of starting the negotiation from zero.
5. Write an invite nobody has to convert
An invite with a single time and no local conversions will be misread by at least one participant. Include all of them:
Platform weekly — 45 min
Tue 17 Nov · 08:00 New York (EST) · 13:00 London (GMT) · 14:00 Berlin (CET) · 21:00 Singapore (SGT)Agenda: launch readiness, open decisions, owner for the follow-up.
The zone abbreviations are not decoration: “13:00 London” in July is a different instant from “13:00 London” in January, and writing GMT or BST explicitly forces the reader to notice. Better still, attach a calendar file whose start and end are stored in UTC — the calendar app then computes each attendee's local view from the same instant, and a clock change cannot move it.
Two small details that prevent most follow-up questions: give the meeting an end time (a 45-minute block with an end reads as a promise that it will not sprawl), and put the local times in the description rather than the title, so they survive being forwarded.
6. What to do when there is no overlap at all
Some teams genuinely have none: San Francisco and Sydney share almost nothing, and adding Bangalore or São Paulo can close the last usable window. Before forcing a 06:30 call, try one of these:
- Split the meeting. Two 25-minute calls, each with the region that is awake, plus a shared written summary, often beat one 50-minute call that half the team attends half-asleep.
- Make the default asynchronous. A written update with a deadline and an explicit list of decisions needed keeps the same information moving without the hour. The next guide covers how to structure that handoff.
- Use the boundary hours deliberately. 07:00 and 20:00 are the two hours that can touch both ends of a long chain. Rotate between them rather than always spending one region's evening.
- Record and summarise. If a call must happen at an odd hour, record it and post a three-line summary within a day. The people who could not attend then get the outcome, not just the invitation.
A five-line checklist before you send
- Every participant's city is listed, in their current offset — including anyone who changed clocks recently.
- The slot does not cross midnight for anyone.
- Nobody's weekend is being used as a workday.
- The person outside working hours is at the edge of their day, and the rotation is written down.
- The invite carries every local time and a UTC-backed calendar file.
You can run that checklist in about two minutes with the CrossClock planner: add the cities, read the scored windows, and export the invite. Everything stays in your browser — no account, no upload.
Next: the four traps daylight saving sets for recurring meetings.
Read the DST guide