Working Across US and India Time Zones: A Practical Overlap Guide
India Standard Time (IST) is a single time zone for the entire country — UTC+5:30, with no daylight saving changes. That half-hour offset (rather than a full hour) trips people up constantly when they’re converting by habit instead of checking, so it’s worth calling out on its own.
The actual gap
Depending on the US time zone and the time of year:
- US Eastern Time to IST: 9.5 hours ahead of IST for most of the year, narrowing to 10.5 hours during the few weeks when the US has entered daylight saving time but hasn’t yet, or vice versa.
- US Pacific Time to IST: 12.5–13.5 hours ahead of IST, depending on the time of year.
Because IST doesn’t observe daylight saving, the gap to any US time zone shifts by an hour whenever the US clocks change in March and November — even though nothing changes on the India side.
Where the overlap actually is
For US East Coast and India, the realistic overlap is early morning IST (roughly 6–9 a.m. IST) meeting late evening US Eastern (roughly 8:30–11:30 p.m. the previous day). That’s genuinely late for the US side and early for the India side — there’s no version of this pairing that’s convenient for both.
For US West Coast and India, it’s even tighter: the closest thing to an overlap is very early morning India time meeting the end of the US workday, and even that requires one side to be well outside normal hours.
This is why many US–India teams default to one of two patterns instead of forcing daily live overlap:
- A single shared “bridge” window, often early morning IST / previous evening US time, reserved for the meetings that genuinely need real-time discussion — planning, blockers, decisions — and nothing else.
- Handoff-style async work, where the India team’s end-of-day summary becomes the US team’s start-of-day briefing, and vice versa. This works well for workflows that are naturally sequential (support queues, code review, QA) rather than collaborative in real time.
Practical tips specific to this pairing
- Double-check the half hour.A 30-minute offset means a meeting converted “roughly” — rounding IST to the nearest full hour — will be wrong by 30 minutes. It’s a small error that’s easy to make and annoying to debug.
- Watch for the US DST transition specifically, since India’s side of the gap never moves. The shift always shows up as a change in what IST time corresponds to a fixed US meeting time, not the other way around.
- Diwali and major Indian holidays vs. US federal holidaysdon’t overlap, so a shared team calendar that only tracks one country’s holidays will consistently miss half the relevant dates.
Quick reference
| US zone | Typical gap to IST |
|---|---|
| Eastern (ET) | 9.5–10.5 hours ahead of IST |
| Central (CT) | 10.5–11.5 hours ahead of IST |
| Mountain (MT) | 11.5–12.5 hours ahead of IST |
| Pacific (PT) | 12.5–13.5 hours ahead of IST |
For the exact current difference — including which side of a DST transition you’re on right now — check the US to India time comparison rather than relying on a remembered number, since it’s the part most likely to have quietly shifted since you last checked.