How to verify a technology launch before publishing

In technology coverage, the word “launch” can refer to different moments: a public unveiling, the opening of pre-orders, the start of actual sales or arrival in a particular market. Unless the specific milestone is stated, an apparently clear date can be misleading. The useful question is not simply “When does it come out?” but which milestone has a date, for which version and in what territory.

It helps to treat announcement, availability and distribution as separate states. A company can announce a product without offering it yet, take orders before deliveries begin, or sell it in some regions before others. An article should describe only the status supported by the source consulted; if the page says pre-orders are open, do not turn that into a claim that the product is on sale or being delivered.

For a product-specific fact, the strongest source is usually documentation published by the manufacturer or seller: a press release, product page, technical specification, official store or support page. These sources do not all serve the same purpose. An announcement may confirm that the company unveiled a product; a purchase page may show that a particular variant is available in a market; support documentation may clarify compatibility or requirements.

Independent media outlets and calendars are useful for finding news and tracking changes, but a list of upcoming launches is no substitute for confirmation from the company. For example, Eurogamer maintains a guide to 2026 video game release dates, while DeVuego offers a calendar of Spanish video game releases. These are tracking tools within their respective areas, not primary evidence of the availability of any device or of all its dates. Use them to find out what to check, not to treat something as confirmed when it has not yet been documented.

For every claim, record the link and what it proves. If a secondary source attributes a date to an announcement, look for the original announcement; if it cannot be found, attribute the information clearly and avoid stating it as a confirmed fact. There is no universal rule guaranteeing that an official page is always up to date: it is important to check the publication or revision date and the specific page containing the information.

A date is useful only when its scope is clear. Check whether it refers to the announcement, the start of pre-orders, sales or shipping, and whether the manufacturer specifies a country or region. Do not extrapolate a date from another market to Spain or turn a general forecast into a local date. When the official site does not specify a territory, explain that limitation rather than filling in the detail from context.

Price also depends on the variant and market. Check that the figure corresponds to the model in question, which currency it uses and whether it comes from the brand, an authorized seller or a third party. If you report a retail price, identify the seller and when you checked it; promotions, taxes and shipping costs can change the final amount. Without a verifiable source for the price and its market, it is better not to publish it as a definitive figure.

Before writing, use this checklist to confirm the product’s exact name, variant, market, availability milestone, associated date and source of the price. If any element is missing, limit the wording to what is actually established. “The brand announced the product” is not the same as “it is already on sale in Spain.”

Technical specifications, manuals and support pages can help verify features and conditions of use that a promotional announcement may not detail. Check that the documentation applies to the same product name and variant as the item being covered: a figure that is correct for one configuration should not be presented as valid for the whole product family. It is also worth distinguishing specifications announced by the brand from performance that has not yet been independently demonstrated.

Compatibility calls for a specific check. A list of requirements or compatible devices published by the manufacturer can define the scope of a claim, but may not address every case. If the documentation does not mention an operating system, accessory or region, that does not automatically prove incompatibility; it means the source consulted does not confirm it. Describe the omission as a limit of the available evidence.

Google Merchant Center, meanwhile, publishes a product data specification for people preparing information for its services. This can be a reference for understanding the structure of certain commercial data, but it is not independent certification that a product exists, is available or meets the specifications attributed to it. Evidence about the product should still come from sources suited to each individual fact.

A comparison with the previous generation is reliable only if both models are identified and the same type of information is checked against valid documentation for each. For example, compare features the brand lists on an equivalent basis, without inferring improvements from component names or ambiguous promotional material. If the methodology, configuration or market differs, say so; a table cannot make unlike data comparable.

Avoid presenting a feature as a confirmed difference if it appears only in rumors, leaks or third-party reports. You can explain that information is attributed to an independent source, but keep that claim separate from the confirmed data. A page update or product listing does not, by itself, prove that the physical product has changed: it could reflect a variant, a region or a textual correction.

If the brand has not published a comparable specification for the previous generation, state that there is not enough basis for a precise comparison. Missing data is not an invitation to estimate. In a service article, it is more useful to acknowledge what cannot be compared than to fill the space with a speculative conclusion.

Upcoming-release lists can group different kinds of products and draw on information with varying degrees of certainty. Some tracking sites focus on video games, while others publish retailer or media calendars. Their value lies in making information easier to find and providing context; on their own, they do not establish that a launch is official or that a date is still current.

When sources disagree, return to the company’s source and check whether it refers to the same model, region and milestone. If there is no primary confirmation, attribute the information precisely to its publisher and use appropriately qualified terms such as “expected” or “according to the calendar consulted.” Do not let those phrases stand in for verification: make clear which detail remains unconfirmed.

Before publishing, keep a simple verification note: claim, link, date checked and scope. Recheck time-sensitive information if the article is updated or recirculated. Dates and commercial terms can change; this methodological guide cannot predict those changes or confirm any specific product. Its practical conclusion is narrower: publish each detail with the level of certainty and market that the source actually supports.