Design system
Case study: Time stamp guideline
Design system
Case study: Time stamp guidelines
​Summary
A detailed timestamp guideline was introduced to define when and how time should be displayed across the platform. It extends beyond current Maersk Design System standards to better support operational and user needs. Clarifying how times should be displayed when showing system‑generated timestamps versus time‑ and location‑sensitive data with geographical context.
​Problem
A supply chain customer incurred significant demurrage and detention charges due to a misinterpretation of displayed timestamp. The platform displayed timestamps in UTC format, while the customer interpreted them as local time. Although the Maersk design system recommends using UTC format for consistency, it lacks clear guidance for user context. In practice, many customers expect and rely on local time displays, as they are not familiar with converting UTC to their local time zone.
Maersk design system time zones best practice
Approach
Enhance and extend the existing Maersk Design System date and time guidelines to better support supply chain platform's operational complexity and global user base.
SCP date and time guidelines
Solution
A comprehensive timestamp guideline that defines:
-
When to display UTC versus local time
-
How to present timestamps with clear location or timezone context
-
Standardized rules for high-impact elements such as deadlines, cut-offs, demurrage & detention timers, and system logs
This ensured consistent and intuitive time representation across all modules and touchpoints across the platform.
Container tracking - date and time display
Impact
-
Consistent time display across the platform
-
Reduced customer risk of costly errors from timezone misinterpretation
-
Stronger cross-functional alignment in implementation
-
Improved clarity for users managing time-critical operations