corrigendum

A corrigendum is an officially published correction to an existing document, such as an international standard, regulation, technical report, or specification. In industrial and regulated environments, it commonly refers to a correction issued by a standards body or publisher to fix identified errors without republishing the entire document as a new edition.

What a corrigendum includes

A corrigendum typically addresses issues such as:

  • Typographical or formatting errors that may affect interpretation
  • Incorrect references, figures, tables, or cross-references
  • Minor technical errors, such as mis-stated parameter values, variable names, or units
  • Clarifications where the original wording is misleading or internally inconsistent

The corrigendum is normally published as a short stand-alone document that specifies exactly what text, figure, or reference is replaced, deleted, or inserted in the original document.

What a corrigendum does not usually cover

A corrigendum generally does not introduce major new requirements, restructure the document, or change the overall scope or concept of the standard or procedure. Substantive changes of that kind are more often handled in separate amendments or full revisions.

Operational meaning in industrial and regulated environments

In manufacturing, OT/IT, and quality-managed environments, corrigenda are part of document control and standards management. Typical impacts include:

  • Tracking which standards and technical documents are in use, including their edition and any corrigenda applied
  • Updating internal procedures, specifications, or system configurations when a corrigendum corrects a value or requirement that affects operations
  • Adjusting validation, verification, or test documentation if a corrected requirement changes acceptance criteria or calculations
  • Maintaining evidence that the organization is aware of and has evaluated relevant corrigenda as part of change control

For example, if a cybersecurity standard used for OT system design issues a corrigendum that corrects a misprinted network security parameter, engineering and compliance teams may need to review configurations, risk assessments, and related work instructions.

Relationship to amendments and revisions

Standards and formal documents may evolve through several mechanisms:

  • Corrigendum: Corrects identified errors or inconsistencies, usually without changing the overall technical intent.
  • Amendment: Adds, removes, or modifies specific requirements or sections, often to address new technology, practices, or interpretations.
  • Revision (new edition): Replaces the previous edition and may significantly restructure or expand the content.

Organizations that rely on external standards for MES/ERP integration, automation, safety, or quality should track all three types of changes as part of formal document control.

Common confusion

  • Corrigendum vs. errata: In some publishing contexts, errata are informal or publisher-level error lists, while a corrigendum is an official, controlled correction issued under the same governance as the original document. Usage can vary by organization.
  • Corrigendum vs. amendment: A corrigendum focuses on corrections to what should have been in the original document. An amendment intentionally changes or adds content after publication.

Link to standards such as IEC 62443

For standards like IEC 62443, individual parts may remain in force for many years while receiving targeted corrigenda and amendments. Plants and system integrators that reference specific parts of such standards in their OT cybersecurity, validation, or quality systems often need to:

  • Record the exact part, edition, and any associated corrigenda or amendments
  • Assess whether corrections affect existing designs, risk assessments, or controls
  • Apply change control and revalidation processes when necessary

In this context, a corrigendum is treated as an official change record that must be evaluated and, when relevant, incorporated into controlled documentation and systems.

Content classification

Visible verification fields for authorship, dates, taxonomy, and ST assignments.

Published:

Updated:

Tags:

FAQ category:

FAQ tag:

Glossary category:

Colour:

Content type:

Location:

Audience:

Intent:

Dev-only relationship debug

Content relationships

Rendered from saved content and bridge metadata. Nothing in this panel writes back to WordPress.

Inline glossary links

No inline glossary links found in saved content.

Attached glossary terms

No glossary bridge terms attached.

Attached FAQs

No FAQ bridge items attached.

Diagnostics

Inline glossary links
0
Attached glossary terms
0
Attached FAQs
0
  • No glossary or FAQ relationships found for this item.