A source can be authentic and still be out of date for the sentence you want to publish. A freshness review asks whether the source is appropriate for the claim at the time of publication. It does not reduce reliability to a single age threshold.
Record three dates
Keep source_published_at, source_updated_at when available, and checked_at. The first describes when the source originally appeared. The second may indicate a revision. The third records your own review. Do not invent an update date when a page does not display one.
Classify the claim
Stable background, product availability and developing news need different attention. An explanation of a basic data structure can remain useful for a long time. A sentence saying a feature is available today requires a check that matches the current access conditions. Age is a clue to investigate, not proof that a statement is false.
An illustrative claim record could be:
{
"claim_id": "availability-01",
"claim_type": "current_availability",
"source_published_at": null,
"source_updated_at": null,
"checked_at": null,
"needs_current_review": true,
"decision": "hold"
}
The null values are intentional. They demonstrate missing information rather than fabricating dates for a real source.
Preserve what changed
When you revisit a source, compare the relevant qualification with the draft. Has an invitation-only pilot become a public release? Has the page removed a region or account restriction? Does a later source supersede the original? Record the evidence and update the wording only to the extent that the source supports it.
Set a specific hold rule
For example: “Do not publish an available-now claim until eligibility has been checked against the current official source.” That rule is more inspectable than asking an assistant to “make sure everything is fresh.” An assistant can help locate time-sensitive language, but the editor still needs to examine the source.
Finish by checking the headline and takeaway. Those are common places for a careful paragraph to become an overbroad promise. Keep the qualification wherever the claim appears, and record unresolved questions before the brief moves forward.
Walk through an example with missing dates
Suppose a saved note says ‘the tool is available,’ but the note contains neither a source date nor the eligible audience. First, mark the statement for review. Next, open the original source and identify the scope of its availability claim. If the page provides no publication or update date, record that absence rather than treating the day you opened it as its publication date.
Then search within the source for the qualification that matters: invited users, a beta label, a region, an account type or a future date. If the qualification is absent, preserve the unresolved question. The review may end with a narrower sentence or with a hold. It does not have to end with a publishable announcement.
Keep the alert actionable
A freshness flag should explain what to check. ‘Availability scope not established’ gives the next reviewer a task. ‘Old source’ is much less precise. Record the affected claim and the decision that depends on it. If the article merely uses the source as a historical example, a historical date may be enough; if it recommends an action today, the current conditions matter.
A drafting prompt can say: ‘Identify language that asserts present availability. Return the claim identifiers and the source qualification each one requires. Do not update dates or guess access conditions.’ Review the returned list against the article, including its title and captions.
Disclosure: This article and its illustrative cover were generated with AI. The record is a design example, not a tested validation system.
Top comments (1)
A freshness record is strongest when it names what could change, not just when the page was opened—for example, the eligible account type or region behind an availability statement. I’d keep that qualifier beside checked_at so the next reviewer can repeat the same check rather than re-reviewing the page vaguely.