Applies to: Riva Cloud and Riva On-Premise customers synchronizing calendar data for users in affected Canadian regions.

Overview

Beginning November 1, 2026, affected regions of British Columbia, Alberta, and Manitoba will remain on permanent daylight time instead of turning their clocks back one hour.

Customers should verify their operating-system, Outlook, and CRM user time-zone settings. Updating the desktop time zone alone does not update the CRM user profile or necessarily correct existing calendar events.

These changes apply to specific geographic regions, rather than every location using Pacific, Mountain, or Central time.

Recommended Actions

1 Update Workstations and Customer Managed Servers

Install the applicable operating-system updates containing the new time-zone rules on users’ workstations and customer-managed servers involved in calendar processing, including Riva On-Premise servers.

Complete any required restart and verify the configured time zone. Servers intentionally configured to use UTC do not need to be switched to a local time zone.

Riva Cloud customers do not need to update Riva’s hosted servers.

2 Verify Outlook Calendar Settings

For affected users, select the appropriate regional time zone:

Verify settings in the Outlook applications users access, including Outlook on the web. Mobile devices should also have current operating-system updates and the correct regional time zone.

3 Verify the User Time Zone in the CRM

Review each affected user’s time-zone setting in their CRM user profile or personal settings, and update it where necessary.

The desktop, Outlook, and CRM may maintain separate settings. Updating one does not necessarily update the others.

For Salesforce:

• Users already assigned to the appropriate Canadian identifiers, such as America/Vancouver, America/Edmonton, or America/Winnipeg, can retain those selections.
• Users assigned to US equivalents should be changed to the appropriate Canadian time zone.

For other CRMs, confirm the supported regional setting with your CRM provider. Do not select a replacement based only on its current UTC offset; its seasonal rules may differ.

4 Review Existing Appointments and Recurring Meetings

Review calendar items scheduled for November 1, 2026, and later, particularly meetings created before the new rules were available.

Changing a user’s default calendar time zone does not automatically correct every existing appointment. Where an event uses the previous seasonal rules, the organizer may need to update its time zone, confirm the intended start and end times, and send an updated invitation.

Important: Microsoft advises that changing a recurring meeting series’ time zone can reset exceptions, such as individually rescheduled occurrences. Record these exceptions before making changes and recreate them afterward.

How Existing Invitations May Appear

Outlook saves a meeting’s scheduled moment in UTC and displays it in each participant’s configured local time zone. The time zone saved in the original invitation therefore matters.

The following examples use a single meeting on November 4, 2026, with participants in:

• Vancouver: UTC−7.
• Calgary: UTC−6.
• Toronto: UTC−5.

Unless otherwise stated, all participants are using updated regional time-zone settings.

Example 1 An Eastern Organizer Scheduled a 9 am Meeting

A Toronto organizer sent an invitation three weeks earlier for 9:00 a.m. Eastern time on November 4.

The meeting remains at 9:00 a.m. Toronto time:

Vancouver is two hours behind Toronto in November under the new rules.

A Vancouver participant still using the old seasonal Pacific setting could instead see 6:00 a.m., because that setting falls back to UTC−8. Their calendar setting would need correction.

Example 2 A Pacific Organizer Scheduled a 9 am Meeting Using the Old Rules

A Vancouver organizer previously scheduled 9:00 a.m. on November 4 using the old Pacific Time (US & Canada) rules.

Those rules calculated the November meeting using UTC−8. If the saved meeting remains unchanged, participants using updated regional settings would see:

The saved meeting still represents the same moment, but that moment is now 10:00 a.m. in Vancouver.

If the organizer intends the meeting to remain at 9:00 a.m. Vancouver time, they should update the invitation to use the new British Columbia time zone, confirm the intended start time, and send the update.

The corrected meeting would display:

These examples are conditional. If the invitation already used the new regional rules, it may already show the intended times. Recurring series require additional review because their time-zone rules and exceptions can affect individual occurrences.

Riva Cloud Policy Considerations

A standard Riva Cloud policy is not expected to require changes solely because of the new time-zone rules. However, compatibility with this specific change should be confirmed with Riva Support.

Riva documents that policies created in Riva Cloud 2017.5 or later use each user’s CRM time zone by default to determine peak, off-peak, and blackout synchronization periods.

Review older or customized policies with Riva Support if they do not use each user’s CRM time zone. Do not adjust the policy schedule to compensate for an incorrect calendar setting or meeting invitation.

Validate Synchronization

After verifying the settings, test:

• A single appointment scheduled after November 1.
• A recurring meeting spanning the transition.
• A meeting with attendees in regions that continue changing clocks.

Confirm that Outlook and the CRM show the intended local start and end times for each user. Also verify that synchronization occurs during the expected peak, off-peak, and blackout periods.

If Times Do Not Match

Contact Riva Support with:

• Your Riva product and version, where applicable.
• Your CRM and email platform.
• The affected users’ locations and configured time zones.
• An example showing the expected time and the time displayed in each system.
• Whether the issue affects single appointments, recurring meetings, or both.

References

Microsoft: Outlook Time Zone Changes for British Columbia, Alberta, and Manitoba

Salesforce: Canada’s Time Zone Updates

Riva: Create a Sync Policy for Exchange — Riva Cloud