How Coruson deals with Time and Time Zones

When recording time Coruson always stores times entered in Coordinated Universal Time (UTC).   

UTC is the primary time standard by which the world regulates clocks and time.  It is within one second of mean solar time at 0° longitude and is not adjusted for daylight saving.  Where English is spoken the term, Greenwich Mean Time (GMT) is often used as a synonym for UTC but is in fact a time zone..

When Users are using the Coruson and Coruson Reporting Applications many Reports have a local time field.

The users should enter the local time when the event occurred into this field.

The application will store this date and time as a UTC time but display as the time entered, the date field will not be altered.

Submission email notification will display the local time, as defined by the time zone selected in the Users device.

When viewing on the Web client the date and time will be displayed in the Users selected time zone, as chosen in their user profile (not the mobile device): -

As Coruson stores times in UTC there is no need for the User to make any manual conversions. The Coruson system will always display the time and date in relation to the Users selected time zone either defined by the mobile device or their User Profile on the Web.

The following examples may make this clearer.

Scenario 1

• On the Mobile device the time is set to London British Summer Time (BST)*
• User enters date and time of 24/9/19 09:00
• Info displayed in Date & Time field is 24/9/19 09:00 (same as entered in picker)
• User submits report
• On Web the Date and Time display as 24/9/19 08:00 (UTC time)

Scenario 2

• On Mobile the time is set to Honolulu
• User enters date and time of 24/9/19 22:00
• Info displayed in Date & Time field is 24/9/19 22:00 (same as entered in picker)
• User submits report
• On Web the Date and Time display as 25/9/19 08:00 (UTC time)

*BST = GMT & UTC plus 1 hour (normally runs between the end of March and end of October in the UK).