Dates can make an article look current, but a recent timestamp alone does not establish that its important claims were checked again. Checking review dates and revisions means tracing a claim to the material that supports it, then comparing the relevant dates and changes. This helps readers distinguish a substantive review from a minor edit and identify where the evidence may no longer support the wording.
What the evidence can show
A page may display a publication date, an updated date, a review date, or several of these. They can describe different events. Publication usually marks when a page first appeared; an update may mark a later edit; and a review date may indicate that someone assessed the content. None of these labels, by itself, reveals what was checked, who checked it, or whether the underlying sources changed.
Look for evidence at the level of individual claims. A statement about a process, feature, fee, eligibility condition, or time period may rely on a separate source for each detail. The source should address the same subject, apply to the relevant period, and support the exact wording. A source that is newer than the article can still be irrelevant; an older source might remain applicable, but its continuing relevance needs to be explained rather than assumed.
Hypothetical example: An article says a feature is available “now” and shows an updated date from this month. Its cited guide, however, carries a revision date from two years earlier and describes the feature as planned. The page date does not resolve that conflict. The claim needs current, directly relevant support, or more cautious wording.
| Evidence item | What to compare | What it may indicate |
|---|---|---|
| Article date | Publication, update, and review labels | Which editorial event the date appears to mark |
| Source date | Issue date, revision date, and applicable period | Whether the evidence may cover the claim’s timeframe |
| Claim wording | Specific details against the source text | Whether the source supports the whole statement |
| Change record | Earlier and current versions, if available | Whether the edit altered evidence or only presentation |
A timestamp can also reflect a spelling correction, layout change, or other copy edit. Such a change may be perfectly ordinary, but it should not be treated as proof that every factual statement received a fresh review. Conversely, a page with no visible update date is not automatically inaccurate. The available evidence may simply be limited, so record that limitation separately from any conclusion about accuracy.
How to check the details
Start by recording the page’s visible dates and the precise claim under review. Preserve the wording rather than reducing it to a broad subject label: “available to some users” and “available to all users” are materially different claims. Note any qualifiers, such as a location, account type, product version, or stated period, because a source that omits them may not support the claim as written.
Next, identify the cited source and inspect the source itself where possible. Record its title or other identifying details, its date, and the relevant passage. Check whether the page points to a specific document version or merely to a general page that can change without leaving a clear history. If you cannot access an earlier version or confirm a source date, state that plainly; do not infer a revision from the appearance of a page.
Use these checks to compare the evidence:
- Does the source directly support the claim, including its qualifiers, numbers, and time references?
- Is the source dated, and does its date apply to the version or period described in the article?
- Is there evidence the source itself was revised after the event or change the claim discusses?
- Does the article’s update history identify substantive factual changes, or only formatting and copy edits?
Hypothetical example: A comparison page has a recent review date, while one claim about a fee cites a document marked “revised” several years earlier. Check the document’s fee section, version history, and stated effective period. If those details do not establish the current fee, classify the claim as not confirmed by the material available. Do not fill the gap with a guess or treat the newer review label as supporting evidence.
When a claim depends on more than one source, check each link in the reasoning. A source may establish that a policy existed, while a different source is needed to show when it took effect or whether it remains in force. Note contradictions rather than choosing the newest-looking date automatically. Date order helps organise the inquiry, but relevance and direct support matter too.
Recording a useful conclusion
A useful record lets another reader see what was checked and repeat the comparison. For each claim, capture its exact wording, the page date labels, the supporting source and its date, the passage relied on, and any version information. Then note the result in measured terms: supported by the cited source for the stated period, partly supported, not supported by the material located, or uncertain because a date or version could not be verified.
Separate observations from interpretation. For example, “the article displays an update date of 12 May; the cited document displays a revision date of 3 February two years earlier” is an observation. “The article was not reviewed” is a stronger conclusion that those dates alone may not establish. Where change history is unavailable, say so instead of describing an edit as absent or unchanged.
Finally, distinguish factual corrections from editorial maintenance. If an edit log or comparison shows only punctuation changes, record that as a copy edit, not a new evidentiary review. If a changed claim has newly dated support, record both the change and the source version. A careful conclusion can therefore be modest: the dates reveal what is visible, the source comparison shows what is supported, and any remaining uncertainty stays explicit.