Meeting planners & scheduling
Team availability visualizer
Map your team's working hours onto a single day. Set the workday, add everyone's cities, and read the heatmap to see exactly when the most people are online at once.
How to use the team availability visualizer
List your team's locations
Add a city for each person or each office. The visualiser works from real zones, so two people in the same country but different states are shown correctly apart.
Set the working day
Adjust the working-hours window to match your team's norms. A 9-to-5 assumption is wrong for plenty of teams and produces overlaps nobody would actually attend.
Read the coverage
The stacked view shows how many people are inside working hours at each moment of the day, so you can see both your peak collaboration window and your thinnest coverage.
Find the gaps
Look for hours where coverage drops to zero. Those are the windows where nothing gets answered — useful to know before you promise a response time.
Reading a distributed team's real working day
Once a team spans more than about six hours of longitude, its working day stops being a single block and becomes a wave. There is a period when the east is winding down and the west is starting up, which is the only time everyone is genuinely available, and it is usually much shorter than people assume.
Making that visible changes how a team operates. If the shared window is two hours, spending it on a status meeting is expensive — that is the time for the decisions that genuinely need everyone. Everything else moves to writing, which is the actual reason well-functioning distributed teams are written-first. It is not a culture preference; it is arithmetic.
Coverage matters as much as overlap. A team spread thinly across many zones may have almost no shared hour but excellent round-the-clock coverage, which is exactly what you want for support and exactly wrong for a design team that needs to think together. Seeing both numbers helps you tell which shape you have built.
The gaps are worth naming explicitly. A stretch with nobody working is fine as long as everyone knows it exists and no promise depends on it. Discovering it during an incident is worse than planning around it.
When you'd reach for it
Planning a hire
See what a candidate in a new region would do to your coverage and your shared window before you commit.
Setting core hours
Base a core-hours policy on where the overlap actually is rather than on headquarters' clock.
Support rota design
Find the hours with no coverage and staff or document around them.
Onboarding a new team member
Show them, on day one, when their colleagues are actually reachable.
Justifying async practice
A picture of a two-hour shared window makes the case for written updates better than an argument does.
Incident response planning
Know which region will be awake when something breaks at a given hour.
Questions & answers
- How is availability decided?
- Each city is 'available' at an hour of your day when its local time falls inside the working window you set. The window applies to everyone, so you can model a shared workday.
- What does the bottom row show?
- The count of people available at each hour of your day. The brass cells mark the hours with the most overlap — your best windows for a all-hands or standup.
- Can I change the working hours?
- Yes, drag the start and end sliders to widen or shift the workday and watch the overlap change.