When daylight saving time changes — or gets abolished permanently — your device clock might update correctly while your apps quietly shift every meeting, alarm, and scheduled event by exactly one hour. Here's how to find which apps are broken and fix each one specifically.
Q1: My device clock is correct but Google Calendar events all shifted by one hour. How do I fix it?
This is the most common DST problem. Google Calendar stores events in UTC and converts to your local time zone — if your time zone setting is wrong or stale, every event shifts.
Fix on desktop (calendar.google.com):
- Go to Settings (gear icon) → General → Time zone.
- Confirm your primary time zone is set to a named zone (e.g., "Central Time - Chicago"), not a raw UTC offset (e.g., "UTC-6"). Named zones update automatically for DST rule changes; UTC offsets don't.
- If it already shows the correct named zone: click it, select a different zone, then switch back to your original zone. This forces a re-sync.
- For events that still look wrong after the zone fix: open the event → Edit → scroll to the time field → confirm the time shown matches your intent → Save.
Fix on iPhone (Google Calendar app):
- Go to Settings (iPhone) → Privacy & Security → Location Services → Google Calendar → set to "While Using." Google Calendar uses your location to auto-detect time zone.
- Inside the Google Calendar app: tap your profile photo → Manage your Google Account → Data & Privacy → Time zone → confirm it matches your current location.
Q2: My iPhone alarms went off an hour early (or late) after the DST change. What happened?
iPhone alarms tied to named days ("Every weekday") use the system time zone. If your iPhone's time zone didn't update after a DST policy change, alarms fire at the wrong time.
Fix:
- Go to Settings → General → Date & Time.
- Toggle Set Automatically off, wait 10 seconds, toggle back on.
- Confirm the time zone shown (below the toggle) reflects your actual location — if it shows a city in a different DST zone, tap it and update.
- After correcting, open the Clock app → Alarm → check each alarm's time. Alarms with a specific time (e.g., "7:00 AM") should now fire correctly. Delete and recreate any alarms that still look off.
Q3: Outlook calendar meetings all shifted by an hour for just me — not for other attendees. How do I fix it without rescheduling everything?
This is a time zone mismatch between your Outlook profile and the meeting organizer's profile. The fix is in your Outlook time zone setting, not in the individual meetings.
Fix on Outlook desktop (Windows):
- Go to File → Options → Calendar → Time zones.
- Confirm "Current time zone" matches your actual location.
- If it shows the right zone but events are still shifted: uncheck "Adjust clock for daylight saving time automatically," click OK, then re-enable it. This resets the DST offset calculation.
- Restart Outlook after changing.
Fix on Outlook Web (outlook.com or Microsoft 365):
- Go to Settings (gear icon) → General → Language and time → Time zone → change to your zone → Save.
- Log out and log back in to apply.
Q4: My Zoom, Teams, or Google Meet meetings are showing the wrong time in my calendar after DST. Do I need to reschedule them?
No — in most cases, the meeting invite itself is correct. The display is wrong because your calendar's time zone setting is off. Fix your calendar's time zone (see Q1 for Google Calendar, Q3 for Outlook) and the meeting times will display correctly without rescheduling.
Exception: If the meeting organizer created the invite in a different time zone and used a raw UTC offset instead of a named zone, the invite won't auto-adjust for DST. In this case, contact the organizer to resend the invite using a named time zone.
Q5: My recurring work schedule app (Shift, When I Work, Deputy, etc.) is showing wrong shift times after DST. Who fixes it?
Workforce scheduling apps store shifts in UTC. After a DST change, shifts can appear an hour off for users in affected time zones.
- Check the app's time zone setting first: Most workforce apps have a "My Time Zone" setting in your profile or account preferences. Verify it matches your actual location and uses a named zone.
- If the wrong time affects only you: update your profile time zone — the shift data itself is fine.
- If it affects your whole team: this is an admin-level setting. Contact your manager or the app's admin to update the organization's base time zone.
- Specifically for When I Work: go to Account → Profile → Time Zone → update → Save.
- Specifically for Deputy: go to My Profile → Timezone → update → Save changes.
Q6: My smart home automations (lights, thermostat schedules) didn't adjust for DST. How do I fix them?
- Amazon Alexa routines: Open the Alexa app → More → Routines → find the affected routine → tap the time trigger → update the time manually. Alexa schedules use the time zone set in your Alexa app: More → Settings → Account Settings → Time Zone — confirm it's correct.
- Google Home automations: Open Google Home → tap your device → Settings → Device Information → Time Zone → reselect your zone. Then go to Routines and verify trigger times.
- Smart thermostats (Ecobee, Nest): Both auto-update for standard DST changes. If they didn't adjust after a permanent DST change: Ecobee → Main Menu → Settings → Time → set manually. Nest → Settings → Schedule → confirm times are correct.
Bottom Line
DST-related app problems almost always come down to one of three things: a calendar using a raw UTC offset instead of a named time zone, a device time zone setting that didn't auto-update, or a smart home automation with a hard-coded time that doesn't adjust automatically. Fix the time zone setting at the account level first — that resolves calendar display issues without touching individual events. For smart home devices, the trigger times need manual correction after any permanent DST change since they don't self-adjust for policy changes the way standard annual DST does.
Which app is giving you trouble? Drop it in the comments with what the time is showing vs. what it should be.
Comments
Post a Comment