Evidence

Source hierarchy

We prefer sources that can support the exact claim being made. Product pages and social posts are useful starting points, but they are not interchangeable with customer evidence.

  1. Primary records: manufacturer documentation, manuals, regulatory filings, patents, pricing pages, and dated company statements.
  2. Customer evidence: statements from a named operator, case studies with specific sites or tasks, procurement records, and direct customer confirmation.
  3. Independent reporting: reputable publications and specialist outlets with named sources or original reporting.
  4. Discovery sources: event demonstrations, videos, social posts, and aggregators. These can identify a lead, but material claims need stronger support or an explicit qualification.

Citation rules

Links sit near the claim they support. We use the earliest reliable primary source where possible, record the date behind time-sensitive claims, and do not cite a search result as evidence. If sources disagree, the article says so.

Status labels

What deployment language means

Announced
The company has publicly described the robot, product, program, or target. An announcement is not proof that a working unit exists.
Prototype
A working unit has been shown or documented, but there is no confirmed customer operation. Controlled demos stay in this category.
Pilot
A customer or partner is testing the robot in a limited environment, time period, or task set. A pilot is not treated as a commercial rollout.
Customer-confirmed
A named customer has confirmed the relationship or use. This label does not by itself establish payment, fleet size, or production use.
Paid deployment
A source confirms that a customer is paying for units or robot services in operation. We do not infer payment from a partnership announcement.
Scaled deployment
Multiple units are operating beyond a small trial in a repeatable customer workflow. We state the reported fleet size and location when sources provide them.
Preorder
The seller is accepting reservations or orders for future delivery. A preorder is not counted as a shipped unit or active deployment.
Shipping
Customers are receiving units. We distinguish limited early deliveries from broad commercial availability whenever the evidence allows it.

Review labels

Source-based review or hands-on review

Source-based review

The assessment comes from cited specifications, pricing, demonstrations, customer evidence, and comparable products. It does not imply that a RoboZaps contributor used the robot.

Hands-on review

A named contributor physically used or observed the product in a way that supports the stated findings. We describe the setting, duration, unit, and limits of that access.

RoboZaps does not turn these evidence labels into a composite editorial rating. Articles explain the tradeoffs and the evidence behind them.

Verification

Fact-checking and freshness

Before publication, material specifications, prices, availability, deployment claims, and quoted statements are checked against their cited sources. Reviews receive a separate editorial pass. When an article is materially updated, we recheck the affected claims and update its visible date.

Credits

Authors and reviewers

The author owns the reporting, analysis, and final claims. A reviewer checks sourcing, status labels, clarity, and internal consistency. Review credit does not convert the reviewer into the article’s author, and a person credited in both roles appears only in the authorship lane for that article.

Accountability

Corrections and commercial disclosure

Factual errors are corrected in the article. Material changes are noted with what changed and when. Commercial relationships, affiliate links, sponsored access, loaned products, or other support that could affect a reader’s judgment are disclosed on the relevant page. Payment does not buy a conclusion or remove a documented limitation.

To flag an error, use the RoboZaps contact form and include the article URL and the source that supports the correction.