Scheduling Across US and India Time Zones: The Complete Guide

The US–India corridor carries more scheduled remote work than any other pair of regions on earth, and it is also one of the least forgiving. India Standard Time runs 9 hours 30 minutes ahead of US Eastern Time in the American summer, and 10 hours 30 minutes ahead in winter. Against the West Coast it is 12 hours 30 minutes or 13 hours 30 minutes. At those distances the two working days do not overlap at all — the Indian day has ended before the American one starts.

This guide covers the exact windows, the half-hour offset that catches out even experienced schedulers, and the handoff patterns teams use when there is no shared working time to find.

The Core Numbers

India uses a single timezone for the entire country — Asia/Kolkata, at UTC+5:30 — and does not observe daylight saving. That means the Indian side of this relationship never moves. Every seasonal change you experience on this corridor comes from the American side.

Note the direction of the seasonal change, because it is counterintuitive. When the US springs forward in March, the gap to India narrows by an hour. American daylight saving actually makes this corridor slightly easier for seven months of the year, which is the opposite of what most people assume.

The Half-Hour Offset Is Not a Detail

India is one of a small number of places whose offset is not a whole number of hours. Nepal is at UTC+5:45, Iran at UTC+3:30, parts of Australia at UTC+9:30. For India this means that a meeting at the top of the hour anywhere in the Americas or Europe always lands on the half hour in India.

A 9:00 AM call in New York is 6:30 PM in Bangalore. Not 6:00, not 7:00. Every mental conversion on this corridor has to carry the thirty minutes, and the ones that go wrong usually go wrong by exactly that much.

Calendar software handles this correctly without being asked. The failures happen in the places software is not involved — a time written into a Slack message, a date agreed verbally on a call, a recurring meeting described in a wiki page as "4 PM IST / 6 AM ET" that was accurate when written and silently wrong after the next US clock change.

Where the Overlap Actually Is

India and US Eastern

This is the workable end of the corridor. During US summer time, when the gap is 9h30m, there is a genuine if narrow window:

The practical window is 8:00–10:00 AM Eastern, which lands between 5:30 and 7:30 PM in India. Someone is always giving something up — either the American side starts before their normal day, or the Indian side stays past theirs. Most established teams settle on around 8:30 AM Eastern as the least contentious point.

India and US Pacific

There is no good answer here, and it is worth saying so directly rather than pretending otherwise. At 12h30m to 13h30m apart, the two cities are close to antipodal on the clock. When it is 9:00 AM in Los Angeles it is 9:30 PM in Bangalore; when it is 9:00 AM in Bangalore it is 8:30 PM the previous day in Los Angeles.

The two options both hurt:

• Early Pacific: 7:00 AM in Los Angeles is 7:30 PM in India. The American side starts early, the Indian side finishes late, and both are at the outer edge of reasonable.
• Late India: 9:00 PM in India is 8:30 AM in Los Angeles. Comfortable for California, genuinely intrusive for India — this is family time being given up, week after week.

Teams that sustain this pairing for years do it by keeping live contact to an absolute minimum. One call a week, not one a day.

The Handoff Model

The most durable pattern on this corridor stops treating the time difference as a problem to be solved and starts treating it as a property to be used. The twelve-hour gap means that when one side stops working, the other is starting — which is a continuous working day if the handoff is good enough.

What that requires in practice:

• A written end-of-day handoff, every day, without exception. What moved, what is blocked, what the other side should pick up. The discipline matters more than the format.
• Decisions documented with their reasoning, not just their outcome. When the person who made a call is asleep for the next ten hours, "we chose B" is not enough — the next person needs to know why, or they will reopen it.
• Blocking questions raised before the sender's day ends, not during it. A question asked at 6:00 PM India time gets an answer that night. The same question asked at 11:00 AM waits until tomorrow.
• One synchronous slot, protected. A single overlapping call, held reliably, does more than three unreliable ones. It becomes the place where anything genuinely ambiguous gets resolved.

Rotating the Cost

On corridors where any workable slot inconveniences someone, the question is not how to eliminate the cost but who pays it. Left alone, it lands on the same people permanently — almost always the offshore side, because they are the ones who joined an existing schedule.

Two approaches that work:

Alternate the burden by week. One week the call is at 8:00 AM Eastern (evening in India); the next it is at 7:00 PM Eastern (early morning in India). Neither side is permanently disadvantaged, at the cost of a schedule people have to check.

Alternate by meeting type. Keep the daily standup at a time that suits India and hold the less frequent, higher-stakes meetings at a time that suits the US. The frequent cost falls on the side with more people affected by it; the occasional cost falls on the side with more decision-makers present.

We cover the fairness question in more depth in timezone meeting fatigue, which looks at what happens to retention when the burden is never rotated.

Practical Rules

• Book in UTC. India does not change its clocks and the US does, so any recurring meeting fixed in either local time will drift twice a year. UTC does not move.
• Write the half hour every time. "6:30 PM IST", never "6-ish". The thirty minutes is where the errors live.
• Name the city, not the country. "US time" is four different zones. Say New York or Los Angeles.
• Watch the March and November transitions. The gap changes by an hour twice a year, entirely from the American side. Anyone with the offset memorised will be wrong for a fortnight.
• Check the Indian holiday calendar. India has a substantial number of public holidays, many regional rather than national, and they do not align with American ones.

Related reading

• How to read a timezone difference correctly — half-hour offsets, date lines, and the conversions people get wrong
• Async-first scheduling for remote teams — reducing dependence on the one shared hour
• Scheduling across Asia-Pacific timezones — IST alongside JST, SGT and AEST
• Bangalore time zone reference and Mumbai time zone reference