Assess the significance

Identify the incorrect statement, where it appeared and what a reader could reasonably have understood from it. Distinguish a typographical fix from a correction affecting project status, availability or a numerical claim. Record the accurate replacement and the evidence supporting it. Avoid quietly changing important information without considering active conversations connected to the earlier version.

Update the full chain

Correct the maintained page and affected downloadable files. Add a concise correction note where appropriate and contact relevant recipients when the change matters to an ongoing review. Keep a record of the previous version and the reason for the correction. The purpose is not to dramatise a routine edit; it is to keep the information environment trustworthy and prevent different audiences from continuing with incompatible versions of the same claim.

Put the guide to work

Keep a short internal correction log identifying the cause of the error. If the problem came from an outdated source or an unclear approval step, repair that process too. Otherwise the team may correct the visible page while leaving the same issue ready to recur.

Imagine this

Hypothetical example

A project page mistakenly describes a planned facility as operating. The correction changes the status, adds the current milestone and informs the sales team handling active enquiries. Prospects receive the same accurate explanation rather than different answers depending on which file they saw.

Make it practical.

Use this checklist as you read. Checks are not stored.

Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.