Regulations and compliance · Practical guide

Correcting GMP documentation: original entry, reason and impact

Replacing an incorrectly transcribed value takes seconds. Determining which calculations, reports or decisions already relied on it can take longer. Link the original entry to the correct information and assess its consequences. Distinguish a clerical correction, a later addition and a substantive error on paper and in electronic records.

Table of contents

At a glance

How do you correct a GMP entry?

A correction must keep the original entry legible or traceable and identify the person who changed it and the actual time of change. EU GMP Chapter 4 calls for a signature and date and, where appropriate, a reason. Electronic records also need suitable system controls. Assess any downstream results or decisions the original error may have affected.

  • The correct value requires reliable evidence, not merely plausibility.
  • The correction date and original event timestamp must not be confused.
  • The closure includes also the traceable evaluation of affected follow-up data.

1. The correction must not rewrite the story

For human medicines GMP, Chapter 4 section 4.9 requires amendments to entries to be signed and dated, with the original entry remaining readable and the reason recorded where appropriate. A reviewer needs to see the correction itself as part of the record.

For electronic systems, relevant changes must be managed with appropriate controls. Annex 11 addresses, among other things, audit trails and the assignment of data actions. An electronic user identifier and a paper-based correction note are technically distinct but must reflect the required change context.

Sources: [1] [2]

2. Identify three distinct scenarios

Not every change originates from the same root cause. A typing error in an existing, correct original source is to be handled differently from a missed entry without immediate supporting documentation. A new clinical finding is not automatically the correction of a previous spelling error.

The example decision matrix helps identify the nature of the event. It does not replace impact assessment or any required deviation procedure. In particular, a later addition must remain distinguishable from a contemporaneous original entry.

Own decision support tool for record changes
SituationRequired basisAppropriate representation
Transmission error Reliable original test or work record Incorrect entry and documented correction to be linked
Illegible entry Other reliable source, if available Do not invent a value from memory
Forgotten entry Actual available time-stamped evidence Add current date notation for subsequent amendments
New professional assessment New information and original decision Change in assessment rather than faking typos
False value already reused Affected calculations and decisions Correction plus assessment of downstream effects

Sources: [1] [3] [4]

3. Legible on paper and clearly amended

An appropriate paper correction should enable the original entry to be clearly visible and should clearly attribute the change to the responsible person and the date. The specific entry must be unambiguous: which number was amended and which information is now valid? For changes requiring justification, the reason should be clearly derived from the record or a clearly referenced supporting document.

Overwriting, illegible overwriting, or inadvertent replacement of entire sections may compromise this relationship. If a replacement sheet is required, the original record and the transfer must be clearly traceable. Proper documentation is more important than an aesthetically flawless sheet.

Sources: [1] [3]

4. Consider the electronic value not only the visible value

In an application, a corrected number can be displayed correctly while the history is missing or a report continues to use the old value. Therefore, check both the change itself and its further processing. An audit trail entry only helps if it can be assigned to the correct record and the relevant decision.

The required technical solution depends on the intended use. A commentable table field is not automatically an appropriate audit trail. Conversely, electronic form functionality does not imply that every text modification requires the same level of technical review. Relevant data and risks are decisive.

Sources: [2] [3] [5]

5. Calculation example: A decimal error persists

An original invoice shows 12.50 mg. Accidentally, 125.0 mg is transferred during calculation. The prescribed volume is 0.100 L. Using the incorrect value, the concentration is calculated as 125.0 ÷ 0.100 = 1,250 mg/L; the correct value is 12.50 ÷ 0.100 = 125 mg/L.

The incorrect concentration is therefore ten times higher than the correct one. The error is resolved based on the original documentation, not by assuming that the smaller value appears more plausible. The correction must also take into account the already prepared report and any decision potentially based on it.

Expected outcomes for a correction with downstream effects
EvidenceOriginal versionCorrected or reviewed versionRequired Connection
Original record 12.50 mg Unchanged 12.50 mg Reliable source of the original information
Transfer 125.0 mg 12.50 mg Person, Date, and Transfer Error
Calculation for 0.100 L 1,250 mg/L 125 mg/L Identify both versions of the calculation
Report Contains 1,250 mg/L Corrected status or appropriate amendment Do not completely eliminate the previous report.
Usage determination Possible incorrect basis Impact assessed and decided Not solely concluded with cell correction

Sources: [6] [1]

6. Define the scope prior to closing the case

Investigate where the erroneous value was used: in subsequent calculations, transferred datasets, reports, or quality-related decisions. A corrected source record does not necessarily update downstream systems. Even an automated update must preserve the appropriate technical and scientific context.

Investigations and corrective actions should be proportionate to the significance. A minor, clearly defined typing error does not necessarily require a standalone CAPA project. However, recurring patterns or unclear implications may indicate the need to investigate underlying root causes. Immediate containment is possible prior to completion of the full root cause analysis.

Sources: [7] [6] [2]

7. Treat Late Entries Honestly as Such

If an activity has not been documented in a timely manner, this gap cannot be closed by a back-dated form. Note when the entry actually arises and on which documents the description is based. Event date and documentation date can then be different and should not be confused.

A reminder may support an investigation, but it is not considered an authentic original record. If the execution or a value remains unverified, this uncertainty must be addressed in the evaluation. A subsequent complete table does not prove that the original activity was performed as planned.

Sources: [1] [3] [4]

8. Checklist prior to closing a correction

A appropriate correction should make both the correct information and the path to it understandable. It should be reconstructible by a qualified person without reliance on mere verbal explanation.

Use the following custom list according to the purpose of the record. The required review and approval roles arise from your quality system; not every change requires the same universal signature template.

  • Nature of the action indicated: Correction, addition, or new assessment.
  • Original entry and reliable correct source obtained.
  • The record identifies who made the change and when it actually occurred.
  • Document the basis where required or where understanding is necessary.
  • Affected calculations, exports, and decisions reviewed.
  • Remaining uncertainty disclosed.
  • Planned inspection and further use completed.

Sources: [1] [2] [7]

Project experience and collaboration

Correct an error while preserving the original entry

Your team selects a typical correction from actual work. A later reviewer must be able to identify the original entry, the reliable basis for the change and the person who made it. Paper records need different controls from electronic records with roles and history. We check how the procedure handles these differences and uncertainty discovered later. An illegible or unsupported source value must not be hidden behind a replacement that appears certain.

Frequently asked questions about Correcting GMP documentation

Must a detailed justification be provided for every paper correction?

Chapter 4.9 requires the rationale to be provided, if applicable. A trivial, clearly understandable spelling correction and a professionally significant result change do not necessitate the same level of explanatory detail. The factual situation must be understandable; a concise reference to an appropriate investigation may be more efficient than extensive text.

Sources: [1]

May the original entry be made illegible?

No. The change should leave the original entry legible. For electronic data, the relevant original information must remain appropriately traceable. A tidy final version with no visible history cannot achieve that purpose.

Sources: [1] [2]

Is a wrongly transferred value automatically out of specification?

Not automatically. Initially, a documentation or transfer finding is present. Whether an OOS result or another deviation additionally exists depends on evaluation and acceptance criteria. Assess the situation and its implications, rather than categorizing every correction uniformly.

Sources: [6] [7]

Can we add a missing signature later?

A subsequent addition must not create the impression of an original contemporaneous validation. Assess whether the individual can actually verify today based on the applicable basis. The date and significance of the addition must be clearly and honestly identifiable; the absence of original evidence is not automatically substituted.

Sources: [1] [3]

Must the correction be performed by the same person who entered the original entry?

Not mandatory. Chapter 4, Section 4.9 requires that amendments be signed and dated, the original entry remain legible, and, if applicable, the reason for the amendment be documented. The personnel authorized to make corrections shall be defined by your procedure based on responsibility and authority. The person making the correction must have a reliable basis; their assignment must be clearly identifiable.

Sources: [1] [2]

Does a reason for change suffice in the comment field of a table?

This depends on the other controls in place. A freely editable comment alone does not ensure the integrity of the original value, timestamp, or identity. Review the entire change trail, including storage, authorizations, and review processes. The field name "Reason" does not constitute functional evidence.

Sources: [2] [3]

Can we simply re-export a wrong report?

A new export may be required. However, the connection to the incorrect prior version and the necessary evaluation must be preserved. Clarify who received or used the previous report and how the current valid version can be identified. Simply changing the file name does not resolve these issues entirely.

Sources: [1] [3]

Does every keystroke error require a CAPA?

No. The appropriate action depends on significance, root cause, and pattern. For recurring or systemic errors, a more in-depth root cause analysis and corrective and preventive actions (CAPA) may be required. A single, clearly isolated typing error does not automatically necessitate the same corrective procedure as a significant integrity finding.

Sources: [7]

How should we handle a value that cannot be reconstructed?

Do not invent a plausible substitute. Document the available evidence and the remaining gap. Subsequently, determine the impact on results and usage, and assess whether additional appropriate tests are possible or required.

Sources: [3] [6]

When is the correction considered professionally completed?

When the correct version is verifiable, changes are traceable, and the impact on subsequent data or decisions has been assessed. A newly stored digital value represents only part of the picture. Any open, relevant uncertainties must be considered in the decision.

Sources: [7] [1] [2]

Sources and review date

Source date: 7 October 2026. The technical examples relate to human medicinal product GMP. FDA and MHRA statements are incorporated within their respective areas of applicability. Tables and numerical examples are intended as internal reference tools.

  1. European Commission: EU GMP Chapter 4, DocumentationJanuary 2011; in effect since 30.06.2011; Principle; §§4.1–4.9, in particular timely recording 4.8 and visible correction 4.9; §§4.10–4.12 Storage
  2. European Commission: EU GMP Annex 11, Computerised SystemsRevision January 2011; from 30.06.2011; Principle; §§1,4,5,7,9–13,17; §12.4 Identity, Date and Time; §10 controlled changes
  3. PIC/S: PI 041-1, Data Management and IntegrityPIC/S PI 041-1, 1 July 2021. See section 3.7 for status, sections 7.5–7.8 and 8.1–8.8, sections 9.1.5 and 9.3 and 9.5–9.10, section 12.1 and the glossary.
  4. MHRA: GxP Data Integrity Guidance and DefinitionsRevision 1, March 2018; Sections 6.1–6.11 Data/Metadata/Processing; Sections 6.12–6.17 Transactions, Audit Trail, Review, Access, and Retention
  5. FDA: Data Integrity and Compliance With Drug CGMP, Questions and AnswersFinal Guidance, December 2018; Section III Q1(b)–(d), Q2, Q4–6, Q7–10, Q12–13, and Q18
  6. European Commission: EU GMP Chapter 6, Quality ControlRevision 2014; effective from 01.10.2014; §6.7 Documentation; §6.9 Out-of-Specification/Out-of-Trend; §§6.15–6.17 Test methods, calculations, and laboratory records
  7. European Commission: EU GMP Chapter 1, Pharmaceutical Quality SystemRevision 2013; effective from 31.01.2013; §1.4(xii)–(xiv): proactive change evaluation, post-evaluation, and root cause analysis/CAPA; §1.5 Management

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Implement corrections without introducing new gaps in validation evidence.

We support you with clear correction pathways, appropriate electronic controls, and targeted evaluation of affected follow-up data.

  • Computer system validation →

    Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

Send a project enquiry Customer testimonials →