Time zones
Team Time Zone Planner
Add teammates with their own timezones and working hours to see overlapping windows across a distributed remote work team.
Zones and times stay in this tab. Rosters are not uploaded.
How zones are handled
Roster mode: each row is a person with their own IANA zone and work range so overlaps respect individual hours, not one global daytime band. Daylight saving is applied for the chosen date via the browser. Empty overlap is reported honestly (no invented late-night compromise). Suggested chips speed picking a shared window once an overlap exists. Scale down to Working Hours Overlap Calculator when you only need two custom ranges, or use Meeting Time Finder when everyone shares the same daytime band.
How to use it
Add a row per person with IANA zone and local working hours, pick the meeting date, then read the overlap chips. Copy a chip into the invite only after everyone confirms the local labels. If overlap is empty, adjust one person’s hours or move the conversation to async handoff planning.
Assumptions
Each roster row uses its own IANA zone and work range on the date you pick. Overlap is the intersection of those ranges after DST is applied by the browser. Suggested chips are helpers, not calendar bookings.
Worked example
Scenario
Date 2026-08-26 roster • Ana · Europe/Zagreb · 09:00–17:00 • Sam · America/New_York · 09:00–17:00 • Priya · Europe/London · 09:00–17:00
Output
Overlap chips (UTC 13:00–15:00): • 15:00–17:00 Zagreb • 09:00–11:00 New York • 14:00–16:00 London Suggested pick: 15:30 Zagreb / 09:30 New York / 14:30 London If Manila 09:00–18:00 were added instead of London, three-way overlap would be empty (Manila’s day ends before New York’s morning starts).
Quick comparison
| Option | Detail |
|---|---|
| Shared daytime band | Prefer Meeting Time Finder when everyone accepts the same local window. |
| Per-person roster | Use this planner when hours differ by teammate. |
| Two-person only | Working Hours Overlap Calculator is enough for a pair. |
| Finish vs start | Remote Handoff Time Planner answers shift-gap questions. |
More coordination scenarios
- Zagreb 09-17, New York 09-17, Manila 09-18 on the same date.
- Spot an empty overlap before you send calendar holds.
- Drop one region temporarily to see whether a two-hub window opens.
Practical use cases
- Three regions need one ritual window that respects each local day.
- An interview loop spans timezones and needs real local hours per person.
- You want to spot an empty overlap before you send calendar holds.
- A distributed standup needs a window that does not force anyone into midnight.
- You are comparing a three-person roster against a simpler two-city overlap tool.
Limitations
Rosters are not saved to an account. Does not read Google Calendar or Outlook free/busy. Does not account for lunch gaps inside a work range unless you shorten the hours yourself. Large rosters still need human judgment when the only overlap is a thin slice.
Timezone questions
- How is this different from Meeting Time Finder?
- Meeting Time Finder uses one shared daytime band for every zone. This planner lets each teammate keep their own working hours.
- What happens when overlap is empty?
- You get a clear no-overlap result. Adjust hours, drop a region, or plan async instead of forcing a bad slot.
- Are rosters saved on a server?
- No. Zones and times stay in this tab. Rosters are not uploaded.
- When is Working Hours Overlap enough?
- When you only compare two people. This planner is for three or more roster rows with individual hours.
Timezone math uses your browser’s IANA data for the chosen instant. How our tools work · Editorial policy · Contact