When a company publishes an error, changing one sentence may not be enough
How to correct an important published error and reach people who used the earlier information.
Article language: English

In this article
A company publishes the wrong date for an event. Changing the page is quick. The harder part follows: someone has saved the date, someone has sent the PDF to a team, and another person is waiting for confirmation based on the wrong information. The page may now be correct while readers still act on the old version.
Match the correction to the significance of the error. A typo that does not affect understanding is different from a wrong date, service scope or product specification. Confirm the right information, identify where the error was used and decide what will help the reader act. Not every change needs a public statement, but not every error can be quietly replaced either.
Establish the fact before correcting copies
Consider a fictional company organising a customer workshop. Its description and attachment say Saturday instead of Friday. The team knows the confirmed date but not yet who used the wrong version. First check the underlying agreement and identify the materials affected.
Do not choose between conflicting messages without establishing which is correct. Identify a person who knows and a record that supports the answer. If the situation remains uncertain and silence would mislead readers, say that a check is under way. Do not invent a certain date to close the issue quickly.
Associated Press editorial principles call for clear corrections of factual errors and notification to recipients and readers. This is a news agency's standard, not a procedure binding every company. It illustrates the difference between changing a text and reaching someone who relied on it.
Ask whether a person could have planned attendance using the wrong date. If so, explain the difference and provide a suitable contact route. “Updated” alone does not say whether the date, programme or a punctuation mark in the speaker's biography changed.
Importance depends on the reader's action
GOV.UK guidance on change notes distinguishes minor edits from changes to what users need to know or do and recommends saying specifically what changed. This is a public service's practice and a useful question for a business site, not a universal company rule.
Choose a response proportional to the effect. A neutral typo may need an edit and an internal record. A wrong event date may require a visible note by the right date and contact with registered people. Consider where the error appeared and who might have relied on it. Changing “two days” to “two weeks” can matter more than rewriting an entire paragraph without changing a condition. Character count is not a measure of significance.
This article does not decide legal duties or liability for a publication. It addresses the operational flow of information. Seek an appropriate legal assessment where needed. Record the period during which the wrong date was available using versions and events actually known; do not invent an exact minute.
Distinguish correcting a mistake from a new organisational decision. In this example the workshop was always meant to be on Friday. If the organiser had moved it from Saturday to Friday, the communication should describe an actual change. Readers need to understand whether the old statement was wrong or a previous arrangement has changed.
Map copies that people actually use
Check the event page, form, attachment, confirmation and material used by the team, including other languages where the information appears. The Polish guide to versioning a multilingual offer (in Polish) concerns consistency; after an error, that map also helps define the urgent correction.
Do not assume changing one field updates every copy. A PDF may be separate, a partner may have downloaded an image, and an automated message may contain an excerpt. Note which places the company can change itself and which require contact with another party. Do not mark everything fixed when some copies remain outside your control.

Keep an old version internally where needed to reconstruct the event, even if it should no longer be offered publicly. The people answering questions need to know what the reader might have seen. A Polish article on reporting errors in a team (in Polish) explains a route for a colleague to identify the location, text and reason for doubt without first producing a full list of copies.
For a third-party copy, request a specific check or replacement and provide the material, wrong passage and confirmed wording. Sending a request is not confirmation that the copy was corrected. Track contact and completion separately. Make the new downloadable version recognisable to someone who already has an old file; the exact naming convention depends on the service.
Say what changed and who is affected
For the fictional workshop a note could say: “We corrected the workshop date: it will be on Friday, not Saturday as stated in the earlier description and PDF. Registered participants will receive a separate confirmation.” This is illustrative. Promise a message only if the company will actually organise it.
If the reach of the error is still unknown, say so. You can confirm a page correction while the attachment is being checked. For a longer uncertainty, the Polish guide to communicating a delay (in Polish) discusses when the next update will be available. Tell readers where to find it instead of asking them to compare copies themselves.
Contact people the company can identify in connection with the issue, in accordance with the rules for using their data and the channel. A registered participant has different needs from a casual reader; a universal message to every contact is not automatically necessary.
If a client has already changed their plans, correcting the text may begin a broader response. The Polish article on repairing a service relationship (in Polish) considers the person's situation and possible next action. “The page is correct now” does not tell them what to do with preparations based on the earlier date.
Test the message with someone who knew the old version. Can they identify the right date and next action? Must they confirm attendance again? Identify the new file clearly. A generic “details on the website” may not help a person looking at several similar documents.
The question changes with the error. If a product description claimed an unconfirmed feature, correcting a parameter alone may not establish whether the product fits a customer's use. Refer that question to someone competent to assess it. Correcting the publication and confirming suitability are different tasks.
Preserve meaning after the edit
Read the content where it is actually used. Does the heading agree with the form? Does the button lead to the current file? Does the other language show the correct day? The Polish guide to a CMS publishing process (in Polish) distinguishes saving an edit from reading what the audience sees.
An inaccurate promise also calls for evidence of the actual scope, not merely new words. Where a service was demonstrated, distinguish an example from a working capability. After an edit, read the version visible to the audience. If it still shows the old content, investigate rather than treating a saved change as completion. Check the important passage and user path without requiring a search of the entire internet before contacting people already identified.
In other languages, confirm the meaning of the changed condition. Replacing a number mechanically may leave a wrong weekday or another related phrase. The reviewer needs to know what the error concerned in order to check the whole sentence.
Leave a record so someone else can continue
Record the confirmed fact, corrected locations, outstanding copies and person responsible for further contact. A brief record should let another person answer a client without reconstructing the history from memory. Distinguish a corrected page, a checked new file and a request sent to a partner. The last may still lack confirmation that the third-party copy changed.
If the error came from an incorrect input, correct the source used by future work too. Not every incident requires rebuilding the whole content system, but the specific source of the wrong date or condition needs checking. For repeated errors gather evidence before treating the first explanation as the cause. If an offer is being retired, removing a page may not resolve existing customers' need for contact or information about an ongoing case. The correction should restore a useful basis for action even after the original sentence disappears.







