Best Time to Schedule a Meeting Across Time Zones (2026)

The best time to meet across time zones is the window where both regions are inside normal working hours, and for most pairs that window is short and predictable. The single most useful rule: schedule to the earlier side's late morning. When you meet in the earlier region's morning, it is the later region's afternoon or evening, so both sides are awake and mostly at their desks.

This guide is the lookup table, not the process. If you want the full method for running the poll, rotating the pain, and communicating the zone clearly, our pillar on scheduling meetings across time zones covers that, and the interactive meeting time zone planner does the math for your exact cities and date. What follows is the answer: the realistic overlap window for every common region pair, given in both locals.

A quick definition of "reasonable hours" used throughout, the same model the planner uses: 9:00 to 17:59 local is ideal, 7:00 to 8:59 and 18:00 to 21:59 are awake but outside office hours (fine for the occasional call), and 22:00 to 6:59 is sleep and should not be a standing ask.

Here is the shared working window for the pairs people schedule most, in each side's local clock. Times assume northern-summer clocks (US on daylight time, UK on BST); read the daylight-saving note below the table, because these shift by an hour for a few weeks a year. Half-hour offsets (India at UTC+5:30) and the date line (Australia) are built in.

US East Coast and Europe are the friendliest pair to schedule, with a solid three-hour overlap inside office hours. Meet in the US morning. At 9:00 to 11:00 in New York it is 14:00 to 16:00 in London and 15:00 to 17:00 in Berlin or Paris, so everyone is at their desk. Nextutils, testing New York and London, found the same roughly three-hour shared block, checked against real working hours.

The US West Coast is harder because the gap widens to eight hours with the UK. Your realistic overlap shrinks to the very start of the Pacific day: 8:00 to 9:00 in Los Angeles is 16:00 to 17:00 in London, which is late afternoon for Europe and early for the coast. If your group mixes both US coasts with Europe, push to about 12:00 to 13:00 Eastern (9:00 to 10:00 Pacific), which still lands before 19:00 in Central Europe.

US and Asia is the pair with no comfortable answer, because when one side is working the other is asleep. For the US and India there is no hour inside both sets of office hours, so the fairest slots sit at the edges: 8:00 to 9:00 on the US East Coast is 17:30 to 18:30 in India (an hour later, 18:30 to 19:30, when the US is on standard time). Early on the US West Coast, 7:00 to 8:00 Pacific, maps to Indian evening around 19:30 to 20:30.

US and East Asia (Singapore, Hong Kong, Tokyo) is tighter still and usually crosses into the next day. The practical move for these pairs is to stop hunting for a perfect slot and instead rotate the meeting time so the painful hour moves between regions each occurrence, record every session, and push status updates into a shared document so the live call stays short. India's UTC+5:30 offset also breaks mental math, which is exactly the kind of error the time zone planner removes by computing from a real instant.

Europe and Asia overlap comfortably in the European morning and the Asian late afternoon or evening. At 9:00 in London it is 16:00 in Singapore or Hong Kong, so a London-morning call is an Asia end-of-day call, which most teams find workable. London and India are closer still, with the whole London morning landing in the Indian afternoon.

Australia is the date-line case, and the thing to remember is that you meet across days. When it is late afternoon on the US East Coast it is already the next morning in Sydney: 17:00 to 19:00 in New York is about 9:00 to 11:00 the next day in Sydney. From the UK, early morning works, 7:00 to 9:00 in London is 18:00 to 20:00 in Sydney. Sydney also runs daylight saving in reverse, moving its clocks forward in October when the northern hemisphere is falling back, so the gap swings by two hours across the year rather than staying fixed.

The overlap windows above are not fixed, because daylight saving time starts and ends on different dates in different places. The US springs forward in early March, Europe in late March, and for the two to three weeks in between the gap between New York and London is four hours instead of the usual five. A recurring 9:00 New York call that was 14:00 in London suddenly becomes 13:00, which can push it into someone's lunch or out of their working day.

Three habits keep this from biting. First, always name the time zone when you announce a meeting, and ideally give both locals ("9:00 New York / 14:00 London"). Second, re-check any recurring cross-region meeting in the second half of March and again in late October, when the clocks move. Third, let a tool do the conversion from a real date rather than a remembered offset. Our meeting time zone planner recomputes every window for the exact date you pick, so the daylight-saving shift is already handled, and our guide on when2meet and time zones covers the same trap inside a poll.

The table tells you when a meeting is theoretically possible, but working hours are a model and real calendars have conflicts. The reliable next step is to take the overlap window and confirm it against people's actual availability.

Share a quick availability poll with two or three slots from the right window: everyone marks when they are genuinely free, each person seeing the times converted to their own zone automatically, and you book the slot that works for the most people without a reply-all thread. This matters most for remote teams, where the overlap is narrow and one wrong assumption wastes the only good hour. For the wider method of getting a scattered group to actually respond, see how to find a meeting time that works for everyone.