Reviewing Competitive Claims Without Exceeding the Evidence
Review a competitive comparison by matching its exact wording to current evidence, relevant scope and authorized use.

Write the exact claim before researching it
Start with the sentence intended for a page, presentation or sales conversation. Identify the product, capability, customer context and comparison being made. Broad language such as always, never or best requires a different level of support from a narrow statement about a documented feature.
Record where the claim will appear and who will review it. Keep a private research observation separate from wording approved for external use. The purpose of the review is to establish what can be supported, not to find a source that appears to justify a preferred conclusion.
Match the evidence to the scope
Use current product documentation or other appropriate primary material, keeping the URL, date checked and relevant quotation. Note product editions, deployment conditions and other limits. An absence from one page does not prove that a competitor cannot provide a capability.
Separate direct evidence, customer reports and interpretation. If sources conflict, preserve the conflict and ask the responsible expert to assess it. Do not hide a material caveat in an internal note while publishing a broader headline.
Example: reviewing an integration comparison
Illustrative draft: a comparison says another product cannot synchronize a particular record type. The reviewer finds documentation that supports synchronization under certain conditions. The original sentence is withdrawn; the revised comparison describes the documented conditions and leaves unsupported details open.
The product expert checks the technical interpretation, and the designated reviewer approves the final wording for its destination. The coordinator records the source and replaces distributed copies. A narrower accurate statement is more useful than a dramatic claim that cannot survive a buyer’s question.
Give approved wording a maintenance owner
Store the approved sentence with its sources, scope, review date and destinations. Recheck it when product documentation changes or a seller reports contrary evidence. Pause reuse of a disputed claim while the responsible owner resolves it.
Keep the previous wording and the reason for the correction in the internal history. Confirm that the actual page or deck has been updated. Closing a review ticket is not enough if the unsupported comparison remains in the material buyers receive.
Sources
- FTC Comparative Advertising Policy, www.ftc.gov. Public guidance reviewed on 2026-10-12; applied only within its stated scope.
Related GTM guides
Frequently asked questions
Does missing documentation prove a feature is unavailable?
No. State what was found in the reviewed material and mark unanswered questions for confirmation. A missing mention does not establish that a capability cannot be provided.
What should accompany an approved comparison?
Keep the exact wording, supporting source, date checked, product scope, material limitations, authorized destination and review owner together.
What happens when new evidence contradicts a published claim?
Pause reuse, route the evidence to the responsible reviewer, and correct the actual published assets. Retain the earlier wording and the reason for the change in the internal history.