Display Dates Based on Client Browser Locale or Hub Settings

What is the challenge?

Users accessing the platform from different regions see dates in a single, fixed format (e.g., 17 Mar 2026). This causes confusion for users in countries where the expected format is different - particularly in the United States, where Mar 17 2026 is the standard.
When day and month can be swapped (e.g., 04/05/2026), this creates a real risk of misinterpretation, especially during audit, risk, or incident reporting workflows.

What is the impact?

Reduces usability: Users must constantly convert dates mentally, increasing cognitive load.

Creates risk of errors: Incorrect date interpretation can affect audit timelines, control testing dates, incident creation, due dates, and reporting accuracy.

Impacts global rollouts: Multinational clients expect software to respect local conventions automatically.

Increases support overhead: Teams receive unnecessary queries from users unsure whether they are viewing the correct date.

Describe your idea

Enable the system to automatically display dates based on the client’s browser locale/Hub location settings.
Examples:

• US browser/locale: Mar 17 2026 or 03/17/2026

• UK browser/locale: 17 Mar 2026 or 17/03/2026

Key requirements:

• The UI should detect the user’s locale via browser/Hub settings.

• All date fields - lists, record views, dashboards, exports, and date pickers -should render dates accordingly.

• An optional override setting (per tenant) could be considered for organisations with internally standardised date formats.