Short answer
Correct a statement already sent by fixing the record openly. Confirm the right fact with its owner, capture exactly what went out, then update the canonical page with a visible note, send direct recipients a short correction with the right fact in the subject line, and sweep every derivative copy such as social posts and attachments.
TL;DR
- →Preserve the original version and identify the exact error before changing public copy.
- →Match the correction route to the audience, channel and materiality of the error.
- →Document decisions and affected recipients so later questions have a reliable timeline.
Fifteen minutes after a statement goes to reporters, a product lead sees that the launch date says Thursday 18 June. It is Friday 19 June. One colleague is already editing the newsroom page, another wants to resend the whole email, and a third says nobody will notice.
Stop all three for five minutes. Confirm the right fact with its owner and capture exactly what went out. Then choose the route by what the error changes for each reader: a page update with a visible note, a direct correction to everyone who received the statement, and a sweep of every copy downstream. Never edit the original as if it never existed.
Professional codes state the duty plainly. The PRSA Code of Ethics asks members to act promptly to correct erroneous communications for which they are responsible1. The IPRA Code of Conduct asks practitioners to take proper care not to spread false or misleading information unintentionally, and to correct any such act promptly2. Neither code tells you which channel to use or how prominent the correction should be; that is the judgment this plan supports.
What should you do first when a sent statement has an error?
Capture what was sent and confirm the correct fact with its owner before anyone edits a page or sends a message.
Capture the exact distributed version, publication time, channels, recipient lists where available, current links and screenshots of public pages. State the proposed correction in one sentence: “The release says Thursday 18 June; the confirmed launch date is Friday 19 June.” Attach or identify the source that establishes the correction. Do not rely on a vague report that “the date looks wrong.”
Assess what the error changes for each audience. A typo in a descriptive adjective may require a quiet page update. An incorrect time, price, eligibility condition, contact or attribution may affect a reader’s decision and call for direct outreach. The communications lead should decide the route with the relevant fact owner and any required specialist. This article offers an editorial process, not legal advice or a universal notification rule.
Which channels need a correction?
Every channel the wrong version reached: the canonical page, the people who received it directly, every derivative copy and the spokespeople who will field questions.
Update the canonical page
Correct the public source when authorized, retaining an internal record of the original and the revision time. Consider whether a visible correction note is appropriate for the audience and materiality. Do not backdate a page or imply that the original text never existed. If the page carries article structured data, update its dateModified value, which Google’s article markup guidance describes as the date and time the article was most recently modified3.
Notify direct recipients
If reporters, partners, employees or customers received the incorrect statement directly, prepare a concise correction that identifies the specific point, supplies the accurate information and links to the current version. Avoid resending an entire release without saying what changed.
Correct derivative channels
Check scheduled social posts, email campaigns, briefing notes, downloadable files, syndicated copies and internal talking points. Assign owners and a completion time. A corrected web page does not update an attachment already circulating.
Answer follow-up consistently
Give spokespeople a short approved explanation of the correction and a contact route for questions. Do not invent a cause for the error while an internal review is incomplete. If reporters ask questions the team cannot yet answer, use the approach for answering journalists while evidence is still missing: confirm what you can and name what is still being checked. The audience needs accurate current information, not a speculative account of how the error occurred.
What should a correction note to reporters say?
A correction note names the statement it corrects, gives the wrong and the right fact side by side, and links to the current version.
For the invented launch-date error, a direct note could read: “Correction to our statement sent at [time]: the service launch is scheduled for Friday 19 June, not Thursday 18 June. The updated statement is available at [link]. We regret the error.” The draft is short because it identifies the document, the correction and the current source. Add only information the team has approved.
If the error came from a figure the client revised late, trace it the way you would a number changed after approval, because the same value may sit in a headline, a chart and a quote. If the error affects a decision someone may already have made, the team may need a different response. For example, an incorrect customer eligibility condition can require outreach that gives affected people a practical next step. Keep the proposed action with the responsible business owner. A communications writer should surface the consequence, not decide a remedy without authority.
How do you stop the same error from happening again?
Trace the error to the one control that would have caught it, such as a source date beside the claim, a final-version comparison or a channel checklist, and fix that control.
Once the correction is complete, record the timeline in a decision log the next editor will read: error identified, source confirmed, decision owner, channels corrected, recipients notified, and open follow-ups. Keep the original evidence and version links. If a reviewer asks later why a correction was visible or why direct recipients were contacted, the team should have an answer grounded in the circumstances.
Then ask a bounded process question. Did the error arise from an outdated source, a late edit, a disconnected approval, a misunderstood comment, or a channel export? Keep the review focused on the relevant control: source dates beside claims, final-version comparison, named release authority, or a channel checklist. The preserved chronology shows what happened without turning the review into a blame exercise or erasing the original statement.
QuoteIt is built to catch the late-edit kind early. Each claim sits beside the passage it came from and each approval is recorded against the version it covered, so a reviewer sees at once when a date changed after they approved the copy.
Should you delete a press release that contains an error?
No. Correct the canonical page, keep an internal record of the original and add a visible correction note where the error could affect a reader. Deleting it leaves recipients relying on a version they can no longer check.
Do you need to tell reporters about a small typo?
Not always. A typo in a descriptive word may need only a page update. A wrong date, price, eligibility rule, contact or attribution can change what a reader does, so tell the people who received it directly.
What goes in the subject line of a correction?
The corrected fact itself, with the wrong one beside it. A reporter scanning an inbox should understand the change without opening the message.
Should the correction explain why the error happened?
Only with an explanation the team has confirmed and approved. While the internal review is open, say what changed and where the current version is, and leave the cause out.
Who decides how visible a correction should be?
The communications lead, with the owner of the fact and any required specialist. The answer depends on what the error changes for each audience.
Sources
Numbers in the text point here. Each link opens the original page.
- 1PRSA Code of EthicsPublic Relations Society of America
- 2IPRA Code of ConductInternational Public Relations Association, adopted November 5, 2010
- 3Article (Article, NewsArticle, BlogPosting) structured dataGoogle Search Central
Written by
Shruti Sharma, Founder and COO, QuoteIt
Shruti Sharma co-founded QuoteIt and runs its operations, to fix the part of PR work that comes after the draft: who signs off, on which version, and what the client actually approved. QuoteIt ties each approval to the exact wording it covers, keeps the client's sign-off separate from final release, and records who decided what and when, so a statement can be handed over, corrected or reused without reopening the mail trail.
How these posts are researchedDraft your next statement in QuoteIt. Each claim sits beside the passage it came from and each approval is recorded against the version it covered, so a late change to a date is visible before the statement goes out.
Join the Pilot
