When your community’s timezone switches to or from Daylight Saving Time, event times may appear one hour earlier or later. This can happen right after the time change and affects both one-time and recurring events.
This behavior is expected. GroupApp follows standard calendar rules so events stay in sync with the local time in your community’s timezone and with external calendars like Google, Apple, and Outlook.
DST may cause event times to shift by one hour
GroupApp updates event times automatically to match local time
To keep a fixed “wall-clock” time, manually edit the affected event occurrences
Daylight Saving Time changes the local clock twice a year. In spring, clocks move forward by one hour. In the fall, clocks move back by one hour.
When this happens, GroupApp updates how event times are shown so they still happen at the correct local time. The event itself does not change; the clock does. External calendars show the same change.
In spring, clocks move forward by 1 hour
In the fall, clocks move back by 1 hour
GroupApp updates event start times to match the new local time
Google, Apple, and Outlook calendars stay in sync
If an event is scheduled for 2:00 PM before DST ends, it will appear as 1:00 PM after the time change.
This is expected behavior. Nothing is wrong; the clock changed, and your event stayed aligned with the local time rules.
If you haven’t scheduled events across a Daylight Saving Time change before, the time shift can be surprising. It’s also easier to miss if you created events week by week or manually edited some dates in the past.
Changes to your community’s timezone or differences in member locations can make the shift more noticeable.
You may not have scheduled events across a DST change before
Manual edits can hide the automatic time adjustment
Different regions may see the change more clearly
GroupApp uses the same Daylight Saving Time rules for both single and recurring events. Recurring events make the change easier to notice because you can see several upcoming dates at once.
If only some dates show the old time, those occurrences were manually edited and will keep the time you set.
DST rules apply to both single and recurring events
Recurring events show the change across future dates
Manually edited occurrences keep their custom time
If your community expects a session to stay at the same wall‑clock hour year‑round (for example, always 2:00 PM local), you can pin that hour by editing the affected occurrences after the switch. Those edits persist for the dates you change.
Choose: follow local time rules vs. keep a fixed wall‑clock hour.
Edit the post‑switch (or pre‑switch) occurrences to your preferred time.
Your manual edits will stick for those specific dates.
Automatic DST handling keeps your schedule accurate and consistent across regions and calendars. Without it, events would land at the wrong local hour, cross‑timezone conversions would drift, and external calendars wouldn’t match.
Events stay aligned with the local definition of the hour.
Conversions for members in other time zones remain accurate.
Integrations with external calendars remain consistent.
Yes. Everyone sees events in their own local time. When your community enters or exits DST, the display updates for all members, and external calendars reflect the same shift.
No. Your chosen timezone stays the same; only the seasonal offset changes according to that timezone’s DST rules.
Those specific occurrences were manually edited. Manual edits override the automatic DST adjustment for that date.
Pick a consistent approach for each series. If you want a fixed wall‑clock hour, make quick edits right after the switch so the schedule stays predictable for members.
