UK–India Meeting Times — The Half-Year Shift
India is UTC+5:30 all year. The UK is GMT in winter and BST in summer, so a UK–India meeting moves by an hour twice a year. Hold the series on Mumbai time and re-check the London hour after each UK clock change.
India does not observe daylight saving time, so a UK–India meeting has one fixed side. London moves an hour twice a year — back on the week of Monday 26 October 2026 and forward on the week of Monday 29 March 2027 — flipping the gap between 4h30 (UK summer) and 5h30 (UK winter). Hold the recurring series on Mumbai time, let the London invite float, and re-check the London local time after each UK clock change.
India keeps UTC+5:30 all year and the UK does not, so every UK clock change shifts a UK–India meeting by one hour for roughly half the year. Anchor to Mumbai time; London floats.
Direct Answer
India does not observe daylight saving time, so a UK–India meeting has one fixed side. London moves an hour twice a year — back on the week of Monday 26 October 2026 and forward on the week of Monday 29 March 2027 — flipping the gap between 4h30 (UK summer) and 5h30 (UK winter). Hold the recurring series on Mumbai time, let the London invite float, and re-check the London local time after each UK clock change.
Why This Matters
Almost every UK–India scheduling failure is the same story: someone fixes the invite at a UTC or London time, the meeting works for a few months, then one side quietly becomes an hour late or early and nobody can explain why.
The root cause is simple. Mumbai runs India Standard Time (UTC+5:30) all year — India has no daylight saving. London runs GMT in winter and BST in summer. So the gap between the two is 5h30 when the UK is on GMT and 4h30 when the UK is on BST, and it flips twice a year.
For a London-anchored meeting, the Mumbai side of the invite moves by an hour twice a year. For a Mumbai-anchored meeting, the London side moves by an hour twice a year. Since only one of the two ever changes, the stable side is the obvious anchor — and India is the stable side.
The Drift Calendar: Which Weeks Change
These are the exact drift weeks for the next 12 months (computed from the current timezone database on 27 August 2026, for a weekly series starting the week of Monday 7 September 2026):
| Month | Which city changes | What happens |
|---|---|---|
| Oct 2026 | London | Mon 26 Oct: BST (UTC+1) → GMT (UTC+0), clocks back |
| Mar 2027 | London | Mon 29 Mar: GMT (UTC+0) → BST (UTC+1), clocks forward |
Every other month in the window: no change. Mumbai never appears in the table.
Decision Table: Meeting Times by UK Season
For a weekly call held at 14:30 Mumbai time (a slot that lands inside the working day on both sides):
| Season (window) | London sees | Mumbai sees | Gap |
|---|---|---|---|
| UK winter (GMT) — week of 26 Oct 2026 → week of 29 Mar 2027 | 09:00 | 14:30 | 5h30 |
| UK summer (BST) — week of 29 Mar 2027 onward (until the autumn change) | 10:00 | 13:30 | 4h30 |
The practical point: a meeting that starts at 09:00 in a London winter starts at 10:00 in a London summer. If the team forgets the change, someone is a full hour early or late for six months straight.
Workflow: Setting a UK–India Series That Survives the Shift
- Hold the series on Mumbai time. India never changes its clock, so the Mumbai hour of the meeting is the same instant every week and never needs adjusting.
- Flag the two UK change weeks — the week of Monday 26 October 2026 and the week of Monday 29 March 2027. The London-side hour of the meeting shifts by one on each.
- Check the drift row in the meeting planner. It flags the exact occurrence weeks where a participant’s offset changes, so the invite can be reviewed before anyone is caught out.
- Re-confirm the London hour after each change, then export the calendar file — it carries every occurrence at the correct local time.
Where TimeNowHub Does the Work
- The London ↔ Mumbai comparison shows the live overlap window and gap for this corridor.
- /time/mumbai and /time/london show the current local time and whether it is a working day in each city right now.
- Open the meeting planner with Mumbai and London preloaded to score a recurring slot against both sides’ work weeks — the planner marks the weeks where the London side drifts.
Frequently Asked Questions
Does India observe daylight saving time?
No. India has a single time zone, IST (UTC+5:30), all year. That is exactly why the entire half-year shift in a UK–India meeting falls on the UK side, not split between both.
Why does the London side of a UK–India meeting move twice a year?
Because only the UK changes its clock. When the UK moves from GMT to BST (spring) or back (autumn), the London local time of a fixed Mumbai-time meeting shifts by one hour for roughly six months. The dates in the next 12 months are the weeks of Monday 26 October 2026 and Monday 29 March 2027.
What time of day works best for a UK–India call?
UK mornings overlap India afternoons: 09:00 London is 14:30 Mumbai in UK winter and 13:30 in UK summer. A 14:30 Mumbai slot keeps the meeting inside the working day on both sides while giving London a morning start.
When are the next UK clock changes?
Within the next 12 months: the week of Monday 26 October 2026 (clocks back, GMT) and the week of Monday 29 March 2027 (clocks forward, BST). After that the UK stays on BST through the 2027 summer until the next autumn change.