Remote Team Time Zone Planner

Overlap is the real constraint on a distributed team

Distributed teams tend to discover their overlap window by accident, usually when a recurring call has quietly settled at a time that suits the largest office and nobody else. Making the overlap explicit changes the conversation: once you can see that three people share six hours and a fourth shares ninety minutes, the scheduling problem stops being a matter of opinion.

The timeline shows this directly. Each person's working hours are banded across a shared 24-hour axis, so the columns where the bands stack up are the team's genuine collaboration window. Everything outside it is asynchronous work, whether or not the team has admitted that yet.

Spreading the cost rather than concentrating it

When a team spans more than about eight hours of longitude, someone is going to be inconvenienced. The question is whether it is the same person every week. A ranking that only maximised the total score would reliably pick slots that suit the majority and quietly sacrifice whoever is furthest out.

This planner uses the worst individual outcome as its main tie-break, which biases it towards slots that are tolerable for everyone over slots that are excellent for most. Combined with rotating the slot between the two or three top-ranked options, that is usually enough to stop one time zone permanently absorbing the cost of the team's geography.

When the answer is not to meet

Some pairings have no honest overlap. India and the US west coast are the clearest example: a 9:00 AM to 6:00 PM day in Bengaluru and the same day in San Francisco do not touch, so any synchronous call takes place in somebody's evening or before somebody's breakfast.

Seeing that plainly is a useful result. Teams in that position generally do better with a written handover at the edges of the day and a short synchronous call once a week rather than a daily stand-up that one side resents. The planner will still rank the least bad options if you need them, and it will show you exactly what each one costs.

• Bengaluru and San Francisco: no overlap within two standard working days.
• Bengaluru and New York: a narrow overlap in the Indian evening.
• Bengaluru and London: several hours of genuine afternoon overlap.
• London and New York: the widest common window, most of the London afternoon.

Keeping the team current

People move, contracts change and clocks shift twice a year in about half the world. Saving the team means you are editing one person's row rather than rebuilding the whole picture each time, and because offsets are derived rather than stored, the daylight saving part maintains itself.

Teams are saved in this browser only. For a team that several people need, share the link instead: it reproduces the cities and hours for whoever opens it, without carrying anybody's notes.