1. Define the decision
We begin with the buyer, use case, and constraints. This prevents a long feature list from standing in for practical guidance.
2. Gather primary evidence
We prioritize official documentation, pricing pages, security materials, terms, and direct product information. Credible independent sources may add context. Each material fact should connect to a reference and an access date.
3. Verify and classify claims
Content records distinguish verified facts, editorial assessments, and unverified research notes. Unverified notes are not presented as established facts. Published product records include a last-verified date.
4. Assess fit and tradeoffs
Our verdict structure identifies who a product may suit, who it may not suit, notable strengths, and meaningful limitations. These are editorial judgments, labeled as such and explained by an evidence basis.
5. Review before publication
We check internal consistency, links, disclosure status, and whether the conclusion is supported. We do not assign fake ratings or imply hands-on use. If direct testing occurs, the page should explicitly describe its scope and method.
6. Maintain and correct
Software changes. Verification dates communicate freshness, and material corrections should be made when reliable new evidence appears.
Affiliate relationships
Commercial relationships are recorded per product and disclosed on relevant pages. Compensation does not determine inclusion, ranking, or conclusions. See our affiliate disclosure.