Search TechVendorly

METHOD, EVIDENCE AND LIMITATIONS

Know what stands behind a review.

The evidence required before TechVendorly describes an article as a hands-on test, review or comparison.

A reviewable method records the task and conditions, original evidence, results and limitations.

FIVE DIFFERENT KINDS OF MATERIAL

Read the label. Understand the evidence.

RESEARCH

Research-based comparison

A comparison built from current official documentation, pricing and other identified sources. Recommendations reflect the stated use case. Editorial judgements and feature ratings are separate from measured test results.

FRAMEWORK

Planning framework

A structured method or checklist for thinking through a decision. It does not establish a product result.

EXAMPLE

Constructed example

An illustrative scenario created to explain the method. Assumptions and numbers need to be labelled.

DEMONSTRATION

Product demonstration

A walkthrough of product behaviour in a stated context. Vendor-supplied access and limitations must be disclosed.

TEST

Hands-on test

An evaluation supported by the actual setup, method, original evidence and the conditions observed.

OUR REVIEW REQUIREMENTS

A method a reader can examine.

01

Start with the right label

Our current planning guides use original templates and clearly labelled constructed examples. They are not claims that we have tested particular tools or measured business improvements. When we publish a hands-on review, the article must explain the setup and provide original evidence.

02

Document the setup

  • Name the product, plan, test date, and relevant version.
  • Describe the task, sample inputs, environment, and devices used.
  • State who ran the test, how long it ran, and any access supplied by a vendor.
  • Use non-sensitive sample information or properly authorised material.

03

Evaluate the complete job

We look at setup, everyday usability, output quality, integrations, cost, support, and the ability to export or leave. Criteria vary by product type and are stated in the article. A marketing tool should be assessed against a marketing task, not an unrelated benchmark chosen to make it look good.

04

Compare like with like

A comparison uses the same sample task and essential requirements for every product. We identify plan differences and explain where the comparison is incomplete. Scores need a stated method and evidence. We do not add decimal precision that the test cannot support.

05

Check current commercial details

Prices, billing periods, included seats, usage limits, and required add-ons are checked against official information and dated. Taxes and regional differences are identified when relevant. Readers should confirm current terms before buying.

06

Show the limits

A small example does not establish a universal time saving, performance result, or return on investment. We report the conditions we actually observed. We do not call a vendor demonstration an independent test. Access supplied by a vendor is disclosed and does not remove editorial control.

07

Update and correct

We record meaningful changes and correct supported errors. See the editorial policy for our corrections process.

YOUR NEXT STEP

Have a question about a method or claim?

Send the article URL and the detail you would like us to review.