Remote work
Build a roster of your teammates, give each person their own working hours, and instantly see who is online right now and which hour of the day works for the most people at once. Save the team, share the link, or embed the live overlap on your own site.
2 of 4 in working hours now
Pivot zone: You. Times update every minute.
01:00–14:00
2 of 4 in hours
Outside hours: You, Sam
14:00–17:00
1 of 4 in hours
Outside hours: Sam, Lena, Priya
22:00–00:00
1 of 4 in hours
Outside hours: You, Sam, Lena
| Teammate | 00 | 01 | 02 | 03 | 04 | 05 | 06 | 07 | 08 | 09 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| You | 00 | 01 | 02 | 03 | 04 | 05 | 06 | 07 | 08 | 09 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 |
| Sam | 03 | 04 | 05 | 06 | 07 | 08 | 09 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 00 | 01 | 02 |
| Lena | 08 | 09 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 00 | 01 | 02 | 03 | 04 | 05 | 06 | 07 |
| Priya | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 00 | 01 | 02 | 03 | 04 | 05 | 06 | 07 | 08 | 09 | 10 | 11 |
| Overlap | 1 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 1 |
Each cell is a teammate's local hour. Green cells fall inside that person's working hours. The bottom row counts how many are free at each pivot-zone hour.
Set each teammate's real working hours and pick a pivot zone to read the grid in. Your roster is saved in this browser; the share link reproduces it for anyone.
Most time-zone tools are built around a single conversion: you have one time in one place and you want it in another. That is a useful answer, but it is not the question a distributed team lives with day to day. Their question is recurring and multi-person. They have a fixed group of people in fixed cities, each with their own working day, and they need to know two things on repeat: who can I message right now without waking someone, and when can we get everyone on a call without anyone resenting it. Those answers do not come from a converter because a converter has no memory of your team and no concept of each person's hours. This planner is built around exactly that team model. You enter the people once, set their real hours, and from then on the tool keeps answering the live who-is-around question and the best-slot question for you.
The naive way to find an overlap is to assume everyone works the same nine-to-five and slide those windows around the globe. It looks tidy and it is usually wrong. Real teams are full of small, deliberate variations: an early-bird engineer who starts at seven to get focus time, a parent who finishes at four and logs back on after bedtime, a colleague in India whose office runs ten to six. Those couple of hours of difference are exactly the hours that decide whether a meeting is possible. This planner gives every teammate their own start and end, and the overlap score for each hour counts a person as available only if that hour falls inside the window you set for them specifically. The result is a schedule you can actually defend, because it is built from how your team really works rather than from a convenient fiction.
The top of the tool answers the immediate question. Each teammate shows their current local time and a clear online or offline badge, and offline teammates show how long until their working day begins, so you know whether to wait twenty minutes or until tomorrow. Below that, the 24-hour grid lays the whole day out in your pivot zone. Every cell is a teammate's local hour at that moment, the green cells are the hours that fall inside their working window, and the bottom row tallies how many people are free at each pivot hour. Scanning that bottom row tells you instantly where the day's sweet spot is. The best-window cards above the grid do the scanning for you, surfacing the longest, fullest runs and naming anyone a given window leaves out.
Stretch a team across enough longitude and the comfortable overlap shrinks to an hour or disappears entirely. A San Francisco to Sydney pairing has almost no shared working hour at all. Pretending otherwise is how someone ends up dialing in at 11pm every week. The planner names the people each window excludes precisely so you can make the trade-off with eyes open. The healthy responses are well understood: rotate the painful slot so the cost is shared rather than always landing on the same person, default to recorded or written updates for the group that cannot reasonably attend live, and reserve real-time meetings for the moments that genuinely need them. The async-first guide linked below goes deeper on building a rhythm that does not depend on a perfect overlap that does not exist.
The team you build is remembered in your browser, so you are never re-entering the same people. When you want to hand the exact roster to someone else, the share link encodes every teammate and their hours, so a colleague opening it sees the same overlap you do. The embed option publishes a live version on your own site, which distributed teams often pin to a handbook or status page so anyone can check at a glance who is around and when the team can meet. It keeps ticking, respects the visitor's light or dark theme, and links back here.
To lock in a single specific meeting once you have found a window, the meeting scheduler turns it into a slot with a shareable invite. To simply watch the current time in your teammates' cities side by side, use the world clock, and to convert one specific time across zones, the time zone converter does that in one step. For the bigger picture on running a team without a shared working hour, read the async-first standup playbook.
A converter answers a one-off question: what is 3pm in Berlin in New York time. This planner models a recurring problem instead. You give each teammate a name, a city, and their own working hours, and it shows two things a converter cannot: who on the team is online at this exact moment, and which hour of the day puts the most people inside their own working window at once. It is built for the question distributed teams actually ask, which is not what time it is somewhere but when can we all meet without anyone taking a call at midnight.
Yes, and that is the whole point. Real teams are not uniform. One person starts at 7am, another finishes at 6pm, someone in India works 10 to 6 local. The overlap grid scores each hour by how many people are inside their personal window, not a single shared 9-to-5 applied to everyone. That is why the best-window suggestions are trustworthy: a slot only counts a teammate as available if it falls inside the hours you actually set for them.
The pivot zone is the reference clock you read the overlap grid in, usually your own. The grid runs across 24 hours of the pivot day, and each cell shows what local hour that pivot hour maps to for every teammate. Switching the pivot does not change who is available, it only re-labels the columns so you can plan in whichever city's time feels natural to you. Most people leave it on themselves; a manager scheduling for a remote report might switch it to the report's zone.
Your roster is stored in your browser, so the same team is waiting for you on every visit without any account. The share button produces a link that encodes the entire roster, including names and each person's hours, so a colleague who opens it sees exactly the team you built. The embed option drops a live version onto your own intranet, handbook, or status page, which is a common way for distributed teams to publish their working-hours overlap in one place.
Yes. Every teammate is driven by their city's IANA time zone, the same authoritative dataset operating systems use, so the offset shifts automatically on each region's daylight saving date. Because different countries change their clocks on different weekends, the overlap between, say, the US and Europe genuinely narrows or widens for a couple of weeks each spring and autumn, and the grid reflects that rather than assuming a fixed gap. The live status and the best windows are always computed from the current real offsets.
On a team that spans more than about ten hours of longitude there often is no hour when everyone is inside their own working window, and the planner is honest about that. Each suggested window lists the teammates it leaves out, so you can see the trade-off explicitly. The usual answers are to rotate the meeting time so the same person is not always the one taking the awkward slot, to record the session for whoever cannot attend, or to move to asynchronous updates for that group, and the related guides linked below cover each of those approaches.