Meeting Time Planner
Find working-hour overlaps across cities to schedule calls — e.g. the best time to call the US or UK from India.
Common working hours
No overlap in these hours — try widening the window
Updates live as you type
Frequently asked questions
Because India is far ahead of the US, standard 9–6 windows barely overlap. Early morning IST often maps to US afternoon/evening — widen the working hours here to surface workable slots for your specific cities.
For each hour of the day it checks whether the local time in every selected city falls within your working-hours window, then lists the hours where all cities are simultaneously “in office”.
Across very large offset gaps (e.g. India and the US west coast), standard working hours genuinely don’t intersect. The tool tells you so — a real, useful answer — so you can plan an early or late call instead.
Yes. Each city’s current offset, including daylight saving, is resolved live from the IANA database, so the overlap reflects the real clock difference today.
Find a meeting time that works for everyone
Coordinating a call across continents is a classic headache, especially from India where the offset to Western teams is large. This meeting time planner finds the hours when every selected city is simultaneously within working hours.
Pick up to three cities, set your working-hours window (default 9 to 18), and the planner checks each hour of the day: it keeps only those where the local time in *all* cities falls inside the window. The result shows how many overlapping hours exist and lists good slots in your first city's local time, plus the equivalent UTC hours.
How the overlap search works
Under the hood, the planner walks through all 24 hours of a UTC day and, for each one, converts it into the local time of every selected city. It keeps only the hours where every single city's converted local time falls inside your working-hours window — effectively an intersection across however many cities you have selected, not just a comparison between two. Adding a third city can shrink the overlap sharply even when two of the three already overlap comfortably, since the window now has to satisfy all three simultaneously.
A candid note about very large offset gaps
This tool surfaces an honest limitation rather than hiding it: India and the US East Coast have almost no overlap in a strict 9-to-6 working day, and India and the US West Coast have effectively none at all, because the clock gap between them is close to or greater than the width of a standard working day itself. Rather than forcing a misleading answer, the planner reports zero overlapping hours in these cases — your genuine cue to widen the window and consider an early-morning or late-evening call on one side instead of pretending a standard workday can bridge the gap. Daylight saving is handled automatically via the IANA database for every city involved, so the overlap you see reflects the real clock gap for today's date, not a stale fixed offset that would drift wrong twice a year.