Put uncertain dates on an honest timeline

A tidy timeline can conceal uncertain evidence. An exact-looking date may come from a later upload, a timezone conversion, or a software default rather than the historical event itself. The goal is to preserve the precision you have, including its limits. 1. Define the event. A platform may have a prototype, private test, public launch, regional rollout, and later announcement. Write which milestone the record describes before choosing a date. The same discipline applies to a meme's source photograph, first located caption, and later surge in circulation. 2. Collect every relevant date with a label. Use separate notes for event date, publication date, last update, archive capture, and your access date. Record the source of each value. If a page was updated years later, do not assume every paragraph was part of its original publication. 3. Preserve the original display. If a post shows a clock time, record the timezone when known. A conversion across midnight can change the calendar date. If the interface says two days ago, note the time you observed it and treat any converted date as an inference, not a directly printed fact. 4. Match precision to support. Use a year when only a year is established and a month when only a month is established. Do not insert January 1 simply to satisfy a date field. If your tool requires a sortable approximation, keep that technical value separate from the reader-facing date and explain the approximation. 5. Express competing evidence. When two credible sources disagree, record both dates and the reason each gives. Decide whether the record can use a range, a qualified date, or an explicit unresolved note. The Library of Congress EDTF specification provides structured ways to represent uncertain, approximate, and partly unspecified dates; software support varies, so also write a plain-language explanation. 6. State the timeline rule. Say whether entries are ordered by event dates or earliest documented appearances. Otherwise readers may compare unlike things. If several records share a year without finer precision, their visual order should not imply a known sequence within that year. A practical note might read: the source describes a public release in May; a press announcement is dated May 12; no exact release day was verified. That is more useful than quietly turning the announcement into the launch. Review uncertain entries when new primary evidence appears, preserving the prior note so the change remains understandable. Precision earns its place through evidence, not through the formatting of a date picker.

Editorial review: 2026-09-23. New evidence may change this account.

Report a problem with this record