Time Zone Meeting Planner
Add your team's cities and working hours, then find when everyone is free.
The Hidden Cost of Scheduling Across Time Zones
Every distributed team has a version of this story: someone in Berlin sends a calendar invite for 10 AM — which lands at 4 AM in San Francisco. The meeting gets rescheduled. Then rescheduled again. By the time everyone actually joins, three people are exhausted, one is eating lunch, and the person in Singapore logged on at midnight out of sheer obligation. Nobody performed their best thinking. The decision that needed making got punted to next week.
This is not a minor inconvenience. Studies on remote teams consistently show that scheduling friction is one of the top three causes of meeting fatigue, and meeting fatigue correlates directly with disengagement. When your team spans more than two or three time zones, the simple act of finding a shared slot becomes a surprisingly complex puzzle — one that most people solve with a combination of guesswork, a quick Google search, and hopeful calendar math.
Why Mental Time Zone Math Breaks Down
The human brain handles offsets reasonably well up to two cities. Add a third, especially one with a half-hour or quarter-hour offset like India (UTC+5:30) or Nepal (UTC+5:45), and the mental arithmetic becomes genuinely unreliable. People make mistakes. "Oh, Singapore is eight hours ahead of London" is correct during GMT, but wrong during British Summer Time. Daylight saving transitions — which happen on different dates in Europe, North America, and Australia — quietly shift relationships between cities by an hour, and nobody remembers to recalculate.
The result is wasted time and, occasionally, embarrassing no-shows. A product manager at a mid-sized SaaS company once described their team's approach as "email the invite, wait to see who complains, then fix it." That process typically added two days to any meeting that involved four or more cities.
What a Good Overlap Tool Actually Needs to Do
The solution sounds simple: take each person's working hours, convert them all to UTC, find the intersection, and convert back. But the implementation details matter. Working hours aren't universal — a Tokyo team might run 8 AM to 5 PM while a New York freelancer prefers 10 AM to 7 PM. The tool needs to respect each city's custom hours rather than assuming a generic 9-to-5. It also needs to handle half-hour timezone offsets correctly, show results in each person's local time (not UTC), and be honest when no full overlap exists rather than silently showing nothing.
The Time Zone Meeting Planner above does exactly this. You add each city from a dropdown of 35 major time zones, set custom start and end times per location, then hit the button. The algorithm works in 30-minute increments across all 24 UTC hours, checks whether each increment falls within every city's working window simultaneously, and groups consecutive valid slots into a readable window with duration.
Reading the Results: Overlap Windows vs. Partial Matches
When a full overlap exists — meaning at least one 30-minute block falls within every city's working hours — you get a green "Overlap Window" card showing the start and end time in each city's local format, plus the total duration available. A three-hour window between New York and London becomes "9:00 AM – 12:00 PM" in New York and "2:00 PM – 5:00 PM" in London. You pick a slot within that window and everyone's happy.
When no full overlap exists, the tool doesn't just display an error and leave you stranded. It calculates which time slots satisfy the most cities and shows the top "partial match" options, clearly marking which cities are in-hours and which are outside. This matters because the real-world decision is often "we can't get everyone in a perfect slot, so which city takes the early morning hit this week?" Having that information surfaced clearly makes the conversation much faster.
The 24-Hour Visual Grid
Below the text results, a grid shows every city's working status across all 24 UTC hours simultaneously. Green cells are working hours, darker amber cells are the one-hour buffer zones on either side (useful for spotting "almost" overlaps), and dark cells are off-hours. Bright green highlights mark confirmed overlap columns. This visual is particularly useful for asynchronous planning — you can screenshot it and drop it into a Slack thread to show the team exactly where the constraints lie, which often moves the negotiation forward faster than a text description would.
Practical Strategies When No Overlap Exists
A New York plus Tokyo combination with standard 9-to-5 hours produces zero overlap — they're 14 hours apart and business day windows simply don't cross. This is a common source of frustration for teams that include North American and East Asian colleagues. The practical workarounds fall into three categories.
The first is schedule rotation: alternate who takes the inconvenient slot each week. This distributes the burden rather than always having Tokyo log on at midnight. The second is to widen working hours slightly — if one city extends to 7 PM and the other starts at 7 AM, a narrow window often appears. The third, increasingly popular, is to move the synchronous requirement entirely: record a video update, collect async feedback, and reserve live meetings for decisions that genuinely can't happen in writing. Many teams find that once they see the true overlap gap in a tool like this, they realize the meeting could have been a Loom video all along.
A Note on Daylight Saving Time
The planner uses your browser's built-in Intl API with fixed timezone identifiers, which correctly account for DST based on the current date. This means "America/New_York" automatically applies EST in December and EDT in July — you don't need to remember which offset applies right now. The tradeoff is that results reflect today's DST status; if you're planning a meeting three months from now and a transition falls in between, recalculate closer to the actual date.
Getting the Most Out of the Tool
A few habits make this significantly more useful in daily practice. First, save your regular team configuration. Copy the cities and hours into a shared document so anyone on the team can quickly re-run the calculation without reassembling it from scratch each time. Second, use the buffer zones on the visual grid to have honest conversations about flexibility — if Singapore's working day ends at 5 PM but the overlap slot ends at 5:30 PM, a brief conversation about whether a 30-minute extension is feasible is much better than silently scheduling something that puts someone in an awkward position. Third, when partial matches are the only option, present the tool's output rather than just the conclusion: showing teammates the constraint visualization tends to reduce friction compared to just announcing "sorry, Tokyo has to join at 8 AM."
Distributed work is not going away, and time zone diversity on teams is increasingly common rather than exceptional. The scheduling overhead that comes with it doesn't have to eat into actual work time. A few seconds in a planner like this, run before every cross-timezone invite, turns a chronic source of small frustrations into a non-issue.