Press release, changelog, or support doc: which source should a summary cite?

A summary should cite the source that best supports the exact job of the sentence: announcement, change history, or current user guidance.

A press release is useful when the claim is about launch intent, positioning, partnerships, dates, executive wording, or the first public announcement. It is often less useful for current feature behavior because launch copy may simplify limitations. A changelog is useful when the claim is about what changed, when it changed, and which version or release carried the change. A support document is useful when the claim is about what a user can do now.

The mistake is treating these sources as interchangeable. If a summary says “the company launched X in March,” cite the press release or launch note. If it says “version 2.4 added X,” cite the changelog. If it says “users can enable X from settings,” cite the support page and check whether the page has a last-updated date.

When sources disagree, keep both roles visible. A press release may announce a feature that later support docs restrict by country, plan, or device. The summary should not hide that difference. It can say the feature was announced on one date and current usage is limited in the support documentation.

The practical rule: cite the source closest to the claim, not the source that sounds most official in isolation.

Press release, changelog, or support doc: which source should a summary cite?

// COMMENTS

ON THIS PAGE