---
title: "Why did my meeting move an hour after daylight saving?"
url: https://meet.barq.dev/guides/meeting-time-changed-after-daylight-saving
updated: 2026-11-17
author: "Hammad Ali"
---

# Why did my meeting move an hour after daylight saving?

> **Short answer:** A meeting can move an hour on your calendar when its organizing time zone changes offset before yours does. New York and London have a four-hour gap during their clock-change mismatch weeks instead of the usual five. Check the event's named zone and exact date before changing the appointment.


## Why did my meeting time change after daylight saving?

A meeting time changed by daylight saving usually reflects a difference between the zone anchoring the appointment and the zone displaying it. Keeping 09:00 fixed in New York can change London's displayed hour when only one city has changed its clocks. Check the anchor first.


Two commitments are possible: "always 09:00 in New York" and "always the same UTC instant". They aren't interchangeable across the year. Agree which one the appointment is meant to follow before asking the organizer to repair it.


Start with [the general guide to scheduling across time zones](https://meet.barq.dev/guides/scheduling-across-time-zones) if you're choosing a first appointment. This guide is for the narrower problem of a previously sensible time moving after a clock change.


We show booking-page times in the guest's time zone in Barq Meet. That display conversion doesn't mean both people will keep the same wall-clock hour through every seasonal transition.


## When does a New York and London meeting shift by an hour?

The gap becomes four hours after New York starts daylight saving but before London does, and after London ends daylight saving but before New York does. At other example dates below, the gap is five hours. The mismatch is temporary. For a conversation spanning [dated New York and São Paulo hours](https://meet.barq.dev/meeting-planner/new-york-and-sao-paulo), check the shared workday before repeating a familiar start in another season.


The verified dates are 8 March and 1 November for the United States in 2026, versus 29 March and 25 October for the UK. In 2027, the US changes on 14 March and 7 November; the UK changes on 28 March and 31 October.


Sources, as of 17 November 2026: timeanddate's [first-half 2026 dates](https://www.timeanddate.com/time/dst/2026a.html), [second-half 2026 dates](https://www.timeanddate.com/time/dst/2026b.html), [first-half 2027 dates](https://www.timeanddate.com/time/dst/2027a.html) and [second-half 2027 dates](https://www.timeanddate.com/time/dst/2027b.html). Future rules can change. The [2026 and 2027 daylight-saving date reference](https://meet.barq.dev/guides/daylight-saving-time-dates-2026-2027) brings the checked transitions together.


| Date | New York start | London display | Gap |
| --- | --- | --- | --- |
| 2 March 2026 | 09:00 | 14:00 | 5 hours |
| 9 March 2026 | 09:00 | 13:00 | 4 hours |
| 30 March 2026 | 09:00 | 14:00 | 5 hours |
| 26 October 2026 | 09:00 | 13:00 | 4 hours |
| 2 November 2026 | 09:00 | 14:00 | 5 hours |
| 15 March 2027 | 09:00 | 13:00 | 4 hours |
| 29 March 2027 | 09:00 | 14:00 | 5 hours |
| 1 November 2027 | 09:00 | 13:00 | 4 hours |
| 8 November 2027 | 09:00 | 14:00 | 5 hours |

Method: these examples were computed with Luxon using America/New_York as the source and Europe/London as the destination, on each stated date. Every row starts with 09:00 in New York; no fixed abbreviation or manually subtracted offset supplied the conversion.


## Should I move the recurring meeting or change its time zone?

Ask the organizer which city's working hours should stay fixed, then agree any changed time with everyone affected before editing the event. Moving one occurrence to counter a temporary mismatch can create another error after the second clock change. Don't compensate twice.


For example, a weekly call anchored to New York at 09:00 appears at 13:00 in London on 15 March 2027 and at 14:00 on 29 March. If London must keep 14:00 throughout, the organizer needs to plan the New York change during the mismatch.


This is a [recurring meeting](https://meet.barq.dev/glossary/recurring-meeting) daylight saving decision for the people arranging the series. We don't offer automatic recurring-series bookings, so Barq Meet isn't a mechanism for rewriting every occurrence of an existing series.


For a single replacement appointment, [send a dated one-off offer](https://meet.barq.dev/guides/one-off-meeting-links) after agreeing which hours work. Include the date and both local times in your message so nobody has to infer which week you mean. For a conversation spanning [dated San Francisco and Tel Aviv hours](https://meet.barq.dev/meeting-planner/san-francisco-and-tel-aviv), check the shared workday before repeating a familiar start in another season. For a conversation spanning [dated San Francisco and Singapore hours](https://meet.barq.dev/meeting-planner/san-francisco-and-singapore), check the shared workday before repeating a familiar start in another season.


## How do I prevent a DST meeting time shift on new bookings?

Set your availability in the named zone whose working hours you want to protect, then inspect actual dates on both sides of the transition. Use city-based zones such as Europe/London instead of treating a winter offset as permanent. Test the dates that matter.


We let each availability schedule carry its own time zone. In the event editor, "When people can book" selects the schedule, so check the schedule attached to the event you actually share, especially if you maintain several.


1. Identify the host city that should keep its working hours.
2. Open Events and select Availability beside + Create, then select the schedule used by the event.
3. Confirm the named zone and weekly hours for that schedule.
4. Add date overrides when you intentionally want different hours during a mismatch week.
5. Open the public booking page and inspect a date before and a date after each city's transition.
6. Make a test booking and compare the guest confirmation with the intended local start.


We check selected Google calendars again at confirmation. That prevents accepting a newly conflicting appointment; it doesn't choose which country's wall-clock time a recurring series should prioritise.


## How can I check whether the daylight-saving repair worked?

Compare a dated appointment in the host zone and guest zone, then repeat on the other side of the transition instead of checking only today's offset. The expected result is an agreed local time for each participant. Write both times down. The [London-to-Nairobi meeting planner](https://meet.barq.dev/meeting-planner/london-and-nairobi) compares dated working-hour overlap; confirm individual calendars after choosing a candidate window.


A 30-minute test at 09:00 New York on 15 March 2027 should be 13:00 to 13:30 London. On 29 March, the same New York start should be 14:00 to 14:30 London. These are the calculated conversions from the table, not evidence of a product booking performed by us.


| Symptom | Likely explanation | Next check |
| --- | --- | --- |
| Only one participant sees an hour change | Cities changed on different dates | Compare the exact date in both zones |
| Every future date is off | Wrong schedule or display zone | Inspect the named zone, not its abbreviation |
| A corrected event shifts again later | Temporary mismatch was treated as permanent | Recheck the second transition |
| Correct hour has no bookable slot | Availability or busy time excludes it | Inspect the event's schedule and conflicts |

Use [the availability controls](https://meet.barq.dev/features/availability-rules) for deliberate exceptions. Review [included scheduling options](https://meet.barq.dev/pricing), then [create a date-tested booking page](https://meet.barq.dev/app/sign-in) for the next appointment.

## Steps

1. **Identify the event anchor zone**: Ask which city should keep a fixed local meeting hour. Record the event date and both participants' named zones.
2. **Compare dates around the transition**: Check one date before the clock change and one after it. New York and London can change on different Sundays.
3. **Inspect Availability for new bookings**: Open the schedule attached to your event and verify its time zone. Check the selection under When people can book.
4. **Agree any replacement time**: Confirm the intended local hours with the other participant before moving an existing appointment. Handle an existing recurring series with its organizer.
5. **Test a dated appointment**: Inspect the public page and a trial confirmation for the intended date. Repeat the conversion after the second city changes clocks.

## Frequently asked questions

### Does daylight saving mean my calendar lost the appointment?

Usually the issue is the displayed hour, not a missing event. Compare the dated appointment in both named zones and ask the organizer which zone anchors it before deleting or recreating anything. Compare the original appointment's instant and current local display before creating a replacement, because a changed hour label can describe a valid conversion instead of a missing calendar record.

### Should I write EST in every invitation?

Use a named city zone and full date instead. A fixed winter abbreviation can communicate the wrong offset during summer or a mismatch week; America/New_York identifies the rules used for the dated conversion. Use the named city and dated occurrence when converting, checking whether daylight or standard time applies instead of using a winter abbreviation as a permanent label for New York.

### Will both sides always keep the same local hour?

No. When two places change offsets on different dates, one fixed appointment can't preserve both local hours throughout the transition. Agree whose working hours stay fixed, or explicitly arrange different times for those weeks. Decide which city's local clock the arrangement follows, then review an occurrence after each transition so the other side knows when its displayed hour will temporarily or permanently change.

## Related pages

- [How to schedule meetings across time zones](https://meet.barq.dev/guides/scheduling-across-time-zones)
- [Daylight saving time dates 2026-2027 by country](https://meet.barq.dev/guides/daylight-saving-time-dates-2026-2027)
- [Booking availability rules for a day with breathing room](https://meet.barq.dev/features/availability-rules)
- [How to create a custom times link](https://meet.barq.dev/guides/one-off-meeting-links)
- [What is a recurring meeting?](https://meet.barq.dev/glossary/recurring-meeting)
- [Best time to meet: San Francisco and Tel Aviv (2026)](https://meet.barq.dev/meeting-planner/san-francisco-and-tel-aviv)

[Create your free booking link](https://meet.barq.dev/app/sign-in)
