Managing programs across different time zones can be challenging, but with iECHO, handling global scheduling is smooth and hassle-free.

It automatically manages time zone differences and daylight savings time, eliminating the need for manual adjustments. Program administrators and participants both benefit: notifications are sent according to each participant’s preferred time zone, streamlining communication and reducing the need for separate updates.

Here’s how time zones are handled for users:

For Program Admins:

In iECHO, each Participant Group is assigned a default administrative time zone, which is used for scheduling and automated notifications.

As a program administrator, you can create a Participant Group to schedule sessions in either the default time zone of the batch or your own time zone if it differs. Just set the date, time, and time zone that work best for you when creating a session.

Participants from around the world may be in different time zones. When a session is scheduled, the time and date are shown to each participant in their local time zone, which iECHO automatically detects when they log in. Users can also adjust their time zone in their User Profile settings.

For Participants:

Participants will see the date and time of each session in their local time zone, or in the time zone they’ve chosen in their profile settings.

<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" /> How Daylight Savings Time is handled?

In various time zones, the clocks move forward by 1 hour in Spring / Summer and move back by 1 hour in Fall / Winter. This is called “Daylight Savings Time”.

Note: If a program is scheduled in a time zone that observes daylight savings time (DST), recurring sessions will stay on the same schedule. However, for participants in time zones that don’t observe DST, the session time may shift by up to 1 hour.

Daylight Savings Time Update: January 2024

</aside>

Here’s an example of daylight savings time impact: