The Three Weeks a Year India–US–UK Meetings Quietly Break
By Mohak Mangal · Published October 26, 2026 · 7 min read
India sits at UTC+5:30 all year and never changes its clocks. That makes things pleasant for anyone in India and slightly treacherous for everyone else, because the other side of the call keeps moving. If you have recurring meetings with the UK or US, you'll have noticed that a time which worked in January is suddenly awkward in April.
Here's what actually happens, with times worked out from the standard time-zone database.
One fixed 10:00 a.m. IST, four dates
| Date | London | New York | Los Angeles | Singapore | Sydney |
|---|---|---|---|---|---|
| 14 Jan 2027 | 04:30 | 23:30 (previous day) | 20:30 (previous day) | 12:30 | 15:30 |
| 15 Jul 2026 | 05:30 | 00:30 | 21:30 (previous day) | 12:30 | 14:30 |
| 28 Oct 2026 | 04:30 | 00:30 | 21:30 (previous day) | 12:30 | 15:30 |
| 20 Mar 2027 | 04:30 | 00:30 | 21:30 (previous day) | 12:30 | 15:30 |
Look at how little India's relationship to Singapore changes (always 2.5 hours ahead of India, no daylight saving) versus how much London and New York move.
The mismatch windows
The UK and the US don't change their clocks on the same days, which creates short periods when the gap between them is unusual:
- US clocks go forward in mid-March; UK clocks go forward at the end of March. In between, London is still on GMT while New York is already on daylight time. In our example, 20 March 2027 falls in that window: London is 4.5 hours behind India, but New York is 9.5 hours behind.
- UK clocks go back at the end of October; US clocks go back in early November. 28 October 2026 sits in that window. London is already on GMT, and New York is still on daylight time.
The result is that for a few weeks, the London-to-New York gap shrinks from five hours to four, and the India-to-both gaps shift by different amounts. A recurring three-way call is exactly where this bites. A slot that gave everyone a reasonable hour on Tuesday can put the UK person at 8 a.m. instead of 9, or the New Yorker at 5 a.m. instead of 6.
Other things worth knowing
- Half-hour offsets exist. India is +5:30. Nepal is +5:45. Parts of Australia use +9:30 and +10:30. Any tool that rounds to whole hours will be wrong for these.
- Southern hemisphere runs opposite. Sydney moves clocks forward in October and back in April. So the Australia gap moves in the opposite direction from the UK gap.
- Rules change. Governments revise daylight-saving rules. Rely on the time-zone database in your device rather than memorised offsets.
How to keep a recurring meeting sane
- Anchor the series to the group that has least flexibility. If one team is in a fixed shift pattern, anchor to them and let everyone else adjust.
- Check the transition weeks in advance. Put a calendar reminder two weeks before the March and October/November changes to look at the next several occurrences.
- Tell people. "The call moves one hour earlier for the UK from 29 March" prevents a missed meeting.
- Share the bad slot. If one office always gets the 6 a.m. call, rotate or alternate.
- State the zone every time. "10:00 IST" can't be misread. "10 a.m." can.
Plan against a real date, not the typical week
The easiest way to avoid surprises is to look at the exact date. Our meeting time zone planner builds a 24-hour grid for whichever date you pick, using your browser's own time-zone data, so daylight-saving transitions on that day are handled. Check the first meeting of the series and the first after each clock change, and you've covered the risky ones.