How to Schedule Recurring Meetings When Daylight Saving Time Keeps Changing

You set up a weekly team standup in October. Everyone joins at the right time. Then March arrives, daylight saving time kicks in, and suddenly half your team is an hour early while the other half wonders where everyone went. Sound familiar?

Why daylight saving time breaks recurring meetings

Daylight saving time creates scheduling chaos because it’s inconsistent across the world.

The United States springs forward in March and falls back in November. Europe changes in late March and late October. Australia shifts in October and April. And dozens of countries don’t observe DST at all.

When you create a recurring meeting, your calendar app needs to know which time zone rules to follow. If you schedule a meeting for “10 AM” without specifying a time zone, different team members see different times after DST transitions.

Here’s what goes wrong. Your calendar might anchor the meeting to your local time zone. When your clock springs forward, the meeting time adjusts for you but not for teammates in regions that haven’t changed yet. Or worse, teammates in areas that never observe DST.

The result? Your 10 AM meeting becomes 9 AM for some people and stays 10 AM for others.

This isn’t a small problem. Teams waste hours every year rescheduling meetings, missing calls, and apologizing for confusion.

Understanding how calendar apps handle time zones

Most calendar applications store event times in UTC (Coordinated Universal Time) and then display them in your local time zone.

When you create a recurring meeting, the app needs to decide whether the event should:

1. Stay fixed in UTC (the absolute time never changes)
2. Stay fixed in a specific time zone (adjusts when that zone shifts for DST)
3. Float with your device’s time zone (changes whenever you travel)

Different apps make different default choices.

Google Calendar, Outlook, and Apple Calendar typically anchor recurring events to a specific time zone. When that zone observes DST, the event time shifts in UTC but appears consistent to people in that zone.

The problem emerges when your team spans multiple zones with different DST schedules.

A meeting set for “10 AM Eastern” will always be 10 AM in New York. But the gap between New York and London changes from five hours to four hours when the US springs forward before Europe does.

For three weeks each spring and fall, recurring meetings drift by an hour for international participants.

How to set up recurring meetings that survive DST transitions

Follow these steps to create recurring meetings that work across time zones and DST changes.

1. Choose a lead time zone. Pick one reference time zone for the meeting and stick with it. This should typically be where the meeting organizer or majority of participants are located.

2. Explicitly set the time zone in your calendar. Don’t let the app guess. When creating the event, find the time zone selector and choose the specific zone, not just “my current location.”

3. Communicate the time zone in meeting invitations. Always include the time zone abbreviation in the meeting title or description. Write “10 AM ET” not just “10 AM.”

4. Add UTC time to recurring meeting descriptions. Include the UTC offset in the meeting notes. This gives everyone an absolute reference point that never changes with DST.

5. Set calendar reminders before DST transitions. Mark your calendar for the Sunday before DST changes in major regions. Review all recurring meetings that week.

6. Audit recurring meetings twice a year. Check every recurring event after spring and fall transitions. Verify the times still work for all participants.

These practices might seem tedious at first. But they prevent the far more tedious work of chasing down confused teammates and rescheduling missed meetings.

“The single biggest scheduling mistake distributed teams make is assuming their calendar app will handle time zones automatically. It won’t. You need to be explicit about which zone anchors each recurring meeting, or you’ll spend March and November apologizing.”

Common mistakes when scheduling across DST boundaries

Here are the errors that trip up even experienced remote team coordinators.

Mistake	Why it fails	Better approach
Using “floating” time zones	Meeting drifts when you travel	Always anchor to a specific zone
Assuming everyone changes clocks the same day	US and Europe shift on different dates	Check regional DST calendars before scheduling
Setting meetings in your local zone by default	Forces others to do mental math twice a year	Rotate the reference zone or use UTC
Forgetting to update standing meetings	Old recurring events keep the wrong time	Audit and recreate recurring events after transitions
Not documenting the time zone in meeting titles	Participants guess which zone you meant	Always include “ET”, “PT”, “UTC”, etc.

The “floating” time zone mistake deserves extra attention. Some calendar apps offer a “floating” or “no time zone” option. This makes the meeting time follow whatever time zone your device is currently in.

That sounds convenient. But it means the meeting time changes when you travel. And it makes the meeting appear at different times for different participants based on their device settings.

Never use floating time zones for recurring team meetings.

Tools that handle daylight saving time correctly

Not all scheduling tools treat DST transitions equally well.

Here’s what to look for in timezone-aware scheduling software:

• Automatic DST adjustment based on IANA time zone database
• Visual indicators showing when time gaps exist between zones
• Warnings when scheduling across DST transition dates
• Ability to set a permanent reference time zone for recurring events
• Display of multiple time zones simultaneously

Google Calendar handles DST reasonably well if you explicitly set the time zone for each event. But it doesn’t warn you when scheduling meetings during the three-week gap when US and European DST schedules diverge.

Outlook offers strong time zone support and shows multiple zones in the calendar view. The “time zone” dropdown in event creation is more prominent than in Google Calendar.

Specialized tools like 7 meeting scheduling tools that actually respect time zones often provide better DST handling than general calendar apps.

World Time Buddy and similar timezone converters help you visualize how meeting times shift across DST transitions. But you still need to manually update your calendar events.

Some teams find success with the 3-hour window rule for finding meeting times that work regardless of DST changes.

Creating a DST transition checklist for your team

Build a repeating checklist that runs twice a year, two weeks before major DST transitions.

Your checklist should include:

• List all recurring meetings that include participants in regions with different DST schedules
• Verify the time zone setting for each recurring event
• Check if any meetings fall during the overnight transition period
• Send reminders to all participants about upcoming time changes
• Update meeting descriptions with new UTC offsets if needed
• Test that calendar invitations display correctly for participants in each time zone
• Document which regions change clocks and on what dates

The overnight transition period needs special attention. If you schedule a recurring meeting for 2:30 AM in a region that springs forward at 2:00 AM, that meeting time doesn’t exist on transition day.

Most calendar apps will skip that occurrence or shift it forward. But you should never rely on automatic behavior for critical meetings.

Better to avoid scheduling recurring meetings between 1:00 AM and 3:00 AM in any time zone that observes DST.

Alternative strategies for globally distributed teams

Some teams solve the DST problem by eliminating the need for synchronized meetings entirely.

Building an async-first communication culture reduces dependence on recurring meetings. When you don’t need everyone online at the same moment, DST transitions become irrelevant.

Async standups work particularly well for teams spanning 12 or more time zones. Team members post updates on their own schedule. No one needs to wake up at 3 AM or stay late.

For teams that must meet synchronously, the timezone rotation strategy distributes the burden of inconvenient meeting times. You rotate which zone the meeting favors, so no one always gets the bad slot.

This approach naturally accommodates DST transitions. When clocks change, the meeting time shifts for everyone, but the rotation pattern stays fair.

Another option is to schedule meetings in UTC and train your team to think in universal time. This eliminates all DST confusion because UTC never changes.

The downside? Most people struggle to mentally convert their local time to UTC. You’ll spend time explaining “16:00 UTC is 11 AM for you but 9 AM for Sarah.”

What to do when a DST transition breaks an existing meeting

Despite your best planning, you’ll eventually discover a recurring meeting that broke during a DST transition.

Here’s how to fix it:

1. Don’t try to edit the broken occurrence. Calendar apps often struggle to correctly update a single instance of a recurring event after DST shifts.

2. Delete the entire recurring series. Yes, really. Trying to patch a broken recurring event usually creates more problems.

3. Recreate the series with the correct time zone explicitly set. Take 30 seconds to double-check the time zone dropdown before saving.

4. Send a new invitation to all participants. Don’t assume the updated event will sync correctly. A fresh invitation ensures everyone gets the right time.

5. Add a note explaining the change. A brief “Updated to fix DST transition” message prevents confusion.

This might seem drastic. But recreating the series is faster and more reliable than debugging why the third Tuesday’s meeting is an hour off for half your team.

Teaching your team to think in time zones

Individual team members can prevent DST confusion by adopting better timezone habits.

Encourage everyone to:

• Display multiple time zones in their calendar app
• Set their calendar to show time zone labels on all events
• Add a world clock widget to their phone or desktop
• Learn the UTC offset for their own time zone
• Verify the time zone before accepting meeting invitations
• Speak times aloud with the zone included (“Let’s meet at 2 PM Eastern”)

Creating communication guidelines that include time zone protocols helps new team members learn these habits faster.

Some teams use Slack bots or similar tools that automatically convert times when someone posts “Let’s sync at 3 PM.” The bot replies with the equivalent time in each team member’s zone.

These small automation touches reduce the mental overhead of timezone math and prevent mistakes during DST transitions.

When meetings stay synchronized even when times shift

Here’s the good news. If everyone on your team lives in regions that observe DST and they all change on the same date, recurring meetings will stay synchronized.

A meeting at “10 AM Pacific” will always be “1 PM Eastern” because both zones spring forward and fall back together.

The problems only emerge when your team includes:

• Participants in regions with different DST transition dates (US vs Europe)
• Participants in regions that don’t observe DST at all (Arizona, Hawaii, most of Asia, etc.)
• Participants who travel frequently between time zones

For teams that span these boundaries, you need the explicit time zone practices described earlier.

But if your entire team lives in the continental United States, DST transitions should be relatively painless. Your recurring meetings will adjust automatically as long as you’ve set the time zone correctly.

Making your calendar work harder for you

Modern calendar apps offer features that can reduce DST headaches.

Look for these often-overlooked options:

• Secondary time zones. Google Calendar and Outlook let you display a second time zone alongside your primary zone. This makes it easier to schedule meetings for teammates in different regions.

• Working hours settings. Set your working hours in your calendar. When others try to schedule meetings with you, the app will show them which times work.

• Time zone labels in event titles. Some apps can automatically append the time zone to event titles. This provides a constant reminder of which zone anchors each meeting.

• Calendar color coding. Use color-coded calendars for managing team availability to visually distinguish meetings anchored to different time zones.

These features won’t prevent all DST problems. But they reduce the cognitive load of managing meetings across time zones.

The less mental math required, the fewer mistakes you’ll make when clocks change.

Keeping everyone informed during transition periods

Communication matters as much as technical setup when DST transitions approach.

Send a team-wide reminder one week before major DST changes. Include:

• Which regions will change clocks and on what date
• How this affects recurring team meetings
• Where to find the updated meeting times
• Who to contact if their calendar looks wrong

Some teams create a shared document listing all recurring meetings with their reference time zones and current UTC offsets. Update this document after each DST transition.

This gives everyone a single source of truth when they’re unsure if a meeting time changed.

Meeting recordings done right become even more valuable during DST transition periods. When people inevitably miss meetings due to time confusion, recordings let them catch up without disrupting the team.

Your recurring meetings can survive the clock changes

Daylight saving time doesn’t have to wreck your meeting schedule twice a year.

Set explicit time zones for every recurring event. Audit your calendar before transitions. Communicate clearly about which zone anchors each meeting. And consider whether some of your recurring meetings could become asynchronous updates instead.

These practices take a few extra minutes when creating meetings. But they save hours of confusion and rescheduling when clocks change.

Your team will thank you when they show up at the right time, every time, regardless of what the clocks do.