How we pick topics

We cover questions people actually have to decide on: which tool to buy, whether a widely repeated number holds up, what really happened in a breach or outage. A topic makes the list when we can add something a reader can't get from the vendor's own page: a primary source traced, a comparison for a specific kind of team, or first-hand use. We skip news rewrites, and we don't take payment to cover anything (see the About page).

How we check facts

Before an article can be published, the editor has to confirm that every named source, quote and statistic was checked against the original, not against a summary of it and not against what an AI tool said it contained. Each checked source is listed in the article's Sources block, and the numbered markers in the text show which claim each source supports.

Quotes are traced to where the person actually said them. Numbers are traced to the report, filing or dataset they came from, with its date. If we can't find the original, the claim doesn't run.

Evidence labels

Key claims carry a small label saying what they rest on. Measured, Reported and Forecast claims always link to a source; an article cannot be published with one of those labels and no source behind it.

  • MeasuredComes from a measurement, benchmark, dataset or test: ours or a named source's.
  • ReportedWhat a company, official, filing or news outlet says happened. We cite who said it.
  • ForecastA prediction about the future, from an analyst, vendor or researcher. It may not come true.
  • OpinionOur judgment or recommendation, based on the evidence in the article.

Depth and audience labels

Some articles also say how we got to the answer, and who they are written for.

  • Hands-on tested: We used the product or ran the test ourselves; first-hand results are marked Measured.
  • Research-based: Built from documentation, reports and other people's data. We did not test it ourselves.
  • For beginners: Assumes no background; terms are explained as they come up.
  • For teams: Written for people choosing or running tools for a team; assumes working knowledge.

What the dates mean

Published is the day the article first went live. Last verified is the last day an editor re-checked every source, quote and figure in it against the originals. It is set when the article first goes live and again only when that full re-check actually happens, never by an ordinary edit. Updated appears only after a substantive change (new facts, a corrected error, a changed conclusion), not for typo or formatting fixes. Articles that depend on fast-moving data are re-verified on a regular schedule.

Bylines and review

Articles are bylined either to a named person or to the GetCoreTech editorial team. Either way, a person is accountable for what publishes. When a second person reviews an article, their name appears as the reviewer; we only show that credit when the review actually happened. Who is behind the team byline is on the masthead.

How we use AI

AI tools help with research legwork and drafting structure. They are never the source of a fact, quote or statistic, and nothing they produce is published without the checks above. The details are on the AI use disclosure.

Corrections

If we get something wrong, we fix it in the text and add a dated note at the foot of the article saying what changed. Every published correction is also listed in the corrections log. Report an error by emailing corrections@getcoretech.net or through the contact page; we reply within two business days.