Know your audience
Every incident lead has a story where “7:00” meant sunrise to someone in Dallas and 19:00 to the engineer in Berlin. North America still leans on AM/PM, but airlines, militaries, and most of the planet live in 24-hour time. When a brief crosses borders, publish both: “Deployment review — 16:30 UTC (08:30 Pacific / 17:30 London).” Default to 24-hour when there is doubt so nobody has to guess whether “midnight” meant the start or the end of the day.
Example: Calendar invite
Build the invite in UTC, then paste a blunt sentence in the description: “Local times: 09:00 New York / 14:00 London / 23:00 Singapore.” Sanity-check it in the Timezone planner before sending. If people keep second-guessing the date, drop a screenshot of the grid into the doc so the argument ends.
Example: Wallboard copy
Label outage or broadcast wallboards in 24-hour so the clock tiles line up: “Sydney — 07:15” beside “UTC — 20:15.” If a feeder system spits out 12-hour values, keep them but add the suffix in plain text: “07:15 AEDT” or “07:15 (UTC+11)” so runners don’t have to translate mid-shift.
Avoiding AM/PM traps
- Write midnight as 00:00 or 24:00 (and say “midnight at the start/end of the day” for 12-hour) so crews don’t show up twelve hours early.
- Never label noon as 12:00 AM—call it 12:00 PM or “12:00 (noon)” so finance and legal stop misfiling deadlines.
- Always note the weekday when you cross the dateline: “Tuesday 07:00 Auckland (Monday 15:00 New York)” keeps travel and ops in sync.
Rolling out a new format
When you migrate a company from 12-hour to 24-hour notation, start with status mails and paging templates before touching customer copy. Include a tiny legend (07:00 ↔ 7 AM, 19:00 ↔ 7 PM) in every announcement so nobody has to ask. Have teams dry-run their invites through the Timezone tool to confirm both display modes read correctly.
Quick conversion cheats
- Add 12 to PM hours to reach 24-hour (2 PM → 14:00) and subtract 12 from anything ≥13 when people insist on AM/PM.
- Remember 00:00 is midnight at the start, 24:00 is midnight at the end—use the right one so day-close reports line up.
- Pad single-digit hours with a leading zero (09:05) so dashboards and runbooks stay aligned when pasted into sheets.
Try the tools
Related guides
FAQ
- Can I force 12-hour output in TimeyKit tools?
- The tools stay in 24-hour for clarity, but the narrative text usually includes AM/PM equivalents. If a client demands 12-hour, copy the values out and let your OS clock or spreadsheet reformat the final line.
- Why do some countries write 2400?
- Military and aviation checklists use 2400 to mark the end of a day. Civil schedules prefer 00:00 to mark the start of the next day. They describe the same instant—choose the one that keeps your auditors happy.
- Is 24-hour format harder for stakeholders?
- Only during the first sprint. Pair early messages with a legend and your audience stops stumbling within a week.
Need to double-check another slot? Open the Timezone tool.