Relative time fits the recent past; absolute time fits reconstruction
Aliases: time ago · fuzzy time · calendar time · recency label
What it is
“Three minutes ago” answers “how close to now”. “19 Sep 14:32” answers “which cell on the calendar this fell into”. Relative time fits the recent past; absolute time fits reconstruction. Fresh updates, messages, comments: people want recency. Reconciliation, evidence, lining several events into a history: people want a clock face that can be aligned. Year-month-day order and twelve- versus twenty-four-hour clocks are a different set of locale habits; they are not this question.
Why it happens
Recent events are encoded in memory as distance from now: a few seconds, a few minutes, just now. While that distance is short, a relative label and memory share a ruler; no conversion is required. Overnight, distance coding dulls: “two days ago” stops lining up with a weekday, a meeting, a file version. Absolute time pins the event to a shared calendar, so tracing, comparing and citing have a public coordinate.
A list whose job is “is there anything new” is faster with relative labels, because they speak the sort key. Pull one record out of the list to verify it, and relative fails: two inboxes, two zones, a week later, none of them can recover the same instant from “three days ago”. The two formats are not aesthetic options; they answer two questions.
Studying it
Ask people which of a set of timestamps is newer, or which event happened first, comparing relative labels, absolute clock faces, and both side by side. Split a near window (minutes to hours) from a far window (days to weeks), or the result is a false average — “relative is always better” or “absolute is always clearer”.
Independent variables: label type (relative / absolute / mixed), distance from now, whether the task requires aligning across records. Dependent variables: accuracy and speed of recency judgements, accuracy of placing two events on a calendar, whether people can later say “which day it happened”.
In the lab, “now” is pinned by the experimenter; in a real UI, “now” keeps moving. How well a relative label is understood also depends on whether it is allowed to go stale — a separate layer, not to be folded into one accuracy score for “should we use relative”.
Where it stops holding
Legal, medical, financial and audit records need absolute time from day one; relative loses the coordinate at verification. On a pure chat timeline, a dense absolute clock face washes out recency; a date anchor at day boundaries is often enough. The same record may change format from list to detail: relative in the list to scan recency, absolute in the detail to cite. In cross-zone collaboration, “three hours ago” still holds, because it names a distance; once the question is “when did it happen”, relative does not help, and the display must land on an absolute instant with a zone.
Applying it
- Use relative on lists whose job is recency within a few hours of now. Use absolute where the task crosses days, verifies, or cites.
- On a timeline, insert date anchors when crossing today / yesterday / earlier. Do not ship a whole column of only “n days ago”.
- Do not make relative the only format: at least the detail must offer a copyable absolute instant.
- How to check: take a comment from three minutes ago and one from twelve days ago. Ask “which is newer” and “what weekday was that”. Relative should win the first; relative should fail the second, absolute should succeed. A ledger that only says “two days ago” should fail a reconciliation task — that is the counterexample.