Vellox Group Ideas Portal
Customers are experiencing confusion and reduced confidence due to inconsistent timezone handling across date fields in the Safety Module and related global reports. Date values are currently stored and displayed using a mix of UTC, local time, and “as‑entered” formats—with no consistent timezone indicator. This leads to misinterpretation of event timelines and poses potential compliance risks, especially for globally distributed teams and regulated environments.
Current Behaviour Causing Issues
Event Date – Stored exactly as entered (no UTC conversion) and displayed as‑entered.
Closed Date – Stored in UTC and converted to local time in some UI views.
Reminder Date – Stored exactly as selected in the date picker (no UTC conversion).
Last Updated Date – Mixed behaviour; some entries are stored in UTC, others in local time, and typically displayed as local.
Reported Date – Stored in UTC; converted to local time only in hard‑coded Global Reports. Newer reports revert to showing raw UTC.
The current mix of storage formats and inconsistent timezone display creates:
Confusion for users navigating Safety screens and reports
Misinterpretation of key incident timelines
Difficulty reconciling dates between modules
Challenges for global teams working across timezones
Increased compliance and audit risk when timelines appear inconsistent
Request
Implement a consistent, standardised approach to handling and displaying all date/time fields across the Safety Module and reports, including:
A single storage model
A consistent display model (local time shown with a clear timezone indicator)
Full visibility of the actual timezone used (e.g., UTC+10 / AEST)
This enhancement will significantly improve clarity, compliance, and customer confidence while reducing errors caused by ambiguous or mixed timezone behaviour.
