Twelve-hour clocks must mark a.m. and p.m.
Aliases: am pm · 12-hour ambiguity · seven in the morning or evening
What it is
A twelve-hour clock splits the day into two loops of 1–12, so the same digits name two instants. The a.m. / p.m. mark is the bit that unbinds that two-to-one map. Without it, “7:00” may be the start of work or dinner. A twenty-four-hour clock has no such ambiguity. The issue is the digits’ double meaning, not which calendar day owns a midnight span, and not how many minutes a notch is.
Why it happens
Speech often drops a.m. and p.m. and lets context fill in (“see you at seven” at the office defaults to morning). An interface does not share that context; the dropped bit must be written back. Worse is 12:00: some people treat 12 a.m. as midnight, others as noon, and surveys keep finding that error. A control that offers hours 1–12 but paints a.m./p.m. as fine print, or defaults to a.m., will move half of bookings to the wrong half-day. Users from 24-hour regions may type 19 into an hour box, get 7:00, and never touch the meridian. The ambiguity is in the encoding: two digits map onto two absolute instants.
Studying it
Have twelve-hour and twenty-four-hour users each fill a set of instants (7 for work, 7 for dinner, noon, midnight). Record wrong half-day and 12:00 interpretations. Factors: forced a.m./p.m. choice, 12 written as 12 or 0, defaults. Outcomes: half-day error rate, 12:00 confusion. Do not use only afternoon-tea times as stimuli; that hides midnight/noon. Pair spoken “seven” with the interface digits to see whether context compensation happened.
Where it stops holding
A product used only in 24-hour regions, with a 24-hour locale, need not mount a twelve-hour clock. When the OS locale is twelve-hour, an author-forced 24-hour clock fights the user’s clock face; ambiguity becomes “is 19 evening 7.” Speech input “seven pm” heard as 7:00 with pm dropped fails at recognition. All-day events should not travel a twelve-hour clock.
Applying it
- On a twelve-hour UI, make a.m./p.m. as visible as the hour, and require an explicit choice; do not default to a.m.
- Write 12:00 as “noon / midnight,” or add a disambiguating label such as 12:00 p.m. (noon); do not leave a bare 12 AM.
- Allow a switch to 24-hour time, and keep the absolute instant when converting between writings.
- Verify by booking 7 in the morning and 7 in the evening, noon and midnight. Any of the four landing on the wrong half-day means the mark is still too soft. Then ask what 12 a.m. is, and listen whether the explanation matches the system.