How Time Zones Affect Certificate Completion Dates

Updated June 26, 2026 20:39

Absorb records Certificate dates in Coordinated Universal Time (UTC) and converts them into the time zone of whoever is viewing them. As a result, the same Certificate date can appear differently to Learners and Admins in different time zones, and may even appear to shift to a different calendar day. This article explains how that conversion works for both completion dates and uploaded Certificate dates, where differences can appear, and what to expect when working across multiple time zones.

How Time Zone Conversion Works

Certificate dates follow the same conversion logic throughout Absorb, whether the date is generated on completion or entered manually during an upload:

When a date is recorded, Absorb uses the time zone of the device the Learner or Admin is using at that moment.
The date and time are stored in UTC.
When the date is displayed, Absorb converts the stored UTC value into the time zone of the person viewing it.

Certificate Completion Dates

In Absorb, Certificates are issued dependent on the time zone the Learner is in, and recorded in UTC. This can result in a certificate with a completion date that differs for an Admin in one time zone, while it appears as correct to the Learner in their own time zone.

For example, if a Learner completes a Course at 11:00 PM Pacific Time (PT) on Wednesday, November 16th, Absorb records this as Thursday, November 17th at 7:00 AM UTC. For an Admin, Absorb automatically displays the recorded UTC completion date according to their local machine time zone. If the Admin has their computer set to Eastern time, the completion date will show as Thursday, November 17th, due to this time difference.

Example of a certificate completion date stored in UTC and displayed differently across time zones

Uploaded Certificate Issued and Expiration Dates

When a Course is configured to allow Learners to upload certificates earned outside the system, the Learner can record an Issued Date and an Expiration Date for the Certificate they upload. These fields include a time picker, so the time of day is captured alongside the calendar date and is converted using the same logic described above.

For example, a Learner in New York (UTC-5) selects an Issued Date of March 1, 2026, recorded as 12:00 AM in their device time zone. Absorb stores this as March 1, 2026 at 5:00 AM UTC. When the date is displayed, Absorb converts that stored value into each viewer's time zone:

Learner in New York (UTC-5): March 1, 2026 at 12:00 AM
Same Learner after switching their device to London (UTC+0): March 1, 2026 at 5:00 AM
Admin in Calgary (UTC-7): February 28, 2026 at 10:00 PM

Because the recorded time is close to the start of the day, the calendar date can appear to move to the previous day for viewers in earlier time zones.

Recording an Accurate Time

Selecting an accurate time of day for the Issued Date and Expiration Date improves the precision of the stored record and reduces unexpected calendar-date shifts, especially for certificates with same-day issue or expiration windows.

Where Date Differences Appear

A converted Certificate date can appear in several places, and the same value may display differently in each depending on the viewer's time zone:

The Certificate Upload page, where the Learner records the dates.
The Learner's transcript.
The Admin view of the transcript and User records.
Reporting, including any report that displays Certificate dates.

Working Across Multiple Time Zones

This behavior is working as designed. When your organization operates across multiple time zones, expect the same Certificate date to display differently for each viewer, and to shift if a Learner changes their device time zone after uploading. For more on how time zone settings are applied, see Overview of the Time Zone Selector.