A displayed time needs a stated time zone

What it is

“Three in the afternoon”, with no saying of which clock, is not an instant. It is a phrase. A displayed time needs a stated zone wherever the tacit pact “this is my local afternoon” no longer holds: the clock face carries a zone — an abbreviation, a city, or “your local”. A recency scan of “three minutes ago” names a distance and can go without a zone. Once a clock face is spoken, the zone has to be in the room.

Why it happens

People map a seen clock face onto the watch on their own wrist. That pact holds on a single-zone, single-person calendar. The moment a record will be opened by someone in another zone, pasted into mail, or taken onto a phone that has travelled, the pact breaks: the same string “15:00” is read as different instants. The ambiguity does not alarm on the interface; it detonates at the meeting that does not line up.

A label turns the mapping from default into explicit. City names are stabler than abbreviations: CST may be China Standard or North American Central; abbreviations collide inside a shared vocabulary. On a surface that really is “your local now”, writing “local” is itself an affiliation — better than writing nothing and leaving people to guess server zone versus their own.

Where it stops holding

A purely local alarm that never leaves this device, is never shared, and is never opened across zones can omit affiliation — another layer is noise. Relative distance (three hours ago) does not point at a clock face; a zone adds nothing. When Beijing time and London time are already written as a pair, repeating an abbreviation after every digit is stacking. Timetables printed for one market’s local clock (flights, broadcast) can state affiliation once in the header; as soon as one page mixes two markets, every row has to re-state it.

Applying it

• Any clock face that can be copied, forwarded, or opened in another zone carries its affiliation. Prefer a city or “UTC±”. Do not toss a colliding three-letter abbreviation alone.
• A purely personal, purely local clock face may say “local”. The server’s zone must not silently pose as local.
• Relative distances need no zone. The layer that drops from relative onto a clock face must carry one.
• How to check: send a record that says “15:00” to someone in another zone. They should be able to say which clock that three o’clock sits on, not default to their own. Write CST as a counterexample; two people should produce two expansions. A device-local alarm may omit the zone.

Related

• Same group: I4.05.2 Cross-zone collaboration should show the other person's local time · I4.05.3 DST transitions create nonexistent and repeated clock times
• Nearby: I4.04 Time display format · I4.08 Time zones and daylight saving
• Search terms: timezone label · ambiguous local time · zone abbreviation