Robotics Announcements: How to Attribute Quotes and Avoid Invented Endorsements

A robotics announcement may contain a product description, a customer statement and a quotation from a company executive. Those items do not all carry the same evidential weight. A reporter can make a daily briefing more useful by identifying who made each claim, what the source actually establishes and which questions remain unanswered.

Locate the original statement

Start with the document, interview, presentation or recording in which the statement appears. Record the speaker, organisation, date, publication or event, and a link to the source where readers can access it. If the wording comes from a translated or edited version, identify that version and check the original where possible. A quotation without a traceable source should be treated as a claim requiring further verification.

A company press release can establish that the company made a particular announcement. It does not, on its own, establish an independent test result, regulatory approval or the purchasing decision of an unrelated organisation. Attribute the claim to its maker and do not remove a condition that limits what the statement says.

Distinguish a description from an endorsement

A hypothetical supplier release might say that a robot was demonstrated at a customer facility and include a customer representative’s quotation about the demonstration. Those facts, if supported by the release, do not by themselves prove a long-term contract, a purchase of a particular quantity or approval of every advertised feature. This scenario is illustrative and does not refer to an actual supplier or customer.

When a release says “partner,” check whether it describes a reseller, a demonstration host, a research collaborator or another relationship. If the source does not explain the arrangement, preserve the original wording and note the absence of detail. Do not turn the label into a broader commercial claim for a more dramatic headline.

Preserve the relationship between source and claim

The W3C PROV Primer introduces concepts for describing the origin of information, activities and participants. A newsroom can use that idea to record where a quote was published, who checked it, and how it was incorporated into a story. This is a general provenance resource, not a rule that verifies the truth of any robotics announcement.

Keep a source register with the title, publisher, link, publication date and relevant passage. When a quotation appears in a document supplied privately, check whether the sender has permission for publication and whether the source can be identified to readers. Do not disclose personal contact information merely to show that a source exists.

Check the terms used to describe a product

A robot’s application, mobility, manipulation capability and intended users may be described differently across sources. The International Federation of Robotics’ service robot page discusses service robots and their uses. Its terminology can provide useful context, but it does not independently classify every product mentioned in a press release.

Before using a category in a headline, compare the source’s description with the definition actually cited. If a demonstration shows one capability but the vendor discusses a planned feature, keep those descriptions separate. Avoid inserting a technical performance claim unless a suitable source supports it under stated conditions.

Explain the limits of a quotation

Quotes can convey what a person said, but a short extract may omit assumptions, test conditions or an important qualification. Read enough of the surrounding material to understand the intended scope. If the statement concerns a future plan, retain the future tense; if it reports a test on a specific setup, identify that setup when the source provides it.

Where independent confirmation is unavailable, say so rather than suggesting that a claim has been verified. An editor may ask for supporting documentation, but an unanswered question should remain unanswered. The objective is to give readers a clear account of the evidence, not to fill every gap with an inference.

Publish a source note readers can follow

Before publication, check that each linked page supports the nearby sentence and that the speaker’s name, organisation and date match the original. If the source changes or is withdrawn, record what was checked and revisit the article when new evidence is available. A source register should also identify any access restriction, so that a reader is not promised a freely available document when the publisher requires registration. The site’s article on updated source pages covers why a page update is not automatically a new event.

The industry information section provides further context. This checklist is an editorial method; it does not assert a specific partnership, certification or product outcome. Current news still requires its own current, first-hand evidence.