How to record a source freshness date so readers know whether a summary is still current

A source freshness date helps readers distinguish “this was published then” from “this was checked recently.”

The basic pattern is to record four dates when they are available: source published, source last updated, page retrieved, and summary reviewed. The published date belongs to the source. The updated date belongs to the source owner if they provide it. The retrieved date shows when the page or file was accessed. The reviewed date shows when the writer compared the summary against the source trail.

This matters because many summaries stay useful after their original source date, while others become risky quickly. A tax threshold, product plan, API field, visa rule, price comparison, or government PDF may change without changing the visible title. A reader who sees only “2024 report” may assume the summary is old. A reader who sees “source checked on 2026-06-24; no material change found” can judge the page more fairly.

Write the freshness note near the claim it protects. For example: “Source published 2025-11-08, last updated 2026-02-14, checked against this summary on 2026-06-24.” If the source changed, say what changed. If the check found no relevant change, say that narrowly rather than claiming the whole topic is current.

Avoid turning the date into a decoration. If readers cannot tell which claim was checked, the date does not help. The practical goal is a source trail that lets someone decide whether to trust, reopen, update, or replace the summary.

How to record a source freshness date so readers know whether a summary is still current

// COMMENTS

ON THIS PAGE