🌍 Time Zone Meeting Planner

How to Schedule Meetings Across Time Zones Without Losing Your Mind

Every distributed team eventually hits the same wall: someone sends a meeting invite for "2pm," and three people on three different continents start doing mental arithmetic. Is that 2pm EST? 2pm GMT? Does London observe BST right now? What time is that for the person in Bengaluru who has a 5:30 offset? By the time everyone figures it out, someone has already missed the call.

This guide walks you through using the Time Zone Meeting Planner above — and more broadly, how to think about scheduling across time zones so you can stop doing the math manually every single time.

Step 1: Understand Why Time Zone Math Keeps Tripping Teams Up

The surface problem looks simple: just add or subtract hours. But three things make it genuinely hard in practice. First, daylight saving time (DST) shifts happen at different dates in different countries — the US moves in March, the EU moves in late March, and many countries (India, Japan, China, most of Africa) never observe DST at all. So the offset between New York and London can be 5 hours in February but only 4 hours in late March. Second, not all offsets are whole hours. India sits at UTC+5:30, Nepal at UTC+5:45, and parts of Australia at UTC+9:30. Third, a "working day" slot that seems reasonable in one zone can land at 11pm or 5am for a colleague, and people are reluctant to say so directly.

Step 2: Set the Meeting Date First

Before you touch anything else in the planner, pick the date. This matters enormously because DST status changes the offsets. The tool uses the actual UTC offsets for that specific date, so a search for next Tuesday accounts for whether any of your selected cities are currently in or out of daylight saving. Click the date field at the top and choose your target day.

Step 3: Define Realistic Working Hours

The default is 9am to 6pm, which is a reasonable starting point. But think about your team's real constraints. Does your engineering team in Berlin actually start at 10am? Does your sales team in New York frequently have calls until 7pm? Widen the window if your team is flexible. Narrow it if you want to protect lunch breaks or school pickup times. The "Work Day Starts" and "Work Day Ends" dropdowns apply the same window to every zone — so if you set 9am–6pm, the tool looks for hours where everyone's local clock reads between 9:00 and 17:59.

Step 4: Add Your Team's Time Zones

The planner starts with three zones pre-loaded: New York, London, and Mumbai/Kolkata. Click the dropdown in any row to change it. Each row also has a short text field on the left where you can type a custom label — "Berlin office," "Client in Dubai," "Sarah (Auckland)" — so the results make sense at a glance instead of showing raw city names.

To add more zones, click the + Add Zone button. You can compare up to as many zones as you need, though in practice anything beyond five or six starts to get visually crowded. If you add the same zone twice by accident, the calculator silently deduplicates them when running the search.

Step 5: Read the 24-Hour Timeline

After clicking Find Overlapping Hours, the timeline appears above the results. Each row represents one time zone. The horizontal axis runs from midnight to midnight local time for the reference UTC day. Three colors tell the story:

• Light gray — outside of that zone's working hours. Nobody should be expected to take calls here.
• Green — within that zone's working window, but other zones may not also be available simultaneously.
• Orange — the sweet spot. Every single zone you've added is simultaneously within working hours right at this 30-minute block.

You can hover over any individual segment to see the exact local time for that zone at that moment. This is useful when someone questions the result — you can point to the block and confirm it shows 9:30am in Tokyo and 2:30pm in London at exactly the same UTC moment.

Step 6: Use the Meeting Windows Summary

Below the timeline, the tool groups consecutive orange segments into labeled windows. Each window shows the exact local start and end time in every zone, along with the total duration. If you have a 4-hour overlap between New York and London, it might show "Window 1 — 240 min (4h)" with times like "Mon 9:00 AM to 1:00 PM" for New York and "Mon 2:00 PM to 6:00 PM" for London.

These windows are what you paste directly into a calendar invite or Slack message. No conversions, no back-and-forth. Just: "We have availability from 9am–1pm EST / 2pm–6pm GMT. Proposed time: 10am EST / 3pm GMT. Does that work?"

Step 7: Handle the "No Overlap" Situation Constructively

Some zone combinations genuinely have zero overlap on a standard work schedule. New York and Mumbai are a classic example — when Mumbai's business day starts (9am IST = 3:30am EST), New York is asleep, and when New York starts (9am EST = 7:30pm IST), Mumbai's day is over. The planner will tell you this directly rather than suggesting a 5am call nobody asked for.

When you hit this wall, you have four real options. First, extend hours on one or both ends — if New York can start a call at 8am and Mumbai can stay until 7pm, a narrow window opens. Second, rotate the burden — one team takes an early call one week, the other takes a late one the next. Third, accept that real-time synchronous meetings across certain zone pairs simply are not practical, and switch to async tools: recorded video updates, shared documents, or a strong written handoff protocol. Fourth, stagger your team's schedules intentionally — one person in a "bridge" zone (like Dubai or London) who overlaps with both sides.

Step 8: Check Around Holidays and DST Transitions

Run the planner for the specific date, not just "any Tuesday in March." The last Sunday in March is when Europe switches clocks, so a meeting that worked cleanly on March 20 might shift by an hour on March 31. Similarly, the US switches in early November, which temporarily closes a one-hour gap with the UK. Build the habit of checking the tool for the actual scheduled date, especially for recurring meetings that span months.

A Quick Reference for Common Zone Pairs

If you work with the same zones repeatedly, it helps to know the rough patterns. New York and London overlap for about 4–5 hours in winter (9am–1pm EST). San Francisco and London have almost no overlap on standard hours — maybe 1 hour in the late afternoon UK time. Singapore and Sydney overlap well (both in UTC+8 to +11 territory). Berlin and Nairobi share almost the entire day since they are only 2 hours apart. Once you know your team's core pairs, you internalize the windows quickly — but use the tool whenever a new team member or client location enters the picture, because even one new zone can shift the entire picture.

The goal is not to be clever about time zone math. The goal is to stop doing it manually. Use the tool, paste the result, and spend that saved mental energy on the actual work.