How to Write a Public Correction That Resolves the Error

How do you write a public correction?

Write a public correction by identifying the affected announcement, stating the verified replacement fact and acknowledging the error clearly. Explain any action readers need to take. Then check the versions you control and contact relevant recipients of the wrong information. Keep a record of what changed and what remains unresolved. Sensitive, regulated or disputed matters require qualified review, not a generic template.

The difficult part is often not the sentence. It is knowing whether the corrected sentence has reached the places where the wrong one still matters. This guide proposes a practical workflow for an ordinary company announcement. It is communications education, not legal or crisis-management advice.

Is this a correction, an update or a clarification?

Was the fact originally wrong, subsequently changed, or accurate but unclear? Establish the timeline.

GOV.UK's publishing guidance distinguishes factual inaccuracies from policy changes. Our proposed company-announcement categories are:

These are categories, not universal rules. Do not minimise an omission. Explain an earlier error and later change when necessary.

What should you verify before drafting?

Locate the exact affected passage and its supporting record. Ask the factual owner to resolve the discrepancy against the authoritative event schedule, product record or other appropriate evidence. A newer draft is not automatically a better source.

The PRSA Code of Ethics, which applies to PRSA members, calls for prompt correction of erroneous communications for which practitioners are responsible. It also calls for investigating the accuracy of information released on behalf of those represented. Neither requirement is a licence to rush out an unverified replacement.

Our suggested intake note contains the location, disputed wording, proposed replacement, source, factual owner and current verification status. Record a report as a report until checked. Do not publicly accuse an employee, supplier or reader of causing the error because their name appears in the document history.

Pause affected scheduled versions through the organisation's authorised workflow while the issue is resolved. That is different from stopping every unrelated communication. The PR brief should identify the escalation contacts; this correction record tracks the specific published problem.

What belongs in the public notice?

For a confirmed factual error, our proposed notice has a clear label, an identifiable announcement, the correct fact, a concise account of what was wrong and any necessary reader action. Add the correction date and, where timing matters, the time zone.

The Associated Press's corrections policy requires a correction label rather than a euphemism for a factual error. AP also distinguishes telling subscriber editors from making the correction visible to news consumers. These are AP's newsroom standards, not legal requirements imposed on every business.

Consider this entirely fictional example. An imaginary online design briefing was always scheduled for 14:00 UTC on 18 November 2026. Its announcement incorrectly said 15:00 UTC. The following is sample copy, not a real event notice:

Correction — 10 November 2026: Our announcement of the online design briefing gave the wrong start time. The briefing begins at 14:00 UTC on 18 November, not 15:00 UTC. The event has not been rescheduled. Please use 14:00 UTC when adding it to your calendar. We apologise for the error.

The difference is one hour: 15:00 minus 14:00. Both times use UTC, so this example involves no daylight-saving conversion. In a real notice, confirm every date, time and action against the actual arrangements.

“Details have been refreshed” would leave this reader with an unanswered question: which time should they use? An apology may accompany the answer, but cannot replace it. Nor should the notice add an unsupported explanation such as “a technical glitch” simply because the cause is not yet known.

How do you find the affected copies?

Start from the distribution record, not from memory. List each asset containing the wrong fact: the announcement page, attached document, graphic, caption, social post, email or partner listing. Include scheduled versions as well as already published ones.

For each entry, ask two separate questions: can your team change this asset, and who needs the corrected information? Editing a web page does not rewrite the email already received by somebody else.

Use the variation matrix from the company-news repurposing guide as a starting inventory. Search for the disputed fact across the identified assets, but inspect the context: the same time may legitimately describe a different event.

Check the platform's current capabilities and your publishing permissions before choosing an action. Do not assume a caption edit changes an image, that every post is editable, or that deletion removes screenshots and copies elsewhere. Ask the channel owner to confirm the available correction method.

What does a correction tracking record look like?

The following is an original fictional checkpoint for the same imaginary briefing. It describes administrative states, not measured audience awareness or a completed campaign.

There are four tracked assets, but they are not four verified corrected copies. One published page has been checked; one replacement still needs checking; one audience has been sent a follow-up; one outside publisher has received a request. Adding those actions into a single “100% fixed” claim would erase the distinctions the record exists to preserve.

Give each remaining task an owner and a follow-up point appropriate to the event's timing. Keep the original publication time separate from the correction time. Where there is no confirmation, write “not confirmed” rather than treating silence as completion.

What if another publisher used the wrong information?

Send a focused request through the publisher's appropriate editorial contact. Identify your original announcement, the affected passage in their coverage, the verified replacement and an accessible supporting source. Say clearly when your organisation supplied the error.

Request correction of the factual point, not favourable framing or removal of legitimate criticism. Do not manufacture a media relationship, promise a result, or describe a request as an agreed amendment. Record the response and inspect the published result where possible.

If the factual position is disputed, separate the evidence from the desired wording and involve the appropriate communications lead or qualified adviser. This workflow does not determine defamation, privacy, contractual or regulatory obligations.

What should stay out of the notice and shared record?

Do not republish confidential information, personal data or harmful allegations merely to demonstrate exactly what was wrong. PRSA's ethics code separately requires safeguarding confidences and privacy. Transparency is not permission to expose protected information again.

Have qualified privacy, legal or other responsible specialists decide what can be disclosed, retained, restricted or removed in sensitive cases. Keep authorised supporting records access-controlled under the organisation's retention requirements; do not create an unrestricted screenshot archive or delete evidence on your own initiative.

For an ordinary scheduling error, the public needs the right time and relevant context. It does not need the internal approval thread, individual email addresses or speculation about who is to blame.

When can you close the correction record?

Review the open tasks, not just the notice's wording. Confirm the owned versions that required changes, document external requests and leave unresolved items visibly assigned. Closure of your team's work must not imply that every outside copy has changed or every reader has seen the notice.

Finally, record a specific process question for the next announcement: which field or handoff allowed the discrepancy to survive? Add the resulting check to the team's PR operations workflow once the cause is established. Correcting the record is an immediate responsibility; claiming the problem can never recur would be another unsupported statement.

Sources

• PRSA: Code of Ethics.
• Associated Press: Telling the Story, Corrections/Correctives.
• GOV.UK: Help users prepare for change.