Press release corrections: requests and verification

Press release corrections need a specific description of the error, the accurate replacement, supporting evidence and the URLs affected. Send that request through the publisher’s correction process, then inspect the resulting public pages. A change to the company’s original release does not establish that every distributed copy has been corrected.

An incorrect availability date can change what a reader believes they can buy. A wrong number can alter the meaning of a funding announcement. Work from the claim and its consequences, then decide which pages and assets need an update.

Separate an error from a new development

Start by asking whether the original statement was inaccurate when published or whether the underlying situation changed later. An incorrect product launch date requires a correction. A genuine launch delay announced after an accurate release is a subsequent development.

A clarification can explain wording that was technically accurate but reasonably open to a stronger interpretation. For example, an announcement may need to explain that access is limited to an invitation-only preview. Describe the limitation precisely and supply the evidence for it.

This classification helps the publisher assess the request. It should not be used to conceal a material error behind a more favorable label. Reuters’ standards describe transparent, prompt corrections across stories, captions, graphics and scripts.

Write a change request the editor can verify

Identify the exact sentence or field that is wrong and the replacement you propose. Add the primary document that establishes the accurate fact, plus a contact able to answer factual questions. Avoid sending only a rewritten full release that leaves the editor to discover what changed.

A sample correction record can use these fields:

Keep personal contact details in the private request, not in a public correction note. If the error appears in several languages, compare the meaning of each version rather than assuming that changing one source file updates all translations.

For the underlying evidence file, use the press release source pack. A version history is more useful when it links the original claim, the corrected fact and the document supporting the change.

Request a visible explanation for material corrections

A factual correction may warrant an explanation that tells readers what was wrong and what has changed. The Society of Professional Journalists’ Code of Ethics recommends acknowledging mistakes and explaining corrections clearly. It is professional guidance, not a universal contract governing every publisher.

The publisher determines its correction policy and wording. Ask how a material change will appear on the page and whether the original publication date remains visible. Do not assume that a silent replacement or removal is the appropriate treatment for every error.

If a headline, cover or caption repeats the mistake, include it in the request. Readers can encounter those assets separately from the article body, including through a saved preview or an existing social post.

Keep publication and update dates understandable

A correction is not a new first publication merely because the page changed. Keep the historical publication record and identify a substantive update appropriately in the reader-facing page.

Google’s byline-date guidance recommends consistency between visible dates and structured date values. It also distinguishes the page’s publication or update date from the date of the event described. These recommendations help Google interpret the page; they do not guarantee which date a search result will show.

For a launch that has been delayed, the event date in the text may change while the original publication date remains the same. Record the subsequent development where readers can understand the sequence.

Verify each affected public placement

List the company’s release, distributed copies, downloadable files and any separately written coverage that repeats the claim. Then record the observed state for each URL. A corrected company page is evidence about that page only.

Check the body, headline, caption and linked attachment where each carried the error. If an independent story is affected, send the factual evidence to its publisher through the appropriate process; the company does not control that newsroom’s editorial decisions.

Use the distribution report checklist to keep corrected pages, pending requests and inaccessible copies distinct. Preserve the original evidence and the time of the correction request so the remaining work is concrete.