A correction note tells readers what changed on a page and helps the editorial team connect that change to a documented review. Put the accurate wording in the affected passage first. Then write a dated note that identifies the meaningful error and explains the current wording in plain language.
Start with the exact published version. An editor who changes a sentence without recording which version was affected can leave a reviewer unable to tell what readers saw. Save a reference to the old wording under your publication’s records policy, identify the source used for the correction, and give the revision to someone who can check it independently.
Locate the affected wording and copies
Record the page address, heading, and paragraph or figure that needs attention. If a reader reported the issue, preserve the useful details of the report in the editorial record. Avoid copying personal information into an ordinary task ticket when the team does not need it to resolve the wording.
Look for the same passage in places the publisher controls. A short summary on a landing page may repeat a sentence from a longer guide. A downloadable file or a translated page may have been produced from an earlier edition. Record each surface separately, because a corrected article does not automatically establish that every copy has been updated.
For each affected surface, write down:
- The address or file identifier and the version currently available.
- The old wording or a reference to the retained version.
- The proposed replacement and the source passage supporting it.
- The person responsible for the change and the reviewer who will check it.
- The status of the update and any copy that still needs a decision.
A spelling edit and a change that affects a reader’s interpretation call for different editorial treatment. Decide whether a visible correction note helps explain the change. Record that decision even when the team concludes that a routine edit needs no separate note.
Make the note specific and readable
A useful note names the affected part of the page, describes the error, states the correction, and gives the date. Write it so that someone arriving after the update can understand the current information without finding an old copy. When a note refers to a source, identify the source and version in the page’s normal reference format.
Avoid a vague sentence such as “This page has been updated” when the reader needs to understand a substantive correction. Likewise, do not make the correction broader than the evidence the reviewer checked. If the new source leaves a question unresolved, say what is known within the published scope and return the unresolved question to the review process.
Place the note where a reader can associate it with the affected material. Depending on the page, this may be close to the corrected paragraph or in a clearly labeled correction section. Make the note distinguishable from the page’s general review date. A review can occur without a correction.
Work through a fictional correction
Imagine that a page about a publisher’s editorial process says a source list was reviewed in March. The editorial log shows that the review took place in May. The paragraph itself has no other identified error, but the date matters to readers trying to understand when the review happened.
The editor records the page address and saves a reference to the published March wording. The reviewer checks the dated editorial log, confirms the May review, and verifies that the log belongs to this page rather than a related guide. The editor changes the sentence and prepares a note:
Correction: The review date in the source list was changed from March to May after the editorial team checked the review record.
In this fictional example, the published note also includes the actual correction date. The team checks the downloadable version and finds the same incorrect month. It assigns an editor to replace that file, updates the file’s revision record, and checks its public link. A second reviewer opens the page and the download, confirms the May wording in both, and records the completed checks.
The outcome is a correction readers can understand and an internal trail showing which record justified it. If the download cannot be updated immediately, the editor records the outstanding work and decides how to make the difference clear to readers until the replacement is available.
Verify the published change
After approval, open the actual public page and follow the route a reader would use. Confirm the corrected wording, the correction note, the note’s date, and any reference. Check that the note belongs to the correct section and that the page remains understandable when read from the beginning.
Then check each affected copy against its assigned task. A reviewer can record the observed page or file version, the date checked, and any unresolved issue. If the live copy differs from the approved revision, return it to the person responsible for publication and repeat the check after the change is applied.
Keep internal evidence where the editorial team can retrieve it. The public note can explain the change without reproducing private correspondence or the full internal review discussion.
Frequently asked questions
Should every edit have a public correction note? Decide according to the nature of the change and the publication’s editorial policy. A meaningful change that alters interpretation benefits from a clear explanation. Record routine edits in the internal history when that is your established practice.
What if the original source has changed? Record which version supported the earlier wording and compare it with the version now available. Ask the reviewer to identify whether the difference changes the article before writing the note.
Should the old wording stay on the public page? Include enough detail for readers to understand the correction. Decide whether to quote the earlier wording based on its usefulness and the publication’s records and privacy procedures.
What if a related download cannot be corrected today? Give the pending file an owner and an expected follow-up. Make its status clear through the publishing process, then verify the replacement and its public link when ready.