How to check whether an old source still supports a current claim

An old source can still be useful, but only if the claim you are making has not changed faster than the source.

Start by separating the source date from the claim type. A 2019 protocol explanation may still support a definition. A 2019 pricing page probably cannot support today's cost. A 2022 support article may explain a feature path but not the current button name. The question is not “is this source old?” but “what part of my claim could have changed since this source was published?”

Use a four-step check. First, mark the exact claim the source supports. Second, identify whether the claim is factual history, definition, current availability, policy, price, version behavior, or user instruction. Third, look for a newer primary source from the same owner or a stronger public record. Fourth, decide whether to cite the old source, replace it, or keep it with a date warning.

When the old source still supports the claim, make the summary narrow. Write “the 2021 release note introduced the feature” rather than “the feature works this way today.” When it does not support the current claim, keep it only as history and cite a newer source for the present state.

The practical test is whether a reader could reuse the sentence tomorrow without accidentally treating history as current guidance.

How to check whether an old source still supports a current claim

// COMMENTS

ON THIS PAGE