Cross-Timezone Meeting Finder
☆Stop burning the 6am and 10pm calls. Map everyone's workday onto a 24-hour grid and the overlap windows where nobody joins at midnight appear by themselves.
Your inputs are saved on this device
Offsets are standard time; DST can shift clocks by ±1 hour. Example preset: San Francisco + London + Sydney (watch Sydney hit 2am).
Advanced ▾
US East Coast ↔ India is roughly a 9.5-hour gap with no fully-comfortable window — pick the rotation rule (below) instead of a fake overlap. Remember the burnout cost of repeated 6am/10pm calls documented by scheduling sources.
24-hour overlap grid
—Green = that hour is inside someone's workday (UTC axis). Amber column = the recommended window.
Add members to see windows.
Recommended window—
Rotate the early/late slot so no single timezone carries every off-hours call.
Why this matters
The recurring complaint on remote-team threads is not "my calendar is full" — it is the 6am standup and the 10pm debrief that quietly become normal. City Clock, Kumospace, Cash Nomads and eume all document how those hours wreck circadian rhythm, and the widely-cited HQ-timezone pattern puts one region permanently on the second shift: US East Coast to India is a roughly 9.5-hour gap with no clean overlap at all. A retrospective on a $150K engineer's exit blamed exactly this. This tool makes the invisible visible: a 24-hour grid where every green cell is a tolerable hour and every blank one is an off-hours call nobody should quietly absorb.
How it works
Each member has a city offset and an acceptable local window (default 8:00–18:00). For every UTC hour h, each person's local hour = (h + offset) mod 24. The cell turns green when that falls inside their window. Hours where everyone is inside become the overlap windows; within them, the recommended window is the hour whose midpoint sits furthest from every member's edges — the most "central" call. The rotation meter estimates how lopsided the burden is: if one timezone always hosts the early shift, the bar fills amber and the advice switches to a rotation rule.
What the results mean
A wide green overlap means your team can meet inside everyone's workday — pick the amber column and move on. A thin or empty overlap means no honest shared window exists: the fair answer is not to squeeze someone's 7am, but to rotate the off-hours slot weekly and document the rule, so the cost never falls on one person. Before sending invites, re-check live clocks — daylight saving drift is a classic cause of the 2am surprise. Write the rotation rule into your team charter once, exactly like the anchor-day pattern scheduling teams already use on the office side: two predictable windows beat one permanently unfair one.
Frequently Asked Questions
Why are 6am and 10pm meetings a problem?
Scheduling sources (City Clock, Kumospace, Cash Nomads, eume) link recurring early/late calls to circadian disruption. The practical fix is a grid-first habit: only book hours inside everyone's window, or rotate the burden.
Does this account for daylight saving time?
Offsets are standard time values. DST moves clocks by an hour in many regions — a documented cause of missed calls. Always check live local time before inviting.
My team spans US East Coast and India. Is there a perfect window?
The gap is about 9.5 hours — no fully-comfortable window exists. Use the rotation advice instead: one week a morning call for one side, next week the other side's afternoon.