How we verify claims before publishing, and what we do when we get something wrong.
What gets checked
Every factual claim in every article: prices, dates, version numbers, feature descriptions, benchmark figures, company statements, and anything quoted. Opinion and judgement are clearly separated from fact, and only the factual part is checked.
The questions we ask of every claim
- Where did this come from?
- When was it true? Software pricing and features change weekly.
- Is this the primary source, or someone else’s report of it?
- Can we verify it independently, without relying on the vendor?
- Does our wording match the evidence, or have we overstated it?
Primary sources first
We link to original documentation, pricing pages, filings, papers and specifications rather than to other publications’ coverage of them. Where we cite another publication, we say so and link to it.
Superlatives require evidence
Claims like fastest, most accurate, cheapest, or best are not published unless we ran a defined test that supports them, and the test is described in the article. Where we have an impression but not a measurement, we say that plainly instead.
Vendor claims
A feature listed on a vendor’s website is a claim, not a fact. We describe features we have verified ourselves. Where we report an unverified vendor claim because it is newsworthy, we attribute it clearly and say we have not tested it.
Benchmark figures
Published benchmark scores are reported with the name of the benchmark, who ran it, and when. We do not present a vendor’s own benchmark as independent, and we note when a benchmark is self-reported.
Anonymous sources
We prefer named sources. Where we use an anonymous one, we say why anonymity was granted and what we did to corroborate. We do not publish single-source anonymous claims about a company’s conduct without corroboration.
Dates on everything
Reviews carry a last-tested date. Articles carry a published date and, where changed, a modified date. If you are reading something old, the page will tell you.
When we get it wrong
We fix it, and we log it publicly. See our corrections policy. If you have spotted an error, write to contact@uncommonbits.com.
Last updated 6 September 2026.