Correcting GxP Records
Every GxP record will eventually need a correction, and how you make it is itself a controlled activity. A defensible correction preserves the original entry, shows the new value, and explains why the change was made, by whom, and when. An indefensible correction — an obliteration, an over-write, an untraceable electronic edit — destroys the record’s value as evidence and reads to an inspector as concealment, whatever the intent. Correction convention is where GDocP and data integrity meet at their most concrete.
What an explainer is not
A topic explainer is SPEQ’s synthesis of what a practice involves, cited to the standards that govern it. It does not reproduce their text, and it does not determine which of them apply to your product or process.
[ POSITION IN THE FRAMEWORK ]
7 DIMENSIONS · 25 LINKSCorrecting a GxP record is a controlled act across the documentation, CSV, and GMP disciplines: a single-line strike-through or audit-trailed edit preserves the original — obliteration or an untraceable edit reads as concealment.
06 · QUALITY MATURITY — CORRECTING GXP RECORDS, REACTIVE TO ADAPTIVE
Corrections obscure the original — fluid, over-writing, no reason; electronic values are edited in place, sometimes with the audit trail off.
The strike-through rule is trained, but reasons-for-change are routinely omitted and privileged 'super-user' edits bypass the audit trail.
Paper corrections preserve the original with reason, initials, and date; electronic edits are audit-trailed with a reason for GMP-critical data.
Correction patterns are reviewed — direction, clustering near deadlines, repeat fields — and material changes escalate into investigation.
Honest correction is easy and routine, correction analytics feed DI governance, and impact triage reliably separates a slip from an investigation.
SPEQ’s shared five-stage progression, labelled synthesis — not the FDA QMM rating scale. Where does your organization sit? Score your quality system →
07 · REGULATORY & EVIDENCE
GOVERNING STANDARDS · 4
Derived from the 4 standards SPEQ maps to this subject, across 4 regulatory bodies: FDA, EMA, MHRA, PIC/S.
RECORDS & OBJECTIVE EVIDENCE
- Paper corrections with single line, corrected value, reason, initials, and date
- Audit trails retaining previous value, new value, user, timestamp, and reason
- Reason-for-change enforced for GMP-critical electronic data
- Investigations linked to corrections that affect a result or decision
- Periodic review of correction patterns within data-integrity governance
COMMON INSPECTION FINDINGS
- Correction fluid, over-writing, or obliteration of the original entry
- Reason-for-change routinely omitted on material corrections
- Values edited in place with the audit trail absent or disabled
- Privileged or back-end 'super-user' edits bypassing the audit trail
- OOS or released-record changes made without an investigation
The paper correction rule
The canonical convention for a paper correction is a single line through the original entry so it remains legible, the corrected value written alongside, and the change initialled and dated by the person making it, with a reason where the reason is not self-evident. The original must never be obscured — no correction fluid, no over-writing, no scribbling out. The point is that a later reader can see both what was first recorded and what it was changed to, and reconstruct why.
The reason for change is the part most often omitted and the part inspectors most want. "Transcription error," "wrong units," "misread instrument" — a short, honest reason turns a bare correction into a documented one. Where a correction is substantial or affects a result, GDocP expects it to be traceable to a supporting record (a deviation, an investigation, a recalculation) rather than left to a one-word margin note.
Corrections in electronic systems
In compliant electronic systems, records are not edited in place and over-written; changes are captured by the audit trail, which retains the previous value, the new value, the user, the timestamp, and — where the system is well-configured — the reason-for-change expectation for GMP-critical data. The original value is never lost; it is superseded and preserved. This is precisely the electronic analogue of the single-line strike-through.
Two anti-patterns recur. The first is systems that permit a value to be changed with no audit trail or with the audit trail switched off — which converts an ordinary edit into an undetectable one. The second is bulk or administrative edits made outside the normal user path (direct database changes, privileged "super-user" corrections) that bypass the audit trail entirely. Both are serious findings because they defeat the mechanism that makes electronic corrections trustworthy.
When a correction becomes an investigation
Not every change is a simple slip of the pen. Correcting an out-of-specification result, changing a reported value after review, or altering a released batch record crosses from correction into change control and investigation territory. The test is impact: if the change could affect a quality decision or a reported result, it needs the rigour of a deviation or an OOS investigation, not just a strike-through.
SPEQ synthesis: a useful triage question is "who relied on the original value, and what did they decide with it?" If nobody had acted on it yet, a documented correction is proportionate. If a batch was released, a certificate issued, or a submission made on the strength of the original, the correction is the visible tip of an investigation that must establish scope, impact, and whether other records are affected.
Corrections as an integrity signal
Patterns of correction are read diagnostically. A record littered with corrections may point to a form that does not match the work, an unclear procedure, or inadequate training. Corrections that always move a result in the same direction, cluster around release deadlines, or repeatedly touch the same critical field can indicate pressure or manipulation, and inspectors mine audit trails for exactly these signatures.
The mature response is not to suppress corrections — a record with zero corrections across thousands of entries is itself suspicious — but to make honest correction easy and routine, and to review correction patterns as part of periodic data-integrity governance. A culture where people feel able to correct openly is more trustworthy than one where the record is suspiciously pristine.
FREQUENTLY ASKED
What is the correct way to correct a paper GxP record?
Draw a single line through the original entry so it stays legible, write the corrected value alongside, and initial and date the change with a reason where the reason is not obvious. Never use correction fluid, over-write, or obscure the original — a later reader must be able to see both the original and the corrected value.
How are corrections handled in electronic systems?
Compliant electronic systems do not over-write data in place; the audit trail retains the previous value, the new value, the user, the timestamp, and ideally a reason for change. This is the electronic equivalent of the single-line strike-through — the original is superseded but never destroyed.
When does correcting a record require an investigation?
When the change could affect a quality decision or a reported result — for example altering an out-of-specification result, a value used for batch release, or a released record. That crosses from routine correction into change control and investigation, requiring scope and impact assessment, not just a strike-through.