Your PM in San Francisco sends a meeting invite for 10:00 AM. Your lead engineer in Berlin squints at the calendar and wonders if that's their morning or their evening. Your support lead in Mumbai wants to know if this means they'll be up past midnight. Three people, three timezones, one meeting — and this kind of low-grade friction shows up every single day on distributed teams.
The underlying problem is that humans think in "wall clock" time ("10 AM means morning") while computers need to think in UTC offsets ("UTC-8 in winter, UTC-7 in summer") and most of us live somewhere in between those two models. Daylight saving time makes it worse: America/New_York is UTC-5 for half the year and UTC-4 for the other half (with a one-week offset against Europe's DST schedule that wrecks meetings every March and November). Memorize the wrong offset and you silently book someone into a 6 AM call they have no intention of attending.
This tool takes a single moment — say, "Tuesday 2:00 PM in New York" — and instantly shows you what that same instant looks like in every city you care about. Pick five or six offices, enter the time in any one of them, and the comparison table updates live. Each row shows the local time, the UTC offset currently in effect for that zone, whether DST is active right now, and the day-of-week — because "Tuesday in NY but Wednesday in Tokyo" matters when someone on the call is technically in tomorrow.
The day-shift indicator is the part that saves the most scheduling headaches. A meeting at 4:00 PM in San Francisco is still Thursday locally, but it's already Friday morning in Sydney and Friday late-evening in Tokyo. If your colleague in Sydney is strict about not working Fridays, that invisible day boundary quietly excludes them. It highlights cross-day shifts in color so you catch them before the invite goes out instead of in the awkward "wait, what day is it for you?" reply.
The tool always uses IANA timezone identifiers (America/New_York, Europe/Berlin, Asia/Kolkata) rather than fixed UTC offsets. That distinction matters: a hardcoded "-5" is wrong four months of the year for New York; "America/New_York" is correct in every month, including the DST switch weeks. The full timezone list is searchable — type a city name, a country, or an abbreviation and it narrows down. That's because abbreviations themselves are ambiguous: "CST" means Central Standard Time in the US, China Standard Time, Cuba Standard Time, and Australia's Central Summer Time simultaneously, and guessing wrong by 13 hours is embarrassing in a meeting title.
The overlap-planner tab answers the harder question: "When are we all available?" Pick your cities, set a minimum overlap (say, 1 hour between 9–5 local in each), and it surfaces the windows. It's rough — it doesn't know about anyone's local holiday or lunch break — but it reduces 10 rounds of Slack negotiation down to opening one link.
Common scenarios where this actually saves you: booking a weekly sync across a US-EU-APAC team without making any one region suffer permanently, debugging a cron job scheduled in UTC that fires at an unexpected local hour for your users, explaining to a non-technical stakeholder why "tomorrow" in one region is "yesterday" in another during handoff docs, setting SLA deadlines that expire at "end of business" in a specific region, and verifying that a CI/CD deploys at a window you chose rather than at midnight UTC because someone forgot to convert.