Timezone Meeting Planner

What is a timezone meeting planner?

Distributed teams need a single view of “if we meet at 10:00 in New York, what time is that for London, Lagos, and Singapore?” This tool answers that for every hour in your chosen range. Unlike a static world clock, you model per-person busy intervals in local time—minute-accurate, multiple blocks per person, optional overnight ranges—so you can favor rows where no one is in a sleep block, lunch hold, or focus window.

All calculations run in your browser. We do not store your date, selected cities, or busy windows on our servers. When you copy TSV, that text goes to your clipboard only.

How busy periods work

Each busy row uses native time pickers (hours and minutes) in that person’s local timezone. Intervals are half-open [start, end): an entry 12:00–13:00 blocks 12:00 up to (but not including) 13:00. If start is later than end on the clock, the interval crosses midnight—ideal for sleep (22:30–07:00). You can add multiple periods per person (lunch, school run, another focus block).

• Enable “I’m busy locally” to model your own blocks in the anchor zone the same way.
• Rows with a green left border are instants where no one’s local time falls inside any busy period—strong candidates for a meeting.

Who this is for

• Engineering leads scheduling incident reviews or release windows across regions.
• Recruiters and interviewers lining up panel slots without pinging people at 2:00 a.m. local time.
• CSMs and support pods picking a standing sync that stays humane for APAC, EMEA, and the Americas.

FAQ

Does it handle daylight saving changes? Yes—under the hood we use real IANA zones, so future dates follow each region’s DST rules.

Is my data private? Yes. This page does not send your meeting matrix or busy rules to Codeground; it’s client-side only.

Why so many timezones in the list? We show the full IANA set so you can match your OS or calendar app exactly; pick the same name you use elsewhere to avoid one-hour mistakes.