Track a Public-Relations Correction From Report to Outcome

A correction record should separate the reported problem, the evidence available to review it, a proposed request and what the publisher actually did. That separation matters when several people discuss the same sentence: a draft request is not a published correction, and a reply from one person is not proof that a page changed.
This guide uses a fictional community exhibition notice. No real publication, journalist, organization or correction request is involved. The example is a way to organize a review, not a promise that a publisher will amend its material or that any particular wording is legally required.
Capture the exact issue before drafting a request
Record the publication and page identifier, the words or detail being questioned, the time and source of the observation, and the person reporting it. If the relevant page cannot be accessed, record that limitation. Don't reconstruct an unavailable sentence from a later discussion and present it as a quotation.
In the invented notice, the issue might be a displayed opening time that differs from the organizer's approved schedule. Keep the page wording and the organizer's supplied schedule in separate fields. The discrepancy is a question for review until the relevant source and the applicable date are checked. A difference between two documents does not by itself explain which one is current.
The exhibition media fact sheet prepares attributable information for a planned announcement. This correction record begins after a possible discrepancy has been reported and follows what happens to that report. It shouldn't rewrite a prior fact sheet as though a publisher had already accepted a change.
Identify evidence and its limits
Keep a reference to the specific source used to assess the claim, including its revision or date where available. Note who supplied it and what it can establish. A draft schedule may show an intended time, while a later approved schedule may answer a different question. If the approving person or the version is unknown, leave the issue open.
Give the reviewer a short, checkable comparison: reported page wording, source wording, reference date and unresolved question. If a page contains several statements, separate them into distinct issues. A single label such as “wrong article” makes it difficult to see what has actually been checked or corrected.
Avoid collecting private correspondence simply because it may be related to the event. Decide which information is needed to understand the disputed statement and who is allowed to review it. If the issue involves personal, legal or safety consequences, the record should direct the matter to the appropriate responsible person rather than inventing a resolution.
Keep proposed wording separate from an approved correction
A possible request might say, “Please check the opening time against the organizer's approved schedule attached for review.” In the fictional case this is proposed language only. It doesn't assert that a publisher received the request, accepted the source or updated its page.
Google Docs' suggested-edit guidance describes how suggestions can be accepted or rejected instead of silently replacing the original text. If the team uses that feature, a visible suggestion can make the proposed wording easier to review. It does not send a request to a publisher or prove that the publisher agreed.
Record the person who can approve the request and the person responsible for contacting the publisher. A contact person may gather facts without having authority to make a public statement. When proposed wording changes, keep the new version linked to the issue rather than overwriting the record of what was previously discussed.
Name the issue and retain the reviewed revision
Google Docs' version-history guidance explains named versions and the access needed to review prior changes. When the record is kept there, a named review stage can identify the request that was approved for sending. It cannot prove that a message was sent, delivered or read.
Use a simple sequence of states with evidence for each: reported, under review, request approved, request sent, response received, and publication checked. These are suggested record labels, not a claim about a publisher's internal workflow. A state should move only when the person maintaining the record has the evidence for that particular step.
The customer feedback reply log follows a proposed reply to feedback. A correction request has another recipient and a different outcome: the external publisher controls its own page, and the team may observe no update even after sending a request.
Record the response and observe the outcome separately
If a response is received, record what it actually says. “We will review this” isn't the same as “we changed the notice.” If the publisher rejects the request or offers a different wording, retain that distinction and ask the responsible person whether further action is appropriate. Don't convert silence into either agreement or refusal.
When an authorized reviewer checks the publication again, record the date, accessible page and observed wording. If the page is blocked, moved or unavailable, mark the outcome unverified; don't substitute a cached excerpt as proof of the current page. If a change appears, compare it with the reported issue without assuming why the publisher made it.
Close the record only with the narrow conclusion the evidence supports: for example, “the page now shows the supplied time, checked on the recorded date,” or “a request was sent and no later page check is available.” The fictional notice in this guide has no actual message, response or published correction.