Best Meeting Times for US and India Teams
By Mark Fulton · 2026-08-25 · 13 min read
The window that works is early US morning against late India afternoon. From New York, an 8:00 or 9:00 AM start lands at 5:30 or 6:30 PM in India for the 34 weeks the US is on daylight time, and one hour later in India, 6:30 or 7:30 PM, for the 19 weeks it is on standard time. Chicago runs an hour behind that, Denver two hours behind, San Francisco three. India never changes its clocks, so every one of these numbers moves on the US side only, twice a year, which is why one recurring invite is right for eight months and wrong for four.
How far apart are the US and India?
India Standard Time is UTC+05:30. It covers the whole country on a single zone, and it does not observe daylight saving. The national standard is maintained by CSIR-National Physical Laboratory, and in software it is the IANA zone Asia/Kolkata.
The US is the complicated half. Four continental zones, each of which advances an hour in spring and falls back in autumn, which means there is no single "US to India" number. There are eight.
| US zone | US on daylight time | US on standard time |
|---|---|---|
| Eastern (New York) | IST is 9h 30m ahead | IST is 10h 30m ahead |
| Central (Chicago) | IST is 10h 30m ahead | IST is 11h 30m ahead |
| Mountain (Denver) | IST is 11h 30m ahead | IST is 12h 30m ahead |
| Pacific (San Francisco) | IST is 12h 30m ahead | IST is 13h 30m ahead |
| Arizona (Phoenix) | IST is 12h 30m ahead | IST is 12h 30m ahead |
The figure most people quote is 9.5 hours. That is one cell of this table: New York, during daylight time. It is wrong for Chicago, wrong for Denver, wrong for San Francisco, and wrong for New York for about nineteen weeks of every year.
Arizona is the useful oddity. It stays on Mountain Standard Time all year, so Phoenix is the one mainland US city whose distance from India never moves. Hawaii is the same story further out, sitting 15h 30m behind IST year round.
Which windows work for each US time zone?
Read these two grids the same way. Pick your US city on the left, pick the hour you want to start in your own local time along the top, and the cell tells you what time that is in India.
The markers describe who is being asked for something: ✓ means both sides are inside a normal 8:00 to 19:00 working day, ~ means one side is just outside it, and ✗ means someone is genuinely sacrificing.
US on daylight time (March 8 to November 1, 2026)
| US city | 7:00 AM | 8:00 AM | 9:00 AM | 10:00 AM | 11:00 AM |
|---|---|---|---|---|---|
| New York (EDT) | 4:30 PM ~ |
5:30 PM ✓ |
6:30 PM ✓ |
7:30 PM ~ |
8:30 PM ✗ |
| Chicago (CDT) | 5:30 PM ~ |
6:30 PM ✓ |
7:30 PM ~ |
8:30 PM ✗ |
9:30 PM ✗ |
| Denver (MDT) | 6:30 PM ~ |
7:30 PM ~ |
8:30 PM ✗ |
9:30 PM ✗ |
10:30 PM ✗ |
| San Francisco (PDT) | 7:30 PM ~ |
8:30 PM ✗ |
9:30 PM ✗ |
10:30 PM ✗ |
11:30 PM ✗ |
US on standard time (November 1, 2026 to March 14, 2027)
| US city | 7:00 AM | 8:00 AM | 9:00 AM | 10:00 AM | 11:00 AM |
|---|---|---|---|---|---|
| New York (EST) | 5:30 PM ~ |
6:30 PM ✓ |
7:30 PM ~ |
8:30 PM ✗ |
9:30 PM ✗ |
| Chicago (CST) | 6:30 PM ~ |
7:30 PM ~ |
8:30 PM ✗ |
9:30 PM ✗ |
10:30 PM ✗ |
| Denver (MST) | 7:30 PM ~ |
8:30 PM ✗ |
9:30 PM ✗ |
10:30 PM ✗ |
11:30 PM ✗ |
| San Francisco (PST) | 8:30 PM ✗ |
9:30 PM ✗ |
10:30 PM ✗ |
11:30 PM ✗ |
12:30 AM ✗ |
The second grid is the first one shifted. Every India time moved an hour later, and every row lost a column of usable slots. Nothing about anybody's habits changed. The US clocks moved and India stayed put.
Turn that into hours, and the picture is blunt. Assume the US side works 8:00 to 18:00 and the India side works 9:30 to 20:00, which is generous to both:
| US zone | Overlap, US on daylight time | Overlap, US on standard time |
|---|---|---|
| Eastern | 2h 30m | 1h 30m |
| Central | 1h 30m | 30m |
| Mountain | 30m | none |
| Pacific | none | none |
For a Pacific team there is no slot in which both sides are inside ordinary working hours, in either half of the year. That is not a scheduling failure to be solved with a better calendar tool. It is the geometry, and the honest response is to decide out loud who takes the hit rather than hunting for a window that does not exist.
There is a second direction worth checking, and it is the one most guides skip: India morning against the US previous evening.
| US city | India 9:00 AM, US on daylight time | India 9:00 AM, US on standard time |
|---|---|---|
| New York | 11:30 PM previous day | 10:30 PM previous day |
| Chicago | 10:30 PM previous day | 9:30 PM previous day |
| Denver | 9:30 PM previous day | 8:30 PM previous day |
| San Francisco | 8:30 PM previous day | 7:30 PM previous day |
For the East Coast this direction is never worth it. For the West Coast it flips with the season. In the US winter, San Francisco can take a 7:30 PM call on Tuesday evening and meet India's Wednesday morning, which is a far more humane ask than the 8:30 PM India time that a 7:00 AM Pacific start produces in the same months. A Pacific team that meets India in the US morning all summer and in the US evening all winter is not being inconsistent. It is following the grid.
Why does the gap change twice a year?
Because only one side is moving. Under 15 U.S.C. 260a, US daylight saving time runs "commencing at 2 o'clock antemeridian on the second Sunday of March of each year and ending at 2 o'clock antemeridian on the first Sunday of November." NIST states the same rule and notes the exceptions: Hawaii, American Samoa, Guam, Puerto Rico, the US Virgin Islands and Arizona do not observe it, with the Navajo Nation the exception inside Arizona.
For the current cycle that means the US fell into daylight time on 8 March 2026, returns to standard time on 1 November 2026, and springs forward again on 14 March 2027. Thirty-four weeks on daylight time, nineteen weeks on standard time. India does neither, on any date.
The consequence lands in your calendar app, and it is deterministic rather than buggy. A recurring invite stores the organizer's time zone. Create the series in a New York calendar and it holds 9:00 AM Eastern forever, which means the India side watches it walk from 6:30 PM to 7:30 PM on 1 November and back again on 14 March. Create the same series in a Bengaluru calendar and it holds 6:30 PM IST forever, so the New York side is the one whose meeting moves. Both behaviours are correct. The choice is which side you want the surprise to land on, and the mistake is not making the choice at all.
Pick an anchor deliberately and write it into the invite description. If the meeting exists to unblock the India team before they go home, anchor it to IST and let the US time move. If it exists to unblock the US day, anchor it to the US city. Then put the two transition dates in the shared calendar as all-day reminders, because the week they arrive is the week somebody joins an empty room. If you want the underlying mechanics, how UTC, offsets and DST actually fit together is the longer version of this paragraph.
What do you do when the US team spans both coasts?
Do the arithmetic before you open a scheduler, because it settles the argument.
New York and San Francisco are three hours apart. India is 9h 30m ahead of New York in the US summer, 10h 30m in the winter. So the span from your earliest participant to your latest is 12h 30m or 13h 30m. A working day is about nine hours long. Twelve and a half is more than nine, so there is no instant at which all three sites are inside normal hours. None. Not on a Tuesday, not with a better tool.
What is left is a choice between three shapes, and it is worth putting them side by side rather than picking one by feel.
US on daylight time
| Slot | New York | San Francisco | Bengaluru | Who pays |
|---|---|---|---|---|
| A | 8:00 AM | 5:00 AM | 5:30 PM | San Francisco, heavily |
| B | 9:30 AM | 6:30 AM | 7:00 PM | San Francisco a lot, India a little |
| C | 11:00 AM | 8:00 AM | 8:30 PM | India |
US on standard time
| Slot | New York | San Francisco | Bengaluru | Who pays |
|---|---|---|---|---|
| A | 8:00 AM | 5:00 AM | 6:30 PM | San Francisco, heavily |
| B | 9:30 AM | 6:30 AM | 8:00 PM | San Francisco and India, both |
| C | 11:00 AM | 8:00 AM | 9:30 PM | India, heavily |
Slot B is the one teams reach for, because splitting the difference feels fair. Look at what it actually costs in winter: a 6:30 AM alarm in California and an 8:00 PM finish in Bengaluru, every single week, for the same two people. That is not a compromise. It is two permanent losers and one comfortable winner in New York.
How do you make a rotating early or late call fair?
"Rotate the pain" is the standard advice and it almost always dies within two months, because nobody wrote down what a turn is or who took the last one. Give the rotation an arithmetic and it survives.
1. Write down each site's real band. Not the theoretical nine to five. Ask each site for the earliest hour and the latest hour they will genuinely take a call, and record both. The answers are usually asymmetric. A team in Bengaluru that starts at 10:00 often has more room at 19:30 than a team in San Francisco has at 06:30, and that asymmetry is the raw material for a fair schedule.
2. Score each slot in minutes outside the band. For a 60-minute call, count how many of those minutes fall outside each site's stated band. A 6:30 AM start against an 8:00 AM band costs that site 60 minutes. A 7:30 AM start costs 30. An 8:00 PM finish against a 19:30 band costs 30. Every slot now has a number per site instead of a vibe.
3. Keep a running total per site. One column per site, one row per occurrence, the cost you just scored. This is the step everyone skips, and skipping it is exactly why rotations stop. Without a ledger, "it is your turn" is an opinion.
4. Assign the next occurrence to whoever is lowest. The site with the smallest running total takes the next uncomfortable slot. The rule is mechanical, so it does not require anyone to advocate for themselves, which matters when the sites are not equal in seniority or in confidence.
5. Reset the totals when the US clocks change. On 1 November and again on 14 March the whole grid moves and every score you accumulated was computed against a different set of options. Zero the ledger and re-score the slots.
One calendar mechanic makes this stick: build the rotation as a small number of separate weekly series, one per slot, rather than one recurring series with per-occurrence overrides. Overrides on a recurring series are the thing that silently misbehaves across a DST boundary, and a rotation that misfires once loses the trust it needs.
Which meetings should not be meetings?
If your best overlap is 90 minutes a day, and for a Pacific team it is zero, then live time is the scarcest thing the team owns. Spend it accordingly.
Worth the window: decisions where people actually disagree, first contact with a new person, anything where someone is stuck and a screen share ends it in five minutes, anything with a personal or sensitive edge. These are the things that go badly in writing.
Not worth the window: status updates, demos that a recording would carry better, document review, anything that is one person talking while eight people listen. If the agenda would work as a document with comments due before the next overlap opens, it should be a document.
There is an upside hiding in a ten-hour gap that a co-located team cannot buy. Written handoffs at the end of one side's day, read at the start of the other's, mean work moves twice a day instead of once. The India team closes with what changed and what is blocked, the US team opens with it, and by the time India logs back on there is an answer waiting. Handled that way the gap is a relay, not a tax. The teams that suffer most are the ones trying to run a synchronous culture across it and paying for the attempt in 6:30 AM alarms.
Put both cities on one board
Static tables answer the general question. The specific one, "is 9:30 AM next Tuesday still 7:00 PM for them", is easier to answer by looking. Put your city, the India office and any third site on the world clock, which reads live from the IANA time zone database and so handles the November and March switches on its own, with no edits from you. The free board holds four cities, which covers New York, San Francisco and Bengaluru with a slot to spare. SmartClock Pro lifts the cap and lets you label each row with the team rather than the city, so the board reads the way you actually think about it.
FAQ
What is the best time to call India from the US? From the East Coast, 8:00 to 9:00 AM local, which is 5:30 to 6:30 PM in India while the US is on daylight time and 6:30 to 7:30 PM while it is on standard time. From Central, an hour earlier on your clock for the same India time. From Mountain and Pacific, there is no slot that is comfortable for both sides, so the choice is a very early US morning or, for the West Coast in the US winter, a 7:30 PM call against India's 9:00 AM the next day.
Does India observe daylight saving time? No. India Standard Time stays at UTC+05:30 all year, across the entire country, and there is no seasonal clock change to track. Every shift in the US to India gap comes from the US side.
Why is India 30 minutes off the hour? India Standard Time is set from the 82°30′ East meridian, which runs roughly through the longitudinal middle of the country. Longitude converts to time at four minutes per degree, and 82.5 degrees multiplied by four minutes gives 330 minutes, which is 5 hours 30 minutes. Half-hour and quarter-hour offsets are not unusual once you look: Nepal sits at UTC+05:45, and the IANA time zone database carries dozens of zones that are not whole hours from UTC.
How many overlap hours do US and India teams get? Taking a US day of 8:00 to 18:00 and an India day of 9:30 to 20:00, the East Coast gets 2 hours 30 minutes while the US is on daylight time and 1 hour 30 minutes on standard time. Central gets 1 hour 30 minutes and then 30 minutes. Mountain gets 30 minutes and then nothing. Pacific gets nothing in either half of the year. Anything beyond those numbers is somebody working outside their normal day, which is fine as long as it is named and shared rather than assumed.