How Daylight Saving Time Affects International Meetings

People often assume a city pair always has the same time difference. That is not always true. Some countries observe daylight saving time, some do not, and some change clocks on different weekends.

A recurring meeting can drift by one hour for one team while staying fixed for another. That small shift is enough to create missed calls, late arrivals, and confusion that looks like a calendar bug even when the calendar is behaving correctly.

Daylight saving time moves local clocks forward during part of the year, usually to make better use of evening daylight. The exact rules depend on the country or region. Some places observe DST, some used to observe it and stopped, and some have never used it.

The key point for scheduling is that UTC does not move, but local clocks can. If London moves from UTC+00:00 to UTC+01:00 and another city does not change, the difference between those two places changes.

One-off meetings are easier because you only need to check one date. Recurring meetings are harder because they travel through the calendar. A meeting that works perfectly in February might be awkward in March, fine again in April, and then shift again later in the year.

The issue is especially visible when two countries change clocks on different weekends. The United States and the United Kingdom are a familiar example. For a short period, the usual time difference between New York and London can change by one hour.

There is no single worldwide daylight saving rule. Europe, North America, Australia, New Zealand, parts of the Middle East, and parts of South America all have different histories and policies.

This means a simple sentence like "the meeting is always at 3 PM UK time" may not be enough for a global team. That time may shift relative to colleagues in India, Singapore, Japan, Dubai, or parts of Africa where clocks do not move.

Most modern calendar apps understand timezone rules. The problem is not usually that the software cannot handle DST. The problem is that people expect the meeting to stay at the same local time for everyone, which is not always possible.

For example, a meeting anchored at 10 AM New York time will remain 10 AM for New York attendees. But during certain weeks, London attendees may see a different local time than usual. If the meeting is anchored to London instead, New York may be the side that shifts.

Always check the exact date of a future meeting. For recurring calls, review the next daylight saving change dates for the main cities involved. Do this before the meeting series is created, not after people start declining invites.

For important recurring meetings, look ahead at least three months. Check whether any required city changes clocks during that period. If it does, decide whether the meeting should stay fixed for one anchor city or whether it should be adjusted to preserve a better overlap.

• Use city names instead of ambiguous timezone abbreviations.
• Repeat the selected time on booking confirmation pages.
• Check daylight saving changes before publishing event times.

Every recurring international meeting has an anchor, even if nobody names it. The anchor is the timezone that stays fixed when rules change. If the organizer creates the meeting for 10 AM New York time, New York is probably the anchor.

That may be the right choice, but it should be intentional. If the meeting is for a London-based customer, London may be the better anchor. If the meeting is for a global internal team, rotating anchors may be fairer.

If a team spans North America, Europe, and Asia-Pacific, daylight saving time is only one part of the fairness problem. There may be no meeting time that is comfortable for everyone. In that case, rotating times is often more respectful than pretending one slot is neutral.

A rotating schedule shares the inconvenience. One month may favor Europe and North America. Another may favor Asia-Pacific and Europe. The important thing is to make the rotation visible and predictable.

Many meetings survive because they are familiar, not because they need to be live. Daylight saving transitions are a good moment to ask whether a recurring meeting still deserves a place on the calendar.

If the goal is a status update, a written note may work better. If the goal is a decision, collect input beforehand and invite only the people needed for the final discussion. If the goal is team connection, consider regional sessions instead of one global call.

Before creating a recurring international meeting, list the required cities, choose an anchor timezone, check the next DST changes, review public holidays, and confirm whether the selected time remains fair across the next few months.

Before a transition week, send a short reminder. People appreciate a simple note more than a surprise. "Clocks change in the US this weekend, so please double-check your local time for next week's call" is enough.

Daylight saving time affects meetings because local clocks change unevenly around the world. The fix is not complicated, but it does require attention. Use city-based timezone tools, check the exact date, choose an anchor timezone, and communicate clearly.

For one-off calls, a quick date-aware conversion is usually enough. For recurring meetings, look ahead and decide what should happen when clocks change. The earlier you make that choice, the less confusion your team has to absorb later.