US Clocks Change November 1: Check This Week’s UK and India Calls
If you work with UK clients, October 25, 2026 can change how a US-based meeting appears on their calendar. It is not the US clock-change date. The UK moves back today; US locations that observe daylight saving time move back on November 1. For a cross-border team, that creates a week when the usual difference between local clocks changes.
Two dates to put in your scheduling notes
GOV.UK lists October 25 for the UK’s 2026 autumn change: clocks go back one hour at 2 a.m., returning to Greenwich Mean Time. NIST gives November 1 at 2 a.m. local time for the US change, when 2 a.m. becomes 1 a.m. The US Naval Observatory independently lists the same November date.
GOV.UK: 2026 UK clock-change dates
NIST: 2026 US daylight-saving rules and exceptions
US Naval Observatory: 2026 daylight-saving dates
A 9 a.m. New York meeting across three dates
These calculated examples keep the meeting fixed at 9 a.m. in New York. London and India show the same instant on each listed date. They are date-specific conversions, not a permanent offset to copy into every invitation.
- Friday, October 23: New York 9 a.m. EDT → London 2 p.m. BST → India 6:30 p.m. IST.
- Monday, October 26: New York 9 a.m. EDT → London 1 p.m. GMT → India 6:30 p.m. IST.
- Monday, November 2: New York 9 a.m. EST → London 2 p.m. GMT → India 7:30 p.m. IST.
The UK participant sees that New York-anchored meeting an hour earlier during the intervening workweek. The India participant’s change comes with New York’s November transition. CSIR-NPL defines Indian Standard Time as UTC(NPLI) plus five hours and thirty minutes.
CSIR-NPL: how Indian Standard Time is maintained
Agree which location owns the meeting time
Before changing an invitation, decide which local time the team intends to preserve. A call fixed to New York’s working day and a call fixed to London’s working day need different conversions. Write the date, city and local time together when asking colleagues to confirm. A message saying only “same time as usual” leaves that decision unresolved.
For the coming week, review one occurrence after October 25 and another after November 1. Compare the organizer’s intended time with each participant’s displayed time. Prioritize client appointments, interviews, webinars and support handovers, where a missed hour has a practical cost. Check room and attendee availability before approving a new time.
Use the rule for the actual location
NIST lists exceptions including Hawaii and most of Arizona. Do not apply the New York examples to every US colleague. NIST also explains that operating-system software supplies local-time and daylight-saving corrections; keep that software current if devices disagree.
A useful scheduling note is specific: “Monday, October 26, 2026, 9 a.m. New York / 1 p.m. London / 6:30 p.m. India.” Confirm the intended occurrence and its named time zones before sending a correction. An unfamiliar clock difference by itself is not evidence that the invitation is wrong.
Check the dates before your next call
