Use Internationally Clear Date Formats

· 2 min read

The problem

What does 03/04/2026 mean? March 4th if you’re in the US. April 3rd if you’re in most of Europe. There’s no way to tell without context.

This isn’t a hypothetical problem. As an Italian working at a US-headquartered tech company, I’ve been burned by this more times than I can count. Once I showed up to a meeting that had been rescheduled “to 04/05” and blocked out April 5th. The meeting was on May 4th. I sat there wondering why nobody joined.

The core issue is simple: MM/DD/YYYY and DD/MM/YYYY are ambiguous whenever the day is 12 or less. 01/02/2026 could be January 2nd or February 1st. You’re relying on the reader to guess which convention the writer used.

I don’t want to have to send a Slack message and wait for a reply just to confirm a date. That’s a conversation that shouldn’t need to happen. Save the back-and-forth for things that actually matter.

The fix

Use ISO 8601 by default: 2026-03-08.
Unambiguous, sorts correctly as plain text, and it’s an actual international standard, not a regional convention.

Use named months when writing for humans: 8 Mar 2026 or Mar 8, 2026.
Less clinical, just as clear. Both work no matter where the reader is from. The key is to never write a date where the month and day could be swapped.

Where it bites you

  • International teams. Your Dublin team reads 04/05 as April 5th. Your Boston team reads it as May 4th. Someone misses the deadline.
  • Travel and bookings. A hotel confirmation showing 06/07 could mean you arrive a month late. Visa appointments, flights, rental cars: one ambiguous date and you’re scrambling.
  • Code and data. ISO 8601 sorts naturally as text, works in filenames, and is the default in APIs and databases for a reason.

Why it matters

Inclusivity isn’t just about the big visible things. It’s also about the invisible defaults we impose without thinking. Choosing a clear date format is a small act of caring about the person on the other side, wherever they are.