Clear, unambiguous dates and times prevent missed meetings, costly travel mistakes, and confusion across countries and time zones.
“Catch up moved to 10/05 at 6. See you then”
Think about this, is that 10th of May or 5th of October? Is it 6 am or 6 pm?
People in different regions format the date in different ways:
Figure: 10/05/25 reads differently to Aussie, American and Chinese
Software can also misinterpret it. For example, entering 10/05/2025 on an Aussie laptop could be read as October 5th, 2025, if opened on an American system.
This is why you should avoid numeric-only formats... they can cause major confusion. To make it even clearer, include abbreviated weekdays with dates.
"This email was sent on 10/05/25."
❌ Figure: Bad example - Use slashes on their own, it’s ambiguous
"The email was sent on Sat 10 May 2025."
✅ Figure: Good example - Use "DD MMM YYYY" and include the abbreviated day of the week
Use valid formats to avoid confusion - both 24-hour and 12-hour formats are universal when used correctly:
❌ Figure: Bad example - Incorrect or ambiguous times
✅ Figure: Good example - Correct formatting for time
Avoid the 12 am / 12 pm trap.
Figure: Will you attend this event on the night of the 14th or the 15th?
Always include a time zone for cross-location events: AEST (UTC+10), AEDT (UTC+11), PT (UTC–8), etc.