In-depth practical guides

Keep an editorial correction log

Explain what changed, why, with which evidence and in which language versions.

Updated :

Proof sheets, dividers and editing notebook. Illustrative scene.

AI-generated illustration · Proof sheets, dividers and editing notebook. Illustrative scene.

Can a reader understand the correction without reconstructing the whole history?

A useful correction links an old claim, new evidence and revised content. The log preserves traceability without copying sensitive details or treating every punctuation change as a major event. Decision-relevant changes remain identifiable.

  1. Classify change

    Distinguish wording, clarification, factual correction, scope change and withdrawal. Record affected claims and pages. Style updates are not new factual checks.

  2. Keep evidence

    Record source passage, date, version and reason. Retain a proportionate internal trace of old wording. Uncertain evidence calls for a qualification, not replacement with another unsupported certainty.

  3. Correct dependencies

    Check summaries, tables, FAQs, structured data, downloads and pages reusing the claim. Apply corrections across languages and list variants actually reviewed.

  4. Explain the decision

    For substantive change publish a short dated note on nature and scope. Assign follow-up responsibility. Do not reset publication dates to simulate new articles.

Situations and decisions

Typical situations for preparing a check. They do not describe completed assignments or actual observations.

An incorrect unit

Fictional case: a table says euros instead of thousands of euros. Correct unit, values, summary and calculation example; editing the label alone leaves derived conclusions inconsistent.

One language remains outdated

Illustrative case: French is corrected but a translation retains an old qualification. Mark it pending instead of claiming every language was reviewed.

Record to retain

  • Old and new claim
  • Reason and source passage
  • Affected pages, formats and languages
  • Date, validation and follow-up

Official references

Related source profiles

Related protocols

Checks before reaching a conclusion

  • Is the reason precise?
  • Are derived materials corrected?
  • Are reviewed languages listed?
  • Does the public note reflect actual scope?

A log linking reason, evidence, correction and derived-content status.

Frequently asked questions

Does every edit need a public note?

No. Set impact-based editorial rules. A meaning-neutral typo differs from corrected numbers, attribution or conclusions.

Can a correction be labelled verified?

Only for the actual checked scope. Give evidence, dates and limits. One corrected item does not validate the whole document.

TOOLS / REGISTERS

Write a record

A log does not certify an entire page. Corrections must not expose confidential information. Public history can be summarised while an appropriate internal trace is retained.

  • Access date and time zone
  • Exact URL
  • Claim to verify
  • Previous wording / value
  • Corrected wording / value
  • Reason and supporting document
  • Version / revision
  • Language / region
  • Review owner
  • Next review
  • Decision / next action