WorldTimeConverter Logo
WTC
Guides7 min read

How to Schedule a Meeting Across Time Zones (The Complete Guide)

You send the invite. Everyone accepts. Then 20 minutes before the call, someone from the Singapore office messages: "Wait, is this 9 AM your time or mine?"

That moment — right there — is why scheduling meetings across time zones is genuinely hard. It's not because the math is complicated. It's because people accept invites without checking, tools show times in local time without clarifying which local, and abbreviations like "EST" and "EDT" look almost identical but mean completely different things six months apart.

The good news: once you have a system for this, it stops being a problem. Here's the one that actually works.

Why Cross-Timezone Meeting Scheduling Goes Wrong

Most timezone scheduling failures aren't calculation errors. They're communication errors.

Someone says "10 AM" without specifying which timezone. Someone else reads a calendar invite that shows their local time but assumes it's the sender's local time. A recurring meeting gets set up in summer without accounting for the fact that DST will shift it by an hour in November.

The other issue: not all time zones shift equally. India doesn't observe Daylight Saving Time. China doesn't. Japan doesn't. So when the US springs forward in March, the EST-IST gap changes from 10.5 hours to 9.5 hours — but your recurring calendar invite, if it was set with "IST" as a fixed UTC offset rather than a named timezone, won't update.

📊 57% of workers use at least 3 different time zones in their weekly work — Harvard Business Review. And only a fraction of those workers have a reliable system for finding the right meeting time. The rest are recalculating every week or getting it wrong once a quarter.

The specific failure modes:

Step-by-Step: How to Find the Best Meeting Time

Step 1 — Know everyone's local working hours

Start with real constraints, not theoretical UTC offsets. Most people work 9 AM–6 PM in their local time. That's what you're optimizing for.

Write it out:

Now find where those windows overlap.

Step 2 — Convert to UTC and find the intersection

UTC is your neutral reference point. Convert each team's working hours to UTC and look for the intersection.

Winter example (US on EST, UK on GMT):

The overlap between New York (UTC 14–23) and London (UTC 9–18) is UTC 14:00–18:00 — that's 9 AM–2 PM in New York and 2 PM–6 PM in London.

Step 3 — Check DST dates before booking recurring meetings

If you're setting up a weekly recurring call, note when DST transitions happen and add a calendar reminder to review the meeting time two weeks before.

US spring forward: second Sunday in March. US fall back: first Sunday in November.

UK spring forward: last Sunday in March. UK fall back: last Sunday in October.

There's a 3-week mismatch window in spring where the US has switched but the UK hasn't. During those 3 weeks, the New York–London gap is 4 hours, not 5.

Step 4 — Use a meeting time finder, not manual math

The manual approach works. But it's error-prone at scale — especially when you add a third timezone or try to account for DST transitions.

The meeting scheduler on this site lets you pick multiple timezones and see the overlap hours visually. You can see which times work across all locations at once, rather than doing the math separately for each pair.

Best Times to Meet for US + India Teams

This is the one people ask about most, and for good reason — the gap is large and awkward.

EST to IST is 10.5 hours (winter/standard time). During US summer (EDT to IST), it's 9.5 hours.

Working hours overlap:

| New York (EST) | New York (EDT) | Mumbai (IST) | Verdict | |---|---|---|---| | 7:00 AM | 7:00 AM | 5:30 PM / 4:30 PM | Mumbai late, NY early | | 8:00 AM | 8:00 AM | 6:30 PM / 5:30 PM | Possible | | 8:30 AM | 8:30 AM | 7:00 PM / 6:00 PM | Best window | | 9:00 AM | 9:00 AM | 7:30 PM / 6:30 PM | Good, India still in office | | 10:00 AM | 10:00 AM | 8:30 PM / 7:30 PM | India too late |

The practical sweet spot for US East Coast + India calls: 8:00–9:30 AM EST in winter, 8:00–9:30 AM EDT in summer. That's 6:00–7:30 PM IST in summer, or 6:30–8:00 PM IST in winter. Both sides are technically in working hours — just barely.

Don't push it past 9:30 AM EST. By 10:00 AM New York, your Mumbai colleagues are at 7:30 PM IST in winter, which is past normal office hours. Some teams can accommodate it, but it's not a reasonable default.

📊 16% of companies globally are now fully remote — Owl Labs State of Remote Work. For India-US remote teams specifically, the overlap window is narrow enough that most companies have adopted async-first communication and treat the 8–9:30 AM EST window as a weekly sync, not a daily default.

Best Times to Meet for US + Europe Teams

More manageable than US-India, but still requires attention.

New York to London: 5 hours in winter, 4–5 hours in summer (depending on DST transition dates).

New York to Paris/Berlin/Amsterdam: 6 hours in winter, 5–6 hours in summer.

Working hours overlap for US East Coast + Western Europe:

| New York (EST) | London (GMT) | Paris/Berlin (CET) | |---|---|---| | 9:00 AM | 2:00 PM | 3:00 PM | | 10:00 AM | 3:00 PM | 4:00 PM | | 11:00 AM | 4:00 PM | 5:00 PM | | 12:00 PM | 5:00 PM | 6:00 PM |

The 9 AM–12 PM EST window gives you comfortable overlap with all of Western Europe — London is at 2–5 PM, Paris is at 3–6 PM. Both sides are solidly in working hours.

For US West Coast (PST): add 3 hours to the New York times. 9 AM EST = 6 AM PST, which rules out West Coast participation in morning Europe meetings. The US West Coast and Europe have almost no comfortable overlap — the best you can do is 12 PM PST / 8 or 9 PM in Europe, or very early morning PST with normal Europe working hours.

Practical Rules That Actually Prevent Scheduling Problems

Rule 1 — Always include the timezone abbreviation in meeting invites. Not just "9:00 AM" — "9:00 AM EST" or "9:00 AM IST." Better still, send the link from a live converter showing that exact time in every participant's timezone.

Rule 2 — Set recurring meetings with named timezones, not fixed UTC offsets. In Google Calendar, when you set an event to "Eastern Time," it auto-adjusts for DST. If you set it to "UTC-5" manually, it won't.

Rule 3 — Rotate the inconvenient time. If the US-India overlap means someone always gets the awkward 8 AM or 8 PM slot, rotate it. Week one: New York takes 8 AM. Week two: Mumbai takes the later evening call. This distributes the inconvenience instead of making one side always absorb it.

Rule 4 — Build in a 5-minute buffer. Timezone confusion means one person is always a couple minutes late because they recalculated at the last second. Starting at 9:05 instead of 9:00 costs nothing and removes that stress.

Rule 5 — Check DST transition weeks proactively. Around March and November in the US, and around March and October in Europe, add a calendar reminder to verify your recurring meetings are still at the right time.

Frequently Asked Questions

What's the best time to schedule a meeting between the US East Coast and India?

The sweet spot is 8:00–9:30 AM Eastern Time. In winter, that's 6:30–8:00 PM IST — late but within working hours for India. In summer (EDT), it's 5:30–7:00 PM IST, which is more comfortable. Avoid scheduling past 10 AM ET — by then it's past 8 PM in India.

What's the best time for a US and UK call?

9 AM to 12 PM Eastern Time gives comfortable overlap — London is at 2–5 PM (winter) or 2–5 PM (summer). Note that during the 3-week DST mismatch in spring, the gap between New York and London is 4 hours instead of 5.

How do I handle DST changes for recurring meetings?

Set your recurring meetings using named timezones (like "Eastern Time" or "India Standard Time") rather than fixed UTC offsets. Calendar apps like Google Calendar will auto-adjust named-timezone events for DST. Also add a reminder in March and November to verify your recurring meetings look correct.

Why does the EST-IST time difference change during the year?

Because the US observes Daylight Saving Time and India doesn't. In winter, EST is UTC-5 and IST is UTC+5:30 — a 10.5-hour gap. In summer, the US switches to EDT (UTC-4), making the gap 9.5 hours. India's clock never moves.

Is there a free tool to find the best meeting time across multiple timezones?

The meeting scheduler here shows overlap hours across multiple timezones simultaneously. Enter your team's locations and it highlights the windows where everyone is in their working hours — no manual math.

Related Articles

← All articles