ChronoClockTime intelligence
UTC
--:--:--

Team

Team time zones

One bar per person, laid out on your own 24-hour clock. The filled band is their working day, the vertical line is right now, and the band at the bottom is the stretch when nobody has to take the call at a strange hour.

The team day

reading your time zone

Working out your local time zone. The timeline appears as soon as the page knows what clock you are on.

There is no hour today when every person on this roster is inside their own working hours. Either move a meeting to the edge of somebody's day on purpose, or split it into two calls and write the decision down for the third zone.

Roster

3 people

The roster is saved in this browser under cc-teamtz. The share link carries the whole team in the address itself, so nothing is uploaded anywhere.

3 on the rosterno shared hoursUTC

How to use the team time zone view

Build the roster once. Search a city for each person, correct the name, and set the hours they actually work rather than the hours in their contract. Someone who starts at 07:30 to be home for the school run has a different overlap than the default nine to five, and the bar is only as useful as the hours you put in it.

  1. Read every bar against the ruler at the top, which is your own clock. A band that starts three columns to the left of yours means that person is three hours ahead of your morning.
  2. Look at the bottom band before you book anything. It marks the minutes when every person on the roster is inside their own working day.
  3. If the bottom band is empty, say so out loud instead of picking a time and hoping. Somebody is going to take that call outside their day, and it should be a decision rather than an accident.
  4. Press Copy team link and paste it in the channel. Whoever opens it sees the same roster on their own clock, which is usually the fastest way to end a thread about what time works.

Why the bars move on their own

Offsets are computed from the real time zone rules in your browser, not from a fixed number of hours. When the United States changes clocks two weeks before Europe does, the bands shift for that fortnight and the overlap changes with them. That gap is the single most common cause of a missed call in March and October, and the view shows it instead of hiding it.

Picking a time when nothing overlaps

Teams spread across more than about nine hours of longitude often have no shared working hour at all. The usual answers are to rotate which zone takes the awkward slot week by week, to keep one short call and move everything else to writing, or to accept a standing thirty minute overlap at the edge of two days and protect it. All three work. Pretending an overlap exists does not.

Frequently asked questions

Where is my team stored?

In this browser, under the local storage key cc-teamtz. Nothing is sent to a server, so the roster does not follow you to another device unless you send yourself the share link.

What is in the share link?

The whole roster, encoded into the part of the address after the hash: names, zones and working hours. Browsers never send that part to a server, so the link travels through your chat tool and nowhere else. Anyone who opens it can edit the roster in their tab, and nothing changes for you unless they save it.

Does it handle daylight saving time?

Yes. Each band is placed by asking the browser what the offset for that zone is on that day, so bars move when a zone changes clocks and the overlap is recalculated. Zones that never change, such as India or Arizona, simply stay put while the ones around them shift.

Why does someone's band appear split in two?

Because their working day straddles the edge of your day. Someone in Tokyo working 09:00 to 18:00 may be at work during your late evening and again during your early morning, which is two pieces of the same working day seen from your clock.

Related tools