Recurring Google Calendar meetings across regions can shift their displayed local relationship around daylight saving changes. Check the actual occurrence dates instead of relying on a fixed hour difference remembered from another season. Regional rules can change, and Google’s guidance warns about limitations for distant past or future events.
Confirm the intended anchor
Open the recurring meeting on a computer and inspect its source time zone and repeat pattern. Determine which region’s local schedule the meeting is meant to follow. An event fixed to that schedule is not necessarily meant to preserve the same wall-clock hour for every participant worldwide.
Review the boundary dates
Inspect occurrences before and after the relevant regional clock changes. Compare both the local time and date for the participants’ zones. Use the service’s city or region choices rather than a bare numeric offset that assumes one permanent relationship.
Do not change the whole series solely because one region’s displayed hour moved as expected. First compare the actual agreed meeting with its authoritative source.
Verify any necessary correction
If a genuine error is confirmed, choose the appropriate recurrence scope and review guest updates and room availability. Check the saved result on representative dates. For long-range schedules, recheck closer to the event when regional rules or product data may have changed. A valid repeat rule does not prove that every distant occurrence has been independently confirmed. Keep the intended regional anchor clear so participants can distinguish an expected seasonal conversion from an actual change to the meeting agreement.
References
Reviewed against the linked official product guidance on November 4, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.