Remote Team Time Zone Overlap and Meeting Slot Finder
Distributed teams do not fail because of time zones; they fail because nobody measured the overlap before designing the working agreement. Two zones eight hours apart still share about one civil hour a day. Three zones spanning thirteen hours often share none — which is a scheduling constraint, not a scheduling problem, once you accept it and design asynchronously.
With a narrow overlap, protect the window for decisions only and move status updates to writing.
| UTC | You | Colleague B | Colleague C | Status |
|---|---|---|---|---|
| 00:00 UTC | 0:00 | 19:00 | 5.5:00 | — |
| 01:00 UTC | 1:00 | 20:00 | 6.5:00 | — |
| 02:00 UTC | 2:00 | 21:00 | 7.5:00 | — |
| 03:00 UTC | 3:00 | 22:00 | 8.5:00 | — |
| 04:00 UTC | 4:00 | 23:00 | 9.5:00 | — |
| 05:00 UTC | 5:00 | 0:00 | 10.5:00 | — |
| 06:00 UTC | 6:00 | 1:00 | 11.5:00 | — |
| 07:00 UTC | 7:00 | 2:00 | 12.5:00 | — |
| 08:00 UTC | 8:00 | 3:00 | 13.5:00 | — |
| 09:00 UTC | 9:00 | 4:00 | 14.5:00 | — |
| 10:00 UTC | 10:00 | 5:00 | 15.5:00 | — |
| 11:00 UTC | 11:00 | 6:00 | 16.5:00 | — |
| 12:00 UTC | 12:00 | 7:00 | 17.5:00 | — |
| 13:00 UTC | 13:00 | 8:00 | 18.5:00 | — |
| 14:00 UTC | 14:00 | 9:00 | 19.5:00 | — |
| 15:00 UTC | 15:00 | 10:00 | 20.5:00 | — |
| 16:00 UTC | 16:00 | 11:00 | 21.5:00 | — |
| 17:00 UTC | 17:00 | 12:00 | 22.5:00 | — |
| 18:00 UTC | 18:00 | 13:00 | 23.5:00 | — |
| 19:00 UTC | 19:00 | 14:00 | 0.5:00 | — |
| 20:00 UTC | 20:00 | 15:00 | 1.5:00 | — |
| 21:00 UTC | 21:00 | 16:00 | 2.5:00 | — |
| 22:00 UTC | 22:00 | 17:00 | 3.5:00 | — |
| 23:00 UTC | 23:00 | 18:00 | 4.5:00 | — |
Reading the availability grid
The grid walks all twenty-four UTC hours and prints the local clock time for each participant, marking rows where everyone falls inside their own working day. Any green row is a defensible meeting slot; a blank grid means someone must take a call outside their hours, and that cost should rotate rather than always land on the most junior person.
Designing around a thin overlap
When overlap drops below two hours, use it exclusively for decisions and unblocking. Push status, demos and design reviews into recorded video and written documents with a twenty-four hour response expectation. The handover note at the end of each region's day becomes the highest-leverage artefact the team produces.
Daylight saving breaks your calendar twice a year
The US, EU and UK shift on different dates, and much of Asia, Africa and South America does not shift at all. For two to three weeks each spring and autumn, a fixed UTC meeting drifts by an hour for some participants. Anchor recurring invites to a specific city time zone rather than to UTC so the calendar handles the shift for you.
Working-hour overlap between major hubs (9-17 local)
| Pair | Offset gap | Daily overlap | Best slot (UTC) |
|---|---|---|---|
| London ↔ New York | 5 h | 3 h | 14:00-16:00 |
| London ↔ Bengaluru | 4.5 h | 3.5 h | 09:00-11:30 |
| New York ↔ Bengaluru | 9.5 h | 0 h | None — async |
| Berlin ↔ Dubai | 2 h | 6 h | 08:00-13:00 |
| San Francisco ↔ London | 8 h | 1 h | 16:00-17:00 |
| Sydney ↔ San Francisco | 18 h | 0 h | None — async |
People also ask
What is the best meeting time between London and New York?
Between 14:00 and 16:00 UTC, which is 14:00-16:00 in London and 09:00-11:00 in New York — inside standard working hours for both.
How do I schedule across three time zones with no overlap?
Rotate the inconvenient slot so the same team never absorbs the early or late call, and shift everything except live decisions to written asynchronous handovers.
Should recurring invites be anchored to UTC?
No. Anchor them to a specific city so daylight saving changes are applied automatically. UTC-anchored invites silently drift for half the participants twice a year.
Three worked examples
Same engine, three different starting points — useful if you want to see how sensitive the answer is before you type your own numbers in.
Example 1: your utc offset 0 hours
On the lower / more conservative end. With a narrow overlap, protect the window for decisions only and move status updates to writing.
Example 2: your utc offset 0 hours
A typical middle-of-the-road setup. With a narrow overlap, protect the window for decisions only and move status updates to writing.
Example 3: your utc offset 0 hours
On the higher / more demanding end. With a narrow overlap, protect the window for decisions only and move status updates to writing.
Quick answers about the Remote Team Slot Overlap
What exactly does the Remote Team Slot Overlap work out?
Distributed teams do not fail because of time zones; they fail because nobody measured the overlap before designing the working agreement. You enter your UTC offset, colleague B UTC offset, colleague C UTC offset and working day starts (plus 1 more optional details) and the result panel updates straight away, so you can compare two or three versions of the same question in a few seconds.
What do I need before I start?
Only 4 fields: your UTC offset, colleague B UTC offset, working day starts and working day ends. colleague C UTC offset is optional — leaving it blank simply switches the tool to the simpler estimate.
How is it calculated — reading the availability grid?
The grid walks all twenty-four UTC hours and prints the local clock time for each participant, marking rows where everyone falls inside their own working day. The same maths runs inside this page, so hand-checking the result on paper gives you the identical figure.
Why do two calculators give me different answers for remote Team Slot Overlap?
When overlap drops below two hours, use it exclusively for decisions and unblocking. Different sites pick different assumptions, so always check which method a calculator states before you trust the gap between two numbers.
What does the "Working-hour overlap between major hubs (9-17 local)" table on this page tell me?
It is the reference range this tool works against — 6 rows from "London ↔ New York" (5 h) up to "Sydney ↔ San Francisco" (18 h). Use it to sanity-check whether the number you just calculated sits where you expected it to.
Do I have to press a button or reload the page to see the result?
No. Remote Team Slot Overlap runs completely inside your browser, so the moment you change a value the cards recalculate — there is no submit step, no page reload and no waiting for a server round trip. That also means it keeps working on a weak or intermittent mobile connection.
Is it free, and do you keep what I type?
It is free with no sign-up, no app install and no usage limit. Nothing you enter into Remote Team Slot Overlap leaves your device — the calculation is JavaScript running locally, so there is no upload of your figures to DrHint or anyone else.
Can I use it on a phone?
Yes — the layout stacks to a single column on small screens and the number fields open the numeric keypad on both Android and iOS. Many people bookmark this page or add it to their home screen and re-open it whenever the question comes up.
Anything to be careful about with the result?
Between 14:00 and 16:00 UTC, which is 14:00-16:00 in London and 09:00-11:00 in New York — inside standard working hours for both. Treat the output as a well-grounded estimate for planning, not as a professional, legal or medical decision on its own.
Next useful tool
Count working days between two dates, excluding weekends and any number of custom public holidays, with a weekend-day and calendar-day breakdown.
Find bedtimes and wake times that land at the end of a 90-minute sleep cycle, including fall-asleep latency, so you wake in light sleep instead of deep sleep.
Convert a word count into silent reading time, presentation speaking time and audiobook narration length, with WPM control and a speech-length reference table.
Calculate the exact gap between two dates in years, months, days, total weeks, hours and minutes, with leap-year handling and business-day context.
Check any age gap against the half-your-age-plus-seven rule, see the socially acceptable dating range for both partners and the percentage age difference.
Count down the exact days, weeks and hours to every milestone birthday from your date of birth, plus the weekday each milestone falls on.