You join your weekly call at the usual time. Your coffee is ready, your notes are open, and the meeting room is empty. You check the invitation. Same day. Same meeting. So why is nobody there?
The meeting may not have changed at all. The time difference between you and the other participants may have.
On Sunday, 25 October 2026, the clocks go back one hour in the United Kingdom, moving from 2:00 a.m. to 1:00 a.m. as British Summer Time ends. For people coordinating across borders, that change can affect client calls, online lessons, interviews, and deadlines.
The easy mistake is assuming that the time difference you used last week will still work next week.
Your Clock Can Stay the Same While the Time Difference Changes
We often remember international schedules as a simple rule: “London is two hours behind me.” It is convenient, and for part of the year, it may be correct. But a time difference is not necessarily permanent.
Some countries move their clocks seasonally. Others keep the same time throughout the year. When one location changes and the other does not, the gap between them shifts.
Consider someone in Istanbul working with a client in London. Before the October change, a meeting at 10:00 a.m. in London falls at noon in Istanbul. After the UK clocks go back, that same 10:00 a.m. London meeting falls at 1:00 p.m. in Istanbul.
The client has kept the same working hours. The person in Istanbul has not changed their clock. Yet the appointment now happens an hour later in their day.
This is why remembering a city’s current time difference is useful for today, but unreliable as a permanent scheduling rule.
A Weekly Meeting Needs a Home Time Zone
“Every Tuesday at ten” sounds clear until the participants live in different countries. Ten o’clock where?
A recurring meeting needs an anchor: the time zone whose local time the appointment follows. If a client call is intended to happen at 10:00 a.m. London time every week, the invitation should use London’s time zone. Participants elsewhere may then see their local meeting time change when seasonal clock changes affect the difference.
The alternative is a meeting anchored to your own location. In that case, your local start time stays consistent while the client’s may shift. Neither arrangement is automatically wrong. The problem is leaving everyone to assume a different one.
Before the clock change, check what your recurring appointments are actually tied to. A quick clarification now can prevent a missed call later.
Why Writing “GMT” Can Cause Confusion
People sometimes use “GMT” as a casual substitute for UK time. However, the UK uses British Summer Time during the summer period and Greenwich Mean Time after the autumn clock change.
That distinction matters when you write a meeting time manually. An invitation saying “10:00 GMT” during British Summer Time does not mean the same thing as “10:00 London time.”
For everyday coordination, a city, date, and local time are usually easier to understand than a loosely used abbreviation. “Tuesday, 27 October, at 10:00 a.m. London time” gives the other person a much clearer reference than “Tuesday at ten.”
When creating the calendar event, choose the appropriate location-based time zone rather than assuming a fixed offset will work all year.
Your Calendar Helps, but the Invitation Still Matters
A calendar can display an event in each participant’s local time when the event and device settings are correct. That makes it much more dependable than repeatedly calculating the difference in your head.
But it cannot resolve every ambiguity in a message. A calendar invitation and a separate email saying “same time as usual” can leave people following different instructions. Manually copying a time into a reminder can also preserve an old conversion after the clocks change.
Open the actual event and check its displayed time for the relevant date. If you are hosting, make sure the invitation reflects the location whose schedule you intend to follow. If you are attending, check that your calendar is displaying your current time zone.
The same care applies to deadlines. “Submit by midnight” needs a date and a time zone when the people involved are in different countries. A deadline should not depend on whose midnight the reader happens to imagine.
Check the Date, Not Just the Current Difference
Looking up the time in another city answers a useful question: what time is it there now? It does not, by itself, establish the difference on every future date.
That matters particularly when scheduling across a clock-change weekend. If you arrange next week’s call using this week’s difference, the calculation may be wrong by the time the meeting arrives.
For an upcoming appointment, check the conversion for the appointment’s date in your calendar. For a recurring call, look at the first occurrence after the clock change rather than assuming it matches the previous week.
Before 25 October, take a moment to review your next international meeting, online class, or client deadline. You do not need to memorise time-zone rules. You need a clear date, a named location, and an invitation that everyone can interpret consistently.
Compare Current Local Times with DF Tools
The DF Tools Time Zone Converter lets you compare the current local times in two cities and see the difference between them, including applicable daylight-saving adjustments and date differences. It is a simple way to check whether now is a suitable time to contact a client, colleague, or friend abroad. For a meeting on a future date, also verify that specific date in your calendar, especially when it falls after a seasonal clock change.
.jpg)