Confirm what changed and who can authorize it.

A correction can begin with a resident question, an organizer update or a department discovering an error. Record the reported issue without treating an unverified message as the new truth. Ask the responsible source to confirm the correct fact, its effective time and any remaining uncertainty.

Identify who is authorized to approve the change and whether the agency’s urgent communication procedure applies. If information is still uncertain, agree on the appropriate public treatment with that owner rather than inventing a precise answer.

Find every version that may still be used.

Search the content record for the underlying item, not only its current page title. Include the service page, document, calendar entry, social caption, image text, newsletter draft, scheduled post and any translated version. Note which items are drafts, scheduled, live or superseded.

The calendar workbook links channel revisions through a shared item identifier. The content audit can help identify additional pages or attachments that use the same fact.

For an event that changes repeatedly, maintain a stable authoritative event destination when the subject is the same. Do not create another near-duplicate event page for each correction.

Use a correction record with a responsible next action.

StepRecordVerification
ConfirmOld statement, corrected fact, source and effective time.The responsible reviewer confirms the source.
ContainAffected scheduled or draft versions and the action required.An authorized publisher checks what was paused or replaced.
ReviseCorrected copy, links, images and language versions.The approver identifies the exact revision and channels.
PublishAction taken for each affected destination.The live page or post is inspected, not only the editor preview.
CloseCompleted locations, unresolved exceptions and follow-up owner.Remaining obsolete versions have an explicit treatment.

On a small screen, scroll the table sideways to see every column.

This is a recommended working record, not a legal retention rule. Follow the agency’s approved records, communication and incident procedures when deciding what to retain, replace or withdraw.

A scheduler reviews a laptop beside a paper content calendar and a small stack of revised notices, crossing out an obsolete item with a pencil.
Checking scheduled content after a change.

Decide how people will recognize the correction.

A minor typo and a changed service deadline do not necessarily need the same public response. With the authorized owner, decide whether the original should be edited, supplemented by a visible correction, replaced, or treated another way under the agency’s process.

Consider people who saw the earlier version. A new post may be needed to reach them, but it should point to the corrected authoritative destination and make the important change understandable. Do not assume every platform supports the same editing or notification behavior.

Keep corrected image text, captions and accessible alternatives consistent. The federal accessible-publication guidance (opens in a new tab) is useful reference context when planning alternatives and checking published content.

Inspect the actual destinations and the remaining queue.

Open the public version and check the critical facts, links, attachment labels and any visible correction notice. Verify the exact account or destination. Then check the scheduled queue and reusable drafts so the obsolete version is not published again.

If another organization controls a copy, record who was asked to correct it and whether the correction was verified. Keep unresolved external copies visible as exceptions. Do not report the whole correction complete merely because your own page is updated.

Fix the process that let the old version survive.

Look for a missing owner, unclear source, unlinked channel revision, expired draft or absent queue check. Update the working process and assign the next review. Keep the correction history in the approved record rather than overwriting evidence your agency needs.

The governance guide assigns responsibility, while the social strategy guide connects channels to public tasks. For help preparing and maintaining the workflow, explore government content support.

Correct cancellations and recurring events at the authoritative destination.

For a recurring community activity, maintain one authoritative series resource when the reader’s task and content remain the same. Identify affected occurrences explicitly. Do not create a competing page solely because a reminder is published this week. Distinct meetings or events can require their own occurrence records when their participation details and records form separate tasks.

Fictional example. Cedar Bay’s weekly workshop cancels one session. The existing series page marks that specific full date canceled and keeps later confirmed sessions distinguishable. The cancellation source and check time are recorded. If no replacement is confirmed, the text does not invent one.

Pause scheduled versions carrying the canceled date, revise and reapprove affected reminders, and check the live calendar and source page. Use clear cancellation wording rather than silently deleting the event and leaving old posts apparently valid. Keep records according to the agency’s approved procedure.

For a reschedule, connect the old occurrence to the confirmed replacement and state what changed. The calendar revision record tracks each affected channel, and the meeting-record guide explains why a statutory meeting occurrence may need a separate record.

A community-center staff member updates an event notice at an information counter while a colleague checks the correct event date in a booking folder.
Correcting one occurrence in an event series.