Every screen in a regulated product has two readers. The first is the operator, live, doing the work. The second arrives months later: an auditor, an incident reviewer, a lawyer with a screenshot. They ask a different question. Not "what should I do?" but "what did the system claim was true at that moment?"
Most interfaces are designed only for the first reader. The screenshot that surfaces in a review is then ambiguous: unlabelled states, relative timestamps ("2 hours ago," measured from when?), colour as the only carrier of meaning.
01 · THE SCREENSHOT TEST
Our working test: print the screen, hand it to someone with no context, and ask them to state what the system believed. If they can’t, the second reader loses, and the second reader is the one whose reading has consequences.
A screen that cannot be defended six months later was never finished.
02 · CONCRETE RULES
Absolute timestamps alongside relative ones. State names written out, not implied by colour. The data source named on the surface, not in a tooltip. Each rule costs a little density budget, which is why it has to be a requirement, not a courtesy.
03 · A WORKED FAILURE
Take a flagged payment and a screenshot of the operations console, taken by the on-call engineer in the evening. The screenshot shows the payment marked "cleared · 2 hours ago." The review needs to know whether the payment cleared before or after the fraud rule changed at 14:00. The screenshot cannot answer. The timestamp is relative. Nobody recorded the capture time. The console has no way to replay its own past.
Six people now spend forty minutes dating one image: mail headers, chat logs, the engineer’s memory of stand-up. The best available answer is "probably after," and a regulator reads "probably after" as "unknown." The screen told its first reader everything and its second reader almost nothing.
The fix costs two lines of layout. Absolute time renders beside relative time: "cleared 14:22 UTC (2 h ago)." A small UTC clock sits in the corner of every screen, so any screenshot dates itself. Neither line survives a consumer design review, and both read as noise until the day the screenshot is evidence.