How to maintain a corrections log

What belongs in the log

Log a change when a factual statement, number, quotation, identity, attribution, legal status or material date was wrong or became inaccurate. Also log a source revision that changes the conclusion. Routine spelling, punctuation and layout repairs do not normally need individual entries unless they alter meaning.

Correction entry fields

• Timestamp: date and time the public correction was made.
• Page: stable page title and URL.
• Previous statement: enough text to identify the error without repeating harmful material unnecessarily.
• Corrected statement: the replacement wording now shown.
• Reason: factual error, source revision, new primary record, misattribution or clarification.
• Evidence: primary source URL, document identifier, publication date and access date.
• Scope: every table, chart, summary or linked page that also required repair.

Correction, update or clarification?

Use correction when the earlier publication was wrong. Use update when an accurate time-bound statement is supplemented by later events or data. Use clarification when the facts remain correct but wording could reasonably mislead. Do not relabel an error as an update to avoid acknowledging it.

Source revisions need their own trail

Official datasets can be revised. The CSO’s General Revisions Policy requires revised results to be identified and substantial revisions explained. When a cited table changes, record the prior value, new value, table code, revision label and the effect on the article’s conclusion. If the conclusion does not change, say so.

Legislation and parliamentary records can also be amended, commenced or corrected. Re-run the relevant legislation check or debate check and attach the new official record.

Publication workflow

1. Freeze a copy or hash of the pre-correction page for the internal audit trail.
2. Verify the replacement against the primary source.
3. Correct every affected representation, including metadata and structured data.
4. Add a dated note on the article when the change is material.
5. Add the central log entry and link it back to the article.
6. Recheck internal summaries, charts and downstream pages.

Safety and privacy boundary

A corrections log is not a place to republish unnecessary personal data, an unsupported allegation or the full text of harmful material. Identify the repaired claim narrowly. For a sensitive person or case assertion, retain the evidence privately where appropriate, publish only what is necessary, and seek legal review when the risk cannot be resolved by primary records.