Conference Call Scheduler

The score is the percentage of active locations whose local meeting time falls entirely within the defined business hours window (default 09:00–18:00). A score of 100% means every participant joins during normal working hours; a lower score flags that at least one location is outside that window.

New York and Singapore are roughly 12–13 hours apart, making a mutually convenient business-hours slot almost impossible. The scheduler will show a low overlap score and flag which location falls outside working hours, so you can decide who makes the early-morning or late-evening compromise.

Yes. The calculation uses the UTC offsets baked into the IANA time-zone identifiers (e.g. America/New_York, Europe/London). Because the offsets reflect real-world DST rules for the chosen date, times automatically adjust when a region is observing summer time.

The scheduler currently supports up to four locations. If your team spans more regions, choose the four locations with the widest spread first — they are the hardest to reconcile — and the overlap result will highlight the most constrained window for everyone.

A common sweet spot is 08:00–09:00 US Eastern time, which translates to 13:00–14:00 in London and 18:30–19:30 in India. It keeps the US East Coast within core hours and India just at the edge of working hours. Enter these locations in the scheduler to verify and fine-tune.

Enter the hour (in 24-hour format) when participants in each location typically start and finish work. The default is 09:00–18:00, which suits most office environments. If your team operates a different shift — say 08:00–17:00 — update both fields before running the calculation.

Yes — the date determines the exact UTC offset for each time zone on that day, which matters around DST transitions. Always enter the actual meeting date rather than today's date if you're planning weeks ahead.

UTC (Coordinated Universal Time) is the global reference clock with no offset and no DST adjustment. Selecting it is useful when one participant works in a location that officially runs on UTC, or when you simply want to anchor the meeting to the universal baseline for easier manual cross-checking.